h1902 Utilizing SNMP Cap Emc Disk Lib WP LDV

EMC® Disk Library for
mainframe
DLm8000
Version 3.4
User Guide
P/N 300-013-636
REV 01
Copyright © 2012 EMC Corporation. All rights reserved.
Published November, 2012
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 DLm8000 User Guide

CONTENTS
Preface
Chapter 1 Overview of EMC Disk Library for Mainframe DLm8000

Introduction to Disk Library for mainframe ..................................... 18
DLm8000 architecture ................................................................... 19
VTEC ........................................................................................ 19
Backend storage...................................................................... 25
Mainframe channel interfaces.................................................. 26
DLm8000 devices and capacity ..................................................... 30
................................................................................................ 31
Tape emulation........................................................................ 32
Virtual tape drive states ........................................................... 33
Data formats............................................................................ 33
Support for physical tape drives .................................................... 34
High availability features of DLm8000 ........................................... 35
VTEC ........................................................................................ 35
VG8 ......................................................................................... 35
Features and benefits .................................................................... 38
Chapter 2 DLm Operations

Management access to DLm .......................................................... 42
Gather connection data ........................................................... 42
Access the DLm Console .......................................................... 43
Set date and time .................................................................... 45
User administration ................................................................. 47
Network and DR configuration restrictions ............................... 51
Access a VTE.................................................................................. 52
VT console ............................................................................... 53
VTE reboot ............................................................................... 55
Power up DLm ............................................................................... 55
VMAX....................................................................................... 56
VNX VG8 server power-up ........................................................ 56
ACP power-up .......................................................................... 58
VTE power-up........................................................................... 60
Power down DLm ........................................................................... 63
VTE power down ...................................................................... 64
EMC Disk Library for mainframe DLm8000 User Guide 3

Contents
Halt the VNX VG8 server........................................................... 66

Verify Control Station powerdown ............................................ 67
Power down VMAX ................................................................... 68
Power down the ACP ................................................................ 68
Start and stop tape devices ........................................................... 69
Support access to DLm .................................................................. 70
ESRS........................................................................................ 70
Modem support ....................................................................... 71
Chapter 3 DLm Administration

Tape libraries................................................................................. 74
Backward compatibility ........................................................... 76
Initialize scratch volumes ........................................................ 76
Configure virtual devices................................................................ 78
Planning considerations .......................................................... 78
DLm configuration files ............................................................ 79
Configure global parameters.................................................... 79
Add devices............................................................................. 82
Scratch synonyms.................................................................... 88
Save configuration................................................................... 91
Delete a device range .............................................................. 91
Manage configuration files ............................................................ 92
Activate or install a configuration............................................. 92
Create a new configuration ...................................................... 93
Copy a configuration................................................................ 93
Modify or delete a configuration .............................................. 93
Tape Erase..................................................................................... 94
Space erase policy................................................................... 94
Time-to-Live erase policy ......................................................... 95
Both ........................................................................................ 95
Manage VTE and ACP logs.............................................................. 96
VTE logs................................................................................... 96
Support data ........................................................................... 97
Back-end tape support .................................................................. 99
Direct Tape .............................................................................. 99
Export to and import from tapes............................................. 102
DLm diagnostic reporting............................................................. 103
VTEC ...................................................................................... 103
ConnectEMC .......................................................................... 106
AWSPRINT library utility ............................................................... 106
DLm8000 site configuration considerations ................................. 106

Contents
Chapter 4 SRDF Replication

SRDF Replication Overview .......................................................... 110
SRDF Synchronous (SRDF/S) .................................................. 110
Prerequisites for SRDF replication .......................................... 111
SRDF connections and configuration............................................ 111
SRDF replication capabilities ................................................. 111
SRDF/S active-passive configuration for VNX ......................... 112
Configuration files on source and target systems ................... 113
Disaster recovery capabilities ...................................................... 113
SRDF benefits .............................................................................. 114
Chapter 5 Mainframe Tasks

Configure devices ........................................................................ 116
Real 3480, 3490, or 3590............................................................ 116
Manual tape library ..................................................................... 117
MTL considerations for VTE drive selection................................... 119
MTL-related IBM maintenance...................................................... 121
EMC Unit Information Module ...................................................... 121
Missing Interrupt Handler ............................................................ 122
Dynamic device reconfiguration considerations ........................... 123
DFSMShsm considerations .......................................................... 123
Specify tape compaction ............................................................. 123
Locate and upload the DLm utilities and JCL for z/OS ................... 124
Downloading and using the DLm utilities and JCL for z/OS ..... 124
GENSTATS utility .................................................................... 126
DLm scratch utility program ................................................... 127
DLMCMD utility program ........................................................ 135
DLMVER utility program ......................................................... 137
Initial program load from a DLm virtual tape ................................ 139
Create a stand-alone IPL tape on DLm .................................... 139
IPL from the stand-alone IPL tape........................................... 140
IPL considerations for DLm .................................................... 140
Chapter 6 z/OS Console Support

z/OS Console operation............................................................... 142
DLMHOST .................................................................................... 142
Installing DLMHOST ............................................................... 142
Running DLMHOST................................................................. 143
DLMHOST configuration file ................................................... 144
Using z/OS Console support ........................................................ 145
DLMHOST commands ............................................................ 146

Contents
WTOR command examples..................................................... 148
Appendix A Virtual Tape Operator Command Reference

Virtual Tape Operator command reference ................................... 150
Syntax ................................................................................... 150
CLOSE VSTATS PATH .............................................................. 150
EXPORT.................................................................................. 150
FIND....................................................................................... 152
HELP ...................................................................................... 152
IMPORT.................................................................................. 153
INITIALIZE .............................................................................. 153
LOAD ..................................................................................... 155
QUERY ................................................................................... 156
QUIESCE ................................................................................ 163
READY.................................................................................... 164
REWIND ................................................................................. 164
SAVE TRACE ........................................................................... 165
SET ........................................................................................ 165
SHOW.................................................................................... 169
SNMP .................................................................................... 170
STARTVT ................................................................................ 170
STOPVT.................................................................................. 170
UNLOAD................................................................................. 171
UNQUIESCE ........................................................................... 171
UNREADY ............................................................................... 172
Appendix B AWSTAPE Information

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

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

DLm statistics files ...................................................................... 182
Extraction utility .......................................................................... 182
Hourly statistics..................................................................... 183

Contents
Volume statistics ................................................................... 184

Mount statistics..................................................................... 185
Unmount statistics ................................................................ 185
Example 1.............................................................................. 186
Example 2.............................................................................. 186
Example 3.............................................................................. 188
Example 4.............................................................................. 188
Appendix E System Messages

Message format........................................................................... 192
DLm system messages................................................................. 193
Call home messages.................................................................... 363
EMCvts messages ........................................................................ 364
z/OS system messages................................................................ 366
DLMCMD messages ............................................................... 366
DLMHOST messages .............................................................. 367
DLMLIB message ................................................................... 371
DLMSCR messages ................................................................ 371
DLMVER messages ................................................................ 375
Healthcheck messages ................................................................ 376
VTEC errors that generate ConnectEMC events ............................. 380
Index

Contents

FIGURES
Title Page
1 Front view of the VTE...................................................................................... 20

2 Rear view of a VTE.......................................................................................... 22
3 Front view of the ACP ..................................................................................... 23
4 Rear view of the ACP ...................................................................................... 23
5 24-port AT-9924TL switch .............................................................................. 24
6 Brocade VDX 6720 switch.............................................................................. 25
7 DLm8000 Single site block diagram............................................................... 31
8 DLm8000 Two site block diagram .................................................................. 32
9 VTE to storage controllers — Network topology............................................... 37
10 DLm Console login page ................................................................................ 44
11 DLm8000 Console ......................................................................................... 45
12 DLm date and time......................................................................................... 46
13 User ID creation ............................................................................................. 48
14 LDAP user authentication............................................................................... 50
15 Disabling DR configuration ............................................................................ 52
16 VT console ..................................................................................................... 53
17 VG8 power up example .................................................................................. 57
18 ACP indicators and controls ........................................................................... 58
19 Rear view of the ACP ...................................................................................... 59
20 VTE indicators and controls............................................................................ 61
21 VT console with VT application....................................................................... 70
22 EMC Secure Remote Support.......................................................................... 71
23 Global options ............................................................................................... 80
24 Control units.................................................................................................. 83
25 Add devices section....................................................................................... 84
26 Scratch Synonyms ......................................................................................... 89
27 Save configuration......................................................................................... 91
28 System status................................................................................................ 97
29 Gathering ACP and VTE support data.............................................................. 98
30 SNMP configuration ..................................................................................... 104
31 Alert messages ............................................................................................ 105
32 DLm8000 two-site configuration .................................................................. 107
33 SRDF Synchronous (SRDF/S) ........................................................................ 110
34 SRDF/S active/passive configuration ........................................................... 112
35 AWSTAPE single disk file.............................................................................. 174

Figures

TABLES
Title Page
1 ACP rear panel connectors ............................................................................. 24

2 FICON adapter LED indicators ........................................................................ 27
3 DLm Capacities ............................................................................................. 30
4 DLm system access details ............................................................................ 42
5 ACP rear panel connectors ............................................................................. 59
6 Example of LIBRARY-ID and LIBPORT-ID ........................................................ 118
7 Parameters in DLMSCR ................................................................................ 128
8 DLMSCR report output messages ................................................................. 130
9 Error code from DLMCMD ............................................................................. 136
10 Load display data ........................................................................................ 178
11 Format Control Byte ..................................................................................... 178

Tableses

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 IBM
and IBM-compatible mainframes using disk storage systems in place of physical
tapes. This guide provides information about the features, performance, and
capacities of DLm 3.4 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.
Related documentation
The following EMC publications provide additional information:
◆ EMC Disk Library for mainframe Physical Planning Guide
◆ EMC Disk Library for mainframe DLm8000 Version 3.4 Release Notes

Preface
◆ EMC Disk Library for mainframe Command Processors User Guide

◆ 40U-C Cabinet Unpacking and Setup Guide
The EMC documents specified here and additional Celerra information are available in
the EMC Online Support website.
Conventions used in this document

EMC uses the following conventions for special notices:

DANGER indicates a hazardous situation which, if not avoided, will result in death or
serious injury.

WARNING indicates a hazardous situation which, if not avoided, could result in death
or serious injury.

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

Preface
| 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
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

CHAPTER 1
Overview of EMC Disk Library for Mainframe
DLm8000
This chapter provides an overview of EMC Disk Library for mainframe DLm8000.
Topics include:
◆ Introduction to Disk Library for mainframe........................................................ 18
◆ DLm8000 architecture...................................................................................... 19
◆ Tape emulation ................................................................................................ 32
◆ Support for physical tape drives ....................................................................... 34
◆ High availability features of DLm8000 .............................................................. 35
◆ Features and benefits....................................................................................... 38
Overview of EMC Disk Library for Mainframe DLm8000 17

Overview of EMC Disk Library for Mainframe DLm8000
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 replication between two DLm
systems in the same or 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.
In summary, 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).

DLm8000 architecture
The major components of a DLm8000 system are the virtual tape emulation controller
(VTEC) and the backend storage system that comprises of one VG8 gateway and a
VMAX.
Note: Total supported capacity and number of cabinets depend on the drive capacity.
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:
◆ Two to eight Virtual tape engine (VTE)
◆ Two Access control points (ACPs)
◆ Two 1 Gb Ethernet switches for management network
◆ Two 10 Gb Ethernet switches for data transfer
VTE
Each DLm configuration can have 2—8 VTEs. The mainframe virtual tape emulation
software, Virtuent, executes on the VTEs. Each VTE is connected to the mainframe
through two FICON channels and emulates up to 256 tape drives. VTEs 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 10 Gb
data network.
DLm8000 architecture 19
AB C D E F G
Disk 0 Disk 1
L K J
GEN-000718
Figure 1 Front view of the VTE
The VTE controls and indicators are as follows:

◆ A and B — LAN 2 (Eth 0) and LAN 1 (Eth 1) LEDs activity:
• Blinking green light indicates network activity.
• Continuous green light indicates a link between the system and the network to
which it is connected.
◆ C — Power button: Turns the system power on or off.

Do not press the Power button while the VTE is online to the host. Follow the
shutdown procedure in “Power down DLm” on page 63 before pressing the Power
button
D — Power/Sleep LED:
• Continuous green indicates that the system is powered on.
• Blinking green indicates that the system is sleeping.

• No light indicates that the system does not have power applied to it.
◆ E — Disk activity LED.
◆ F — System status LED:
• Continuous green indicates that the system is operating normally.
• Blinking green indicates that the system is operating in a degraded condition.
• Continuous amber indicates that the system is in a critical or nonrecoverable
condition.
• No light indicates that POST is running, or the system is off.
◆ G — System identification LED: A blue light glows when the ID button has been
pressed. A second blue ID LED on the rear of the unit also glows when the ID
button has been pressed. The ID LED allows you to identify the system you are
working on in a bay with multiple systems.
◆ H — System identification button: Toggles the front panel ID LED and the server
board ID LED on and off. The server board LED is visible from the rear of the
chassis and allows you to locate the server from the rear of the bay.
◆ I — Reset button: Reboots and initializes the system.

Do not press the Reset button while the VTE is online to the host. Follow the
shutdown procedure in “Power down DLm” on page 63 before pressing the Reset
button.
◆ J — USB 2.0 port: Allows you to attach a Universal Serial Bus (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 port: Allows you to attach a video monitor to the front of the VTE.
Figure 2 Rear view of a VTE
ACP
The DLm8000 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.
The ACPs provide a user-friendly console (DLm Console) to execute various setup and
configuration tasks. The ACPs connect to the DLm management LAN of the DLm.
Note: You must connect both ACPs to your network.

A B C D E F G CNS-000979
Figure 3 Front view of the ACP
A. USB port B. Power button

C. System status LED D. System power LED
E. Hard drive activity LED F. NIC 1 LED
G. NIC 2 LED
AC power Mouse Com 1 Modem Eth 1 Eth 2 Eth 3 Com 2
B MG MT
CS
USB ports (For USB disk, USB mouse

Keyboard Video Eth 0 or USB keyboard)
Figure 4 Rear view of the ACP
Table 1 ACP rear panel connectors
Connector Description
AC Power AC power. Connect an AC power cord between the AC power plug

and a power distribution unit.
Com 1 Modem for remote support and dial home capabilities.
Com 2 Serial connection from service laptop.
Eth 0 Connects to management switch port.
Eth 1 Customer network.
USB USB connection. Plug USB drive in here to upload or download

files. You can also use the USB connectors for a USB mouse and
keyboard.
Mouse Use with KVM mouse. Alternatively, you can use a USB mouse
connected to a USB port.
Keyboard Use with KVM keyboard. Alternatively, you can use a USB
keyboard connected to a USB port.
Video Use with KVM monitor.
DLm management network

The DLm has an internal Gigabit Ethernet network for management purposes. In a
DLm8000, the ACPs, VTEs, VNX VG8, and VMAX systems management ports are
connected to a pair of 1 Gb Ethernet switches to protect against a single switch failure.
2
AT-9924TL-EMC
GEN-001778
Figure 5 24-port AT-9924TL switch

10 Gb VTEC-VNX connection
In a DLm8000, data from the mainframe is transferred via FICON to the VTE. From the
VTE, it is passed to a VNX Data Mover using a 10 Gb Ethernet connection. The 10 Gb
Ethernet network has a pair of 10 Gb Ethernet switches to protect against a single
switch failure.
Figure 6 Brocade VDX 6720 switch
Backend storage
The DLm8000 uses the combination of a VNX VG8 gateway connected to a VMAX
storage array to serve as the backend storage. The primary benefit of a
DLm8000-based system is the use of SRDF for replicating data to remote systems
thereby allowing customers to take advantage of the associated Disaster Recovery
(DR) capabilities and applications of SRDF.
VG8 gateway
DLm8000 can be configured with VNX VG8 gateway with:
◆ 2 to 8 storage controllers (Data Movers)
◆ 2 Control Stations
The Control Stations are configured as primary and secondary to ensure high
availability. The VG8 is configured with one standby Data Mover and one to seven
active Data Movers. There are no internal disks or caches in the VG8 gateway.
10 GbE Brocade 5100B Fibre switches

A pair of 10GbE Brocade 5100B 48-port Fibre switches connect VG8 Data Movers to
the VMAX. They provide the fabric for the Data Mover-to-VMAX FA director ports. The
two Brocade DS-5100Bs switched are shipped separately and will be rack mounted in
the VG8 cabinet.
VMAX storage
The VG8 gateway is attached to a VMAX 20K with a minimum of 7 FC drives (three
RAID1 pairs plus a spare). The data drives are 2TiB 7.2 RPM SATA using FBA 6RAID6.
The Control Devices are 300GB 10K RPM Fibre Channel 4 Gbps. Enginuity 5875 is the
only supported uCode family.
Mainframe channel interfaces

A VTE contains mainframe channel interfaces. These channel interfaces are two Fibre
Connectivity (FICON) interfaces per VTE.
The FICON interfaces can be either single mode or multimode. Do not mix a single
mode and multimode FICON within a single DLm system. A DLm system configured
with eight VTEs provides 16 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 2 on page 22 shows the rear view of the VTE with the channel interfaces to the
right of center of the unit. DLm8000 supports only FICON connections.
FICON channel
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.
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.

In DLm 8000, the FICON adapter has three light-emitting diode (LED) indicators, listed
in Table 2 on page 27, visible from its rear. 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
Connect DLm to a FICON channel

DLm can be connected directly to the mainframe FICON channel or it can be connected
through a FICON switch. I/O generation examples for both kinds of connections are
shown next.
In either case, to properly define a DLm V348x, or 3480, 3490, or 3590 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 3590
• A real 3490
• A real 3480
◆ The 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 direct FICON connection

Basic, dedicated non-shared (non-EMIF) mode
CHPID PATH=(0A),DED,TYPE=FC
CNTLUNIT CUNUMBR=EA80,PATH=(0A), +
UNITADD=((00,32)),UNIT=3590
IODEVICE ADDRESS=(EA80,32),CUNUMBR=(EA80), +
STADET=Y,UNIT=3590
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=3590
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=3590
Note: With EMIF (shared) mode, specify LPAR=n in the DLm virtual device(s) 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=3590
Note: With EMIF (shared) mode, specify LPAR=n in the DLm virtual device(s) 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=3590
DLm8000 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 DLm Capacities
Capacity DLm8000
Max useable capacity (TB) 1792 TB
Min useable capacity (TB) 12 TB
Add-on useable capacity (TB) 12 TB
Disk capacity (TB) 2 TB
Note: The 1792 TB max raw capacity is calculated as [256 TB/VG8 storage controllers
(Data Movers) * 7 active storage controllers].
Details of FICON connections are as follows:

◆ Adapter type - FICON
◆ Number of ports - 1
◆ Number of unique LPARs - 256
◆ Number of control units - 16
◆ Number of links - NA
◆ Maximum number of paths supported per VTE - 4096

Figure 7 DLm8000 Single site block diagram
DLm8000 devices and capacity 31

Figure 8 DLm8000 Two site block diagram
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, 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 eight VTEs
can emulate up to 2,048 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 states

A virtual tape drive is in one of the two basic states at any given 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.
DLm8000 devices and capacity 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 supports one physical IBM 3592 tape drive or TS1120
attached 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.
DLm8000 supports 1-8 Fibre Channel attached tape drives.

High availability features of DLm8000

DLm includes failure recovery mechanisms in various parts of its architecture to
ensure optimum availability.
VTEC
DLm8000 contains a minimum of two VTEs and 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.
◆ DLm8000 has 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 secondary 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. In DLm8000, 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.
VG8
Each DLm8000 will have one VG8 with a minimum of two storage controllers (Data
Movers) configured in the system.
Each VG8 storage controller has the following I/O :
◆ 4 x 8 GbE FC ports (1 x 4-port card) for connection to FC switches
◆ 4 x 10 GbE optical ports (2 x 2-port cards), providing two connections to the 10
GbE switches.
◆ Management ports for internal management network.
High availability features of DLm8000 35

◆ The VNX VG8 supports maximum filesystem size (16 TB) and maximum LUN size
(16 TB).
◆ The VNX VG8 and VMAX sub-systems are dedicated to the associated DLm8000
system. No sharing of DASD data on the DLm8000 is allowed.
◆ Storage controller failover — The VG8 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.
Each VG8 within the DLm8000 can have up to eight storage controllers, where
seven are active and one is a standby. The number of active storage controllers is
based on the storage capacity of the system.
Local storage controllers are not supported in a DLm8000. Only active or standby
are allowed.
Each storage controller is a completely autonomous file server with its own
operating system image. During normal operations, the VTEs interact directly with
the storage controllers. Storage controller failover can protect the VMAX server
against hardware or software failure.
◆ Fail-Safe Network (FSN) — FSN is a high-availability networking feature supported
by the VG8 storage controllers (Data Movers). 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 a single link or multiple links. VMAX
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 VG8 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.To use this feature, each storage
controller in the VG8 server must have:
• Two optical 10 GbE ports to connect the storage controllers to the switches in
the VTEC (one for each 1 GbE switch)
• Two ports configured together using an FSN failure recovery
VG8 server comes with RAID 6 protection to ensure high availability.

Ethernet
switch
VTE-N
Storage Controller !
enclosure 1
!
Lnk
Lnk
Rx
Tx
Rx
Tx
0 2 0 2
1 3 1 3
Storage Controller
enclosure 0
!
VTE1
Lnk
Lnk
Rx
Tx
Rx
Tx
0 2 0 2
1 3 1 3
Storage Controllers Ethernet VTEs

switch GEN-001931
Figure 9 VTE to storage controllers — Network topology
Figure 9 on page 37 shows multiple VTEs connected to the storage controllers

through two Ethernet switches. This illustrates the high availability of the network
storage and FSN.
High availability features of DLm8000 37

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, local or remote DLm
systems
◆ Support for synchronous replication using SRDF/S for business continuance and
disaster recovery
◆ No single point of failure of mainframe tape data because the DLm8000 system
has a minimum of two VTEs
◆ Local storage controllers are not supported in a DLm8000. Only active or standby
are allowed
◆ Support for two erase policies for space reclamation :
• 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.

◆ 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 39


CHAPTER 2
DLm Operations
This chapter explains the routine DLm operations:

◆ Management access to DLm ............................................................................. 42
◆ Access a VTE .................................................................................................... 52
◆ Power up DLm .................................................................................................. 55
◆ Power down DLm.............................................................................................. 63
◆ Start and stop tape devices.............................................................................. 69
◆ Support access to DLm..................................................................................... 70
◆ Support access to DLm..................................................................................... 70
DLm Operations 41
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 and the VNX VG8 Control Stations. 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 data

To connect to the DLm system, you will need some IP addresses and 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 4 on page 42 lists the details that you will need before you access the DLm
system and can be used as a checklist. Fill out the Actual column with the current
actual values..
Table 4 DLm system access details
Item Default Actual
DLm Console
HA IP address Customer assigned
Username dlmadmin
Password password (first login)
Note: The system

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

DLm Operations
Table 4 DLm system access details
Item Default Actual
ACP2
IP address Customer assigned
Username dlmadmin
Password password
Access the DLm Console

The DLm Console is a web-based console that is used to configure and monitor the
DLm system. It is the management interface to the DLm system. DLm Console can be
accessed through the web browser on the ACP desktop. During initial setup, if you
provided the EMC service personnel with an additional IP address to directly access
the DLm Console, you will be able to use that IP address to access DLm Console from
outside the DLm (using a web browser).
Connect to the DLm Console

To connect to the DLm Console:
Note: This procedure assumes that you have access to and are connected to the Data
Center LAN to which the ACP is connected 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://192.168.1.1
Your web browser may announce that you’re attempting an untrusted connection
as illustrated. Select Continue to website (not recommended).
Depending on the browser, you may get a different security warning from that
displayed below. Regardless of this warning, it is safe to connect to ACP.
The login screen opens as shown in Figure 10 on page 44.
Management access to DLm 43

DLm Operations
Figure 10 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 11 on page 45. At first login, DLm
prompts you to change the DLm Console password.

DLm Operations
Figure 11 DLm8000 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
(The VT Console is a console that allows you to or monitor and operate a VTE.
Figure 16 on page 53 provides more information.). 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 43.

DLm Operations
2. Click External.
3. Click the Time tab if it is not already displayed.
Figure 12 DLm date and time
4. Use one of these two methods to set the date and time on a VTEC:
• Configure the system to use a Network Time Protocol (NTP) server.
Note: EMC strongly recommends that you use an NTP server.
If the ACP 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.

DLm Operations
• Manually set a specific date and time.

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:
page 43.
2. Click External.
3. Click the Authentication tab.

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

• Native
“Native” on page 48 provides instructions to add, modify, or delete users of
Native authentication type.
• LDAP (including Active Directory)
“LDAP” on page 49 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.

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 user 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.
Select the LDAP authentication type when the DLm system is attached to your
corporate network, and you already have the appropriate directory server installed
and running on the network. If you select LDAP without the required connectivity, your
login fails and you must try again using the Native authentication type.

DLm Operations
Figure 14 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
– Bind password: The password for the Bind DN

DLm Operations
◆ 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
Network and DR configuration restrictions

All configurations defined in DLm Console must have exactly the same network and
DR configuration.
IMPORTANT
DR must be disabled in all DLm8000 configurations. The DR daemon enabled check
box should be unchecked on all configurations you define on DLm Console.
The DR daemon enabled check box in the External > DR tab of DLm Console must
always be unchecked for all configurations defined in DLm Console. (DLm Console can
fail if this check box is not unchecked in any of the configurations.) Unchecking the
box will gray out the DR Configuration area as shown in Figure 15 on page 52.

DLm Operations
Figure 15 Disabling DR configuration
Access a VTE
You can access the VTE through the DLm Console.
page 43.
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. DLm 8000 has a
maximum of eight VTEs. Only the icons matching the VTEs installed on DLm are
displayed on the DLm console.
2. In the Console column, click the icon corresponding to the VTE you want to
access.

DLm Operations
Figure 16 VT console
The VT console for that VTE opens.

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.
Access a VTE 53
DLm Operations
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 69
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
• 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

DLm Operations
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.

page 43.
The System status tab of the System menu opens by default.
2. In the Reboot column, click Reboot for the VTE you want to reboot.
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. VMAX
2. VNX VG8 Network Server
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.
Power up DLm 55
DLm Operations
VMAX
Refer to EMC Symmetrix Power Up and Power Down Procedure (2-PDP Bays or 4-PDP
Bays) [P/N 300-012-669] for information.
VNX VG8 server power-up

The following steps explain the procedure for powering up the VNX VG8 Network
Server:
1. Turn off the cabinet circuit-breakers to remove all power from the VG8 cabinet.
2. Verify that the VG8 Data Mover enclosure power cables are disconnected from the
cabinet Power Distribution Panel (PDP). You will connect these power cables later.
3. Verify that each Control Station power cable is disconnected from the PDP. You will
connect this power cable later.
4. Turn on (I position) the left and right cabinet circuit-breaker switches at the back
of the cabinet near the bottom.
5. Connect the Data Mover power cables to the PDP and wait for the Data Movers to
power up. Look for a blue power LED on the front of the Data Mover enclosure to
indicate that they are powered up.
Figure 17 on page 57 shows an example of a VG8 with two Control Stations and
two Data Mover enclosures. In the figure, the Data Mover power cables are labeled
3, 4, 5, and 6.

DLm Operations
Figure 17 VG8 power up example
6. Connect the power cables for the first Control Station (CS 0) to the PDP. In the
example shown in fgure x, this is power cables 1.
7. If the system power LED on the front of the Control Station indicates that the
Control Station is off, turn on the Control Station by pressing the Power button on
the front. Ensure that the Control Station is powered up before continuing.
8. After you have confirmed that CS 0 is up and healthy, power up CS 1.
9. Check the system and hardware status as follows:
a. From a browser, type the IP address of the primary Control Station.
b. Log in to the Unisphere software as sysadmin and define the scope as Global.
c. Use the drop-down list at the top left Dashboard to select the system name
and view its System Information page.
d. On this page, verify that the Status fields for the VNX display OK
Power up DLm 57
DLm Operations

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.
ACP power-up
To power up and start the ACP:
1. Before powering up the ACP, make sure you are connected to the 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 18 on
page 58.
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 18 ACP indicators and controls

DLm Operations
A. USB port B. Power button

C. System status LED D. System power LED
E. Hard drive activity LED F. NIC 1 LED
G. NIC 2 LED
AC power Mouse Com 1 Modem Eth 1 Eth 2 Eth 3 Com 2
B MG MT
CS
USB ports (For USB disk, USB mouse

Keyboard Video Eth 0 or USB keyboard)
Figure 19 Rear view of the ACP
Table 5 ACP rear panel connectors
AC Power AC power. Connect an AC power cord between the AC power plug

and a power distribution unit.
Com 1 Modem for remote support and dial home capabilities.
COM 2 Serial connection from service laptop.
USB USB connection. Plug USB drive in here to upload or download

files. You can also use the USB connectors for a USB mouse and
keyboard.
Power up DLm 59
DLm Operations
Mouse Use with KVM mouse. Alternatively, you can use a USB mouse
connected to a USB port.
Keyboard Use with KVM keyboard. Alternatively, you can use a USB
keyboard connected to a USB port.
Video Use with KVM monitor.
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 61.
Note: You can power up the VTEs in any order as they operate independently of
each other.
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.

DLm Operations
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 61 shows these controls and indicators on the front of a VTE.
A LAN 2 activity • Blinking green light indicates network activity.

LED (eth0) • Continuous green light indicates a link between
the system and the network to which it is
connected.
B LAN 1 activity • Blinking green light indicates network activity.

LED (eth1) • Continuous green light indicates a link between
the system and the network to which it is
connected.
C Power/sleep Toggles the system power on/off.

Button
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 63 for
shutting down a VTE before pressing the
Power/Sleep button on any active VTE.
Power up DLm 61
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 • Continuous green indicates the system is

LED 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
identification are working on in a rack:
(ID) 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 63 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
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.

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.
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
Note: Vary off the tape devices from the host before you power down a VTE.
2. VNX VG8
3. VMAX
4. ACP
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 63

DLm Operations
VTE power down

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.

Do not power off the VTE, when devices are online to the host. Follow the shutdown
procedure; do not use 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. Vary the devices offline to the mainframe.

3. Verify that all the tape drives are offline:
a. Open a web browser.
b. In the browser, type the ACP IP address:
https://ip_address
where ip_address is the address of the ACP.

The DLm Console opens displaying the System status tab of the System menu
by default. The console displays icons for each configured VTE.
c. In the Console column, click the icon corresponding to the VTE you want to
access.
d. At the VT Console prompt, type the command:
quiesce all
The quiesce command prevents new tapes from being mounted on that VTE,
but does not affect tapes already mounted.

DLm Operations
e. At the VT Console prompt, type the command:

query paths assigned
The desired response is:

No paths currently established and assigned.
f. If you do not see this response, refer to EMC Knowledgebase solution
emc280222 "What to do if there are active paths when shutting down or
restarting a VTE" for information on how to identify and remove any online
devices.
g. Once the devices are offline, it is still possible that tapes were left mounted. To
verify, in the virtual tape console, at the VT Console prompt, type the
command:
query mount
That command gives a list of the devices and VOLSERs of any mounted tapes.
The heading is always displayed; it is expected to not list any mounted tapes.
h. If any tapes were listed, follow the instructions provided in the EMC
Knowledgebase solution emc280282 "What to do if there are mounted tapes
when shutting down or restarting a VTE".
i. Quit from the VT Console:
quit
4. Stop the VT application.

a. Access the ACP:
1. Start an SSH client like PuTTY.
2. Select the SSH connection type.
3. 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.
4. Click Open.
b. Log in to the ACP as root. The password is Just4Eng&Use.
c. At the ACP SSH prompt, type the following command to open an SSH session
to a VTE:
ssh vte#
Power down DLm 65

DLm Operations
where vte# is the VTE name. For example, for VTE 1, type: ssh vte1.
d. To stop the tape emulation application, type:
vtd stop
5. 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,6,7, or 8).

The VTE you specified in the poweroff command enters the shutdown state.
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.
Halt the VNX VG8 server

A planned powerdown of the VNX VG8 server and integrated storage array requires
access to the VNX VG8 Control Station. Call EMC Customer Support for assistance.
Before you power down the VNX VG8 server:

1. Vary off all tape drives and power down all VTEs to stop all I/O activity.
2. Log in to the Control Station as root, using a Telnet or SSH session. To perform a
planned powerdown, you must be within close proximity to the VNX VG8 server.
3. If you wish to verify the system's health, type:
/nas/bin/nas_checkup
4. To halt the Celerra server, type:

/nasmcd/sbin/nas_halt now
A prompt similar to this one appears:

[root@celerra156-cs0 root]# nas_halt now

DLm Operations
******************** WARNING! ********************

You are about to HALT this Celerra including all of its
Control Stations and storage controllers. 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 number of
storage controllers and the amount of storage managed by the VNX VG8 server.
Your connection ends before you get a command complete message.
Verify Control Station powerdown

To verify that the server has been shut down:
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
Power down DLm 67

DLm Operations
Power down VMAX

Refer to the EMC Symmetrix Power Up and Power Down Procedure (2-PDP Bays or
4-PDP Bays) [P/N 300-012-669] for information.
Power down the ACP

You can power down and reboot the ACP without affecting the operation of the VTE.
To power down the ACP:
1. Access the ACP:
a. Start an SSH client, such as PuTTY.
b. Select the SSH connection type.
c. Type the IP address of the primary ACP in the hostname (or IP address) field.
The primary ACP is always assigned the highly available IP (HA IP) address
and can reside on either 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.

DLm Operations
b. After you have powered down the secondary ACP, power down the primary
ACP:
poweroff
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 52.
2. In the VTE console, type the appropriate command. For example, to start the VT
application, type:
Start and stop tape devices 69

DLm Operations
STARTVT
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 quit and press Enter to close the console window.
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 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.

DLm Operations
Figure 22 EMC Secure Remote Support
Modem support
DLm provides external modems to allow remote access to the ACPs for support and
diagnostic purposes. The supplied modems are attached to the ACPs. A telephone
line should be connected to the ACP modem (which in turn should be cabled to the
COM1 port of the ACP). Figure 4 on page 23 Two modems are supplied and are
connected to each ACP.
The ACP can be configured to send messages to EMC using the ConnectEMC function
when problems are detected within the VG8 or the VTEC. The ConnectEMC options
include sending the messages via a modem through a customer-supplied analog
telephone line.
Support access to DLm 71

DLm Operations

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

◆ Tape libraries ................................................................................................... 74
◆ Configure virtual devices .................................................................................. 78
◆ Manage configuration files ............................................................................... 92
◆ Tape Erase ....................................................................................................... 94
◆ Manage VTE and ACP logs ................................................................................ 96
◆ Back-end tape support ..................................................................................... 99
◆ DLm diagnostic reporting ............................................................................... 103
◆ AWSPRINT library utility.................................................................................. 106
◆ DLm8000 site configuration considerations ................................................... 106
DLm Administration 73
DLm Administration
Tape libraries
EMC service personnel define your storage during initial setup. This section describes
how the tape libraries are set up. DLm 3.4 supports enhanced filesystem (EFS)
configuration.
In an EFS-enabled DLm system, the tape library is made up of one or more filesystems
and may be sub-divided into storage classes. 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.
A DLm system that has EFS enabled 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 initializing new tape volumes or writing to scratch 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.
IMPORTANT
Too many VOLSERs in a filesystem leads to performance issues. EMC strongly
recommends that you limit the number of VOLSERS to 30,000 per filesystem.
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.
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.
Note: To provide the best overall performance in FICON environments, multiple

filesystems in each library are desirable.

DLm Administration
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.
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 VG8 Server using
DLm tools.
2. Define the lock file system and tape library 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.
Lock filesystem for EFS

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) 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 VG8 Server .
◆ 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 filesystem 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).
Tape libraries 75
DLm Administration
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.
Backward compatibility
If you install a DLm 3.x-based VTE into an existing multiple-VTE 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.1.
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.x enhanced
filesystem architecture.
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 in a VT console window when you start any tape drives on
DLm. Otherwise, no scratch tapes will be available for use within the DLm system.
In an EFS-enabled DLm system, 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

DLm Administration
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 of any tape drive pointing to the tape library.
◆ count is the number of serial numbers to initialize.
◆ n is the class to which these volumes are to be added to. CLASS= is a required
parameter when using Enhanced File System (EFS), and is not valid when EFS is
not being used. Unless DIR= is also specified, the new tapes will be spread
across all subdirectories of the specified CLASS.
◆ dirname optionally specifies the subdirectory to create the volumes in. Specify
only the subdirectory, not the full path; the base tape library directory is derived
from the PATH of the DEV= parameter. For example, if the tape library is /tapelib,
specifying DIR=L2 would initialize the tapes in /tapelib/L2. DIR is an optional
parameter when using Enhanced File System (EFS), and is not valid when EFS is
not being used.
DIR is an optional parameter. DIR is not a requirement. If DIR is not specified,
INITIALIZE spreads the new tapes across all subdirectories of the specified CLASS.
CLASS is a required parameter.
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 spread across all
filesystems with class 0.
Tape libraries 77
DLm Administration
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=000000 COUNT=1000 will result in the 1,000 tape
volumes being created with serial numbers ranging from 000000 to 000999.
VOL=001000 COUNT=1000 will result in volumes ranging from 001000 to 001999
being created.
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 124
Configure virtual devices

You can define up to 256 virtual 3480, 3490, or 3590 tape drives on each DLm VTE.
During initial setup, EMC service personnel define your storage based on the details
provided by your system administrator.
Planning considerations
◆ For z/OS systems, plan for one virtual device that will always be 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, (two virtual devices if DLMHOST logging is requested), to
remain offline and be used by DLMHOST to communicate with the VTE.

DLm Administration
DLm configuration files

The DLm Console allows you to configure the VTE and save your 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 91 allows you to select the
configuration file for a VTE. “Manage configuration files” on page 92 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 parameters

Each DLm includes a configuration utility, which is a browser-based graphical
interface, to configure the virtual tape driveson each VTE.
1. Access the DLm Console using the web browser. “Access the DLm Console” on
page 43 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 79

DLm Administration
Figure 23 Global options
4. Enter values in the fields under Global options at the top of the Devices panel:
• 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.
“Tape Erase” on page 94 provides more information about DLm’s erase policy.

DLm Administration
• 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.
• Erase scratched tapes after: Indicates the duration after which the data of a
scratched tape will be automatically erased . 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 95 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 utilities 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

DLm Administration
independent of any mainframe security programs (such as RACF and ACF/2).

By default, these utilities are disabled. Selecting the Tape import/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.
• 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.
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>
The addition of a VOLSERLOCKDIR parameter enables Enhanced File System
(EFS) support.
For example, if the lock directory has been defined as the filesystem located at
mount point /lockfs/LOCK, enter:
VOLSERLOCKDIR /lockfs/LOCK
Add devices
Define the virtual tape devices (drives) to be emulated to the mainframe by this VTE in
the Control units section.
Note: Filesystems must be created before you try to add devices. This is done by EMC
service personnel during initial setup.“Tape libraries” on page 74 provides more
information about tape libraries and filesystems.

DLm Administration
Control unit Device Type
Figure 24 Control units
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
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

DLm Administration
Each device on each VTE 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 the VTE
writes to the library. The available values are Yes, No, and Force. The default
value is Yes.
When IDRC is set to 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.
When IDRC is set to 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.
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.

DLm Administration
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.
• Encryption key class

Enter a valid RSA key class to enable the drives to do encryption. When this
field is configured, the tape drive makes a call to the RSA Key Manager using
this key class each time the drive opens a tape volume for output.
• 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 with a VSE system. All virtual tape drives attached to the same VSE
system or guest should have a unique GROUP number. When DLMMOUNT
or a tape manager requests a mount, only virtual drives in the same GROUP
are considered for the mount. Each VSE requires a unique GROUP number.
When not coded, all drives default to GROUP=0.
– LABELS=S/N/A
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 isS 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)

DLm Administration
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
device types 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
4 — Trace errors, status, headers, and data
5 — Perform a full packet trace (for customer support only)
– VOL=(xx,yy,…)
VOL allows 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

DLm Administration
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 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.
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 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.

DLm Administration
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.
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 an optional parameter to associate a synonymwith 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) specifies that any load request received for
SCRTCH must be satisfied with a VOLSER that starts with either "00" or "01". 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. When enhanced file system (EFS)is in use, DLm first identifies
all filesystems assigned to the storage class (or classes) for this scratch
synonym 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. The synonym DRTAPE will use volume
serial numbers beginning with 00 or 01 in Class 0 storage. The synonym CLASS
will use only the specific VOLSERs CLASS1 and CLASS2, in Class 0 storage.
◆ DRTAPE=((00,01),CLASS=(CLASS1,CLASS2))
establishes the scratch synonym DRTAPE using VOLSERs beginning with 00 or 01
located in either storage class 1 or storage class 2.

DLm Administration
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 Configuration operations 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 92 provides more information.
Delete a device range

1. Select the Devices menu at the top of the page.
2. Scroll down to the Current devices section.

DLm Administration
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 92 describes the procedure to install the
updated configurations.
Manage configuration files

Activate or install a configuration
You must install a configuration for it to be used by a VTE. If you 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.

When you click Install, the virtual tape application (VT) restarts. If your VTE is
currently online with the mainframe, EMC 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 VT 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.

DLm Administration
See “Configuration files on source and target systems” on page 113 for information
about configurations on the source and target systems in the replication environment.
Create a new configuration

1. Select the Configuration menu at the top of the DLm Console.
2. Enter a configuration name in the text box adjacent to the Create configuration
named: button.
3. Click the Create configuration named: button.
4. Select the Devices menu at the top of the DLm Console and enter the
configuration values described in:
• “Configure global parameters” on page 79
• “Add devices” on page 82
• “Scratch synonyms” on page 88
5. Save the configuration as described in “Save configuration” on page 91.
Copy a 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 configuration

2. Select the configuration file you wish to modify or delete.
3. Do one of the following:
• To modify the configuration file:
Manage configuration files 93

DLm Administration
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.
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)
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 79.
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 some time before being erased.

DLm Administration
Time-to-Live erase policy

The TTL erase policy gives you better control over the length of time 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.
You can specify the time in:
◆ Days
◆ Hours
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.
Both
DLm starts erasing space if either of the both conditions - Space erase or TTL policy is
satisfied.
Tape Erase 95
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 DLm Console” on
The System status tab of the Status menu opens by default.

DLm Administration
Figure 28 System status
2. Click the icon in the Logs column corresponding to VTE for which you need
the logs.
The logs appear in a new window or a new tab. Click Previous to view the previous
logs. Use Previous and Next to navigate through the logs.
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.
Manage VTE and ACP logs 97

DLm Administration
Figure 29 Gathering ACP and VTE support data
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.

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 or TS1120 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 or TS1120 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 or TS1120 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.
For the device being mapped to the physical drive, you must replace the Tape Library
parameter with the following parameter:
DRIVE-nnnnnnnnnnnn
where nnnnnnnnnnnn is a 12-digit serial number for the tape drive. (Figure 25 on
page 84 shows Tape Library field in the Add devices section of the Tape Device
Configuration page.) 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
Back-end tape support 99

DLm Administration
Library field for the mapped 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 83.)
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 82 provides more information.
2. In the Add devices section, enter DRIVE-<12-digit drive serial number>.
a. Access the VT console as described “Access a VTE” on page 52.
b. Obtain the drive serial number by typing the following on the VT console:
show drive list
If the tape drive is not listed you will need to follow the next steps:
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.
Open the VT console as described in “Access a VTE” on page 52 and enter the
following commands:
scsiadd
This rebuilds the SCSI device table.

lsscsi
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
If the tape drive is still not listed you will need to reboot the VTE from the
webconsole interface as described in “VTE reboot” on page 55.

DLm Administration
3. Update the appropriate tape drive configuration.

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.
4. Vary the drives defined on this VTE online to the mainframe.
Segregate the devices

After mapping a device as described in “Device mapping” on page 99, 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 and the tape drive's display screen. The request remains
outstanding until the physical drive becomes ready. This requires an operator to
mount a tape and ready the drive.
The tape cartridge written will be compatible with 3592 cartridges written from any
mainframe-attached 3592 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 3592 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.
Back-end tape support 101

DLm Administration
Export to and import from tapes

As an alternative to Direct Tape, when a mainframe tape drive is 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 DLm Console” on
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 80 opens.)
4. Select the Tape import/export enabled check box. “Configure global parameters”
on page 79 provides more information about this field.
5. Save the configuration as described in “Save configuration” on page 91 and
install it on the VTE as described in “Activate or install a configuration” on
page 92.
Once 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 52 provides instructions.
2. After connecting to the individual VTE, you can type the EXPORT and IMPORT
commands in the VT console.

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 150 provides details about how to use the EXPORT command.
“IMPORT” on page 153 provides details about how to use the IMPORT command.
DLm diagnostic reporting

The different subsystems of the DLm system generate messages as they operate. The
major sources of messages in DLm are:
◆ VTEC
◆ ConnectEMC (reports VTEC and VNX VG8 Server issues)
VTEC
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
◆ 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:
1. Configure the message destinations.
2. Configure which messages should be sent. “Configure messages and recipients”
on page 104 provides more information.
For z/OS messages you must install the z/OS started task and then configure which
messages you want sent. “DLMHOST” on page 142 provides more information.
DLm diagnostic reporting 103

DLm Administration
SNMP
The VTEC contains SNMP MIBs that monitor the system and report events. Once
configured, the VTEC can send SNMP alerts to a designated SNMP manager. SNMP
alerts are sent as SNMPv2c traps on port 162 using the community name 'public.'
To configure the VTEC to send SNMP alerts:
page 43.
2. Click External.
3. Select the Notify tab.
Figure 30 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.
Configure messages and recipients

You can configure which messages get sent to an SNMP management console or the
z/OS master console.
page 43.
2. Click Messages.
Three tabs appear representing informational, warning, and error messages:
• Error message routing
• Warning message routing
• Informational message routing

DLm Administration
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.
All messages in the Errors message routing tab are preselected and cannot be
deselected.
Figure 31 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 diagnostic reporting 105

DLm Administration
ConnectEMC
The VNX VG8 ConnectEMC function can automatically notify the EMC service center or
other service providers if the VTEC or VNX VG8 system detects a serious problem.
ConnectEMC sends messages using email, FTP, or a VNX VG8 modem (through a
customer-supplied analog telephone line).
You can configure the VTEC to generate ConnectEMC events for error level SNMP traps.
“VTEC errors that generate ConnectEMC events” on page 380 provides a list of traps
that generate ConnectEMC events.
AWSPRINT library utility

The awsprint utility allows you to produce lists of the tapes in the DLm virtual tape
library. 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 152 provides the details of the command.
DLm8000 site configuration considerations

Figure 32 on page 107 , shows a DLm8000 SRDF configuration along with the
mainframe and VMAX DASD.

DLm Administration
Figure 32 DLm8000 two-site configuration
The mainframe block in Figure 32 on page 107 can represent multiple mainframes or
multiple LPARS within one, or mainframes with functions that include production
LPARS for both VMAX DASD and VMAX Tape.
The VG8 IP replication is not supported since all replication will be handled by SRDF.
DLm8000 site configuration considerations 107

DLm Administration

CHAPTER 4
SRDF Replication
This chapter provides information about the DLm SRDF Replication (SRDF) feature. The
major topics include:
◆ SRDF Replication Overview ............................................................................. 110
◆ SRDF connections and configuration .............................................................. 111
◆ Disaster recovery capabilities ......................................................................... 113
◆ SRDF benefits................................................................................................. 114
SRDF Replication 109

SRDF Replication
SRDF Replication Overview

EMC's Symmetrix-based remote replication technology (SRDF) enables the remote
mirroring of data center information at scale and with minimal impact to production
application performance. SRDF provides data mirroring between physically separate
DLm systems and acts as a foundation for Symmetrix-based disaster restart solutions.
This process of replication comprises of independent file-systems, host operating
systems, DBMS, and uni-directional source-to-target architecture.
SRDF Synchronous (SRDF/S)

The SRDF Synchronous Mode maintains a real-time mirror image of the data of the
remotely mirrored volumes. The data is written in the global memory of both the
systems, before the application I/O is completed. The data on the source volumes
and the target volumes are fully synchronized at the completion of an I/O sequence
through a first-in, first-out queue (FIFO) model. The data movement is managed at the
block level with synchronized mirroring. Using SRDF/S, the system pairs can be
located up to 200 km apart in a campus environment.
The I/O process in SRDF/S is described in Figure 33 on page 110.
Figure 33 SRDF Synchronous (SRDF/S)
1. The local system containing the primary volumes (Source) receives a write option
from the host.
2. The write I/O is transmitted to the remote Symmetrix system (secondary target
volume). The local Symmetrix system does not accept other write options to the
primary volume.

SRDF Replication
3. An acknowledgement from the remote Symmetrix system is sent to the local

Symmetrix system.
4. An I/O completed message is sent to the local host from the local Symmetrix
system. The additional host writes are accepted to the primary volume by the local
Symmetrix system.
Prerequisites for SRDF replication

◆ VNX software must be installed on both the source and destination systems.
◆ SRDF links must be operational between the two systems.
◆ The Symmetrix systems and the VNX Data Movers must be set up correctly.
All SRDF/S volumes must be synchronized.
SRDF connections and configuration

SRDF in DLm8000 offers uni-directional mirror relationship replication connections.
The DLm systems support FICON directors, and also offer native Gigabit Ethernet and
Fibre capability. An EMC Gigabit Ethernet director can be installed in place of a
traditional Remote Link Director (RLD) or Remote Fibre Director (RFD) or native Gigabit
Ethernet connectivity. There is a built-in compression to maximize the bandwidth
utilization of the DLm systems while using a Gigabit Ethernet director.
SRDF replication capabilities

SRDF offers the following capabilities:
1. Switched SRDF: Enables the Symmetrix system to be connected through any SAN
switches.
2. Dynamic SRDF devices: Provides the capability to change SRDF Groups and device
pairings as needed
3. Concurrent SRDF: Concurrent SRDF offers the capability to maintain multiple,
host-independent, remotely mirrored copies of data.
4. Campus implementations: There are several SRDF Campus implementations
available that enable units to be up to 66 kilometers apart.
SRDF connections and configuration 111

SRDF Replication
5. Metropolitan area networks implementations: Allows the customer to use the

entire bandwidth on the "dark fibre ". This depends on the ability of the customer
or the carrier for the dark fibre installation.
SRDF/S active-passive configuration for VNX

In an active/passive configuration, the SRDF/S provides a complete disaster recovery
solution by writing data on two systems source (R1) and the remote destination (R2)
which is located in different locations, before allowing any application to continue.
This guarantees that the second copy of the data is accurate till the last transaction,
and is available for immediate use. All the writes are handled in a serial fashion in the
synchronous mode of replication.
In an SRDF/S active/passive configuration:
1. The SRDF replicates the data to the destination soon as there is a write sequence
on the source. The source and destination are connected using SRDF/S links.
2. The write is transferred to the remote system using SRDF.
3. A cyclic redundancy check (CRC) is performed onthe datain cacheby the remote
system and an acknowledgement is sent to the source system.
4. The write-acknowledgement signal is sent to the host/server that initiated the I/O
request.
Note: The next write I/O is sent to the destination system only after the first write is
acknowledged in step 3.
Figure 34 SRDF/S active/passive configuration

SRDF Replication
The destination remains on standby when the mirroring between the systems is
carried out. The destination is powered up and its Control Station is fully operational
when on standby, and provides complete hardware redundancy for the source.
Configuration files on source and target systems

Only the source DLm has filesystems mounted and exported and devices defined. The
active configuration file on the source DLm is usually called Production configuration.
The source DLm also has a Standby configuration that has no filesystems mounted
and no devices defined. The target DLm also has a Production configuration and a
Standby configuration. The Standby configuration is the active configuration on the
target DLm.
In case of a failover, the target takes over and the Production configuration on that
DLm must be loaded as the active configuration. The DLm that was originally the
source DLm should now have the Standby configuration as its active configuration.
Disaster recovery capabilities

SRDF offers various levels of Symmetrix-based disaster recovery solutions. SRDF
offers the capability to maintain multiple, host-independent, remotely mirrored
copies of data, and allows the Symmetrix systems to be in the same room, in different
buildings within the same campus, or hundreds to thousands of kilometers apart.
SRDF maintains copies of data in different physical locations and enables you to
perform the following operations by integrating with your strategies for:
◆ Disaster restart, disaster restart testing
◆ Recovery from planned outages, remote backup
◆ Data center migration, data replication, and mobility
SRDF helps in meeting the following objectives:
◆ Recovery Point Objective—Identifying point in time to the preferred system and
preferred data which must be recovered after an outage
◆ Recovery Time Objective—Identifying the period of time within which the systems,
applications, and functions must be recovered after an outage
Disaster recovery capabilities 113

SRDF Replication
SRDF benefits
SRDF offers several benefits:
• It protects against local and regional site disruptions.
• It helps in maintaining continuous data availability and multiple remote
recovery sites.
• It assists in meeting regulatory requirements.
• SRDF provides near-instant recovery.
• It migrates, consolidates, or distributes data across storage platforms which
helps in data center consolidations and technology refreshes.
SRDF enables non-stop operations and provides application restart across volumes.

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

◆ Configure devices........................................................................................... 116
◆ Real 3480, 3490, or 3590 .............................................................................. 116
◆ Manual tape library ........................................................................................ 117
◆ MTL considerations for VTE drive selection ..................................................... 119
◆ MTL-related IBM maintenance ........................................................................ 121
◆ EMC Unit Information Module......................................................................... 121
◆ Missing Interrupt Handler............................................................................... 122
◆ Dynamic device reconfiguration considerations .............................................. 123
◆ DFSMShsm considerations............................................................................. 123
◆ Specify tape compaction ................................................................................ 123
◆ Locate and upload the DLm utilities and JCL for z/OS...................................... 124
◆ Initial program load from a DLm virtual tape ................................................... 139
Mainframe Tasks 115

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.
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.

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.
5. Make sure that each control unit's devices have the same LIBRARY-ID, but a
unique LIBPORT-ID per control unit.
6. Maximum number of tape drives defined in an MTL is 512. If more tape drives are
needed, a second MTL must be defined.
Manual tape library 117

Mainframe Tasks
Table 6 on page 118 contains an example of having the same LIBRARY-ID with its
unique LIBPORT-IDs.
Table 6 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 88.
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.

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 125 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 DLMZOS.JCL.CNTL. Step 4 on page 125 provides
download 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).
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.
MTL considerations for VTE drive selection 119

Mainframe Tasks
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.
IMPORTANT
Ensure the tape device is offline before you run any utility with the DEV=
parameter.
The device specified in the DEV= parameter must be offline. When the DLMCMD,
DLMSCR, or GENSTATS utility is used with the DEV= parameter when the specified
device is online, DLm displays the corresponding 182I message and terminates
the operation.
For DLMCMD and DLMSCR steps, this parameter eliminates the need to code a
DLMCTRL DD statement.
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.

Mainframe Tasks
c. Use ACS routines to select the appropriate library that limits the available
drive selection to that one drive.
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.
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 124.
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.
MTL-related IBM maintenance 121

Mainframe Tasks
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.
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.
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

Mainframe Tasks
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.
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.
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
Dynamic device reconfiguration considerations 123

Mainframe Tasks
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.
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 6, “z/OS Console Support,” provides details about this utility.
Downloading and using the DLm utilities and JCL for z/OS
To use any of these utilities, or the UIM:
1. Download the file DLMZOS-<version number>.XMI from the EMC support website
(http://Powerlink.EMC.com). Select Navigator > Disk Library Tools and transfer the
file to the mainframe as follows:
ftp target_system_name

Mainframe Tasks
(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:
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
• DLMHOST - The DLm utility that provides a command interface to VTEs and a
mechanism to list selected VTE log messages.
4. Transfer the DLMZOS.JCL file to the host. You must first unzip this file from the
DLMZOS.JCL <version>.zip file.
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)
Locate and upload the DLm utilities and JCL for z/OS 125
Mainframe Tasks
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.
7. If you plan to use the DLMCMDPR or GENSTATP procedures for Command Process
jobs, (See EMC Disk Library for mainframe Command Processors User Guide)
perform the following steps:
a. Copy the DLMCMDPR and GENSTATP procedures to a common PROCLIB.
b. Create a PDS dataset for the DLMCMD1, DLMCMD2, and DLMCMD3 REXX
programs contained in the DLMZOS.JCL dataset. Specify this REXX dataset in
the REXXLIB parameter in the DLMCMDPR and GENSTATP procedures. You can
optionally keep the REXX programs in the DLMZOS.JCL dataset and instead
just specify the DLMZOS.JCL dataset name in the REXXLIB parameter.
c. Specify the dataset name of the DLMZOS.PGMS dataset created in step 3
above in the BTILIB parameter in the DLMCMDPR and GENSTATP procedures.
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

Mainframe Tasks
◆ 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.
EMC Disk Library for mainframe Command Processors User Guide 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 DLMZOS.JCL.CNTL. Step 4 on page 125 provides
download instructions.
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 regularly 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. (Step 4 on page 125
provides download instructions.) The sample JCL is found in the RUNSCRA and
RUNSCRB members of DLMZOS.JCL.CNTL. RUNSCRB illustrates the use of the DEV=
parameter.
Mainframe Tasks
Table 7 on page 128 lists the DLMSCR parameters that may need to be specified.
Table 7 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.
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

SCR scratched state, 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.

Mainframe Tasks
Table 7 Parameters in DLMSCR (page 2 of 2)
Parameters Specification
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 119.
USETMC [CA-1 TMS environments only] This parameter enables DLMSCR to directly read
the CA-1 Tape Management Catalog (TMC) to find DLm-resident VOLSERs which
have been scratched and send the appropriate scratch requests to DLm for
processing. Use of the USETMC option requires that the DLMSCR DD JCL
statement point directly at the TMC (or a copy of the TMC).
SYNC [CA-1 TMS environments only] This parameter is valid only if specified along
with the USETMC parameter. It enables DLMSCR to synchronize the status of
the VOLSERs in the Tape Control Data Base (TCDB) and the DLm library with
those in the CA-1 TMC.
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 selected device must be associated with a library and associated filesystems
that are READ/WRITE (not READ ONLY).
◆ 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.
DLMSCR report output messages
Note: ALL messages are proceeded by: mm/dd/yyyy hh:mm:ss VOLUME xxxxxx.
Table 8 DLMSCR report output messages
Hex Code Volume Rejected Message Comments
0x01 REQUEST REJECT - INVALID Invalid data length (must be 17, 23, or 40 bytes).
LOAD/DSPLY
0x02 REQUEST REJECT - ALREADY Volume already scratched.

A SCRATCH
0x05 REQUEST REJECT - INVALID Invalid VOLSER specified - The input volume serial number does
VOLSER not conform to the standard volume naming convention. Check the
input TMS report.
0x06 REQUEST REJECT - VOLUME Volume in use on the same or different VTE or there is a possibility
IN USE of a STALE LOCK.

Mainframe Tasks
Table 8 DLMSCR report output messages
Hex Code Volume Rejected Message Comments
0x07 REQUEST REJECT - VOLUME Volume not found in file system; Make sure input tape device
NOT FOUND number points to correct tape library (i.e /tapelibxxx).
0x08 REQUEST REJECT - I/O ERROR I/O error has occurred during scratching process - refer to btilog for
additional information.
0x09 REQUEST REJECT - VOLSER File is locked - volume might be in use by another tape drive on this
LOCKED VTE or another VTE or there is a possibility of a STALE LOCK
0x0A REQUEST REJECT - Tape library directory is not accessible - Verify tape unit selected for
DIRECTORY PROBLEM A utility points to correct tape library.
0x0B REQUEST REJECT - Tape library directory is not writeable - Verify that tape library is
DIRECTORY PROBLEM B marked for Read/Write.
0x0C REQUEST REJECT - Invalid or missing VOL1 label in volume - Using AWSPRINT verify
INVAL/MISSING VOL1 volume VOL1 record has not been overwritten.
0x0D REQUEST REJECT - VOLSER The volume serial number from the TMS report and the VOL1 HDR
MISMATCH do not match; VOL1 HDR might have been overwritten.
0x0E REQUEST REJECT - Invalid or missing HDR1 label in volume - The HDR1 record is not in
INVAL/MISSING HDR1 the correct format; overlayed because of error; use AWSPRINT
utility to determine error.
0x0F REQUEST REJECT - Data Set Name mismatch - The last 17 alphanumerics of dsname
MISMATCHING DSNAME on the volume from input does not match HDR1 name on the
volume HDR1. This can be overridden using NODSNAMECHK.
0x10 REQUEST REJECT - INVALID The TMS input report date does not match the execution date of
DATE PASSED DLMSCR
0x11 REQUEST REJECT - CREATE Date mismatch - DLMSCR, unless overridden using NODATECHK,
DATE=TODAY defaults to no scratch same day.
0x12 REQUEST REJECT - FILE NOT File not writable - The filesystem directory is probably marked as
WRITEABLE Read Only; This might be target site.
Note: The hex codes listed are the error codes that the VTE returns to DLMSCR when
DLMSCR requests an action on a volume.
Mainframe Tasks
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.
◆ DLm does not scratch a volume created on the current day unless NODATECHK is
specified.
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. This action cannot be overridden by NODSNCHK.
◆ 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.

Mainframe Tasks
◆ 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.
ZARA considerations
DLMSCR expects the LIST SCRATCH type of scratch report to be used as input from
ZARA.
CA-1 considerations
Although there are various reports supported by TMS (CA-1), DLMSCR expects
Report-05 or Report-06 or Report-87 to be used.
The report generation parameters should request the field DSN17 instead of the
default DSN. (See PRIMUS EMC204223.) Otherwise, the report for multi-volume
multi-file tapes will have the incorrect DSN for all but the first VOLSER. Those volumes
with incorrect DSN will fail the DSN validity check performed by DLMSCR before
scratching a tape.
Unique to CA-1 TMS environments only, DLMSCR supports the following 2 additional
run time parameters:
◆ USETMC - When this parameter is specified, DLMSCR directly reads the CA-1 Tape
Management Catalog (TMC) to find DLm-resident VOLSERs which have been
scratched. A separate execution of the CA-1 scratch report utility (EARL) is not
Mainframe Tasks
required. Use of the USETMC option requires that the DLMSCR DD JCL statement
point directly at the TMC (or a copy of the TMC). DLMSCR scans the TMC and
sends the appropriate scratch requests to the DLm for processing.
Note: When using the USETMC option, DLMSCR sends a scratch request for any
scratch volume (those that pass prefix filtering) it finds in the TMC. This might
result in a large number of DLm500I messages followed by DLm524W messages
being issued to the DLm VTE btilog whenever DLMSCR is run. This is normal. The
DLm500I message indicates that the VTE application has received a request to
scratch a VOLSER. The DLm524W message indicates that the VOLSER was already
scratched.
◆ SYNC - This parameter is valid only if specified along with USETMC. The SYNC
option causes DLMSCR to synchronize the Tape Control Data Base (TCDB) and the
DLm library with the CA-1 TMC. The status of the VOLSERs in the TCDB and in the
DLm library will be changed from active to scratch or from scratch to active as
required to match the status of the CA-1 Tape Management Catalog (TMC).
Note: When using the SYNC option DLMSCR sends an unscratch request for any
active volume it finds in the TMC. This may result in a large number of DLm500I
messages followed by DLm524W messages being issued to the VTE btilog
whenever DLMSCR is run. This is normal. The DLm500I message indicates that the
VTE application has received a request to unscratch a VOLSER. The DLm524W
message indicates the VOLSER was already unscratched.
TMS users who use Scratch Pool Management and need to limit the eligible scratch
volumes to a limited range of VOLSERs must install the TMS usermod CL05219
(CTSMSGEX exit). When this exit is linked into IGX00030, an IPL with CLPA is required
to activate it. The exit causes the first 8 characters of the scratch poolname to be
placed into the Load_Display mount message that is sent to the tape drive. This
poolname can be defined as a scratch synonym so that the VTE application software
can restrict the eligible scratch volumes to a specific prefix group.

Mainframe Tasks
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 125 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 119
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.
◆ 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.
Mainframe Tasks
◆ 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 136 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 DLC070I, ENTER 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.
For example:
//LOG EXEC PGM=DLMCMD,PARM='WTOR'
//DLMLOG DD DSN=DLM.LOGFILE,DISP=OLD
//DLMCTRL DD DSN=DLM.CTRL,UNIT=3590,VOL=SER=BT9999,
DISP=(,KEEP)

Mainframe Tasks
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=3590,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

TDLMVER is a DLm utility that produces a report of DLm load modules that run on the
z/OS platform.
The DLMVER utility reports the versions of:
◆ The DLm mainframe modules on the mainframe:
• DLMCMD
• DLMLIB
• DLMSCR
• DLMVER
• GENSTATS
◆ The z/OS
Sample JCL
The following are sample JCL stream for the DLMVER utility, sample output, and notes
on its processing:
◆ DLMVER sample JCL 1
--- < USER JOBCARD >
---------------------------------------------------
//*
//* SAMPLE DLMVER JCL: PRINT DLM MODULE VERSIONS
//*
//* REPLACE:
//* User.Loadlib
Mainframe Tasks
//* - WITH THE NAME OF THE LOADLIB CREATED

//* DURING THE INSTALLATION OF THE DLM UTILITIES
//*
//* REPORT FORMATING STMTS
//* - SPECIFY PARM='WTO' to instruct DLMVER to issue WTOs instead
//* of writting to DLMLOG file.
//*
//*72cumentation
//* NOTE: If no STEPLIB but JOBLIB is present,
//* DLMVER will print DLm Module versions from JOBLIB.
//* If no STEPLIB or JOBLIB is present,
//* DLMVER will print DLm Module versions from library
//* in linklist that DLMVER was loaded from.
//*
//****************************************************************
******
//* DLM V2.0 - January, 2012
//****************************************************************
******
//*
//* EXECUTE THE DLMVER PROGRAM TO PRINT DLM MODULE VERSIONS
//*
//DLMVER EXEC PGM=DLMVER
//STEPLIB DD DSN=User.Loadlib,DISP=SHR
//DLMLOG DD SYSOUT=*
This JCL example will invoke the DLMVER utility to report on the DLm versions for the
DLm load modules stored in the User.Loadlib. You can modify the STEPLIB to point to
the installed DLm load library.
◆ DLMVER sample JCL 2
//S1 EXEC PGM=DLMVER,PARM='WTO'
Note: DLMVER will report on the DLm load modules present in any active LINKLST
regardless of whether a STEPLIB or JOBLIB is present in the JCL.
Sample output from DLMVER

DLMVER VER 1.00 PARM
DLV010I UTILITY VERSIONS (Z/OS R12 ):
DLMCMD V 4.06
DLMLIB V 4.03
DLMSCR V 4.19
DLMVER V 1.00
GENSTATS V 1.15

Mainframe Tasks
DLMVER Messages
The messages related to DLMVER are:
◆ DLV010I UTILITY VERSIONS ( ):
◆ DLV050I LOG FILE FAILED TO OPEN
“DLMVER messages” on page 375 provides the details.
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.
Initial program load from a DLm virtual tape 139

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 considerations 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.

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

◆ z/OS Console operation ................................................................................. 142
◆ DLMHOST....................................................................................................... 142
◆ Using z/OS Console support........................................................................... 145
z/OS Console Support 141

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 124 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.
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.
DLMHOST 143
◆ 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.
◆ EZSM — - EZSM- Causes z/OS Console messages that are replicated from the DLm
to be prefixed with 'DLM' followed by a severity character, ('E' for error, 'W' for
warning, and 'I' for informational messages). This parameter allows for an
installation to use EzSM DLm Message Alerts that have wildcards for DLME,
DLMW, and DLMI for handling these types of messages.
EMC provides sample JCL to run DLMHOST. “Locate and upload the DLm utilities and
JCL for z/OS” on page 124 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.
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.
Using z/OS Console support 145

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
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:
DLM2401 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.
Using z/OS Console support 147

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
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

APPENDIX A
Virtual Tape Operator Command Reference
This appendix contains the Virtual Tape Operator command reference:

◆ Virtual Tape Operator command reference ...................................................... 150
Virtual Tape Operator Command Reference 149

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.
CLOSE VSTATS PATH

CLOSE VSTATS PATH=xxx
This command closes the vstats file in the path specified to allow a mount point to be
unmounted.
For example:
close vstats path=/tapelib/BT
EXPORT
EXPORT from to [NORUN] [COMPRESS] [KEYCLASS=key_class]
where from is the full path of the tape volume (VOLSER) to be copied and to is the
device name of 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 the VTE not to unload the tape when the export is complete.
◆ compress indicates whether the VTE 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, the VTE
decompresses the data before writing it to the physical tape. Then, if the
compress option is specified, the VTE 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. The VTE copies the encrypted volume as is to the physical tape.
◆ KEYCLASS=key_class- this option tells Virtuent whether or not the data should be
encrypted before it is written to tape. The encryption key class specified must be
defined in the RSA Key Manager.
When the KEYCLASS option specifies a valid encryption key class Virtuent call the
RSA Key Manager in order to get an encryption key and will then encrypt the data
before sending it to the tape drive. If the compress option is also specified,
Virtuent will compress the data before encrypting it and the drive will not be
asked to do compression. If the data in the disk file is already encrypted, Virtuent
will copy the existing encrypted data from the disk to the tape as is. The export
utility will not deencrypt data which is already encrypted on the tape library. In
this case, it is not necessary to specify the encryption key class on the export
command. Tape volumes written by Virtuent using the EXPORT command which
are encrypted (either during the EXPORT or were already encrypted on disk) can
only be processed by the Virtuent IMPORT command or Direct Tape. They cannot
be processed without using a Virtuent controller.
Virtual Tape Operator command reference 151

Tape volumes written to an IBM 3592 drive by EXPORT which are not encrypted are
compatible with other 3592 drives and can be processed by systems other than
Virtuent. For example, a compressed volume written by EXPORT to an IBM 3592
drive could be mounted on a mainframe channel attached 3592 drive and read
directly by a mainframe application.
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.
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|CLASS = CLASSn]
[KEYCLASS=key_class]
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/N1/N10000
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 the VTE should compress the tape volume when it is
written to the drive. The VTE 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, the VTE instructs the tape drive to
compress the data before writing it to the media. If you do not include this option,
the VTE stores the uncompressed volume in the library.
◆ CLASS=n provides storage class in which DLm must store the imported volume in
the library. The default is 0. If CLASS=n is not specified, the to field should
contain the complete library name of the tape volume (VOLSER) being imported.
◆ KEYCLASS=key_class - tells Virtuent whether or not to encrypt the data as it is
writing it to the library. The encryption key class you specify must be a valid key
class in the RSA Key Manager. The default is no encryption indicating Virtuent will
not do encryption as it is writing the data to the library. If the volume was
previously encrypted by Virtuent then the volume is imported as is onto the tape
library. The Virtuent IMPORT command does not decrypt data. Virtuent encrypted
tape volumes can only be decrypted by being mounted and read from the
mainframe.
INITIALIZE
INITIALIZE VOL=volser DEVICE=devname [COUNT=count] [CLASS=n] [DIR=dirname]
[LABEL=S/A/N] [SCRATCH=Y/N] [EPIC=N/Y] [ERRORS=nnnnn]

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.
◆ Unless ERRORS=nnnnn is specified, initializations terminate after encountering
five errors (such as volser already exists). If ERRORS=nnnnn is specified, up to
<nnnnn> errors are tolerated and initializations continue until <nnnnn> have
occurred.
◆ 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
/tapelibwhen using EFS:
INIT VOL=B00000 DEVICE=E980 COUNT=100 CLASS=0
◆ 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.CLASS is a required parameter when using Enhanced File System (EFS), and
is not valid when EFS is not being used. Unless DIR= is also specified, the new
tapes will be spread across all subdirectories of the specified 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, INITIALIZE will spread the new tapes across all subdirectories of the
specified CLASS. During operation, the VTE 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. Specify only the subdirectory name; the base
tape library directory is derived from the PATH= parameter. For example, if the
tape library is /tapelib, specifying DIR=L2 would initialize the tape(s) in
/tapelib/L2. Note: this parameter is only allowed when the Enhanced File
System (EFS) architecture option is enabled.
◆ 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. The VTE
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 [[DEV=]devicename[+]] | ALL | COMPRESSION | CONFIG | ENCRYPTION | LABELS
|LOCKS | MOUNTED | PATHS [ASSIGNED] | SPACE | SCRATCHNAMES | STCLASS | TAPELIB
| VERSION| WARNING | RECOVER | RECOVERAMT]
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 VTE's AHA compression adapters.
◆ QUERY CONFIG shows detailed configuration information for all devices.
◆ QUERY ENCRYPTION shows the status of the encryption keys.
◆ QUERY LABELS shows the header labels, if any, for all mounted tapes.
◆ QUERY LOCKS displays two kinds of VOLSER locks currently set: VOLSER short
term locks set by EFS (Enhanced File System) when searching for or moving files
between filesystems. DD locks for Virtuent VOLSER locking used for NFS
filesystems that don't support NFS NLM file locking.

◆ 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 TAPELIB displays some information about all the tape libraries, such as
high and low water marks, highest usage details and the current penalty value
that affects scratch tape allocation load balancing.
◆ QUERY VERSION displays version information.
◆ QUERY WARNING, RECOVER, or RECOVERAMT are effectively the same, and display
the space usage warning percent, space recovery percent, space recover amount,
recovery update time, and erase policy TTL time.
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.
If a mount previously failed, the most recently requested VOLSER and the reason for
the mount failure are displayed.
QUERY ALL sample output

QUERY ALL sample output
Version 7.03-9768, build 0, built May 24 2012 13:12:16
Licensed Features Enabled:
SCSI Tape Support
Data Exchange (Flat File) Support
Encryption Support
Import-Export Support
EMC DLm Support
EMC Encryption Support
AMDD Support
AMDD Support for EMC
Program started at Wed Jun 13 10:55:53 2012
DLm056I: Channel driver version is 4.4.11,
DLm075I: Interface #0: 197888 (0x030500) bus:5 slot:0 type:15 (PEFA-LP) media:3
(FiCon)
DLm076I: Interface #0: hardware s/n: 000D09137204
DLm077I: Interface #0: Firmware emulation type: TRANS, version: 1245 2012/05/17
DLm070I: Interface #0: TRANSX emulation version set to 3
DLm081I: Interface #0: Current state: running; Desired state: running; Media Down,
Loop Down
DLm075I: Interface #1: 198144 (0x030600) bus:6 slot:0 type:15 (PEFA-LP) media:3
(FiCon)
DLm076I: Interface #1: hardware s/n: 000D09117152
DLm077I: Interface #1: Firmware emulation type: TRANS, version: 1245 2012/05/17
DLm070I: Interface #1: TRANSX emulation version set to 3
DLm081I: Interface #1: Current state: running; Desired state: running; Media Up, Loop
Up
DLm790I: ST driver version: 1.45
DLm841I: System tracelevel is currently set to 1
DLm842I: System debuglevel is currently set to 0
DLm096I: Erase Policy: retain for 1 day (configured this way)
DLm097I: Maximum continuous erase time set to 30 seconds
DLm078I: Disk usage WARNING level set to 88%
DLm079I: Disk space RECOVER level is N/A
DLm084I: Disk space RECOVERAMT set to 5%
DLm120I: Disk RECOVERYUPDATE set to 24 hours
DLm127I: Disk space ERASEPOLICYTTL set to 1D (config)
DLm851I: ProtectVOL1 set ON
DLm099I: New mount on already-mounted drive will be allowed
DLm069I: Resetting Events will not be sent to firmware
DLm112I: Using NEW standard scratch search method
DLm114I: Using DEFAULT method of filesystem allocation
DLm109I: Scratch mounts will ignore full filesystems (UseFullFS=FALSE)

DLm083I: Compression level set to 1 (0=none,1=faster,9=smaller)

DLm010I: Compression hardware available
DLm011I: Compression driver version: 1.1.8
DLm012I: Compression card #0: id=0x193F0363 (AHA363) version=0x120 state=00000000
DLm013I: Hardware compression set ON
DLm013I: Hardware decompression set ON
DLm873I: Attention set to PATHGROUP
DLm871I: AttentionCount set to 45
DLm067I: BusyType set to Busy
DLm853I: Pending Mount Fairness (PMFAIR) set to 0
DLm892I: Write Sync set to 1G
DLm257I: The Maximum Find Volume Display Count is: 1000
DLm687I: Enhanced FS move volume method is: Random
DLm688I: Enhanced FS move for volumes in FLR tape libraries: Disabled
DLm688I: Enhanced FS move for volumes in GR tape libraries: Disabled
DLm256I: Volser Lock Directory set to: /tapelib/.LOCK/
DLm957I: Locking with NLM lock manager turned ON
DLm111I: Maximum tape block size set to 512000
DLm840I: Read-back write verification (non Data Domain) set to DATA
DLm840I: Read-back write verification (Data Domain) set to OFF
DLm116I: Query Space timeout set to 40 minutes
Devicename VOLSER/L
---------- --------
0502 NR-UA
6C00 NR-UA
6C01 NR-UA
6C02 NR-UA
6C03 NR-UA
6C04 NR-UA
6C05 NR-UA
6C06 NR-UA
6C07 NR-UA
6C08 NR-UA
6C09 NR-UA
6C0A NR-UA
6C0B NR-UA
6C0C NR-UA
6C0D NR-UA
6C0E NR-UA
6C0F NR-UA
QUERY COMPRESSION sample output

DLm083I: Compression level set to 1 (0=none,1=faster,9=smaller)
DLm010I: Compression hardware available
DLm011I: Compression driver version: 1.1.8
DLm012I: Compression card #0: id=0x193F0363 (AHA363) version=0x120 state=00000000
DLm013I: Hardware compression set ON
DLm013I: Hardware decompression set ON

QUERY CONFIG sample output

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

DLm409I: Command received: 'query labels'
1D00 S VOL1JJ0031
TCSBT
HDR1LL6.DEMO.BACKUP02JJ003100010001 0101520000000000000IBM OS/VS 370
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

DLm409I: Command received: 'query mounted'
Devicename VOLSER/L
---------- --------
1D00 JJ0031 S R-A2 aws/rw block 2514 (writing 135.6M)
QUERY PATHS sample output

Device Interface/Path# Port LPAR CU Device PathGroup ID
1D00 0 0 0000 6 00 00 0000000000000000000000
0 1 0000 7 00 00 0000000000000000000000
1 0 0000 6 00 00 0000000000000000000000
1 1 0000 7 00 00 0000000000000000000000
1D01 0 0 0000 6 00 01 0000000000000000000000

0 1 0000 7 00 01 0000000000000000000000
1 0 0000 6 00 01 0000000000000000000000
1 1 0000 7 00 01 0000000000000000000000
1D02 0 0 0000 6 00 02 0000000000000000000000
0 1 0000 7 00 02 0000000000000000000000
1 0 0000 6 00 02 0000000000000000000000
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.
QUERY SCRATCHNAMES sample output

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 TAPELIB sample output

/tapelib/T2 (dev 11)
Warn/Warned 75% / 0% checked 01/30/2011 21:52:52to 01/30/2011 21:52:52
Recover/Recovered 95% / 0% recovered never to never
Highest Usage 29% at 01/30/2011 20:16:35
Current Penalty 0%
Last Picked Time at 12/31/1969 19:00:00.000000
QUERY VERSION sample output

Version 7.03, build 9725, built Apr 12 2012 17:00:33
Licensed Features Enabled:
SCSI Tape Support
Data Exchange (Flat File) Support
Import-Export Support
EMC DLm Support
AMDD Support for EMC
Program started at Fri May 21 17:51:31 2010
QUIESCE
QUIESCE [ [DEVICE=]devicename | ALL | * ] [TAPELIB PATH=path]
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.
QUIESCE TAPELIB PATH=path
Quiesced tape library directories will be bypassed when searching for or mounting a
virtual tape. In addition, a quiesced directory will not be checked for free space or
have space recovery performed on it. Any tape already in use in a quiesced directory
will continue to be accessed normally until it is unloaded. Usage of the directory will
return to normal once it is UNQUIESCE'd using the UNQUIESCE TAPELIB command.
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 VTE runs out of disk space in the tape library while writing to a virtual volume.
or
◆ The UNREADY command was entered.
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 172.
The VTE 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][KEYCLASS=key_class|NONE] [EFSMOVE=SPACE/RANDOM/NEVER]
[QSPACETIMEOUT=nn] [PROTECTVOL1=ON/OFF] [ ERASEPOLICYTTL=[nnn / nnnH /
nnnD / OFF] [DEVICE=devicename|ALL]
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.
◆ EFSMOVE=SPACE/RANDOM/NEVER indicates whether files will be moved based
on free space, randomly or never

◆ QSPACETIMEOUT=nn Sets the number of minutes that QUERY SPACE can run
before it is automatically cancelled.
◆ KEYCLASS=[key_class|NONE] sets the encryption key class for the specified
device to the key class name, or to no key class (and thus no encryption). This
option requires a specific DEVICE parameter, and the specified device must not
have a tape mounted for the command to be accepted.
Note: This option is only effective for the first data set on a tape, subsequent data
sets will use the encryption key (if any) of the first data set.
◆ PROTECTVOL1=ON/OFF is a feature that prevents accidental overwriting of a VOL1

label. Any attempt to overwrite a VOL1 label with data or a tapemark, once data
has been written elsewhere on the tape, will be blocked with a write-protect error,
with message DLm920E displayed. Message DLm921I will also be displayed
each time, as a reminder that the feature can be turned off if required. This
feature is on by default.
◆ 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 . 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 can also be used to assign 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
drive serial number. For example,
SET PATH=DRIVE-nnnnnnnnnnnn DEV=xxxx
Where nnnnnnnnnnnn is the 12 digit tape drive serial number and XXXX is the
name of the device that is being set to access the tape drive.
◆ 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 VTE starts to recover
disk space by deleting the data from scratch volumes. Valid values are from 0 to
100.
Note: If the recovery percentage is set to 100, the 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 VTE attempts to recover once the recovery threshold is reached.
◆ SIZE=xxx sets the maximum volume size for virtual tape volumes. The valid range
is 2 MB (2 megabytes) to 32 TB (32 terabytes). The maximum allowable tape size
for all drives is 32 TB but is limited to the amount of available storage in the
filesystem. Since the maximum filesystem size in a VTE is 16 TB, a tape volume
cannot be more than 16 TB. 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, VTE 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.
Note: The SET TIMESTAMPS command works only when entered directly through
the VT Console. It does not work when sent through the DLMHOST or when used
with CP501.
◆ 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.
◆ WARNING=nnn sets the percentage of disk space usage at which the VTE begins
to warn about usage. The valid range is 0 to 100.
◆ ERASEPOLICYTTL=[nnn / nnnH / nnnD / OFF] sets the Erase Policy TTL value to OFF
or sets the Erase Policy TTL to a value in days (default) or hours.
Examples:
• The SET ERASEPOLICYTTL=10D command results in setting the TTL
ERASEPOLICY to 10 days. After the command is executed, a message
"DLm127I "Disk space ERASEPOLICYTTL set to Value" is generated.
• The SET ERASEPOLICYTTL=OFF results in the TTL ERASEPOLICY being turned
off. After the command is executed, a message "DLm127I "Disk space
ERASEPOLICYTTL set to OFF" is generated.
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 SHOW STATUS
This command shows the current SNMP settings.
SNMP ACKNOWLEDGE FAILURE
Enter this command following the error indicating that message(s) were lost to
acknowledge that the user is aware of the lost message(s). This command also stops
the periodic warnings generated as a result of the error.
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.
Note: This command is not available from the mainframe.
Note: The STARTVT command works only when entered directly through the VT
Console. It does not work when sent through the DLMHOST or when used with CP501.
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.
Note: This command is not available from the mainframe.
Note: The STOPVT and STOPVT! commands work only when entered directly through
the VT Console. They do not work when sent through the DLMHOST or when used with
CP501.
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 172.
The UNLOAD command is executed immediately regardless of whether the host might
currently be using the tape.
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.
UNQUIESCE TAPELIB PATH=path

The UNQUIESCETAPELIB PATH command takes a tape library directory out of the
quiesced state. After being unquiesced, the tapelib path once again accept mount
requests. Any mount request that was ignored while a tapelib path is quiesced
remains in a pending state; it is automatically retried when the tapelib path is
unquiesced. Unquiescing a tape library directory does not send any signal to the host.
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 whether the host
might currently be using the tape.
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.

APPENDIX B
AWSTAPE Information
This appendix provides information on AWSTAPE:

◆ AWSTAPE format............................................................................................. 174
AWSTAPE Information 173

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 174 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.

APPENDIX 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 .................................................................................. 176
◆ Load display data........................................................................................... 178
Load Display Command—CCW Opcode x'9F' 175

Load display messages

IBM-compatible 3480/3490/3590E tape drives support a Load Display command
(CCW Opcode 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 176 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 177

Load display data

Table 10 on page 178 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 178 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 179

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.

APPENDIX 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 ......................................................................................... 182
◆ Extraction utility ............................................................................................. 182
Extract DLm statistics 181

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 mounts 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]] [--mounts] [--unmount] infile [--startDate]
[--endDate]
Only one of the --hourly (with or without --minutes),

--mounts, 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.
Usage:
statfmt [--help] [select options] [limit options] infile
select options
[--hourly] [--minutes] [--mount] [--unmount] [--smf] [--drl] [--txt]
[--mountedAt=MM/DD/YYYY:HH:MM:SS] [--volume=VOLSER] [--efs] [--restarts]
limit options
[--volume=VOLSER] [--startDate=MM/DD/YYYY:HH:MM] [--endDate=MM/DD/YYYY:HH:MM]
[--startDate=MM/DD/YYYY] [--endDate=MM/DD/YYYY]
--mount extracts volume mount statistics. One row is output

for each virtual tape mount.
--unmount extracts volume unmount statistics. One row is output
for each virtual tape unmount.
--smf extracts volume mount and unmount statistics. One row is output
for each virtual tape mount or unmount.
--drl extracts volume mount and unmount statistics from DRlogging files.

One row is output for each virtual tape mount or unmount.

--txt extracts volume mount and unmount statistics from logging files.
One row is output for each virtual tape mount or unmount in a straight
text format.
--mountedAt extracts volumes that were mounted but not unmounted prior to
the specified date:time. An optional startDate may be used to limit
the mounted timeframe.
--efs extracts volume removed and added statistics.
One row of text is output for each volume added or removed event.
--restarts prints timestamp of application restarts.
--hourly extracts hourly statistics. One row is output for each
hour in which there was read or write activity.
--minutes extracts statistics broken down by the minute.
If --minutes is specified without the --hourly parameter,
a row is output for each minute of an hour in which there was
read or write activity.
If --minutes is specified along with the --hourly parameter,
one row is output for each hour in which there was read or
write activity, with fields for every minute of the hour.
--startDate extracts only data equal to or later than the date provided.
--endDate extracts only data prior to or equal to the date provided.
--volume extracts only data relating to the VOLSER provided. This option
can be used with the [--mount] or [--unmount] as a limitor or by itself
to display all available information about the volume. Wildcards are
allowed for this field.
infile is a statistics file; for hourly/minutes stats,
specify an hourly stats file (i.e. /var/bti/stats/hourly);
for mount/unmount stats, specify a volumes stats file
(i.e. /var/bti/stats/vstats).
The formatted output goes to stdout; redirect or pipe it if desired.
Exactly one of the [select options] options must be specified
None or any combination of the [limit options] may be specified
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.
Extraction utility 183

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 --mounts or --unmount parameter. In
either of these cases, the infile parameter must be a DLm volume statistics file, that
is, /var/bti/stats/vstats.

Mount statistics
If the --mounts parameter is specified, the following comma-delimited fields are
output for each virtual tape mounts 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 successful mounts, this will be zero; for unsuccessful mounts, that will be
non-zero.
Scratch — For scratch mounts, 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 mounts, 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 7.03-9725.
Copyright (c) 2012
input file is '/var/bti/stats/hourly'
Date,Hour,Mounts,Drives,BlocksRead,Blockswritten,-
BytesRead,BytesWritten
09/21/2012,14,4,1,-1,-1,968,0
09/21/2012,16,7,2,-1,-1,6198537240,1102968477
09/21/2012,17,4,2,-1,-1,7585128104,1100001400
09/22/2012,15,1,1,-1,-1,0,0
09/23/2012,21,3,3,-1,-1,1000480,1000400
09/23/2012,22,4,4,69,68,1000480,1000400
Example 2
# statfmt --hourly --minutes /var/bti/stats/hourly

Copyright (c) 2012

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/2012,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/2012,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/2012,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/2012,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/2012,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/2012,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 --mounts /var/bti/stats/vstats
Copyright (c) 2012
input file is '/var/bti/stats/vstats'
Date,Device,Volser,Error,Scratch,Created,Protected,Howlong,Filesize,
pending Mounts,volumes Mounted
04/16/2012,11:41:13,,,0,0,0,0,37748736,345745915904,0,0
04/16/2012,11:41:13,,,0,0,0,0,37748736,345745915904,0,0
04/16/2012,12:08:22,,,0,0,0,0,37748736,345745915904,0,0
Example 4
# statfmt --unmount /var/bti/stats/vstats
Copyright (c) 2012 .
input file is '/var/bti/stats/vstats'
Date,Time,Volser,BlocksRead,BytesRead,Blockswritten,-
BytesWritten,LowWrite,Filesize,GoodLocates,BadLocates
04/21/2012,14:16:30,N47061,3,240,0,0,-1,-1,0,0
04/21/2012,14:19:05,N47061,4,248,0,0,-1,-1,0,0
04/21/2012,14:20:51,N47061,5,256,0,0,-1,-1,0,0

04/21/2012,14:40:07,N47061,3,240,0,0,-1,-1,0,0
04/21/2012,14:43:43,N47061,3,240,0,0,-1,-1,0,0
04/21/2012,14:44:31,N47061,3,240,0,0,-1,-1,0,0
04/21/2012,14:52:11,N47061,4,248,0,0,-1,-1,0,0
04/21/2012,16:27:01,N47062,2,160,6,533,0,593,0,0
04/21/2012,16:40:10,N47064,2,160,10,82320,0,7880,0,0
04/21/2012,16:42:36,N47064,5,400,7,82080,7690,15329,0,0
04/21/2012,16:42:41,N47064,5,400,59,934048,15139,38466,0,0
04/21/2012,16:44:26,N47064,5,400,59,934048,38276,61593,0,0
04/21/2012,16:44:30,N47064,5,400,59,934048,61403,84786,0,0
04/21/2012,17:04:03,N47063,231018,7391304720,34381,-
1100001400,0,1100207710,0,0
04/21/2012,17:06:31,N47061,4,248,0,0,-1,-1,0,0
04/21/2012,17:08:24,N47061,4,248,0,0,-1,-1,0,0
04/21/2012,17:11:17,N47061,4,248,0,0,-1,-1,0,0
04/21/2012,17:33:22,N47065,237081,7585127360,34381,-
1100001400,0,1100207710,0,0
04/21/2012,15:33:30,N47061,0,0,0,0,-1,-1,0,0
04/21/2012,21:09:43,N47068,69,1000480,68,1000400,0,85185,0,0
04/21/2012,22:28:23,N47066,0,0,0,0,-1,-1,0,0
04/21/2012,22:28:24,N47067,0,0,0,0,-1,-1,0,0
04/21/2012,22:53:37,N47072,69,1000480,68,1000400,0,85185,0,0
04/21/2012,12:08:18,N47071,0,0,0,0,-1,-1,0,0
04/21/2012,12:08:18,N47069,0,0,0,0,-1,-1,0,0
04/21/2012,12:08:18,N47070,0,0,0,0,-1,-1,0,0


APPENDIX E
System Messages
This appendix lists the DLm system, EMCvts, and z/OS system messages. The major
topics are:
◆ Message format ............................................................................................. 192
◆ DLm system messages ................................................................................... 193
◆ Call home messages ...................................................................................... 363
◆ EMCvts messages .......................................................................................... 364
◆ z/OS system messages .................................................................................. 366
◆ VTEC errors that generate ConnectEMC events ................................................ 380
System Messages 191

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 virtual tape
application's debugging level is set to 1 or higher.
System Action: None.
User Action: You really shouldn't 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 Support. Enter the command 'SET DEBUG=0' to turn
debugging off.
DLm010I
Compression hardware [not] available
Description: This message reports on the availability of a hardware compression card
in the controller.
System Action: If a hardware compression card is present (and is not disabled through
configuration or operator command), the card will be used for compressing and
decompressing virtual tape data.
User Action: None.
DLm011I
Compression driver version: x.x.x
Description: This message displays the version number of the hardware compression
card driver.
User Action: None.
DLm012I
Compression card #n: id=xx (model) version=nnn state=xxxxxxxx
DLm system messages 193

System Messages
Description: This message displays information about the hardware compression

card(s) installed in the controller.
User Action: None.
DLm013I
Hardware compression/decompression set ON/OFF
Description: This message reports on the status of the 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 Support for assistance.
DLm015E
Hardware compression driver error
Description: An error has occurred while initializing the hardware compression
adapter.
System Action: Hardware compression and decompression will not be available until
the problem is resolved and the controller is restarted.
DLm016E
Device <devicename> Error opening hardware compression driver: <error message>
Description: An error has occurred while opening the hardware compression adapter.
System Action: Hardware compression and decompression will not be available for
this device until the problem is resolved and the controller is restarted.

System Messages
DLm017I
Removing all .lk file locks owned by this system...
Description: During startup and shutdown, all file locks held by this application, if
any, are removed.
System Action: All .lk file locks owned by this system are removed.
User Action: None.
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.
System Action: Depending on the error, the controller may abend or may need to be
restarted to regain some functionality.
DLm020E
Cannot verify <feature> license: <error message>
Description: The controller was unable to validate the license for the specified feature.
System Action: The specified feature will not be available.
DLm021E
<parameter=value> incompatible with <license> license
Description: The specified parameter is not compatible with the specified licensed
feature.

System Messages
System Action: If the error is in the configuration file, the application startup
terminates. If the error is in a SET command the command is rejected.
User Action: Contact EMC Support for additional assistance.
DLm022E
Unable to find userid 'vtape'
Description: The virtual tape application must run under the user ID 'vtape', but this
user ID does not exist on the system.
DLm023E
Unable to switch to user and group 'vtape'
Description: The virtual tape 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 virtual tape application must be started under the userid 'root'.
DLm025E
Invalid license combination, <license1>+<license2>.
Description: The combination of license files on the system is not valid.
DLm026E
Pid file <filename> must be full path name. Use -? for Help

System Messages
Description: The command line that starts the virtual tape application contains an
invalid argument.
DLm027E
Failed to fork daemon: <error message>
Description: The application failed to daemonize itself.
DLm028E
Internal Error calling setsid: <error message>
DLm029E
Internal Error changing working directory to '/': <error message>
DLm030I
Traces are [un]buffered
Description: The virtual tape 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 application starts,
trace files are written in an unbuffered manner (every event is written to disk
immediately).

System Messages
User Action: The buffered default should be sufficient for most tracing needs, unless
directed otherwise by EMC Support. When traces are buffered be sure to enter the
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 create the process ID file.
DLm032E
Trace task error reading pipe, errno=0x<xx> (<nnn>)
Description: An I/O error has occurred during device tracing.
System Action: The application attempts to continue tracing. One or more events may
be lost from the device trace.
DLm033E
Error writing to <file type> file <filename>: <error message>
Description: An I/O error occurred while writing to the specified file.
System Action: The application continues running without writing additional
messages to the specified file.
User Action: Refer to any earlier message(s) and the 'error message' portion of this
message to determine the cause of the failure. If the problem cannot be corrected,
contact EMC Support for assistance.
DLm034I
<STDOUT/STDERR message>
Description: A message was received from Standard OUT or Standard ERROR.
User Action: None.

System Messages
DLm035E
Error creating directory 'directory': <error message>
Description: The specified directory did not exist, and the virtual tape 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:
User Action: If you are unable to correct the problem, contact EMC Support for
assistance.
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: Startup terminates or continues without the specified feature. The
'error message' text explains the reason for the failure.
assistance.
DLm038I
Creating directory 'directory'
Description: The specified directory did not exist, so the application is now creating
the directory.
System Action: The specified directory is created.
User Action: None.

System Messages
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: Startup terminates. The 'error message' text explains the reason for
the failure.
assistance.
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.
System Action: Startup terminates.
User Action: Verify in the configuration file that the channel configuration data for the
specified device is correct. If the problem recurs, contact EMC 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 will be 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 Support for more assistance.
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 effect 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.

System Messages
User Action: Contact EMC 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 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 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.
DLm048E
Internal Error <process>: <error message>
Description: An internal error has occurred.
System Action: Application terminates.

System Messages
DLm049E
Internal Error <function>: <error message>
Description: An internal error has occurred due to external conditions.
System Action: The function listed cannot be completed.
DLm050E
Invalid command line parameter: <value>. use -? for help
invalid argument.
User Action: Correct the command line argument(s) and restart the virtual tape
application.
DLm052E
Invalid command line Configuration File Name parameter: <value>. Use -? for Help
invalid argument.
User Action: Correct the command line argument(s) and restart the virtual tape
application.
DLm055E
Error getting channel driver version number
Description: The virtual tape application was unable to determine the version of the
channel adapter driver.
DLm056I
Channel driver version is x.x.x
Description: This message displays the version number of the channel adapter driver.

System Messages

User Action: None.
DLm057E
This application requires minimum channel driver version x.x.x!
Description: The channel adapter driver is below the minimum release level required
by this version of the virtual tape 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 Interrupt Handler) timeout value that the virtual tape
application 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, the application 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 virtual tape application is currently running.
System Action: The second copy of the virtual tape 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>

System Messages
DLm062E
Error opening Alert FIFO <filename>: <error message>
Description: The virtual tape 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 virtual tape application continues to function, but channel
adapter alerts will not be noted by the application.
DLm064E
Alert FIFO has been closed
Description: The channel driver has closed the pipe over which it sends alert
messages, which are warning and error messages about channel adapter problems,
to the virtual tape application.
System Action: The application continues to function, but channel adapter alerts will
not be noted by the application.
DLm065E
Invalid data (nn bytes) read from Alert FIFO
Description: The channel driver has sent an unrecognized alert message to the virtual
tape application.
System Action: The application continues to function, but channel adapter alerts will
not be noted by the application.
DLm066E
Error creating/opening Read named pipe <filename>: <error message>

System Messages

DLm067I
BusyType set to Busy/Immediate/Deferred
Description: The virtual tape application 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: The virtual tape application 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
Support. Changing this value could cause channel errors.
DLm068I
Double testing of compressed data set ON/OFF
Description: By default, the virtual tape 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 channel-attached device's
pathgroup ID or assignment, such as a physical removal of paths or a system reset or
restarting of the virtual tape 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 re-issue the
unit-checked command. In addition, some channels expect a low-level indication that
a resetting event has occurred. By default, the virtual tape application sends this
special indication to the channel along with the unit check. For exceptional
conditions, the application can be configured to NOT send the low-level resetting

System Messages
event indication to the channel when it sends a resetting event unit check to the Host.
This message is displayed at virtual tape application startup and whenever the
low-level channel resetting event notification option is switched on or off.
System Action: Low-level channel resetting event status will not be sent to the
channel when this option is set OFF.
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 Support before configuring this option off. Also
see message DLm082I.
DLm070I
<emulation type> emulation version set to n
Description: The virtual tape application 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 nnnn!
Description: The firmware in a channel adapter is below the minimum release level
required by this version of the virtual tape application. Message DLm075I that
precedes this message identifies the channel adapter in question.

System Messages
DLm073E
Interface #<n> (slot <nnnnnn>) returned bad status = <nnn>
Description: The specified channel interface adapter returned an error status to the
virtual tape application. This error can only occur during startup.
DLm074E
Interface #<n> (slot <nnnnnn>) error getting <adapter info>
Description: The specified channel interface adapter returned an error status to the
virtual tape application. This error can only occur during startup.
DLm075I
Interface #n: n (0xxxxxx) bus:n slot:n type:n (adaptertype) media:n (mediatype)
Description: This message displays information about the channel interface
adapter(s) in the controller. This message is displayed at 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
User Action: None.
DLm077I
Interface #n: Firmware emulation type: XXXX, version: nnnn yyyy/mm/dd

System Messages

User Action: None.
DLm078I
Disk usage WARNING level set to nn%
Description: The virtual tape application is configured to warn about tape library disk
utilization when usage reaches nn% full.
User Action: None.
DLm079I
Disk space RECOVER level [set to nn%]/[is N/A]
Description: The virtual tape application is configured to start erasing scratch tape
volumes to recover disk space when disk utilization reaches nn% 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 virtual tape application has detected that the specified virtual device
is attached to a Unisys Host. This message will be displayed once for each virtual
device attached to a Unisys.
System Action: The application will automatically make 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
Support should be contacted for assistance).

System Messages
DLm081I
Interface #n: Current state <state>; Desired state <state>
User Action: None.
DLm082I
Resetting Events will [not] be ignored
Description: A resetting event is any event that resets a channel-attached device's
pathgroup ID or assignment, such as a physical removal of paths or a system reset or
restarting of the virtual tape 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 re-issue 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
controller 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 will not be sent to the Host when this
option is set.
User Action: None. Under normal conditions, the controller 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 Support for more information.
DLm083I
Compression level set to n (0=none,1=faster,9=smaller)
Description: This message 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).

System Messages
User Action: None.
DLm084I
Disk space RECOVERAMT amount set to nn%
Description: The virtual tape application is configured to stop erasing scratch tape
volumes to recover disk space when disk usage has been reduced by RECOVERAMT
percent of space.
User Action: None.
DLm085I
<feature> support enabled
Description: This message displays if support for an optional feature is enabled in the
configuration file.
System Action: The optional feature is enabled.
User Action: None.
DLm086I
<WORM-filesystem-type> default retention: nn Days/Months/Years
Description: This message displays if there is a WORM filesystem default retention
period set in the configuration file.
User Action: None.
DLm087I
Checking of CRCs from channel set ON|OFF
DLm088I
Sending of CRCs to channel set ON|OFF

System Messages
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 virtual tape application will adjust for the differences between an
IBM and a Unisys Host for the specified device(s).
User Action: None (unless the Host is not actually a Unisys Host, in which case you
shouldn't have done 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 is <nnnn> (0xXX) (SET this way/configured this way/by default)
Description: The AMDD pad boundary has been set to the designated value.
User Action: None.
DLm092E
SET AMDD cannot specify a specific device
Description: For EMC DLm and MDL-1000DD/2000DD models only, AMDD is a global
setting and cannot be SET by individual device.
System Action: The SET command is ignored.
User Action: None.
DLm093I
AMDD support for <application-type> is ON/OFF
Description: This node is configured to perform AMDD processing on the specified
data type. This option affects writing of data only; regardless of this setting, reading of
all data types previously written by AMDD is always supported.

System Messages

User Action: None.
DLm094I
AMDD DD marker insertion algorithm: <method>
Description: This node is configured to insert "extra" DD markers into AMDD records
using the specified algorithm. This option applies only to FDR Upstream data being
written to a Data Domain filesystem.
The possible options are:
• STANDARD - No "extra" markers are inserted (default)
• MARKEVERYD - A marker is inserted on every data record
• MARKFILES - A marker is inserted on the first data record of every file
• MARKEVERY8KD - A marker is inserted on every 8K data record
• MARK8K - A marker is inserted at every 8K interval in the file
User Action: None.
DLm095I
AMDD DD <configuration information>
Description: These messages describe configuration parameters that apply
specifically to FDR Upstream data being written to a Data Domain filesystem. The
values which may be displayed include:
• <minimum markable block size is nnnn>This node is configured to insert AMDD
DD markers only on segments of data larger than <nnnn> bytes.
• <maximum marker length is nnnn> This node is configured to write AMDD DD
markers no larger than <nnnn> bytes.
User Action: None.

System Messages
DLm096I
Erase Policy: [retain 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 reaches the RECOVER setting. "retain for..." 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 continuous 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 stop 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 virtual tape application has been explicitly configured to honor a
mount request for a drive that already has a virtual tape volume mounted.

System Messages
System Action: If the virtual tape application 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, the application will unload the tape and honor
the new mount request.
User Action: None. This option is not recommended except in specific circumstances.
Contact EMC Support for more assistance.
DLm100I
Configuration file opened: <filename>
Description: The specified input configuration file was successfully opened.
User Action: None.
DLm101W
Missing or invalid file "/etc/bti/btiximl", using config file "/etc/bti/btixmap0"
Description: The file /etc/bti/btiximl should contain the name of the configuration file
that the virtual tape application will load at startup. If /etc/bti/btiximl does not exist,
the application will load the default configuration file /etc/bti/btixmap0.
System Action: The default configuration file, /etc/bti/btixmap0, is used.
User Action: The /etc/bti/btiximl file should normally point to the desired
configuration file. Reconfigure the system and identify which of the configuration files
you want to use. Contact EMC 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 virtual tape application
startup.
User Action: None.

System Messages
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.
DLm105E
<command> command is no longer supported
Description: The virtual tape application no longer supports this command.
System Action: None, the command is ignored.
User Action: None.
DLm106I
Guaranteed Replication enabled on <nn> devices, checking for any replicating
filesystems...
Description: <nn> virtual tape drives are configured to support the Guaranteed
Replication feature.
System Action: Each of the tape library directories will be checked to see if it is a
replicating filesystem. A subsequent DLm161I message will be displayed for each
tape library found to be on a replicating filesystem.
User Action: None.
DLm107I
Guaranteed Replication delay set to <nn> seconds
Description: The system is configured to wait for <nn> seconds between tape close and
starting a replication-refresh, to make sure that the file is completely written to disk
before replication begins.
User Action: None.

System Messages
DLm108I
Guaranteed Replication timeout set to <nnn> seconds
Description: The system is configured to wait <nnn> seconds for a replication-refresh
to complete. If replication does not complete within this time, an error indication is
returned to the host's WTM command.
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 virtual tape application 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 virtual tape application has been configured to support a maximum
tape block size different from the default of 256K.
System Action: The virtual tape application will support 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
Support.
DLm112I
Using NEW/FAST scratch search method
Description: The virtual tape 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 virtual tape application will use the technique described. The
default method is "NEW".
User Action: None.
DLm113E
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 virtual tape application will use the "NEW" (default) technique.
User Action: Contact EMC Support for more information.
DLm114I
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.

System Messages
DLm115E
Error returned from fsync. fd n. <description> file <filename>: error <error message>
Description: An I/O error occurred while syncing virtual tape data to disk.The 'error
message' text explains the reason for the failure.
System Action: The specified file was not sucessfully fsynced.
User Action: If you are unable to correct the problem contact EMC Support for
assistance.
DLm116I
Query Space timeout set to <nnn> minutes
Description: The system is configured to wait <nnn> minutes for a QUERY SPACE
command to complete. If QUERY SPACE does not complete withinthis time, an error
indication is displayed on the console.
User Action: None.
DLm117I
Query Space <status>
Description: If a QUERY SPACE command is invoked while one is already running, an
'already in progress' status will be displayed. If the QUERY SPACE command exceeds
the QSPACETIMEOUT value, a 'has not completed within the timeout value' status will
be displayed.
User Action: None.
DLm118I
Celerra report interval set to <nn> seconds
Description: The DLm application is configured to check every <nn> seconds for a
Celerra status report written by the Celerra control station. The default is 15 seconds.
User Action: None.

System Messages
DLm119E
Error reading configuration file <filename> line nnn: <error message>
Description: An IO error occurred while reading the specified configuration file.
User Action: Use the configuration program to reconfigure and save the specified
configuration file. If the problem persists, contact EMC Support for assistance.
DLm120I
Disk RECOVERYUPDATE set to <hours>
Description: The Disk Recovery Update time is set to a number of hours in the range of
1 hour to 8760 (365 days) in hours. This is a forced space recovery update based only
on time and not space.
User Action: None.
DLm121E
Cannot open configuration file <filename>: <error message>
Description: The specified configuration file was not successfully opened.
User Action: Use the configuration program to reconfigure and save the specified
configuration file. If the problem persists, contact EMC Support for assistance.
DLm122E
No devices defined in configuration file
Description: There were no virtual tape drives configured in the configuration file.
User Action: Use the configuration program to reconfigure and save the configuration
file. If the problem persists, contact EMC Support for assistance.
DLm123E
Error in config file, line nn: Unrecognized keyword '<keyword>'
Description: The virtual tape configuration file contained an error.

System Messages

file.
DLm124E
Error in config file, line nn: Incorrect number of <keyword> parameters
file.
DLm125E
Error in config file, line nn: Invalid <keyword> value '<value>'
file.
DLm126E
Maximum number of devices (nnn) exceeded, terminating
Description: Too many devices have been defined in the configuration file.
User Action: Use the configuration program to reconfigure with a valid number of
devices.
DLm127I
ERASEPOLICYTTL set to (nnn)(H/D) (config/default)
Description: Displays the erase Policy TTL Time value in hours or days and the
config/default status.
System Action: None
User Action: None

System Messages
DLm128I
Watchdog timer set to nnn seconds
Description: The watchdog timer value is used to monitor various processes to try to
determine if a process has stalled. This value is configurable with the "SET
WatchDogTimer=nnn" command, or in the configuration file with the "WatchDogTimer
nnn" option.
User Action: None.
DLm129E
Error in config file, line nn: <value> is not a valid parameter
file.
DLm130E
Error in config file, index xx: <value> is not a valid parameter
file.
DLm131E
Error in config file, line nnn: No <keyword> parameter
DLm132E
Error in config file, line nnn: Duplicate <keyword> parameters

System Messages

DLm133E
Error in config file, line nnn: Too many <keyword> parameters
DLm134E
Duplicate INDEX=0xXX in configuration file, line nnn
DLm135E
Error attaching device index xx
DLm136E
Error in config file, line nnn: Duplicate "CELERRA DM=" parameter
Description: The Celerra Data Mover address (DM= parameter) on this CELERRA
configuration statement has already been defined on another Celerra definition.
User Action: Correct the configuration file. For more assistance, contact EMC Support.

System Messages
DLm137W
Invalid TRACE= value 'value'
System Action: Startup continues with the default value of 1.
file.
DLm138E
EFS Short Term Lock Directory <DIR> is not mounted correctly.
Description: An NFS EFS Short Term Lock Directory should use the soft instead of the
hard mount option.
System Action: Scratch tapes will not be moved from their initial directory and space
may no longer even out.
file.
DLm139I
Enhanced Filesystem (EFS) support turned ON/OFF
Description: This message reports the status of the Enhanced Filesystem (ESF)
feature.
User Action: None.
DLm140E
Error in config file, line nnn: <feature> not supported
Description: The virtual tape configuration file contains parameters for a feature that
is not licensed for use by this DLm application.
User Action: Contact EMC Support for more information on enabling the licensed
feature.

System Messages
DLm141E
<feature> feature not supported on DLm8000
Description: The specified feature is not supported on the DLm8000.
System Action: If the feature parameter was specified in the configuration file, startup
terminates. If the feature parameter was specified in a command, the command is
rejected.
feature.
DLm144E
Duplicate NAME=value in configuration file, line nn
file.
DLm148I
Firmware takeover feature enabled/disabled
Description: This message displays the status of the "Adapter Takeover" feature. This
feature is enabled by default. When enabled, the channel adapter firmware takes over
responsibility for certain operations on the channel when the Virtuent application is
slow to respond. When the feature is enabled, operations such as cancelling host jobs
or varying devices offline will result in fewer errors and be successful even if the
Virtuent application cannot respond to the host because of heavy or stalled I/O.
User Action: None. This feature should be left enabled unless directed otherwise by
EMC Support.
DLm150W
Device <devicename> Data path <pathname> not licensed for OCFS2
Description: The specified virtual tape library directory is on a type of filesystem that
is supported only as an optional feature, and the license for that feature is not
installed on this system.

System Messages
System Action: During system startup, this is a warning message and startup
continues. However, no virtual tape volumes that reside in this directory can be
mounted until the optional feature license is installed. If this error occurs when
processing a SET PATH command, the SET PATH command will fail and the current tape
library path is unchanged.
User Action: If the configured directory name is correct, make sure the proper
filesystem is mounted. If support for the optional filesystem type is desired, contact
EMC Support for information about obtaining the optional feature license.
DLm151E
Device <devicename> OCFS2 Feature not licensed, directory 'pathname' ignored
Description: The specified virtual tape library directory is on a type of filesystem that
is supported only as an optional feature, and the license for that feature is not
installed on this system.
System Action: This tape library directory is ignored for all purposes unless the
optional feature license is installed.
User Action: If the configured directory name is correct, make sure the proper
filesystem is mounted. If support for the optional filesystem type is desired, contact
EMC Support for information about obtaining the optional feature license.
DLm155I
Device <devicename> data path='<pathname>' [by default][, volser prefix=<volid>]
Description: The specified pathname will be the base tape library directory for this
device; virtual tape volumes for this device will reside 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> will be automatically created as
needed by the virtual tape application, if they haven't been pre-initialized.
User Action: None.
DLm156W
Device <devicename> Data path <pathname> is not accessible!
Description: The specified virtual tape library directory cannot be accessed.

System Messages
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 will fail and
the current tape library path is unchanged.
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 configuration file and restart the virtual tape application.
DLm157W
Device <devicename> tapelib subdirectory 'xxx' is not accessible!
Description: The specified virtual tape library subdirectory cannot be accessed.
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 will fail and
the current tape library path is unchanged.
User Action: Make sure that the proper filesystem is mounted on the specified
subdirectory and it is accessible to the user 'vtape'.
DLm160I
Device <devicename> enabled for Guaranteed Replication
Description: This device is configured to perform Guaranteed Replication.
User Action: None.
DLm161I
Tape library <pathname> enabled for replication
Description: This 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
Celerra 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
Celerra filesystem. 'nn' tasks are waiting for an available SSH session.
User Action: None.
DLm164I
Device <devicename> enabled for FLR
Description: This device is configured to support File Level Retention.
User Action: None.
DLm165I
Tape library <pathname> enabled for FLR
Description: This tape library directory resides on a filesystem that is enabled for File
Level Retention.
User Action: None.
DLm166E
Error reading Celerra #n report file '/pathname/filename': <reason>
Description: An unexpected error occurred while trying to determine the current state
of the specified Celerra by reading the specified report file.

System Messages
System Action: Celerra-related features such as Guaranteed Replication and/or 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.
DLm167I
<option> forced to <value> for MDL-1000DD/2000DD
Description: The specified configuration option has been forced to a specific value for
this controller model.
System Action: The normal default value or configured value is ignored, and the
specified value is used.
User Action: None.
DLm168W
Invalid DEBUG= value 'value'
Description: The configuration file or operator SET DEBUG command contained an
error.
System Action: If a configuration error, startup terminates. If a SET DEBUG command
error, the SET command is ignored.
User Action: If a configuration error, use the configuration program to correct the
configuration file. If a SET DEBUG command error, use the HELP command to obtain
correct syntax.
DLm169I
Celerra #n report file 'filename' successfully read
Description: The specified report file written by Celerra #n was successfully read. The
report is read and the new report data is used whenever the report content has
changed from the last time it was read and stored.
System Action: Celerra-related features such as Guaranteed Replication and FLR will
be enabled as appropriate for this Celerra.
User Action: None.
DLm170W
Celerra #n report file is over 30 minutes old; check Celerra control station

System Messages
Description: The specified status report file written by Celerra #n was written more
than 30 minutes ago. This signifies that the report-writing script on the Celerra control
station is probably not functioning correctly.
System Action: Celerra-related features such as Guaranteed Replication and/or FLR
may not function correctly.
DLm171E
File <filename> line nnn is too long
Description: The configuration file contained an error.
User Action: Reconfigure the specified configuration file. If the problem persists,
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 virtual tape application, the channel
interface adapter, or the adapter device drivers. The SNMP subsystem is responsible
for broadcasting all event messages that were selected during configuration to the
SNMP management station.
System Action: The controller continues to function in a degraded state. Data transfer
and storage continue to operate normally, but the SNMP and/or 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 Support for assistance.
DLm181I
SNMP data dump file <NAME> has been created
Description: This message displays the name of the file that was created to save
SNMP diagnostic information.

System Messages
User Action: None.
DLm182W
Unable to save SNMP data dump
Description: The system is unable to create the file to be used to save SNMP
diagnostic information.
System Action: The error is logged and operation continues. If the failure persists, the
SNMP subsystem will be disabled.
User Action: The user may retry the attempt to save the data by entering the command
'SNMP ACKNOWLEDGE FAILURE'. If the problem persists, contact EMC Support for
assistance.
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 virtual tape application,
the channel interface adapter, or the adapter device drivers. The SNMP subsystem is
responsible for broadcasting all controller event messages that were selected during
Virtuent configuration to the SNMP management station.
System Action: The error is logged and operation continues. If the failure persists, the
subsystem will be disabled.
User Action: If the SNMP subsystem is disabled as a result of this failure, it can be
re-enabled from the virtual tape application console. If the problem persists, or it
cannot be corrected, contact EMC 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 virtual tape application
console. Contact EMC Support for assistance.

System Messages
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
the channel interface adapter, or the adapter device drivers. The SNMP subsystem is
responsible for broadcasting all controller application event messages that were
selected during configuration to the SNMP management station.
System Action: If the failure occurred within the SNMP subsystem, initialization is
aborted and the SNMP services will not be available. If the failure occurred within the
IPMI subsystem, SNMP will continue to function but no system platform events will be
reported.
DLm187E
SNMP message(s) have been lost - <DETAILS>
Description: Due to resource limitations an attempt to send one or more SNMP
messages failed. Failing messages have been lost.
System Action: The failure is logged, and the application continues.
User Action: Examine the controller's log to view the lost message(s). Contact EMC
Support for assistance.
DLm188I
SNMP is [not] operational
Description: This message is 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.

System Messages
DLm190I
SNMP terminated
Description: The SNMP subsystem has shut down normally.
User Action: None.
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>
Description: This message describes some event that has occurred within the IPMI
subsystem. The IPMI subsystem is responsible for monitoring and reporting system
interface adapter, or the adapter device drivers.
System Action: None
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
the channel interface adapter, or the adapter device drivers.
System Action: The condition is logged and operation continues. If the condition
persists, the IPMI subsystem will be shut down.
User Action: If the problem persists, contact EMC Support for assistance.

System Messages
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 monitoring and reporting system
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 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 virtual
tape application, the channel interface adapter, or the adapter device drivers.
System Action: The message is saved to both the system event log as well as the
virtual tape application's event log.
User Action: None
DLm197W
(System Event) <warning message>
Description: This message 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 monitoring and reporting system
virtual tape application's 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 Support if assistance is needed.

System Messages
DLm198E
(System Event) <error message>
Description: This message indicates that a system platform event was detected by the
IPMI subsystem 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 virtual tape application, the channel interface adapter, or
the adapter device drivers.
Virtuent 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 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 virtual tape application validates the tape library for various integrity
issues.
System Action: If any errors are found, subsequent messages will report the
problem(s).
User Action: If any errors are reported, correct the problem(s), then SET PATH= to the
desired path.
DLm202I
Device <devicename> <nn> subdirectories under tape library 'pathname'
Description: While validating the specified tape library, this message displays the
number of subdirectories found in that tape library.
System Action: If any subdirectories exist, they will also be validated.
User Action: None.

System Messages
DLm203I
Device <devicename> There is no <volser> directory, using <pathname>
Description: When attempting to mount, scratch, unscratch, erase, delete, or initialize
a volume, the virtual tape application found that there was no tape library
subdirectory matching the first two characters ("volser prefix") of the specified
volume.
System Action: The system will search 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: Be sure 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.
User Action: The 'error message' portion of this message will describe the error that
occurred. Correct the error and retry the SET PATH command to set the tape library
path to the desired path.
DLm206W
Device <devicename> bypassing full filesystem <pathname>

System Messages
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.
DLm207W
Device <devicename> bypassing stalled filesystem <pathname> (nnn seconds)
Description: The specified filesystem will be skipped while performing a virtual tape
search because it has not responded to I/O requests for the past nnn seconds.
System Action: The specified filesystem is bypassed during this tape search.
User Action: A filesystem should not be this unresponsive. Check your backend
filesystem and network connections for problems. For more assistance, contact EMC
Support.
DLm208W
Device <devicename> bypassing quiesced filesystem <pathname>
Description: The specified filesystem will be skipped while performing a virtual tape
search because it has quiesced.
System Action: The specified filesystem is bypassed during this tape search.
User Action: None.
DLm209E
Cannot unquiesce, tapelib path=<pathname> not accessible.
Description: The specified filesystem cannot be unquiesced because it is not
mounted
User Action: Mount the file system and then request unquiesce
DLm210I
Validating tape library '<pathname>'...

System Messages
requested, the virtual tape application validates the tape library for various integrity
issues.
problem(s).
desired path.
DLm211I
Tape Library SN '<status>'
Description: During startup the virtual tape application 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-SN> Volume List <status>
Description: During startup, and at any other time a VTL volume list update is
requested, the virtual tape application will display the VTL volume list state.
User Action: None.
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>

System Messages
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.
assistance.
DLm216I
VTL-SN Environment Changed, Please Update Volume List. Update of Volume List
could take some time.
Description: The application volume list no longer matches the VTL environment.
User Action: Invoke the <Update Volume List> command to resynchronize the VTL and
application.
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.
DLm218I
Scanning tape drive devices...
Description: The SCSI tape drives are being scanned and cataloged.
User Action: None.
DLm219I
No VTL drives available.
Description: The VTL has no drives available. All configured drives are allocated.
User Action: Configure more VTL drives or fewer channel attached drives.

System Messages
DLm220I
Validating tapelib subdirectory '<name>'...
requested, the virtual tape application validates the tape library and each of its
subdirectories for various integrity issues.
problem(s).
desired path.
DLm221E
Device <devicename> subdirectory name '<name>' is not a valid volser prefix
Description: During validation of the tape library, the virtual tape application 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). This message will only occur if enhanced
filesystem support is NOT enabled on this node.
when processing a SET PATH command, the SET PATH command will fail.
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.
when processing a SET PATH command, the SET PATH command will fail.

System Messages
User Action: Either remove the invalid subdirectory from the tapelibrary base
directory, or rename the subdirectory to a valid enhanced filesystem subdirectory
name.
DLm223I
Device <devicename> volume <volser> not moved because VOLSERLOCKDIR is not
mounted correctly.
Description: The EFS Move feature has been disabled because the VOLSERLOCKDIR
not mounted correctly. The VOLSERLOCKDIR must be mounted with the 'soft' option.
System Action: Scratch tapes will not be moved from their initial directory and space
may no longer even out.
file.
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.
User Action: Be 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.
User Action: The 'error message' portion of this message will describe 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
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.
when processing a SET PATH command, the SET 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.
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.
when processing a SET PATH command, the SET 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 aren't expected to be stored on the internal
system disk(s), 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 will display 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.

System Messages
DLm231W
Unable to determine <pathname> device name: <error message>
Description: The virtual tape application was unable to determine on which disk
filesystem the specified directory is mounted.
System Action: Processing continues normally. This message should not normally
occur, but it will display every time a virtual volume is successfully mounted while the
'pathname' filesystem device cannot be determined.
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 virtual tape application will continue to run, but some features
(such as warnings about the capacity limits of certain filesystems) may not be
functional.
DLm233E
Device <devicename> data path <pathname> is not accessible
Description: During mounting of an explicit VOLSER, the virtual tape application was
not able to access the specified tape library subdirectory.
System Action: This subdirectory is ignored. If there are other tape library
subdirectories, they will be considered in order 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
virtual tape application, or use the SET PATH command to temporarily change the
tapelib path.
DLm234W
Device <devicename> data path <pathname> is not accessible: not readable

System Messages
Description: During mounting of a scratch volume, the virtual tape application was not
able to access the specified tape library subdirectory.
System Action: This subdirectory is ignored. If there are other tape library
subdirectories, they will be considered in order 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
virtual tape 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. Refer to these messages, correct the problem(s), and then SET
PATH= to the desired path.
DLm236W
Error reading filesystem info for <pathname>: error message
Description: An unexpected error occurred while trying to determine what filesystem
holds the specified tape library directory.
System Action: The application will continue to run, but some features that need to
know information about the filesystem, such as Guaranteed Replication, will not be
functional.
User Action: If the error messages describe a correctable problem, correct the problem
DLm237W
Device <devicename> Volume <volser> Error reading Celerra Report: error message
of replication on a Celerra filesystem.

System Messages
System Action: Guaranteed Replication may not function correctly. If replication

reports cannot be properly read in order to guarantee replication before the
Guaranteed Replication timeout period expires, an I/O error will be returned to the
Host.
DLm238I
Guaranteed Replication method is by <method>
Description: The Guaranteed Replication feature is configured to use the specified
method to determine when a given file's replication is complete.
System Action: The specified method will be used to determine when a given file's
replication is complete.
User Action: None.
DLm239E
Error opening Celerra report file <pathname>: error message
of replication on a Celerra filesystem.
System Action: The application will continue to run, but some features that need to
know information about the filesystem, such as Guaranteed Replication, will not be
functional.
DLm240E
Unable to open tape library path: <path>
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
Device <devicename> Unable to read contents of EFS lock file <volser>: <error>

System Messages
Description: While unlocking a volume, the contents (owner) of an EFS lock file could
not be read.
System Action: The owner of the EFS lock could not be determined. The lock remains
in place.
User Action: Verify that the EFS lock directory is mounted and accessible.
DLm242E
Device <devicename> Error deleting <description> file <filename>: <error>
Description: An error occurred while trying to delete the specified temporary file.
System Action: The status of the file is unknown. If the specified file is a lock file the
lock may still be in place.
User Action: If possible, correct the problem described in <error>. Contact EMC Support
if assistance is needed.
DLm243E
Unable to open file <file>: <error>
Description: An error occurred while opening a file for reading.
System Action: The file could not be opened.
User Action: Verify that the file exists.
DLm244E
Error reading file <file>: <error>
Description: An error occurred while reading a file.
System Action: The file could not be read.
User Action: Verify the file exists.
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.

System Messages
DLm246E
Device <devicename> 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 <devicename> 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 <devicename> 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 <devicename> 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.
DLm250I
Device <devicename> Incomplete read from file 'filename'
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 Support.

System Messages
DLm251I
Problem accessing directory <dirname>: <error>
Description: A problem occurred while accessing the destination directory for the new
volume(s).
System Action: No volumes will now be created in this directory.
User Action: None. If the problem persists, contact EMC Support.
DLm252E
Wrong storage class. REQ <requested class>, WAS <actual class> for <dirname>
Description: The INITIALIZE command specified both CLASS= and DIR= parameters,
but the specified directory has a class different from the specified 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.
DLm255I
Max display count <count> exceeded for key: <key>
Description: The number of matches for the find volume exceeded the limit.

System Messages
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
EFS Short Term Lock Directory set to: <directory>
Description: An EFS short term lock directory has been specified for Enhanced
Filesystem Architecture operations.
System Action: The application will use the specified directory for 'create' locks.
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: No more that <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 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.
User Action: verify the VOLSERLOCKDIR setting in the configuration file.
DLm262E
Device <devicename> Unable to unlock volser <volser>: <reason>
Description: A lock could not be removed from a volser.
User Action: Verify the VOLSERLOCKDIR setting in the configuration file.
DLm263I
Device <devicename> moved <volser path> to <volser path>, <size> bytes
Description: A device moved a newly acquired scratch volume from one filesystem to
another filesystem of the same class.
System Action: None
User Action: None
DLm264E
Invalid parameter: <import to>
Description: The IMPORT command TO parameter is not a valid VOLSER name.

System Messages
DLm269I
Device <devicename> forcing CRC storing/large headers for Data Domain filesystem
Description: The device is writing to a filesystem that resides on a Data Domain. This
type of file system requires large headers to be used.
System Action: None
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 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.
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.
DLm272E
Device <devicename> Volume <volser> block #nnnn contains unknown AMDD version id
Description: During a read operation, the data on the specified tape block was
flagged as having been modified by the AMDD feature, but data in the AMDD block
header isn't recognized as valid.
System Action: An equipment check error status is returned to the Host I/O request.

System Messages
DLm273W
Device <devicename> Volume <volser> AMDD skipping incompatible <type> block
#nnnnn, offset <nnnn>: <reason>
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
written
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.
DLm275I
Device <devicename> Volume <volser> <AMDD informational message>
Description: This message is used for displaying any number of AMDD
informational/statistical messages. These messages are only displayed when AMDD
debugging is enabled.
User Action: None.
DLm276I
Device <devicename> Volume <volser> AMDD read <nnnnn> AMDD-modified blocks

System Messages
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.
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 either
"EMC DLm Data Domain", "MDL-1000DD", or "MDL-2000DD".
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.
DLm279W
Device <devicename> Volume <volser> Suppressing AMDD due to encryption
Description: The specified device is configured to use AMDD data optimization, but
the device is also configured to encrypt the data.
System Action: The data being written is encrypted but not optimized by AMDD. This
message will display only once per volume as a reminder.
User Action: None.

System Messages
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: Issue the command with the correct file.
DLm282E
EXPORT TO device already in use. EXPORT command aborted.
Description: The SCSI TO device specified in the EXPORT command is already in use.
The EXPORT command stopped with no action.
User Action: Issue 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: Issue the command again once the current operation that is using the file
has completed.
DLm284E
EXPORT/IMPORT FROM/TO device block could not be created.
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 SCSI device is properly attached to the system. If this problem recurs,

System Messages
DLm285E
EXPORT/IMPORT FROM/TO device is not a valid device type for this command.
Description: One of the parameters specified is not a valid type for this command. The
command stopped with no action.
User Action: Issue the command again with valid parameters.
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: Issue the IMPORT command when the device becomes free.
DLm288E
IMPORT TO file already exists. Import will not overwrite an existing file.
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: Issue the command again with a file that does not already exist.
DLm289E
EXPORT/IMPORT FROM/TO file is invalid. Scratch file not permitted.
Description: Scratch file specified in EXPORT or IMPORT command. Scratch file use is
not permitted in these operations.
User Action: None.
DLm290I
<IMPORT/EXPORT> operation starting: FROM=file (dev=EXFRxxxx) TO=device
(dev=EXTOxxxx)
Description: Message indicating the IMPORT or EXPORT operation is starting.

System Messages

User Action: None.
DLm291I
IMPORT/EXPORT operation finished (successfully/with error): FROM=file
(dev=EXFRxxxx) TO=device (dev=EXTOxxxx)
Description: Message indicating 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/IMFRxxxx) TO=name (dev=IMTOxxxx)
Description: Message indicating the operation has completed and is now rewinding
and/or unloading the tape device per the NORUN flag.
User Action: None.
DLm295E
EXPORT operation reached PEOT. Tape invalid: FROM=name (dev=EXFRxxxx)
TO=name (dev=EXTOxxxx)
Description: The EXPORT command reached the physical end of tape before
completing the export operation.
System Action: The incomplete output tape is overwritten by tape marks to invalidate
the incomplete transfer.
User Action: Repeat the EXPORT operation with a larger tape.
DLm296E
Error rewinding tape after PEOT: FROM=name (dev=EXFRxxxx) TO=name
(dev=EXTOxxxx)
Description: The EXPORT command got an error rewinding the tape after it reached the
physical end of tape. The tape contains incomplete contents.

System Messages

User Action: None.
DLm297E
Error writing tapemark after PEOT: FROM=name (dev=EXFRxxxx) TO=name
(dev=EXTOxxxx)
Description: The EXPORT command got an error writing tape marks after a rewind of
the tape after it reached the physical end of tape. The tape contains incomplete
contents.
User Action: None.
DLm298E
SCSI device not ready, operation aborted: FROM=name (dev=EX/IMFRxxxx) 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 issue the command again.
DLm300W
Device <devicename>, connection n, received pkt 0xXXXX (packettype )
Description: The channel interface adapter sent an unexpected message type to the
virtual tape application.
System Action: The message from the adapter is ignored.
DLm301W
Channel event 'eventtype' (0xXXXX) on device <devicename> <pathinfo> [XXXX XXXX]
Description: The specified exceptional channel event 'eventtype' has been detected.
Some common eventtypes which may occur include: Halt I/O: Host has issued a Halt
I/O command, usually as a result of a Host job being cancelled.

System Messages
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. VirtuentNotReponding: The channel adapter has received a Halt I/O
and/or Selective Reset from the host, but the Virtuent application has not responded.
The channel adapter firmware will take over responsibility to respond to the host until
Virtuent resumes communication with the channel adapter.
System Action: Processing continues normally; it is presumed that the Host will
perform the proper error recovery procedure, to which the controller will respond 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
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 will be 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
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.

System Messages
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 virtual tape application.The virtual tape
application will automatically recover from this situation <count> number of times, but
this count has been exceeded.
System Action: This channel interface remains offline.
User Action: The situation causing the channel interface adapter to reset should be
investigated; contact EMC Support for more assistance if necessary. The channel
interface can be brought back online by entering the virtual tape application's "RESET
CHANNEL ADAPTER n" command.
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 device(s) 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 device(s) online. This may cause I/O errors on the Host channel.
System Action: Stopping or resetting of the channel interface continues.
User Action: None.
DLm307I
Device <devicename> Virtuent has resumed responding to adapter #n
Description: After a channel adapter takeover had occurred (see message VIR301W),
Virtuent has resumed responding to the channel adapter and taken back full
responsibility for host-to-Virtuent communication.

System Messages

User Action: None.
DLm308I
Rebooting Interface #n, slot=nnnnnn
Description: Channel interface #n is being reset.
User Action: None.
DLm309I
Device <devicename> NOT sending a resetting event unit check
Description: A resetting event is any channel event that resets a channel-attached
device's pathgroup ID or assignment, such as a system or selective reset or restarting
of the virtual tape 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 re-issue 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 virtual tape
application can be configured to NOT send resetting event unit checks. This message
is displayed when the controller 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 controller 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 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 startup.

System Messages
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 this device may not continue to
function properly.
DLm312E
Device <devicename> Error reading from Interface #n: error message
Description: An error was returned from the channel adapter.
function properly.
DLm313E
Device <devicename> error sending <info>, error = nn (0xXX)
Description: An error was returned from the channel adapter.
function properly.
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

System Messages
Description: The 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 isn't currently
assigned.
System Action: The I/O command is ignored.
User Action: Check that the virtual tape devices' configuration matches the Host's
configuration.
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
virtual tape application does not recognize as a valid path.
System Action: The unexpected message is ignored. The application continues to run,
but this device may not continue to function properly.
DLm317E
Device <devicename> received data on unexpected connection nn, path=nn
Description: Data was received from the channel adapter from a path on which the
virtual tape application wasn't currently handling a CCW.
System Action: The unexpected data is ignored. The application continues to run, but
this device may not continue to function properly.
DLm318E
Device <devicename> received unexpected data on connection nn, path=nn
Description: Data was received from the channel adapter while the virtual tape
application was not currently handling a CCW that should send data.
System Action: The unexpected data is ignored. The application continues to run, but
this device may not continue to function properly.
DLm319E
Device <devicename> <path> invalid data chaining flags (XXX) for XX CCW

System Messages
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.
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 will remain in this state until until the virtual
tape application is next restarted.
User Action: None. You can use the "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 entered, but
the specified action could not be performed.
User Action: Examine any 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 "RESET/STOP/START
CHANNEL ADAPTER" command.
User Action: None.
DLm331E
Device <devicename> no <type of path> to send Ready Status

System Messages
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 virtual tape application's
point of view, but since a Ready status was not presented the Host will most likely
report that the drive is still not ready.
User Action: Check that the specified device is varied online on the Host. You can
cause the virtual tape application to present another 'Ready' signal to the Host by
entering an "Unready" command, followed by a "Ready" command. If this problem
recurs, contact EMC Support for assistance.
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 virtual tape application will attempt to present the status several
more times. If the Host never takes the status, the virtual tape volume will remain
mounted on the drive, but the Host will most likely report that the drive is still not
ready.
User Action: You can cause the virtual tape application to present another 'Ready'
signal to the Host by entering an "Unready" command, followed by a "Ready"
command. If this problem recurs, contact EMC Support for assistance.
DLm333E
Device <devicename> failed to send Ready interrupt to Host
Description: After several retries, the virtual tape application was unable to present
the asynchronous status ('Ready' signal) to the Host.
System Action: The application continues without the status having been presented
to the Host. The virtual tape volume will remain mounted on the drive, but the Host
will most likely report that the drive is still not ready.
User Action: You can cause the virtual tape application to present another 'Ready'
signal to the Host by entering an "Unready" command, followed by a "Ready"
command. If this problem recurs, contact EMC Support for assistance.

System Messages
DLm335I
Device <devicename> unassigned while volume <volser> mounted
Description: The host has sent an Unassign command to this 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 Support if you need
additional assistance.
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 virtual tape
application.
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 virtual tape
application.
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 virtual tape application has detected a corruption of data written by
the Host.
System Action: The virtual tape 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 virtual tape application will return a unit check to the
Host, with sense of Bus Out Error (displaying "failed" this time).

System Messages
User Action: A data CRC error may indicate failing hardware, cabling, or a weak data
link between the Host and the virtual tape application. Contact your hardware support
personnel for assistance.
DLm341E
Device <devicename> CRC mismatch in data block...
Description: The virtual tape application 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: The virtual tape application 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.
DLm342E
Device <devicename> volser <volser> block nnnnn disk read CRC error
Description: After reading data from the tape library storage, the virtual tape
application detected that the CRC stored with the data does not match the data just
read.
System Action: The virtual tape application will return a unit check to the Host, with
sense of Equipment Check.
User Action: A CRC error indicates that corruption of the stored data has occurred.
Contact EMC Support for assistance.
DLm350E
Unable to get trace flags for interface #n
Description: The virtual tape application 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 will not be available to the virtual tape
application. As a result, some subsequent function may not complete.
DLm351E
Unable to set trace flags for interface #n

System Messages
Description: The virtual tape application 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 virtual tape application 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 virtual tape application 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.
DLm355W
Device <devicename> Attempting to save firmware trace on interface #n
Description: An error or other unusual event has occurred on channel interface #n,
and the virtual tape application will attempt to save a firmware trace from that
interface.

System Messages
System Action: The virtual tape application will attempt to stop the firmware trace and
save it to disk. After the trace is saved, firmware tracing will resume.
DLm356E
Interface #n exceeded automatic save trace limit of nn, NOT saving trace
Description: An error or other unusual event has occurred on channel interface #n. The
virtual tape application will automatically save a firmware trace 'nn' number of times,
but this count has been exceeded for this interface.
System Action: The virtual tape application continues running without automatically
saving the firmware trace.
DLm357E
Interface #n NOT saving trace for unexpected packet
Description: An error or other unusual event has occurred on channel interface #n.
Normally, saving of a firmware trace would be triggered by this event, but the virtual
tape application has been configured to not save a trace for this kind of event.
System Action: The virtual tape application 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 Support for assistance with this option.
DLm366E
Device <devicename> <function> error, Interface #n, error=0xXX (nnn)
Description: An error involving channel interface adapter #n has occurred.

System Messages
System Action: This channel interface may not be available to this 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 virtual
tape application startup.
DLm379E
<function>: <error message>
Description: An internal error has occurred in the virtual tape application during
shutdown.
System Action: Shutdown continues.
DLm380E
Severity n Alert Interface #n (XXX:YYY) <type:subtype (additional parms)>
Description: The virtual tape application 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 virtual tape application
may continue to function normally, or it may require service or other attention.
DLm381I
Channel Interface #n <message>
Description: The virtual tape application has received an informational message from
channel adapter 'n'.

System Messages
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 controller until
the encryption key file is restored or reconfigured.
User Action: Restore the encryption key file from a backup copy, or reconfigure the
key(s) 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 performed on device <devicename>
System Action: The specified encryption key (or none, for 'NONE') will be used for any
blocks 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 key(s) via
the encryption key configuration program.
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.

System Messages
User Action: The user should check the encryption configuration.
DLm395E
Device <devicename>, no matching decryption key, block <block#>
Description: No key currently installed on this system 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) is returned to the host. During an Import or Export operation, this
is a warning rather than an error; the data will be copied in its original encrypted
format to the new location.
User Action: Check that the virtual tape application is configured with the proper
encryption key(s).
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.
DLm399E
Syntax error. Format is 'DRIVE-', not 'DRIVE='.
Description: The correct format for specifying this device is 'DRIVE-'.
System Action: The command was invalid and not performed.
User Action: Specify the command again with valid syntax.

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 virtual tape
configuration file PATH= parameter and restart the virtual tape 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 tape 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 Support for assistance.
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.
DLm403E
Device <devicename> Volume <volser> (filename) invalid AWS block header at nnnnn
(n)

System Messages
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
System Action: The operation reading the volume will fail.
User Action: Delete and re-create the volume that has the invalid format. If this
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, it was unloaded without ever having been written to, so the virtual tape
application tried to delete it. An I/O error occurred during the attempt to delete.
System Action: The volume may or may not have been deleted from the tape library.
User Action: The 'error message' portion of this message describes the error that
occurred. Correct the error.
DLm405I
Device <devicename> Display: 'message1' 'message2' [(blink)]
Description: The Host has sent these message(s) to be displayed on the virtual tape
drive's operator display unit.
System Action: If the message is a Mount message, and the virtual tape drive is
currently unloaded, and the volume serial number falls within the range managed by
the virtual tape application, then the specified volume will be mounted.

System Messages
User Action: None.
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 ACLVolser (value)
Description: The mainframe request for ACLON is rejected because the ACLVolser that
was passed is not in the scratch synonyms list.
System Action: The command is rejected. The current ACL state is not changed.
User Action: None.
DLm408I
Device <devicename> ACL turned <ON/OFF> [ACLVolser = 'volser'] [reason]
Description: The ACL (autofill) feature has been turned on or off.
System Action: The ACLON or ACLOFF request was granted. If the request was to turn
ACL on, the new ACLVolser is also displayed. If ACL was turned off by the virtual tape
application rather than by the host the reason will be displayed.
User Action: None.
DLm409I
Command received: 'command'
Description: The specified operator command was received.
System Action: The specified command is processed.
User Action: None.

System Messages
DLm410E
Device <devicename> error initializing Volume <volser>
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 for a description of the
problem and correct the problem. If the problem recurs, contact EMC Support for
assistance.
DLm411E
Device <devicename> AWS block #nnn too large (xxxxxx) to handle (max=yyyyyy)
Description: The virtual tape application 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 virtual tape application 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.
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 virtual tape application returns an error status to the current Host
IO request.

System Messages
information, and correct the problem. If the problem recurs, contact EMC Support for
assistance.
DLm414W
Device <devicename> tape full writing <data/TM> at PEOT, file <filename>
Description: While writing to a physical tape drive, the virtual tape application
received a response that the physical tape cartridge is full.
System Action: The write operation fails with a unit check.
User Action: Investigate why the host application wrote past logical end of tape
(LEOT).
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.
assistance.
DLm416E
Device <devicename> not responding.
Description: The physical tape device is no longer responding to the virtual tape
application.
System Action: The virtual tape application will set the tape device to NA (Not
Accessible).
User Action: The virtual tape application must be restarted after repairing the problem
with the specified tape drive.
DLm417E
Device <devicename> I/O error: <function description>; error=nnn; <error message>
Description: An error occurred while reading or writing a virtual tape file.

System Messages
I/O request.
assistance.
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 system to
decompress the data.
System Action: The data is decompressed with software. This message will display
only once per volume as a reminder.
User Action: For best performance, data compressed with a 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.
assistance.
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 will be 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 virtual tape application 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 a virtual tape volume
or a physical tape volume.This message will also be displayed at the end of an Import
or Export command, because these commands will read and copy all data until they
reach the end of the input tape volume. This is normal operation of the Import and
Export commands and does not signify an error.
System Action: If this occurs as a result of a Host I/O request, an error status (Data
Check, Tape Void) is returned to the Host I/O request. For an Import or Export
operation, this message is normal and does not signify an error.
User Action: If caused by a Host operation, correct the application causing the error.
For an Import or Export operation, this message is normal and does not signify an
error.

System Messages
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.
DLm425E
Device <devicename> Data block exceeds maximum of yyyyyy bytes
Description: The Host wrote a block larger than the maximum blocksize supported by
the virtual tape application.
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 and/or JCL to write data blocks within the
virtual tape application 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 option(s) that require expanded headers, and retry the host job.
Contact EMC 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: The virtual tape 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> from <blockid>) begun
Description: The virtual tape application is executing the specified Host I/O
command, and it has determined that this command might take a considerable period
of time to complete (more than a few seconds) because there is no index to the
desired location in the virtual tape file to perform the operation quickly, so it issues
this message for informational purposes.
System Action: The command continues normally. If, during the possibly lengthy
operation, a suitable index entry to complete the command quickly is encountered,
fast operation will resume (see message DLm431I). If the command takes a very long
time to complete, 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 virtual tape application's devices.
DLm429W
Device <devicename> <function description> while device not ready
Description: The requested operation requires a tape to be loaded in the physical
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 virtual tape application 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 AWS block header").
Later 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 Messages
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.
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 DLm428I). 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.
DLm433I
Device <devicename> is not writing expanded headers.
Description: The device is set to write expanded headers, but is currently not honoring
the value.
User Action: None.
DLm434W
WARNING: Path <pathname> disk usage at nn%

System Messages
Description: The disk usage for the specified tape library has exceeded the current
WARNING value.
System Action: The virtual tape application will continue 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.
DLm435I
<this is an informational message>
Description: This message is an informational message
System Action: none
User Action: none
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 virtual tape application will erase the data from previously
scratched virtual tape volumes until the disk usage is reduced by the RECOVERAMT
percent of space.
User Action: Consider scratching and erasing unneeded virtual tape volumes to free
some disk space.
DLm437I
Finished space recovery, nn bytes recovered from scratch volumes in <pathname>
Description: The virtual tape application has finished attempting to recover space for
the specified tape library directory, because either (1) the disk usage has been
reduced by the RECOVERAMT percent of space, or (2) it has found no more scratched
volumes to erase. 'nn' bytes is the number of bytes erased from scratch volumes and
made available for reuse.
User Action: None.

System Messages
DLm438I
Finished space recovery, nn bytes recovered from nn scratch volumes in <pathname>
Description: The virtual tape application has recovered the specified amount of space
from scratch tapes that have exceeded their 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 (filename)
Description: The specified virtual tape volume has been mounted; the device will now
present a "ready" interrupt to the Host.
User Action: None.
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>

System Messages
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
re-load 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.
User Action: One or more previous message(s) should explain the reason for the
problem. Correct the problem preventing the scratch volume allocation, and try to
re-load a scratch tape. For instance, enter 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 re-use.
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>

System Messages
Description: The virtual tape application 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 entered for a new (non-existing)
volume.
System Action: The volume is created and mounted, but it will appear to the Host as
an empty, un-initialized (and read-only) tape.
User Action: Don't 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: In order 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 volume serial number that is not a
valid IBM volume serial number.
System Action: The mount request is ignored and the device remains not ready.
User Action: Correct the Host JCL to request a valid IBM volume serial number. An IBM
standard volume serial number consists of the upper-case letters A-Z, numbers 0-9,
and the hyphen.
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.

System Messages
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
current 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 (which may have been configured in the virtual tape
application) for this virtual tape device. The only value which you'll see for 'X' is 'A' for
ANSI labels, because this message does not display 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
configured 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.
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 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 is ignored.

System Messages
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
the specified drive is in the 'quiesced' state,meaning it will not accept any tape
mounts until it is 'unquiesced' (or until the virtual tape application is restarted).
System Action: The mount request remains pending until the drive is unquiesced or is
cancelled by the host.
User Action: UNQUIESCE the drive, or use a different drive.
DLm453W
Device <devicename> Volume <volser> already mounted, new mount request honored
Description: The Host requested the mounting of a volume, and the specified drive
already has a virtual tape volume mounted, 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.
DLm454E
Device <devicename> Volume <volser> not found
Description: The virtual tape application was requested to load a virtual tape volume
that does not exist in the virtual 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 directory(s) are properly mounted and are accessible to the virtual tape
application. If the requested volser is for a scratch tape, make sure that there are
scratch volumes, initialized with the correct label type, available.

System Messages
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 message' portion
DLm456W
Device <devicename> Volume <volser> already mounted, new mount request honored
Description: The Host requested the mounting of a volume, and the specified drive
already has a virtual tape volume mounted. 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
Support for additional assistance.
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
Support for additional assistance.
DLm458W
Device <devicename> Volume <volser> already mounted, new mount request deferred

System Messages
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 virtual tape
application 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.
User Action: The Host will most likely complain 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 re-initialization 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

System Messages
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 re-evaluated.
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> (filename to filename): <error message>;
retrying...
Description: The Host has asked for a previously scratched volume by specific volser.
The virtual tape application 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.
DLm463W
Volume <volser> file is open elsewhere, retrying...
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.
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 volume serial
number onto the virtual tape volume, but the new VOLSER does not start with the
same 2-character VOLSER prefix as the existing volume serial number.

System Messages
System Action: The virtual tape application 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 volume serial
number of the same 2-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 volume serial number in the VOL1 label is invalid.
User Action: Correct the Host job that is attempting to write the invalid volume serial
number to the virtual tape.
DLm466E
Device <devicename> volser 'volser' from VOL1 already exists [as scratch]
number onto the virtual tape volume, but the new VOLSER is the same as a volume
that already exists in the virtual tape library.
User Action: Correct the Host job that is attempting to write the duplicate volume
serial number to the virtual tape, or delete the existing volume from the virtual tape
library before rerunning the job.
DLm467E
Device <devicename> error renaming volume <volser1> (filename) to <volser2>
(filename); <error message>
number onto the virtual tape volume, but the virtual tape application is failing in its
attempt to rename the mounted volume to the new volume name.

System Messages
User Action: Refer to any earlier messages and the 'error message' portion of this
message to determine the cause of the failure. If the problem cannot be corrected,
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.
DLm469I
Device <devicename> Volume <volser1> renamed to <volser2> (filename)
Description: The Host has written a VOL1 label with a different volume serial number
onto the virtual tape volume.
System Action: The virtual volume file was successfully renamed to the new volume
serial number.
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 will be preceded by one or more messages that explain the
reason for the mount failure. Correct the error indicated in the preceding message(s).
DLm471E
Device address xxxx on GROUP n doesn't exist
Description: Mounting of a virtual tape volume on OSADDR 'xxxx' was requested by
the VSE mount program, but the specified device does not exist in the specified
GROUP.

System Messages
System Action: The mount request is ignored and the drive remains Not Ready. A
return code of 0x82 is returned to the Host program.
User Action: Reconfigure the VSE mount program and/or virtual tape application to
use the proper device address(es).
DLm472I
Volume <volser1> is currently on <devicename>, cannot mount <volser2>
Description: Mounting of volume 'volser2' on the specified drive was requested by the
VSE 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.
DLm473E
Invalid mount request x'xx' 'aaaaaaaa' 'bbbbbbbb'
Description: Mounting of a virtual tape volume was requested by the VSE 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 VSE mount program, but there is no free drive in this GROUP.
return code of 0x80 is returned to the Host program
User Action: Retry the Host mount when a virtual drive becomes available.
DLm475E
No free device in GROUP n to mount 'volser'

System Messages
requested by the VSE 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
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 won't be of any consequence, but if the request was for 'Any' drive, the
Host program won't be able to determine on which drive the volume was mounted.
User Action: Reconfigure the virtual tape application and add the correct OSADDR
parameter for each device that will be attached to a VSE system.
DLm477E
Mount requested on <devicename1> by <devicename2> failed
requested by the VSE mount program, but the volume could not be mounted on
<devicename2>. This message will be preceded by one or more messages that explain
the reason for the mount failure.
User Action: Refer to any preceding messages for the reason for the mount failure and
correct the problem(s).
DLm478I
Device <devicename> Requesting mount 'volser' on 'device'
program or a tape manager on the host.

System Messages
System Action: The virtual tape application 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 will result 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 re-initialize the virtual tape volume.
DLm480E
Both active and scratch volser volumes exist in <pathname>, mount ignored
Description: While mounting a volume, the virtual tape application 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.
DLm481E
Mount error renaming volume <volser> (filename to filename): <error message>
The virtual tape application was unable to rename the scratch volume (~VOLSER) to
an active volume (VOLSER).The rename was retried several times over several
seconds, and never succeeded.
System Action: The mount request is ignored, and the drive remains Not Ready.
message to determine the cause of the failure. Contact EMC Support for assistance.
DLm482I
Scratch tape <volser> made active

System Messages
System Action: The virtual tape application 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.
message to determine the cause of the failure.
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
virtual tape application does not support the mounting of unlabeled scratch tapes
because there is no way to track the volume by volser once the Host writes unlabeled
data.
System Action: The mount request is ignored and the device remains Not Ready.
User Action: Specify a specific volume serial number for unlabeled usage, or specify a
labeled tape for scratch usage.

System Messages
DLm486E
Device <devicename> Unable to allocate a [SCRTCH/PRIVAT] volume
Description: The mount request for a scratch tape failed.
System Action: The mount request is ignored and the device remains 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 preceding virtual tape mount request could not be satisfied at this
time.
System Action: The specified mount request will be automatically retried until
successful or until the Host cancels the mount request with a new Load Display
command.
User Action: None.
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 virtual tape library.
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.

System Messages
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 virtual tape application 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
will be automatically changed back to the previous value.
User Action: None.
DLm492I
Device <devicename> not on SMB filesystem, max volume size changed back to size
Description: The virtual tape application 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 down 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 virtual tape application returns an error (Command Reject, File
Protected) to the Host application.

System Messages
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>
Description: The virtual tape application received a write operation from the Host, but
the tape library disk is full. 'nnnnnnn' is the number of bytes written to the tape so far.
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 virtual tape application will leave the drive in the Not Ready state until the virtual
tape application operator changes the drive to Ready. Most Host systems will report
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, issue the READY
command to this drive to resume.
DLm495E
Device <devicename> disk full writing data/TM at nnnnnnn, file <filename>
Description: The virtual tape application received a write operation from the Host, but
the tape library disk is full. The virtual tape application cannot recover and continue
because the tape library is on an NFS filesystem. 'nnnnnnn' is the number of bytes
written to the tape so far.
System Action: The write operation fails (Unit Check status, Equipment Check sense).
The contents of the volume being written are 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 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 will only be displayed once per
volume.

System Messages
System Action: If IDRC=NO is set, the data is written uncompressed to the virtual 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 virtual tape drive with the
correct IDRC parameter, or enter the command 'SET IDRC=ON/OFF/FORCE
[DEV=devicename]' to temporarily override the virtual tape application's
configuration.
DLm497W
Device <devicename> Hardware [de]compression configured off, using software only
Description: The controller has hardware compression/decompression capability but
is currently configured to not use the hardware facility for
compression/decompression. This message will display 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 and/or
decompressed with the compression hardware (which is much faster than software
compression/decompression). In that case, enter the command 'SET
HWCOMPRESSION=ON' and/or 'SET HWDECOMPRESSION=ON to reactivate the
hardware compression/decompression feature.
DLm499W
Device <devicename> Volume <volser> error compressing data: nnn[, falling back to s/w
compression]
Description: An error occurred while writing compressed data to the virtual tape file.
System Action: The data is written uncompressed to the tape library, unless hardware
compression was in use, in which case software compression is tried.
DLm500I
Scratching/Unscratching/Erasing of volume <volser> requested by host via device
<devicename> [dsn='datasetname']

System Messages
Description: Scratching, unscratching, or erasing of the specified virtual tape volume

was requested by the Host. If the request is further qualified by a dataset name, it is
shown in the message.
System Action: The virtual tape application will attempt to scratch, unscratch, or erase
(delete the data of a scratch volume) the specified volume in the virtual tape library. If
a dataset name is specified the volume will first be checked to confirm that it contains
the specified data set.
User Action: None.
DLm501I
Volume <volser> (filename) scratched/unscratched/erased/deleted
Description: Scratching, unscratching, erasing, or deletion of the specified virtual tape
volume was successful.
System Action: The specified virtual tape volume was scratched, unscratched, erased
(data deleted), or deleted (file deleted) from the virtual tape library as requested. If
the request came from the mainframe, 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
was requested, but the specified volume is in use.
System Action: The virtual tape volume status is not changed. If the request came
from the mainframe, a return code of 0x06 is returned to the Host application.
User Action: Change the tape status later when it is not in use.
DLm503E
Error scratching/unscratching/erasing volume <volser> (filename); <error message>
Description: An error occurred during the scratching, unscratching, or erasing of the
specified virtual tape volume.

System Messages
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. If the request came from the
mainframe, 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 message' portion
DLm504E
Scratching/unscratching/erasing of invalid volume 'volser' requested by host via
device <devicename>
was requested, but the requested volser is an invalid volume serial number.
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 volume serial number being sent by the Host program.
DLm505E
Device <devicename> received invalid scratch/unscratch/erase/execute request,
length=nnn
Description: Scratching, unscratching, or erasing of the specified virtual tape volume,
or execution of a 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.
DLm506E
Both active and scratch <volser> volumes exist in <pathname>!
Description: Scratching or unscratching of the specified virtual tape volume was
requested, but the virtual tape application 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. If the request came from
the mainframe, a return code of 0x03 is returned to the Host application.

System Messages
User Action: Determine which of the two files is the correct volume to keep, and delete
the other copy. Contact EMC Support if you need more assistance.
DLm507E
Scratch/Unscratch Error renaming volume <volser> (filename); <error message>
Description: Scratching or unscratching of the specified virtual tape volume was
requested, but the virtual tape application encountered a problem while renaming the
volume to the specified filename.
System Action: The scratch or unscratch request is ignored. If the request came from
the mainframe, a return code of 0x08 is returned to the Host program.
User Action: Refer to 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 exceeded 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.
DLm510W
Device <devicename> data path <pathname> is not accessible
Description: Scratching, unscratching, or erasing of a virtual tape volume was
requested, but the specified tape library directory is not currently accessible.
System Action: The scratch, unscratch, or erase request is ignored. If the request came
from the mainframe, a return code of 0x0A is returned to the Host program.
User Action: Make sure that the device via 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

System Messages

requested, but the specified tape library directory is not currently writable.
System Action: The scratch, unscratch, or erase request is ignored. If the request came
from the mainframe, a return code of 0x0B is returned to the Host program.
User Action: Make sure that the device via 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'.
DLm512E
Device <devicename> Scratching/Erasing/Unscratching/Deleting not allowed on
<drive>
requested by the Host, but the virtual device specified is currently assigned to an
active physical tape drive.
System Action: The scratch, unscratch, erase, or delete request is ignored. A return
code of 0x08 is returned to the Host program if the device is busy and 0x0A is
returned to the Host program if the function is not supported.
User Action: Make sure that the device via which scratch/unscratch/ erase/delete
requests are sent by the Host application is assigned to a virtual tape library directory,
not a physical tape drive.
DLm513E
Device <devicename> Volume <volser> error uncompressing data block #nnnnn: nn
(error message), falling back to s/w decompression
Description: An error occurred while reading compressed data from the tape file.
System Action: The virtual tape application will fall back to s/w decompression.
User Action: None.
DLm514E
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 virtual tape application returns an error (Data Check) to the Host

System Messages
User Action: If possible, recreate the corrupted volume. If this problem recurs, contact
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 or system.
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>
unscratching, erasing, an I/O error occurred while trying to lock the file for exclusive
access.
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 Support for
assistance.
DLm517E
Invalid VOL1 label in volume <volser> (filename)
unscratching, erasing, it was found that the specified volume does not contain a valid
VOL1 label.
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>)
unscratching, erasing, it was found that the volume serial number (volser1) found in
the VOL1 label on the volume does not match the one expected (volser2).
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>)
unscratching, erasing, it was found that the volume does not contain a valid HDR1
label.
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'
unscratching, erasing, it was found that the volume contains the dataset 'dataset1',
not the dataset 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.
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.

System Messages
System Action: The scratch/unscratch/erase request is ignored. A return code of 0x10

User Action: Correct the data being sent by 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 virtual tape application at least one
day after the file on the volume was created.
DLm524W
Volume <volser> (filename) already scratched/unscratched/erased
requested by the Host, but the specified virtual tape volume is already in the state
designated in the message.
System Action: The scratch/unscratch/erase request is ignored. A return code of 0x02
User Action: Be careful not to submit duplicate scratch/unscratch/erase requests to
DLm525E
Volume <volser> (filename) not a scratched/erased tape
Description: Erasing or deleting of 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, and delete requests for previously erased volumes only.

System Messages
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.
DLm527W
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.
User Action: Correct the problem preventing the scratch volume allocation and try to
re-load a scratch tape. If no scratch volumes are available, consider scratching some
old, unneeded volumes or INITIALIZE some more scratch volumes.
DLm530E
OCFS/2 feature not available
Description: An OCFS/2 support license is installed, but an error occurred during
OCFS/2 initialization.
System Action: OCFS/2 support is disabled until the problem is corrected and the
controller is restarted.
User Action: If the preceding error message(s) describe a correctable problem, correct
the problem and restart the controller. Contact EMC Support if more assistance is
needed.
DLm539E
Device <devicename> volser <volser> write verification error: error message
Description: An error occurred while verifying the data just written to disk.

System Messages
System Action: An I/O error status is returned to the current host operation. This
message should be preceded by one or more messages that explain the problem(s)
encountered.
User Action: If the error messages describe a correctable problem, correct the problem
and retry the failing job. Contact EMC Support if more assistance is needed.
DLm540W
Unexpected response received from <servername>: message
Description: While attempting to get filesystem information from the specified server,
an unexpected response was received.
System Action: Any feature such as Guaranteed Replication or FLR that depends on
knowing information about the back-end filesystem may not function properly on this
filesystem.
User Action: If the message describes a correctable problem, correct the problem and
restart the DLm application. Contact EMC Support if more assistance is needed.
DLm541I
Device <devicename> Volser <volser> GR device writing to replicating filesystem
Description: The specified device is configured to use Guaranteed Replication, and
the volume being written is on a replication-enabled filesystem.
System Action: When the tape is closed, a replication-refresh will be performed on the
filesystem.
User Action: None.
DLm542I
Device <devicename> Volser <volser> preparing GR replication (nn second delay)
Description: The specified device is configured to use Guaranteed Replication, the
virtual tape volume resides on a replication-enabled filesystem, the host has written
two consecutive tapemarks to the volume, and a Guaranteed Replication delay has
been configured.
System Action: A replication-refresh is being prepared, and will start in <nn> seconds.
User Action: None.

System Messages
DLm543I
Device <devicename> Volser <volser> starting GR replication-refresh (nn second
timeout)
Description: The specified device is configured to use Guaranteed Replication, the
virtual tape volume resides on a replication-enabled filesystem, and the host has
written two consecutive tapemarks to the volume.
System Action: A replication-refresh is being performed. If the replication- refresh
does not complete in <nn> seconds, an error status will be returned to the host's WTM
command.
User Action: None.
DLm544I
Device <devicename> Volser <volser> GR replication-refresh complete
Description: A Guaranteed Replication replication-refresh has completed successfully.
System Action: Normal ending status is returned to the host's WTM command.
User Action: None.
DLm545W
Device <devicename> Volser <volser> GR device writing to non-replicating filesystem
Description: The specified device is configured to use Guaranteed Replication, and
the volume being written is NOT on a replication-enabled filesystem.
System Action: When the volume is unloaded, no replication-refresh will be
performed.
User Action: None.
DLm546I
Device <devicename> Volser <volser> retrying replication through 'csname'
Description: A Guaranteed Replication replication-refresh attempt previously failed,
but there is an alternate control station on which to retry the request.
System Action: The replication-refresh request will be retried on the specified
'csname' control station.
User Action: Check the Celerra configuration to make sure that the Celerra control
stations are properly configured.

System Messages
DLm547W
Device <devicename> Volser <volser> ssh error with control station 'csname'
Description: A Guaranteed Replication replication-refresh attempt sent to the Celerra
control station 'csname' failed.
System Action: If there is an alternate control station address, the replication- refresh
will be attempted on the alternate address. Otherwise, the replication-refresh will
have failed.
User Action: Check the Celerra configuration to make sure that the Celerra control
stations are properly configured.
DLm548E
Device <devicename> Volser <volser> Guaranteed Replication error: <error message>
Description: A Guaranteed Replication replication-refresh has encountered an error.
System Action: The tape volume will be unloaded, with an error status returned to the
host's unload command. The file is intact on the local storage attached to the DLm,
but replication is not guaranteed.
User Action: Check the <error message> for a description of the problem and correct
the problem, check the replication status, and/or force a manual replication of the
filesystem. If necessary, contact EMC Support for more assistance.
DLm549E
Device <devicename> Guaranteed Replication cannot locate info for 'pathname'
Description: A Guaranteed Replication replication-refresh is being attempted, but
detailed replication information about the filesystem cannot be obtained at the time.
System Action: The Guaranteed Replication replication-refresh is not performed. An
error status is returned to the host's WTM command. The file is intact on the local
storage attached to the DLm, but replication is not guaranteed.
User Action: Force a manual replication of the filesystem to guarantee that the tape
has been replicated. Contact EMC Support for assistance.
DLm550I
Command received from Host: device <devicename>: cmd = 'command'
Description: The specified virtual tape application command was sent from the Host
via the specified virtual tape device.

System Messages
System Action: The command will be executed. Depending on the results of the
command, a return code will be returned to the Host program.
User Action: If the command is successful, none. Otherwise, determine the reason for
the command failure and correct the problem.
DLm551E
Host-initiated commands not allowed
Description: A virtual tape application command was sent from the Host, but the
application is not configured to allow Host-initiated commands.
System Action: The command will not be executed. A failure code will be returned to
the Host program.
User Action: If you want the Host to be able to initiate virtual tape application
commands, correct the configuration to allow for this feature.
DLm552E
Unable to locate script <scriptname>: <error msg>
Description: A virtual tape application RUN command was sent from the Host, but the
application is not able to locate the specified script.
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 virtual tape
application user 'vtape'.
DLm553E
Unable to execute script <scriptname>
application is not able to execute the specified script.
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 virtual tape
application user 'vtape'.

System Messages
DLm555E
RUN command not allowed
application is not configured to allow the RUN command.
the Host.
User Action: If you want the Host to be able to initiate virtual tape application RUN
commands, correct the configuration to allow for this feature.
DLm556W
RUN process #nnnnn has not finished in nn seconds
Description: A virtual tape application RUN command was sent from the Host and
executed by the application, but the specified script did not complete within the
specified time limit.
System Action: The virtual tape application will cancel the process identified by
process ID #nnnnn. A failure code will be returned to the Host.
User Action: If the specified script normally takes longer than the time specified,
specify a longer time on the RUN command.
DLm560E
Device <devicename> Error gathering file segment data for volume <volser>
Description: An error has occurred while opening a previously extended virtual tape
volume on a WORM filesystem. This message should be preceded by one or more
messages that explain the problem(s) encountered.
System Action: The volume is not mounted, and the drive remains Not Ready.
the problem and retry mounting the tape volume. Contact EMC Support if more
assistance is needed.
DLm561E
Device <devicename> Missing or invalid AWSMAP in <filename>
volume on a WORM filesystem. The format of the specified file is invalid.

System Messages
DLm562E
Device <devicename> Error extending volume <volser>: <error message>
Description: An attempt was made to write to (modify) a previously locked virtual tape
volume on a WORM filesystem, but an error occurred while trying to create a new file
to extend the volume. The <error message> portion of this message explains the
problem that occurred.
System Action: The Host write command is rejected with a Unit Check.
DLm563E
Device <devicename> Info in file <filename> doesn't match previous segment
volume on a WORM filesystem. The previous file segment information stored in file
segment 'filename' does not match the actual contents of the immediately preceding
file segment.
DLm564E
Device <devicename> Invalid segment number in segment <n>
volume on a WORM filesystem. The file segment number stored in the file
VOLSER_nnnnn, where nnnnn is the segment number <n> shown in the message, is
not <n>.
DLm565E
Device <devicename> Illegal volume mod attempt, volume <volser>, offset <nnnnnn>,
block <nnn>

System Messages
Description: An attempt was made to write to (modify) a previously locked virtual tape
volume on a WORM filesystem, at a location other than at the end of the existing data.
Once a virtual tape volume is locked on a WORM filesystem, you can append to the
dataset but you cannot modify it in any other way.
User Action: Correct the Host job or application so that it does not try to write
anywhere but at the end of the existing data.
DLm566E
Device <devicename> Volume <volser> maximum number of modifications exceeded
Description: An attempt was made to write to (modify) a previously extended virtual
tape volume on a WORM filesystem, but the volume has already been modified the
maximum of 9999 times.
User Action: Keep the number of modifications to a virtual tape volume on a WORM
filesystem to a minimum, for performance reasons as well as to avoid reaching the
maximum allowable modifications.
DLm567I
Device <devicename> Volume <volser> WORM file has <nn> modifications
Description: The specified volume resides on a WORM filesystem. If the volume had
been previously modified since it was first placed into WORM mode, this
informational message displays the number of times it has been modified.
User Action: None.
DLm568I
Device <devicename> Volume <volser> writing modification #nn
Description: The specified volume resides on a WORM filesystem, and is in WORM
mode. The system is configured to allow appending to WORM files (FLRMOD=YES) and
the host has performed a write to append to this tape.
System Action: The append to the WORM file is allowed. This message will be
displayed once per mounting of any given tape.

System Messages
User Action: None.
DLm569E
Device <devicename> error extending volume <volser>
Description: An error occurred during an attempt to write to (modify) a previously
locked virtual tape volume on a WORM filesystem. This message should be preceded
by one or more messages that explain the problem(s) encountered.
the problem and retry the failing job. Contact EMC Support if more assistance is
needed.
DLm570W
HDR1 has invalid expiration date `xxxxxx'
Description: During opening of an existing virtual tape volume, or when the Host
wrote a new HDR1 label, the virtual tape application determined that the expiration
date in the HDR1 label (xxxxxx) was invalid.
System Action: Processing continues. The virtual tape application treats the volume
as if no expiration date was specified in the HDR1. The only time a volume's
expiration date is of any consequence to the application is if the file is being written to
a WORM filesystem. In this case, if the virtual tape application is configured with a
default retention value, that retention period will be used. Otherwise, the retention
period is treated as zero (no retention) and the file will be written in a non-WORM
mode.
User Action: Correct the host JCL to write a valid expiration date.
DLm571W
Device <devicename> Retention date <yyyy/ddd> out of range, using YYYY/DDD
Description: During opening of an existing virtual tape volume, or when the Host
wrote a new HDR1 label, the virtual tape application determined that the expiration
date in the HDR1 label (xxxxxx) was outside of the range that can be converted to a
retention period by the virtual tape application. The application can process HDR1
expiration dates in the range Jan. 1, 2003, through Jan. 18, 2038.

System Messages
System Action: Processing continues. If the HDR1 date was prior to Jan. 1, 2003, the
virtual tape application regards the volume's expiration date to be Jan. 1, 2003. If the
HDR1 date was after Jan. 18, 2038, the application regards the volume's expiration
date to be Jan. 18, 2038. The only time a volume's expiration date is of any
consequence to the virtual tape application is if the file is being written to a WORM
filesystem. In this case, the file will be written in WORM mode with the modified
retention date.
DLm572E
Unable to calculate retention time for xxxxxx (out of range?)
Description: During opening of an existing virtual tape volume, or when the host wrote
a new HDR1 label, the virtual tape application was unable to convert the HDR1
expiration date (xxxxxx) to a retention period, for an unknown reason.
System Action: Processing continues. The virtual tape application treats the volume
as if no expiration date was specified in the HDR1. The only time a volume's
expiration date is of any consequence to the virtual tape application is if the file is
being written to a WORM filesystem. If the virtual tape application is configured with a
default retention value, the default retention period will be used. Otherwise, the
retention is treated as zero (no retention) and the file will written in non-WORM mode.
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 purposes by
User Action: Verify the existence and properties of the directory. If this problem
persists, contact EMC Support for assistance.
DLm580E
Error getting <volser> file status; <error message>

System Messages
Description: During closing of a virtual tape file, an error occurred 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 recurs, contact EMC Support for
assistance.
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 recurs, contact EMC Support for
assistance.
DLm582I
Device <devicename> Volume <volser> made/left read-only
Description: This message is displayed when an output virtual tape volume written to
a WORM filesystem is unloaded and the volume has been made a read-only volume.
System Action: The virtual tape volume is now in read-only (WORM) mode.
User Action: None.
DLm590E
Device <devicename> Unable to calculate retention time for nD/M/Y (out of range?)
Description: While closing a volume that has no valid HDR1 expiration date, written to
a WORM filesystem, the virtual tape application was unable to calculate a valid
retention period based on the configured default retention period.
System Action: Processing continues. The virtual tape application regards the
volume's expiration date to be zero (no retention). In this case, the file will be written
in non-WORM mode because of this error.

System Messages
User Action: If the volume was to have been written in WORM mode, either correct the
HDR1 expiration date, or specify a valid default retention period value. If this problem
DLm591E
Device <devicename> Unable to set access time: <error message>
Description: While closing a volume written to a WORM filesystem, the virtual tape
application was unable to set the retention period in the file's "last access time".
System Action: Processing continues. The virtual tape application will attempt to write
the file in WORM mode anyway. If successful, the file will be locked with a permanent
retention period.
User Action: Refer to the èrror message' portion of this message to determine the
cause of the problem. If this problem persists, contact EMC Support for assistance.
DLm594W
Device <devicename> Volume <volser> configured FLR but no .FLR file found in
<pathname>
Description: The specified virtual tape drive is configured for EMC FLR support, but the
target directory does not contain a file named .FLR.
System Action: Processing continues. The virtual tape volume just written is not set to
a WORM state.
User Action: Be sure that the correct tape library is configured and the correct external
filesystem is mounted for this device. If you wish tapes to be locked with FLR, you
must create a file named .FLR in each FLR tape library directory.
DLm595W
Device <devicename> configured SnapLock and .SNAPLOCK found but <pathname> is
not a SnapLock directory
Description: The specified virtual tape drive and tape library directory are configured
for Network Appliance SnapLock support, but the virtual tape application has
determined that the target directory is not a SnapLock volume, because the virtual
tape file just closed did not stay Read-Only.
System Action: Processing continues. The virtual tape volume just written is not
protected from further modification.

System Messages
filesystem is mounted for this device.
DLm596W
Device <devicename> configured SnapLock but no .SNAPLOCK file found in
<pathname>
Description: The specified virtual tape drive is configured for Network Appliance
SnapLock support, but the target directory does not contain a file called .SNAPLOCK.
SnapLock'ed.
filesystem is mounted for this device. If you wish tapes to be SnapLock'ed, you must
create a file called .SNAPLOCK in each SnapLock directory.
DLm597W
Device <devicename> Volume <volser> configured FLR and .FLR found but <pathname> is
not an FLR directory
Description: The specified virtual tape drive and tape library directory are configured
for FLR support, but the DLm application has determined that the target directory is
not an FLR filesystem, because the virtual tape file just closed did not stay Read-Only.
protected from further modification.
filesystem is mounted for this device.
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.
assistance.

System Messages
DLm612E
Device <devicename>, Volume <volser>: <message>
Description: The virtual tape application experienced an internal error, and will output
a detailed error message.
I/O request.
assistance.
DLm614E
Device <devicename>, Volume <volser>: could not get hint for block: nnnn
Description: The virtual tape application was unexpectedly unable to find an entry in
an index of block IDs while performing a LOCATE.
System Action: The virtual tape application returns an error status to the Host's
LOCATE request.
assistance.
DLm631E
Device <devicename>, Volume <volser>: could not find block nnnn
Description: The virtual tape application was unable to locate a block specified in a
LOCATE request.
System Action: The virtual tape application returns an error status to the Host's
LOCATE request.
assistance.
DLm636I
Database timeout set to N seconds
Description: Normal response to an operator 'SET DBTIMEOUT=N' command.

System Messages
System Action: The specified database timeout was changed.

User Action: None.
DLm637W
FIND command not supported for PATH-TYPE paths; skipping.
Description: The FIND command does not currently support this PATH-TYPE.
System Action: The FIND command does not query paths of the specified type.
User Action: None.
DLm660I
Device <devicename>, Volume <volser>: For Unisys only, trying again as SCRTCH
Description: The Host requested mounting of volume <volser>, but the volume does
not exist. For Unisys devices only, the virtual tape application will now perform a
SCRTCH mount request.
System Action: The virtual tape application 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.
assistance.
DLm674E
Device <devicename>, Volume <volser>: Bad path specified: full path(pathname)
Description: An internal error occurred while the virtual tape application was
attempting to construct a path name.
I/O request.

System Messages
assistance.
DLm676E
Device <devicename>, Volume <volser>: internal I/O error
Description: The virtual tape application experienced an internal I/O error.
I/O request.
assistance.
DLm677E
Device <devicename>, Volume <volser>: error while renaming tape to 'xxxxxx'
Description: An error occurred while changing a tape's volser.
I/O request.
assistance.
DLm678E
Device <devicename>, Encryption/decryption failed
Description: An error occurred while encrypting or decrypting data.
I/O request.
assistance.
DLm679E
Cannot set FIPS mode for encryption
Description: The initialization of FIPS-mode-certified encryption failed.

System Messages
System Action: The virtual tape application initialization terminates.

assistance.
DLm680E
Device <devicename>, Volume <volser>: internal I/O error while (un)reserving volser
'xxxxxx'
Description: An error occurred while performing a distributed lock or unlock on a
virtual tape.
I/O request.
assistance.
DLm681E
Device <devicename> <path-type> path 'path' specified, but no valid <path-type>
license file exists.
Description: A Centera or HCAP path was encountered, but there is no license for that
feature.
System Action: The virtual tape application will not accept mount requests on this
path.
User Action: If the virtual tape application should be licensed for this feature, contact
DLm682E
Device <devicename> unable to initialize VirtualFile path 'path'
Description: An error occurred while determining the Centera or HCAP path.
System Action: The virtual tape application will not accept mount requests using the
indicated path.
User Action: Ensure that the indicated path is correctly configured. If the problem

System Messages
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 virtual tape application 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.
assistance.
DLm685E
unable to initialize path 'pathname': error message
Description: An error occurred while setting the specified path.
System Action: The path is not changed.
assistance.
DLm686I
Device <devicename> Distributed Lock Mgr informational message <message>
Description: An error occurred while setting the specified path.
User Action: Examine message, contact EMC Support for assistance.

System Messages
DLm687I
Enhanced FS move volume method is: <method>
Description: The enhanced FS will use the displayed method when moving a volume.
User Action: None.
DLm688I
Enhanced FS move for volumes in <FLR/GR> tape libraries: <enabled/disabled>
Description: The enhanced FS move feature will be disabled for the file system type if
selected as disabled or will use the efsmove method chosen for all file systems
when selected as enabled
User Action: None.
DLm701E
Device <devicename> Data Exchange Feature not licensed, mount 'volser' ignored
Description: Mounting of a flat file (data exchange) volser was requested, but this
controller 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
flat file / data exchange feature, you must obtain a license for this feature. Contact
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 virtual tape
application tried to delete it. An I/O error occurred during the attempt to delete.
System Action: The volume may or may not have been deleted from the tape library.
User Action: The 'error message' portion of this message describes the error that
occurred. Correct the error.

System Messages
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 virtual tape library.
User Action: None.
DLm714E
Device <devicename> too many trailer labels!
Description: The virtual tape application 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.
DLm715E
Device <devicename> data in trailer labels!
Description: The virtual tape application received a non-label data record while
processing the trailer labels for a standard labeled flat file.
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 virtual tape 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.

System Messages
DLm724E
Device <devicename> read backwards/previous in flat file
Description: The virtual tape 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 reading.
DLm766E
Device <devicename> file 'filename' already exists [as scratch]
Description: The Host wrote a HDR1 label to a flat file volume, and the virtual tape
application attempted to change the volume's filename from VOLSER.FLAT to
VOLSER.DATASETNAME.FLAT (where DATASETNAME is the dataset 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 dataset name in the JCL for the new
output file.
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 virtual tape
application attempted to change the volume's filename from VOLSER.FLAT to
VOLSER.DATASETNAME.FLAT (where DATASETNAME is the dataset name from the
HDR1 label), but an error occurred during the renaming.
User Action: Refer to the 'error message' portion of this message to determine the
reason for the error.
DLm770E
Cannot set RSA mode for encryption
Description: The initialization of RSA mode encryption failed.

System Messages

assistance.
DLm771E
Cannot get RSA key for decryption
Description: The request for an RSA decryption key failed.
System Action: The Host read is canceled with a unit check.
User Action: Confirm that the proper keys are installed in the RSA key manager, and
that the key manager is accessible from the controller, and that the access certificates
are valid.
DLm772E
Cannot get RSA key for encryption
Description: The request for an RSA encryption key failed.
User Action: Confirm that the proper keys are installed in the RSA key manager, and
that the key manager is accessible from the controller, and that the access certificates
are valid.
DLm773E
Cannot use KEY= with RSA encryption
Description: Cannot use non-RSA along with RSA encryption.
System Action: The KEY= directive is rejected.
User Action: Note that only RSA keys can be configured when the RSA key manager is
in use.
DLm774I
KEYCLASS set to [class|NONE] for device <devicename>
Description: Key class 'class' will be used for encryption on device <devicename>, or if
'NONE' is specified, no encryption will be done on device <devicename>

System Messages
System Action: The specified encryption key class (or none, for 'NONE') will be used
for any blocks written to the specified device.
User Action: None.
DLm775E
Cannot encrypt a tape with more than one key on device <devicename>
Description: Two different keys were attempted to be used for encryption on device
<devicename>
User Action: Use the key that was previously used to encrypt data for this tape.
DLm776E
Cannot stop RSA key module
Description: The attempt to stop the RSA key module failed.
DLm777E
RSA encryption is not available
Description: RSA encryption is either not licensed, not configured, or had an error
during initialization.
System Action: Check the logs for encryption initialization errors.
User Action: Depending on the cause of the error, either obtain a license for RSA
encryption, configure RSA encryption properly, or if there is an initialization error,
DLm778I
Reusing encryption key for device <devicename>
Description: The tape includes a previously encrypted data set, and another data set
is being added, so the previous key will be used for this new data set.
System Action: The previous key is used for the new data set.
User Action: None

System Messages
DLm779I
Not encrypting on device <devicename>
Description: The tape has prior unencrypted data set(s), so this new appended data
System Action: set will not be encrypted.The new data set is written unencrypted.
User Action: None
DLm780E
Restarting RSA peer process
Description: The RSA peer process has exited or become inactive, and needs to be
restarted.
System Action: The RSA peer process is restarted.
User Action: None
DLm781W
Device <devicename> is open as a read only tape
Description: The volume on the physical tape drive is mounted in read-only mode.
System Action: The tape is mounted in read-only mode.
User Action: In order 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.
System Action: The command is ignored.
User Action: Operator intervention is required to issue this command at the physical
tape device.
DLm783W
Device <devicename> tape door is open
Description: The physical tape drive door is open.

System Messages
System Action: The system cannot mount the tape.

User Action: Physically close the tape door.
DLm785W
Device <devicename> Read Buffer too small
Description: The data block read from the physical tape is larger than the maximum
supported by the virtual tape application.
System Action: An error status (equipment check) is returned to the host.
User Action: The tape is not compatible with the virtual tape application because of
the large block(s) it contains.
DLm786E
Device <device name> Failed to Open <device path>
Description: The physical tape drive is not accessible.
System Action: The virtual tape application will not communicate with this tape
device.
User Action: The tape most likely requires manual intervention.
DLm787E
Device <devicename> Unable to set Compression ON/OFF errno <error message>
Description: The physical tape drive did not accept the compression command.
System Action: Data written to this tape device will not be compressed.
DLm788E
Device <devicename> SCSI block #nnn too large (xxxxxx) to handle <operation>
(max=yyyyyy)
Description: The virtual tape application has received a tape block from the host with
a size ('xxxxxx') that is larger than the maximum tape blocksize ('yyyyyy') that can be
presented to the physical tape drive.

System Messages
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: The virtual tape application will continue, but the specified command
cannot be performed.
User Action: Determine that the attached device is a supported device type.
DLm790I
ST driver version info: <description>
Description: This message displays the version number of the st (SCSI tape) driver.
User Action: None.
DLm791I
BTISMC driver version info: <description>
Description: This message displays the version number of the btismc (SCSI Media
Changer) driver.
User Action: None.
DLm795I
Device <devicename> ready
Description: This message displays when a physical tape drive assigned to a 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

System Messages
Description: This message displays when a physical tape drive assigned to a virtual
tape device transitions from ready to not ready.
System Action: None. The drive will appear not ready to the host.
User Action: None.
DLm797E
Device <devicename> can not <command> 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 corefile 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 corefile of the virtual tape application has been saved to
the specified file.
User Action: None.

System Messages
DLm810E
Command failed: command: <error message>
Description: The virtual tape application 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.
DLm812E
<command> feature is not licensed
Description: The specified command requires a feature that is not licensed for use on
this controller.
feature.
DLm813E
Command <command> is not permitted
Description: The specified command is not permitted by the virtual tape application
configuration.
User Action: Refer to configuration documentation for instructions about how to
activate this command.
DLm814E
Parameter #n 'keyword=value' is not a valid VOL= or DEV= parameter
Description: Syntax error on an operator command.
User Action: Use the 'Help' command to see the proper command syntax.
DLm815E
Parameter n 'value' is not a valid VOLSER or synonym

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 reenter the command.
DLm817E
Parameter n 'keyword=value' is not a valid parameter
DLm818E
Invalid device name 'value' specified (too long)
Description: The <devicename> specified in an operator command is invalid.
DLm819E
Unknown device name 'value' specified
Description: The <devicename> specified in an operator command is invalid.
DLm820E
No devicenames match 'devicenames'

System Messages

DLm821I
MediumSense23 set to ON/OFF for device <devicename>
Description: By default, a value of 0x24 (enhanced cartridge) is returned to a host
media sense CCW. In very rare situations a host application might have a problem with
this value. (SPXTAPE is one known program with this issue.) In this case, a
configuration option can be used to return a 0x23 value (non-enhanced cartridge) in
the media sense data.
User Action: The SET MEDIUMSENSE23=YES/NO command can be used to change this
value if required. Contact EMC Support for more assistance with this option.
DLm822I
Guaranteed Replication refresh on Sync set ON/OFF
Description: Guaranteed Replication can be configured to perform a replication
refresh at every tape sync point as well as at close time. This message displays the
current setting of that option.
System Action: If ON, Guaranteed Replication (if enabled and writing to a GR-enabled
filesystem) will perform a refresh every time the virtual tape file is sync'ed to disk.
User Action: None.
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

System Messages
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 in UNREADY first.
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

System Messages
DLm832E
Invalid <parameter> value specified
Description: Syntax error on an operator command. Cannot set the same SCSI path to
all devices
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.
DLm839E
unable to assess space for <path> (nnn)
Description: The virtual tape application 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 within the tape library are mounted and
accessible. If the problem persists, contact EMC Support for assistance.
DLm840I
Read-back write verification set to ON/DATA/OFF

System Messages
Description: The Write Verification option is set to the specified value.

System Action: When the Write Verify feature is set to ON or DATA, after every
synchronization of data to the virtual tape during a write, 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 synchronization. ON checks just the
headers of every block, DATA checks the integrity of all the data as well.
User Action: None.
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.
DLm843I
Filesystem stall detection threshold set to nnn minutes
Description: By default, a filesystem that has had uncompleted I/O pending for more
than 5 minutes is considered "stalled". The time period for which a filesystem is
considered stalled is configurable with the "SET StalledFilesystemThreshold=nnn
command, or in the configuration file with the "StalledFilesystemThreshold nnn"
option.
System Action: A stalled filesystems will be skipped when searching for a virtual tape
during a mount request. When the stalled I/O completes, the filesystem will once
again be used during mounts.
User Action: The default value of 5 minutes should be more than enough time to
detect a stalled filesystem. Contact EMC Support before changing this value.

System Messages
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
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 the application will
report the OSADDR value to BTIMOUNT when it completes a mount on "ANY" drive.
User Action: None.
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
Checking of stored CRC values is ON/OFF
Description: When this option is ON, the CRC value stored for each tape block will be
confirmed when the file is read. When this option is OFF, the stored CRC value will not
be confirmed when the file is read.
User Action: None.

System Messages
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 change takes effect immediately.
User Action: None.
DLm849I
Storing of CRC values is ON/OFF
Description: When this option is ON, the CRC value is stored for each data block
written to the file. When this option is OFF, the CRC value for each data block will not
be written to the file.
User Action: None.
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.
DLm851I
ProtectVOL1 set ON/OFF
Description: By default, the virtual tape application prevents overwriting of VOL1
labels with data (ProtectVOL1=ON). The ProtectVOL1 feature can be disabled by
entering the command "SET ProtectVOL1=OFF"; when off, it can be re-enabled with
"SET ProtectVOL1=ON". The current ProtectVOL1 setting can be determined by
entering the "QUERY ALL" command.
System Action: When the ProtectVOL1 feature is enabled, any attempt by the host to a
VOL1 label with data is rejected with a unit check, with command reject sense.
User Action: None. It is recommended that the ProtectVOL1 feature be left enabled to
protect against accidental corruption of tape volumes by errant mainframe software.

System Messages
DLm852I
Full-erase set ON
Description: The virtual tape application 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 virtual tape application 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 will be 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 unchanged from the previous value.
DLm855E
SCSI Tape Device <device path> does not exist
Description: The device path requested does not exist.

System Messages

DLm856I
nn scratch synonyms: volser,volser,...
Description: This message 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 virtual tape application.
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 will take effect immediately after the current
volume is unmounted.
User Action: None.
DLm859I
Device <devicename> Data path changed from 'oldpath' to 'newpath'
Description: The operator SET PATH= command was accepted.
System Action: The new data path will take effect immediately on the specified virtual
tape drive.

System Messages
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 virtual tape application supported a choice
between using PATH= or DEV= 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 DEV= 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 volume serial number of 'SCRTCH' or
'PRIVAT', or beginning with 'BFL'. BFLxxx volsers are reserved for Data Exchange
("flat") volumes, which cannot be pre-initialized. Scratch volumes should be
initialized with the actual volsers 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'.
DLm863E
SCSI Tape path already in use
Description: The SET PATH command has failed.

System Messages

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. Be 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: During processing of an INITIALIZE command, the specified volume was
found to already exist in the tape library, as either a scratch or a non-scratch volume.
System Action: The new scratch volume is not created, and the original volume is
unchanged.
User Action: Do not attempt to 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: Refer to the èrror message' portion of this message for an explanation of
the error. Correct the error and try initializing the volume(s) again.
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.

System Messages
User Action: Refer to the èrror message' portion of this message for an explanation of
the error. Correct the error and try initializing the volume(s) 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/or re-enter the correct INITIALIZE command.
DLm869I
nn Standard/ANSI-labeled volumes initialized
Description: The virtual tape application 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 only be initialized in tape libraries on direct-access
filesystems.
User Action: Specify a DEV=device that has a tape library defined on a valid
direct-access filesystem.
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 virtual
tape application should resend an asynchronous "Ready" interrupt should it be
rejected by the channel or Host. The default number of retries is 45.

System Messages
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 twelve 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 to which channel path(s) the virtual
tape application should send a "Ready" interrupt when a virtual tape drive comes
ready. The possible values are:
PATHGROUP - the interrupt is sent to every channel path which currently has a
pathgroup ID (PGID) set, but only once per unique PGID (i.e. once per LPAR). This
is the default action. A PGID is typically set by a Host to a value unique to every
LPAR when a path is VARY'ed online.
REQUESTER - the interrupt is sent only on the channel path from which the Load
Display mount request was received.
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.
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;
User Action: None. Changing this setting from the default value may cause problems
with lost Ready interrupts. Contact EMC Support before changing this value.
DLm874E
Setting <parameter> requires a DEVICE= parameter too
Description: The operator SET command was entered without specifying a specific
device to be set.

System Messages
System Action: The <parameter> specified is ignored

User Action: This particular SET command <parameter> requires that a DEVICE=
parameter be specified; re-enter 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 controller 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 virtual tape application will proceed 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.
DLm877I
Support for VSE Host Utilities disallowed/allowed
Description: This virtual tape system was configured or SET to support the supplied
VSE Host Utilities. This option should only be set if the supplied VSE utilities will be
used; the default mode is to disable this support.
System Action: If the message says 'allowed', the supplied VSE Utilities will be
supported by this virtual tape system. If the message says 'disallowed', the supplied
VSE Utility programs will fail with command-reject I/O errors.
User Action: If you want to use the supplied VSE Utilities, enable this option;
otherwise, leave this feature off by default.

System Messages
DLm878I
<debugging feature enabled / disabled / not enabled: message>
Description: A special debugging feature was enabled or disabled through
configuration or with the SET command, or the SET command was rejected due to an
error.
System Action: The effect depends on the feature.
User Action: Special debugging features should only be enabled under direction of
EMC Support.
DLm879I
[Device <devicename> / ALL devices / TAPELIB path] quiesced/unquiesced
Description: The QUIESCE or UNQUIESCE command was entered.
System Action: A quiesced device is in a state where it will not accept any new tape
mounts until it is explicitly unquiesced (or until the virtual tape application is
restarted). If a drive has a volume mounted at the time it is quiesced, it will continue
to function completely normally; it will not accept another mount once the current
volume is unloaded. A quiesced tape library is in a state where it will not be available
for any new tape mounts until it is explicitly unquiesced (or until the virtual tape
application is restarted).
User Action: None.
DLm880I
GroupAccess set to 'R'
Description: By default, virtual tape files are only accessible by the 'vtape' user. This
message signifies that this controller is currently configured to allow other members
of the 'vtape' user group to have Read access to the virtual tape files created by this
node.
System Action: All tapes created while this option is set will have group accessibility.
User Action: Reconfigure this controller if you do not wish other members of the
'vtape' group to have access to virtual tape files. Files that were created while this
option was set will continue to be accessible by all members of the 'vtape' group
unless the file permissions are manually changed by the administrator.

System Messages
DLm881I
OtherAccess set to 'R'
Description: By default, virtual tape files are only accessible by the 'vtape' user. This
message signifies that this controller is currently configured to allow any user to have
Read access to the virtual tape files created by this node.
System Action: All tapes created while this option is set will have global accessibility.
User Action: Reconfigure this controller if you do not wish everyone to have access to
virtual tape files. Files that were created while this option was set will 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.
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.

System Messages
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.
DLm886I
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.
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 system 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 controller will report 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 lower case alphabetic characters.
System Action: The specified serial number is accepted, and will be 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, enter the command again with the proper value.

System Messages
DLm889E
Encryption key n is not available
Description: The specified encryption key is not installed on this system.
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 virtual tape application command 'HELP something' was entered, but
'something' is not a valid virtual tape application command or message number.
User Action: Use the 'Help' command alone to see a summary of the virtual tape
application commands available.
DLm891E
Invalid command syntax
Description: The preceding operator command was invalid.
DLm892I
Write Sync set to <nnnnnn> bytes
Description: The virtual tape application has been configured to sync (flush) data
written by the host to disk storage every <nnnnnn> bytes. This message is displayed
whenever the option is changed, and in response to the QUERY ALL command.
System Action: The virtual tape application will flush the data to disk storage every
<nnnnnn> bytes (in addition to any syncs requested by the host). No extra syncs will be
performed the <nnnnnn> value is 0.
User Action: For best performance, this option should be left at the default value.
DLm893E
<feature> feature not yet supported

System Messages
Description: The preceding operator command used a virtual tape application feature
that is not supported.
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.
DLm895E
CLASS/DIR parameter is only valid on an EFS system
Description: The operator INITIALIZE command specified a CLASS or DIR parameter
but this system is not configured for Enhanced File System (EFS). CLASS and DIR are
only valid on EFS systems.
System Action: The INITIALIZE command is rejected.
User Action: Enter the INITIALIZE command without a CLASS and/or DIR parameter.
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.

System Messages
DLm897E
Unexpected keyword parameter n 'keyword=value'
Description: Syntax error on an operator 'Load' command.
DLm898E
Unknown parameter n 'something'
DLm899I
<Thread> has been in state: <thread state> for <time> seconds
Description: The specified task has been in the specified state an unexpectedly long
time. This most likely means that the task is "stuck" on some operation.
System Action: When the task is no longer in this state, message DLm900I will be
displayed.
User Action: If these messages occur frequently, or the task does not transition back
to normal, contact EMC Support for assistance.
DLm900I
<Thread> transitioned state
Description: The specified task was previously reported to be in a single state for an
unusually long time (see DLm899I). This message is displayed when the task is no
longer in that state.
User Action: None.
DLm901E
Error reading Keyboard Data: <error message>
Description: An I/O error has occurred while reading a command from the keyboard.

System Messages
System Action: The virtual tape application terminates.

DLm902E
Zero Bytes read from Keyboard
Description: An I/O error has occurred while reading a command from the keyboard.
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 will be sent to the SNMP agent as is, but might not be
perfectly formatted.
DLm910W
Device <devicename> <deliberate error message>
Description: This message immediately precedes a deliberate error performed by the
virtual tape application, caused by setting a debugging mode for testing purposes.
System Action: A deliberate error of some kind will follow this message.
User Action: None. Don't be surprised by the error that follows. If you get this message
unexpectedly, contact EMC Support for assistance.
DLm911W

System Messages
DLm912W
DLm920E
Device <devicename> volume <volser> overwriting of VOL1 label blocked
Description: The virtual tape application prevented overwriting of this tape's VOL1
label with data, because the ProtectVOL1 feature is currently enabled.
System Action: The host write command is rejected with a unit check, with command
reject sense.
User Action: The ProtectVOL1 feature can be disabled by entering the command "SET
ProtectVOL1=OFF"; when off, it can be re-enabled with"SET ProtectVOL1=ON".
DLm921I
Set ProtectVol1=OFF to enable VOL1 overwrites
Description: This message follows DLm920E as a reminder that the ProtectVOL1
feature can be turned off if overwriting a VOL1 label with data is desired.
User Action: The ProtectVOL1 feature can be disabled by entering the command "SET
ProtectVOL1=OFF"; when off, it can be re-enabled with "SET ProtectVOL1=ON".
DLm930I
Device <devicename> in contingent allegiance to <pathinfo> for <time> seconds
Description: A "contingent allegiance" is established between a device and the host
from the time any unit check is presented to the host until the host performs a sense
or other I/O operation to this device, or a selective reset or a system reset to this
device, on the same channel path. Until the allegiance is cleared, this device will
remain busy and will be unavailable for I/O on all other channel paths. This
informational message will be displayed if a device remains in this type of contingent
busy condition for an inordinate amount of time.

System Messages
System Action: Until the host clears the contingent allegiance on the specified path,
no I/O can be performed on this device.
User Action: If these messages occur frequently, or the drive does not transition back
to normal, contact EMC Support for assistance.
DLm940I
Device <devicename> Volume <volser> accommodated old-style AMDD DSS block
#nnnnnn
Description: Earlier virtual tape application releases could write incorrect metadata in
a virtual tape block under certain specific rare conditions. Subsequent reading of such
a block would result in a DLm341E CRC error message and return an error to the host.
Later 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.
User Action: None.
DLm950I
Message from Host
Description: A Host program has sent this message to be displayed on the virtual tape
application console.
User Action: None.
DLm951I
Message from another program
Description: An external program has sent this message to be displayed on the virtual
tape application console.
User Action: None.
DLm952E
Unable to get hostname: <error message>

System Messages
Description: The application was unable to get the hostname of the system.
System Action: The DLm application terminates.
User Action: Verify that the hostname of the system is set correctly. Contact EMC
Support for assistance.
DLm953I
Locking with .lk lock files turned ON/OFF
Description: By default, .lk lock files are used to lock virtual tape files against
concurrent usage by any other node. The application can be configured to not use .lk
lock files at any time.
System Action: If OFF, no .lk lock files will be used to lock virtual tape files. If Virtuent
is configured to not use NLM locking for NFS filesystems (see message DLm957I, or
Virtuent is configured to use NLM locking but the tape library filesystem is mounted
with NLM file locking disabled (-o nolock), there will be NO locking of the virtual tape
files while they are in use, and corruption may occur if another system uses the same
files at the same time.
User Action: Turning off the .lk lock files feature is NOT recommended. Contact EMC
Support for more information before turning off .lk lock file locking.
DLm957I
Locking with NLM lock manager turned ON/OFF
Description: By default, virtual tape files on Celerra NFS filesystems are locked against
concurrent usage by other nodes by using the Network Lock Manager (NLM) protocol
(and .lk lock files for all other filesystems). The application can be configured to not
use NLM and to instead use .lk lock files for virtual tapes on all types of filesystems.
System Action: If NLM locking is turned OFF, all locking of virtual tape files is
performed with .lk lock files. If NLM locking is turned ON, files on Celerra NFS
filesystems are locked with NLM, and with .lk files on all other types of filesystems.
User Action: Contact EMC Support for more information before changing file locking.
DLm963I
Locking of Celerra files with .lk lock files turned ON/OFF

System Messages
Description: By default, .lk lock files are used to lock virtual tape files against
concurrent usage by any other node. The application can be configured to not use .lk
lock files for files that reside on Celerra filesystems.
System Action: If OFF, no .lk lock files will be used to lock virtual tape files that reside
on Celerra filesystems. If Virtuent is configured to not use NLM locking for Celerra
filesystems (see message DLm957I) or Virtuent is configured to use NLM locking but
the Celerra filesystem is mounted with NLM file locking disabled (-o nolock), there will
be NO locking of the virtual tape files while they are in use, and corruption may occur
if another system uses the same files at the same time.
User Action: Turning off the .lk lock files feature for Celerra filesystems is NOT
recommended. Contact EMC Support for more information before turning off .lk lock
file locking for Celerra filesystems.
DLm970I
FTIDC Parameter Set ON/OFF
Description: The controller has been configured for FTIDC.
System Action: When set ON, the system will not check if a different VOL1 label
volume serial number is being written on writes.
User Action: None.
DLm971E
Error closing input/output fifo: <filename>
Description: The virtual tape application received an error while closing the specified
file. This error can only happen during program termination.
DLm972E
Error deleting input/output fifo: <filename>
Description: The virtual tape application received an error while closing the specified
file. This error can only happen during program termination.

System Messages
DLm975I
Diagnostic data written to file '<file>' (<num> bytes)
Description: The diagnostic data was written to <file>
User Action: None.
DLm976E
Error writing diagnostic data dump file '<file>': open error <error detail>
Description: The diagnostic data could not be written to <file>.
DLm979E
Error writing diagnostic data dump file '<file>': open error <error detail>
Description: The diagnostic data could not be written to <file>.
DLm980E
Program Check error in thread nnnn (processname), state=XXXXXXXX
Description: An internal program error has occurred.
System Action: The virtual tape application attempts to shut down all virtual devices.
All devices are taken offline to the Host, and the virtual tape application terminates.
DLm981E
Program Check type 'error type'
Description: An internal program error has occurred.
System Action: The virtual tape application will terminate.

System Messages
DLm990I
Shutting down this application...
Description: The virtual tape application is terminating.
User Action: None.
DLm991E
Error shutting down device <devicename>
Description: An error occurred while attempting to shut down a virtual device.
DLm992W
<n> [RUN processes running | volumes mounted]; use vtd force to shutdown
Description: The 'vtd stop' command was entered while one or more virtual tape
drives had a volume mounted, and/or one or more RUN processes were running.
System Action: The 'vtd stop' command is ignored.
User Action: Before shutting down, wait for all Host applications to finish and unload
their tapes, and for all userscripts being executed by RUN commands to complete. If
for some reason the Host cannot unload all of the virtual tape devices, manually
unload all virtual tape volumes with the virtual tape application 'UNLOAD' command.
If, for some other reason, the 'UNLOAD' command cannot unload all the virtual tape
devices, or userscripts being executed with the RUN command will not terminate, the
'vtd force' command will force a shutdown even while tapes are mounted or
userscripts are running.
DLm994E
Required service <service name> failed, unrecoverable <error detail>
Description: A required system service has failed and is unrecoverable.
User Action: Determine why the service has failed and correct it. For more assistance,
contact EMC Support.

System Messages
DLm995E
SCSI Error Detected
Description: A SCSI Error has been reported in the /var/log/messages file.
User Action: Determine why the SCSI Error occurred and correct it. For more
assistance, contact EMC Support.
DLm996E
NFS Server Timeout Detected
Description: An NFS server timeout has been reported in the /var/log/messages file.
User Action: Determine why the NFS server timeout occurred and correct it. For more
assistance, contact EMC Support.
DLm997E
NMI Detected
Description: A NMI has been reported in the /var/log/messages file.
User Action: Determine why the NMI occurred and correct it.For more assistance,
contact EMC Support.
DLm999E
Terminating app
Description: The application is terminating because of some kind of fatal startup
error.
System Action: The application terminates.
User Action: Review any preceding message(s) to determine the cause of the problem.
For more assistance, contact EMC Support.

System Messages
Call home messages

This section lists the EMC Call home messages.
Mgmt001E
ACP1 is not directly accessible from the base Celerra 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 Celerra 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.
Call home messages 363

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.

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 assistance in determining the cause of
this problem.
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 assistance in determining the cause of this problem.
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.
EMCvts messages 365

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.

System Messages
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.
DLMHOST messages
The following messages may be issued by the z/OS started task DLMHOST:
DLH000I
COMMANDS ARE:
STARTLOG,N=nodename/ALL
STOPLOG,N=nodename/ALL
STARTCMD,N=nodename/ALL
STOPCMD,N=nodename/ALL
N=nodename/ALL,C=command
HELP
STATUS
Issued in response to a help or ? command. Followed by a list of eligible commands.

◆ STARTLOG initiates/restarts logging from a single node or all nodes. Logging
device paths must already exist.
◆ STOPLOG terminates logging from a single node or all nodes.
◆ STARTCMD initiates/restarts the command path from a single node or all nodes.
◆ STOPCMD terminates the command path from a single node or all nodes.
◆ N=nodename C=command will pass the specified command to the designated
node. The response will go to the operator or to the file designated by DLMLOG if
parameter LOGFILE is used.
◆ HELP or ? will produce the DLH000I messages.
◆ STATUS will show the current status as indicated in DLH240I.
DLH001I
jobname ENTER COMMAND, EOJ, OR ? FOR HELP
If the WTOR option is used, this is issued as the outstanding WTOR that the operator
can reply to.
z/OS system messages 367

System Messages
DLH002I
jobname USE MODIFY TO ENTER COMMAND, EOJ OR ? FOR HELP
If the NOWTOR option is specified, this message indicates to the operator that the
MODIFY command is available to issue requests.
DLH003I
ENDING BY OPERATOR REQUEST
An EOJ or STOP command was processed.
DLH010I
I/O ERROR ON DEVICE XXXX: CSW=XXXX SENSE=XX
An error occurred on one of the control paths. Appropriate CSW and sense data are
provided. The control path will be marked as inactive.
DLH030I
CONFIG FILE FAILED TO OPEN
The file pointed to by the DLMCFG DD failed to open.
DLH035I
CONFIG FILE HAS NO ENTRIES
An end of file was detected on the configuration file without any entries being
processed.
DLH040I
CONFIG FILE INVALID RECFM
The recfm of the DLMCFG file is not F or FB.
DLH050I
The file pointed to by the DLMLOG DD card failed to open
DLH055I
INPUT COMMAND FILE FAILED TO OPEN -IGNORING DOCMDS PARM

System Messages
If the DOCMDS parameter is used, the DLMCMD DD card is missing or file failed to
open.
DLH060I
CANNOT START - PROGRAM ALREADY ACTIVE
Only one copy of DLMHOST is allowed to run at a time. This can be overridden by
specifying parameter NOENQ
DLH150I
INVALID DEV SPECIFIED
One of the devices specified is not a tape device.
DLH160I
DEVICE NOT FOUND DURING UCBLOOK
The DEV= parameter is specified, but the device does not exist in the current
configuration.
DLH170I
ERROR DURING UCB CAPTURE/UNCAPTURE
An error occurred while capturing/uncapturing a 24-bit UCB address from a 31-bit

one.
DLH180I
DRIVE xxxx IS ALREADY ALLOCATED or BOXED
The designated device is already in use or is boxed
DLH181I
DRIVE xxxx HAS NO OPERATIONAL PATHS
The designated device is marked as having no operational paths.
DLH182I
WARNING – DRIVE xxxxx IS ONLINE. SHOULD BE OFFLINE WHEN USING DEV=
The control drive being used should be an offline device. Results are unpredictable if
an online device is used.

System Messages
DLH190I
DEBCHK FAILED
An error was detected while creating the device control blocks to access the device.
DLH200I
NODENAME NOT FOUND IN CONFIG TABLE
The nodename specified in a command/modify request does not exist in the config
table. Use the STATUS command to list the available nodenames.
DLH210I
INVALID DEVICE xxxx IN CONFIG TABLE
The specified device contains invalid hexadecimal digits.
DLH220I
NODENAME NOT SPECIFIED IN COMMAND
A command was entered, and did not contain a nodename as the target of the
command
DLH230I
NO COMMAND FOUND IN RESPONSE
There was no C= or CMD= in the operator request.
DLH240I
NODENAME CMDDEV LOGDEV CONSNAME
This will be followed by one line showing the status for each node, path and console
assignment.
◆ NODENAME is the name assigned in the config table.
◆ CMDDEV shows the device (if any) assigned as the command
◆ path. A y/n indicates if it is currently active.
◆ LOGDEV shows the device (if any) assigned as the log path. A
◆ y/n indicates if it is currently active.
◆ CONSNAME shows the console name (if any) assigned to receive

System Messages
◆ log messages from this node.
DLH250I
NODE nodename PATH xxxx INACTIVE
A command was requested to be issued to a command path that is marked inactive.
DLH260I
PROCESSING COMMAND: command line
The DOCMDS parameter was used. This lists each command processed from the
DLMCMD file as it is being processed.
DLMLIB message
The following message can be returned by the DLMLIB program running on the
mainframe.
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 running on the
mainframe.
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.

System Messages
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.
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
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

System Messages
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.
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

System Messages
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.
DLS181I
DRIVE HAS NO ONLINE PATHS

System Messages
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
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
Healthcheck messages
This section lists the healthcheck messages generated on the DLm system.
DLmT00E
ACP Failed to Respond to System Health Check Request.
DLmT01E
ACP is operating in degraded mode. Unknown error.
DLmT02E
FLR File System Status Check Failed.
DLmT03E
SSH Keys Check Failed.
DLmT04E
NFS Mounts Status Check Failed.
DLmT05E
DLm ACP Required Services Status Check Failed.
DLmT06E
GR Status Check on Celerra Failed.
DLmT07E
VNX Capacity Check Failed.
DLmT10E
VTE Failed to Respond to System Health Check Request.

System Messages
DLmT11E
VTE is operating in degraded mode. Unknown error.
DLmT12E
DLm VTE Required Services Status Check Failed.
DLmT13E
DLm VTE Required Drives Status Check Failed.
DLmT14E
GR Status Check on VTE Failed.
DLmT15E
Data Mover Connection Check Failed.
DLmT20E
One GB Management Switch is not Responsive.
DLmT21E
One GB Management Switch Status Check Failed.
DLmT22E
All One-GbE Management Switche(s) are not Responsive.
DLmT23E
One-GbE Management Switch Connection Check Failed.
DLmT30E
Ten GB Data Switch is not Responsive.
Healthcheck messages 377

System Messages
DLmT31E
Ten GB Data Switch Status Check Failed.
DLmT32E
All Ten-GbE Data Switche(s) are not Responsive.
DLmT33E
Ten_GbE Data Switch Connection Check Failed.
DLmT40E
Data Domain System is not Responsive.
DLmT41E
Data Domain System Status Check Failed.
DLmT42E
All Data Domain System(s) are not Responsive.
DLmT43E
DD Management Path Connection Check Failed.
DLmT44E
DD Data Path Connection Check Failed.
DLmT45E
DD Capacity Check Failed.
DLmT50E
Celerra System is not Responsive.

System Messages
DLmT51E
Celerra System Status Check Failed.
DLmT52E
All VNX system(s) are not Responsive.
DLmT53E
VNX System Connection Check Failed.
DLmT98E
Unexpected Error.
Healthcheck messages 379

System Messages
VTEC errors that generate ConnectEMC events

DLm errors that generate ConnectEMC events are:
DLm015E DLm119E DLm326E DLm499W

DLm016E DLm121E DLm332E DLm506E
DLm055E DLm226W DLm471E DLm812E

System Messages

DLm074E DLm319E DLm991E
VTEC errors that generate ConnectEMC events 381

System Messages

INDEX
Numerics UNQUIESCE 171

3480, 3490, or 3590 UNREADY 172
configure devices 78, 116 z/OS operator 122
Direct Tape 99 connect
IDRC 123 FICON channel 26
Load Display command 176 considerations
Manual Tape Library 117 DDR 123
real 116, 121 DFSMShsm 123
size range 87 RMM 132
UIM 121, 122 TLMS 133
TMS 133
TSM 133
A ZARA 133
ACP
controls and indicators 23, 59
power down 68 D
status indicators Direct Tape 99
FICON 26 DLm
awsprint library utility 106 ASCII data/labels 177
AWSTAPE 174 command 124, 125, 135
compression 101
ENTER command 136
C label type 86
Channel Command Words 176 power down 63
Command power up 55
DFSMShsm 123 tape drive mapping 99
DISABLE 150 utility version reporting 125
EXPORT 150 DLMCMD utility 135
HELP 152 DLMSCR utility 127
IMPORT 153 documentation, related 13
INITIALIZE 153 Dynamic Device Reconfiguration considerations (DDR)
LOAD 155 123
poweroff 63
reboot 63
REWIND 164 E
SAVE TRACE 165 EMC publications 13
SET 165 EMC support website 13
SHOW 169
SNMP 170 F
statfmt 182 FICON
Syntax 150 connection 26
UNLOAD 171 status indicators 26

Index
format import command 153

AWSTAPE 174
Control Byte 178
U
EMC DLm message 192
utility
Load display data 178
DLm scratch 130
statfmt command 182
DLMCMD 135
DLMSCR 127
G DLMVER 124
GENSTAT utility 126 GENSTAT 126
I V
indicators VTE
FICON 26 configuring virtual device 79
controls and indicators 20
power down 64
L
Library utility, awsprint 106
Z
z/OS
M
compaction of the virtual tape data 123
message
configuring the devices 116
class 192
Load display message 176
DLm system 193
Missing Interrupt Handler 122
DLMCMD 366
operator command 122
DLMLIB 371
utilities 124
DLMSCR 371
EMC DLm 192
EMCvts 364
format 192
Format Control Byte 176
number 192
z/OS system 366
P
password
system 55
power down
ACP 68
VTE 64
Powerlink website 13
T
Tape
direct 99
export command 150
export/import utilities 102

h1902 Utilizing SNMP Cap Emc Disk Lib WP LDV

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

h1902 Utilizing SNMP Cap Emc Disk Lib WP LDV

Загружено:

Авторское право:

Доступные форматы

EMC® Disk Library for

Published November, 2012

2 EMC Disk Library for mainframe DLm8000 User Guide

Chapter 1 Overview of EMC Disk Library for Mainframe DLm8000

Chapter 2 DLm Operations

EMC Disk Library for mainframe DLm8000 User Guide 3

Halt the VNX VG8 server........................................................... 66

Chapter 3 DLm Administration

4 EMC Disk Library for mainframe DLm8000 User Guide

Chapter 4 SRDF Replication

Chapter 5 Mainframe Tasks

Chapter 6 z/OS Console Support

EMC Disk Library for mainframe DLm8000 User Guide 5

WTOR command examples..................................................... 148

Appendix A Virtual Tape Operator Command Reference

Appendix B AWSTAPE Information

Appendix C Load Display Command—CCW Opcode x'9F'

Appendix D Extract DLm statistics

6 EMC Disk Library for mainframe DLm8000 User Guide

Volume statistics ................................................................... 184

Appendix E System Messages

EMC Disk Library for mainframe DLm8000 User Guide 7

8 EMC Disk Library for mainframe DLm8000 User Guide

1 Front view of the VTE...................................................................................... 20

EMC Disk Library for mainframe DLm8000 User Guide 9

10 EMC Disk Library for mainframe DLm8000 User Guide

1 ACP rear panel connectors ............................................................................. 24

EMC Disk Library for mainframe DLm8000 User Guide 11

12 EMC Disk Library for mainframe DLm8000 User Guide

Note: This document was accurate as of the time of publication. However, as

EMC Disk Library for mainframe DLm8000 User Guide 13

◆ EMC Disk Library for mainframe Command Processors User Guide

Conventions used in this document

Note: A note presents information that is important, but not hazard-related.

14 EMC Disk Library for mainframe DLm8000 User Guide

EMC Disk Library for mainframe DLm8000 User Guide 15

| Vertical bar indicates alternate selections - the bar

Where to get help

16 EMC Disk Library for mainframe DLm8000 User Guide

Overview of EMC Disk Library for Mainframe DLm8000 17

Introduction to Disk Library for mainframe

18 EMC Disk Library for mainframe DLm8000 User Guide

Figure 1 Front view of the VTE

The VTE controls and indicators are as follows:

20 EMC Disk Library for mainframe DLm8000 User Guide

Figure 2 Rear view of a VTE

Note: You must connect both ACPs to your network.

22 EMC Disk Library for mainframe DLm8000 User Guide

Figure 3 Front view of the ACP

A. USB port B. Power button

AC power Mouse Com 1 Modem Eth 1 Eth 2 Eth 3 Com 2

USB ports (For USB disk, USB mouse

Figure 4 Rear view of the ACP

Table 1 ACP rear panel connectors

AC Power AC power. Connect an AC power cord between the AC power plug

Com 1 Modem for remote support and dial home capabilities.

Com 2 Serial connection from service laptop.

Eth 0 Connects to management switch port.

Eth 1 Customer network.

Eth 2 Connects to management switch port.

Eth 3 Customer network.

USB USB connection. Plug USB drive in here to upload or download

Video Use with KVM monitor.