EMC Disk Library for mainframe DLm960 - Dell EMC Spain · IPL from the stand-alone IPL tape........

DLm3.3_UG.3.3.book Thursday, July 12, 2012 3:30 PM

EMC® Disk Library for mainframeDLm960Version 3.3

User GuideP/N 300-013-389REV A01


Copyright © 2012 EMC Corporation. All rights reserved.

Published July, 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.

EMC Disk Library for mainframe DLm960 User Guide2

CONTENTS


Preface

Chapter 1 Overview of EMC Disk Library for Mainframe

Introduction to Disk Library for mainframe ..................................... 22 DLm 960 architecture .................................................................... 23

VTEC ........................................................................................ 23Backend storage...................................................................... 29Mainframe channel interfaces.................................................. 31

DLm devices and capacity.............................................................. 38Tape emulation........................................................................ 40Virtual tape drive states........................................................... 40Data formats............................................................................ 41

Support for physical tape drives .................................................... 42 High availability features of DLm960 ............................................. 43

VTEC ........................................................................................ 43Celerra server .......................................................................... 43Data Domain............................................................................ 45Expanded capacity on Data Domain DD880 ............................. 49

Features and benefits .................................................................... 50

Chapter 2 DLm Operations

Management access to DLm .......................................................... 54Gather connection data ........................................................... 54Access the DLm Console .......................................................... 55Access the ACP ........................................................................ 58Set date and time .................................................................... 63User administration ................................................................. 65Access a VTE............................................................................ 69VT console ............................................................................... 70VTE reboot ............................................................................... 72

Power up DLm ............................................................................... 72Celerra server power-up ........................................................... 73DD880 power-up ..................................................................... 75ACP power-up .......................................................................... 76VTE power-up........................................................................... 77

Power down DLm ........................................................................... 79

EMC Disk Library for mainframe Version 3.2 User Guide 3

Contents


VTE powerdown ....................................................................... 80DD880 powerdown .................................................................. 80ACP powerdown....................................................................... 81Halt the Celerra server ............................................................. 81Verify Control Station powerdown ............................................ 82Power down the CLARiiON storage array................................... 83ACP Power down...................................................................... 84

Start and stop tape devices ........................................................... 84 Support access to DLm .................................................................. 85

ESRS........................................................................................ 86Modem support ....................................................................... 86

Chapter 3 DLm Administration

Tape libraries................................................................................. 90DLm 2.x filesystem (Legacy)..................................................... 90DLm 3.x enhanced filesystem (EFS).......................................... 90Backward compatibility ........................................................... 93Initialize scratch volumes ........................................................ 93

Configure virtual devices................................................................ 97Planning considerations .......................................................... 97DLm configuration files ............................................................ 97Configure global parameters.................................................... 97Add devices........................................................................... 101Scratch synonyms.................................................................. 107Save configuration................................................................. 110Delete a device range ............................................................ 110

Manage configuration files .......................................................... 111Activate or install a configuration........................................... 111Create a new configuration .................................................... 112Copy a configuration.............................................................. 112Modify or delete a configuration ............................................ 112

Tape Erase................................................................................... 113Space erase policy................................................................. 113Time-to-Live erase policy ....................................................... 114Both ...................................................................................... 115

Manage VTE and ACP logs............................................................ 115VTE logs................................................................................. 115Support data ......................................................................... 116

Back-end tape support ................................................................ 118Direct Tape ............................................................................ 119Export to and import from tapes............................................. 121

DLm diagnostic reporting............................................................. 122

4 EMC Disk Library for mainframe Version 3.2 User Guide

Contents


VTEC ...................................................................................... 123ConnectEMC .......................................................................... 125Data Domain DD880 alert notifications .................................. 126

AWSPRINT library utility ............................................................... 126

Chapter 4 DLm Replication

Overview ..................................................................................... 128 Replication terminology............................................................... 130 Celarra replication ....................................................................... 132

Supported configurations ...................................................... 132Celerra replication procedure................................................. 133Celerra RepOutOfSyncHours feature....................................... 134DLm Celerra replication and disaster recovery........................ 134Tape catalog considerations .................................................. 137

Deduplication storage replication ................................................ 137Supported configurations ...................................................... 138Replication session setup...................................................... 138Throttling............................................................................... 139Recovery point ....................................................................... 139Recovery time ........................................................................ 139Disaster recovery in Data Domain systems............................. 140Directory replication flow ....................................................... 141

Replication between DLm3.x and DLm2.x systems....................... 142Prerequisites ......................................................................... 142Replication considerations .................................................... 143

Chapter 5 Guaranteed Replication

Overview of GR ............................................................................ 146Tape requirements for GR....................................................... 148

GR configuration.......................................................................... 148 Manage GR .................................................................................. 150

Verify GR configuration .......................................................... 150MIH considerations for Guarantied Replication ...................... 151

Chapter 6 DLm WORM Tapes

Overview ..................................................................................... 154WORM control file .................................................................. 154File locking for WORM ............................................................ 155Retention period.................................................................... 155

Configure WORM ......................................................................... 157


Contents


FLR ........................................................................................ 158FLRRET................................................................................... 159FLRMOD................................................................................. 159FLREXTENTS ........................................................................... 159

Determine if WORM is enabled..................................................... 160 Extend or modify a WORM tape.................................................... 161

Backward compatibility of modified (segmented) WORM tapes..... 162

Scratch WORM tapes ................................................................... 162

Chapter 7 Mainframe Tasks

Configure devices ........................................................................ 164 Real 3480, 3490, or 3590............................................................ 164 Manual tape library ..................................................................... 165 MTL considerations for VTE drive selection................................... 167 MTL-related IBM maintenance...................................................... 169 EMC Unit Information Module ...................................................... 169 Missing Interrupt Handler ............................................................ 170 Mainframe configuration for GR ................................................... 171 Mainframe configuration for deduplicated virtual tapes ............... 172 Dynamic device reconfiguration considerations ........................... 172 DFSMShsm considerations .......................................................... 173 Specify tape compaction ............................................................. 173 Locate and upload the DLm utilities and JCL for z/OS ................... 174

Downloading and using the DLm utilities and JCL for z/OS ..... 174GENSTATS utility .................................................................... 176DLm scratch utility program ................................................... 177DLMCMD utility program ........................................................ 184DLMVER utility program ......................................................... 187

Initial program load from a DLm virtual tape ................................ 189Create a stand-alone IPL tape on DLm .................................... 189IPL from the stand-alone IPL tape........................................... 190IPL considerations for DLm .................................................... 190

Chapter 8 Using DLm with Unisys

Unique DLm operations for Unisys mainframes............................ 192Autodetection........................................................................ 192Load displays ........................................................................ 192Mount "Ready" interrupt ........................................................ 192Query Config command.......................................................... 192Ring-Out Mount request......................................................... 193


Contents


Scratch request ..................................................................... 193 Configuring for Unisys.................................................................. 193

Device type............................................................................ 193Labels ................................................................................... 193Scratch tapes......................................................................... 193

Initializing tapes for Unisys.......................................................... 194 Configuring the mainframe for DLm.............................................. 195

Chapter 9 z/OS Console Support

z/OS Console operation............................................................... 198 DLMHOST .................................................................................... 198

Installing DLMHOST ............................................................... 198Running DLMHOST................................................................. 199DLMHOST configuration file ................................................... 200

Using z/OS Console support ........................................................ 201DLMHOST commands ............................................................ 202WTOR command examples..................................................... 204

Chapter 10 Data Encryption

Overview ..................................................................................... 206Mixed volumes in the same VTE ............................................. 206

How RSA Key Manager works with DLm ........................................ 207 Configure encryption on DLm....................................................... 208

Configure encryption when adding devices ............................ 209Configure encryption on existing devices ............................... 209

Appendix A Virtual Tape Operator Command Reference

Virtual Tape Operator command reference ................................... 212Syntax ................................................................................... 212CLOSE VSTATS PATH .............................................................. 212EXPORT.................................................................................. 212FIND....................................................................................... 214HELP...................................................................................... 214IMPORT.................................................................................. 215INITIALIZE .............................................................................. 215LOAD ..................................................................................... 217QUERY ................................................................................... 218QUIESCE ................................................................................ 226READY.................................................................................... 226REWIND ................................................................................. 227SAVE TRACE ........................................................................... 228


Contents


SET ........................................................................................ 228SHOW.................................................................................... 232SNMP .................................................................................... 232STARTVT ................................................................................ 233STOPVT.................................................................................. 233UNLOAD................................................................................. 234UNQUIESCE ........................................................................... 234UNREADY ............................................................................... 235

Appendix B AWSTAPE Information

AWSTAPE format .......................................................................... 238

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

Load display messages................................................................ 240Format Control Byte ............................................................... 240Messages 0 and 1.................................................................. 240

Load display data ........................................................................ 242Format Control Byte ............................................................... 242

Appendix D Extract DLm statistics

DLm statistics files ...................................................................... 246 Extraction utility .......................................................................... 246

Hourly statistics..................................................................... 247Volume statistics ................................................................... 248Mount statistics..................................................................... 249Unmount statistics ................................................................ 249Example 1.............................................................................. 250Example 2.............................................................................. 250Example 3.............................................................................. 252Example 4.............................................................................. 252

Appendix E System Messages

Message format........................................................................... 256 DLm system messages................................................................. 257 Call home messages.................................................................... 428 EMCvts messages........................................................................ 429 z/OS system messages................................................................ 431

DLMCMD messages ............................................................... 431DLMHOST messages.............................................................. 432DLMLIB message ................................................................... 436


Contents


DLMSCR messages ................................................................ 436DLMVER messages ................................................................ 440

Healthcheck messages ................................................................ 441 VTEC errors that generate ConnectEMC events ............................. 445

Index


Contents



Title Page

FIGURES


1 Front view of the VTE...................................................................................... 242 Rear view of a VTE.......................................................................................... 263 Front view of the ACP ..................................................................................... 274 Rear view of the ACP ...................................................................................... 275 24-port AT-9924TL switch .............................................................................. 296 Fujitsu XG2000R switch ................................................................................. 297 DD880 Controller—Rear view ......................................................................... 308 ESCON converter cable .................................................................................. 359 VTE to storage controllers — Network topology............................................... 4510 VTE to DD storage controllers — Network topology ......................................... 4611 Rear panel of a Gen 2 Control Station and an ACP .......................................... 5612 PuTTY session................................................................................................ 5913 ACP desktop with web browser ...................................................................... 6014 DLm Console login page ................................................................................ 6215 DLm Console ................................................................................................. 6316 DLm date and time......................................................................................... 6417 User ID creation ............................................................................................. 6618 LDAP user authentication............................................................................... 6819 VT console ..................................................................................................... 7020 SPS power switches on DLm960 .................................................................... 7321 DLm960 bay master power switches.............................................................. 7422 ES20 expansion shelf .................................................................................... 7523 Controller power buttons. .............................................................................. 7624 Front panel of the DLm960 ACP...................................................................... 7625 Front view of the VTE...................................................................................... 7726 EMC Secure Remote Support.......................................................................... 8627 Global options ............................................................................................... 9828 Control units................................................................................................ 10129 Add devices section..................................................................................... 10230 Scratch Synonyms ....................................................................................... 10831 Save configuration....................................................................................... 11032 System status.............................................................................................. 11533 VTE logs....................................................................................................... 11634 Gathering ACP and VTE support data............................................................ 11735 SNMP configuration ..................................................................................... 12436 Alert messages ............................................................................................ 12537 DLm replication ........................................................................................... 12938 Unisys Device Panel..................................................................................... 194

EMC Disk Library for mainframe DLm960 User Guide 11

Figures


39 Configuring for encryption............................................................................ 20640 AWSTAPE single disk file.............................................................................. 238

12 EMC Disk Library for mainframe DLm960 User Guide

Title Page

TABLES


1 ACP rear panel connectors ............................................................................. 282 DD880 stream count limits ............................................................................ 303 FICON adapter LED indicators ........................................................................ 324 Differences between the DLm models ........................................................... 385 Details of ESCON and FICON connections...................................................... 396 DLm system access details ............................................................................ 547 Control Station usernames and passwords .................................................... 558 Behavior of GR and non-GR devices ............................................................. 1479 Example of LIBRARY-ID and LIBPORT-ID ........................................................ 16610 Parameters in DLMSCR ................................................................................ 17811 DLMSCR report output messages ................................................................. 18012 Error code from DLMCMD ............................................................................. 18613 Load display data ........................................................................................ 24214 Format Control Byte ..................................................................................... 242


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 z/OS mainframe using disk storage systems in place of physical tapes. This guide provides information about the features, performance, and capacities of DLm 3.0 and later. It also includes installation and configuration information that is required for ongoing operation.

Audience This guide is part of the EMC DLm documentation set, and is intended for use by system operators to assist in day-to-day operation. Installation, configuration, and maintenance tasks must be accomplished by qualified EMC service personnel only.

Readers of this document are expected to be familiar with tape library operations and the associated tasks in the mainframe environment.

Relateddocumentatio

n

The following EMC publications provide additional information:

◆ EMC Disk Library for mainframe Physical Planning Guide

◆ EMC Disk Library for mainframe DLm960 Version 3.3 Release Notes

◆ EMC Disk Library for mainframe Command Processors User Guide

◆ Using Celerra Replicator (V2)

◆ Using SnapSure on Celerra


Preface


◆ 40U-C Cabinet Unpacking and Setup Guide

The EMC documents specified here and additional Celerra information are available in the EMC Online Support website.

The Data Domain documents specified here and additional Data Domain information are available in the Data Domain portal:

https://my.datadomain.com

Data Domain documentation is also available on the Data Domain documentation CD that is delivered with DD880.

Conventionsused in thisdocument

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


Preface


Where to gethelp

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.

Yourcomments

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:

[email protected]


Preface




CHAPTER 1Overview of EMC Disk Library for Mainframe

This chapter provides an overview of EMC Disk Library for mainframe. Topics include:

◆ Introduction to Disk Library for mainframe........................................................ 22◆ DLm 960 architecture ....................................................................................... 23◆ Tape emulation ................................................................................................ 40◆ Support for physical tape drives ....................................................................... 42◆ High availability features of DLm960 ................................................................ 43◆ Features and benefits....................................................................................... 50

Overview of EMC Disk Library for Mainframe 21

Overview of EMC Disk Library for Mainframe


Introduction to Disk Library for mainframeThe EMC® Disk Library for mainframe (DLm) family of products provides IBM System z mainframe customers the ability to replace their physical tape libraries, including traditional virtual tape libraries such as the IBM VTS and Sun/STK VSM, with dynamic tapeless virtual tape solutions, eliminating the challenges tied to traditional tape-based processing.

Some customers have already implemented mainframe host-based tape-emulation solutions such as IBM VTFM (formally known as CopyCross) and CA Vtape. However, these solutions utilize expensive host CPU cycles to perform the tape operations, and use expensive direct access storage device (DASD) space to keep the tape volumes. DLm provides the option for these customers to offload the tape emulation processes from the mainframe host and free up DASD space.

DLm works seamlessly with the mainframe environment, including the major tape management systems, DFSMS, DFHSM, and backup applications such as DFDSS and FDR, and others without the need to change any of the customer's JCL statements. There is no need to start a task or define a specific subsystem to operate DLm, since the mainframe host sees the DLm just as tape devices. DLm tape drives can be shared across LPARs without the need for additional tape sharing software through local device varying or through the implementation of MTL definitions.

DLm provides disaster recovery protection using bidirectional replication between two DLm systems in the same or different sites. It also supports unidirectional replication from one DLm system to up to four DLm systems that could be in different sites. Since the tape information is kept on disk, DLm enables you to perform disaster recovery tests without compromising your business continuance by having to stop replication during testing.

The DLm model DLm960 with the Data Domain DD880 offers deduplication features that deliver the aggregate throughput performance needed for enterprise data centers. This model's in-line deduplication provides the most efficient solution for storing virtual tapes for backup and archive applications. This results in lower storage costs and efficient use of replication links as only the unique data is transported between the sites.

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




DLm 960 architecture The major components of a DLm960 (with an optional DD880) system are the virtual tape emulation controller (VTEC) and the backend storage system. The backend systems supported by DLm960 are:

◆ EMC Celerra server with integrated disk storage arrays

◆ Data Domain® storage system (DD880)

DLm960 comes with one Celerra NS960 (base Celerra) by default. In addition, you can order an optional DD880 and an additional Celerra NS960 (expansion Celerra). DLm960 provides deduplicated storage using Data Domain systems and traditional disk storage using EMC Celerra systems.

Note: All new DD880s integrated into a DLm 2.4.0 or later support only 2 TB drives. However, DD880 systems that are already part of DLm 2.3.x systems and 1TB drives will continue to be supported even after the DLm has been upgraded to 2.4.0. The 1 TB and 2 TB drives should not be mixed in an ES20 shelf.

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:

◆ 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

VTEEach DLm configuration can have 1—6 VTEs. The mainframe virtual tape emulation software, Virtuent, executes on the VTEs. Each VTE is connected to the mainframe through two FICON or three ESCON 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.

DLm 960 architecture 23



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

Disk 1Disk 0

L JK

H

I

BA F GEDC

GEN-000718




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

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

GEN-001930

10G copper for ESCON

Channel 0 and Channel 1for FICON

FC port to tape




Figure 3 Front view of the ACP

Figure 4 Rear view of the ACP

CBA D E F G CNS-000979

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

A

C S

MGMTB

AC power Mouse

Keyboard

Com 1 Modem

USB ports (For USB disk, USB mouse or USB keyboard)

Com 2Eth 3Eth 1 Eth 2

Eth 0Video




Table 1 ACP rear panel connectors

DLm management networkThe DLm has an internal Gigabit Ethernet network for management purposes. In a DLm960, the ACPs, VTEs, Celerra Server, and Data Domain systems management ports are connected to a pair of 1 Gb Ethernet switches to protect against a single switch failure.

Connector Description

AC Power AC power. Connect an AC power cord between the AC power plug and a power distribution unit.

Com 1 Not used in DLm960.

COM 2 Serial connection from service laptop.

Eth 0 Connects to management switch port.

Eth 1 Not used in DLm960.

Eth 2 Connects to management switch port.

Eth 3 Not used in DLm960.

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.

AT-9924TL-EMC2

GEN-001778




Figure 5 24-port AT-9924TL switch

10 Gb data networkIn a DLm960, the data from the mainframe is transferred to the DLm960 storage systems over 10 Giga bit Ethernet connections. The 10 Gb Ethernet network has a pair of 10 Gb Ethernet switches to protect against a single switch failure.

Figure 6 Fujitsu XG2000R switch

Backend storage

DLm960 supports the Celerra server and an optional Data Domain DD880 for storing the data written to the virtual tapes.

In DLm960, the DD880 is to be used for data that deduplicates well and the Celerra server should be used for all other data. Both systems export NFS filesystems and the VTEs then use these NFS filesystems to store the data.

Deduplicating storage The Data Domain system provides DLm's deduplication feature. DLm uses a highly optimized inline data deduplication technology that reduces the footprint by storing only the unique data. This also reduces power consumption and provides a significant total cost saving. The data is streamed from the mainframe through the VTEs to the backend Data Domain storage system. Due to the inline implementation, only the deduplicated, unique data gets stored on the drives.

Each Data Domain system contains:

◆ A storage controller that executes the Data Domain operating system and supports redundant 12 Gb/s SAS connectivity to the backend drive enclosures.

◆ Up to 12 ES20 storage shelves (each containing fifteen 2 TiB SATA drives and providing 27.28 TiB raw capacity and 20.92 TiB of usable capacity).

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

FUJISUXG2000

Dump

Status

Alarm

Mng-LAN Console RS-232C

Power

GEN-001779




The DD880 comes with RAID 6 configuration (12+2) and one hot spare in each ES20 drive enclosure.

Choose deduplication backend storage for data that is stored long term and is highly redundant.

Figure 7 DD880 Controller—Rear view

See Figure 22 on page 75 for the front view of a DD880 controller.

Although DD880 supports up to six VTEs, it has a total stream count limit of 180 streams. This can include backup write streams, backup read streams, directory replication at source, and directory replication at destination. Each of these types of streams has a different limit as listed in Table 2 on page 30.

Irrespective of the type of streams, the total number of streams cannot exceed 180. DD880 can have more streams opened above these numbers, but this can impact performance. The performance will return when the stream counts drop below those limits.

Table 2 DD880 stream count limits

Stream type Stream count limit

Backup Write streams 180

Backup Read streams 50

Directory replication at source 90

Directory replication at destination 180




Celerra storage DLm960 can be configured with a maximum of two Celerra network file servers. Each Celerra file server can have 2-8 storage controllers called Data Movers. All DLm960 systems are configured with a standby Data Mover.

Choose Celerra file storage for a large volume of data that does not need to be stored for long periods of time and is not extensively redundant to warrant deduplication.

The Celerra network-attached file server comes with:

◆ Disks that come in groups of fifteen 1 TB or 2 TB SATA drives (each group is one disk array enclosure [DAE])

◆ Each DAE with 9.5 TB (1 TB drives) or 19.3 TB (2 TB drives) of usable capacity

◆ RAID 6 configuration (12+2) and one hot spare in each DAE

Mainframe channel interfaces

A VTE contains mainframe channel interfaces. These channel interfaces can be either two Fibre Connectivity (FICON) interfaces or three Enterprise Systems Connection (ESCON) interfaces per VTE.

The FICON interfaces can be either single mode or multimode. Do not mix ESCON and FICON within a single DLm system nor single mode and multimode FICON within a single DLm system. A DLm system configured with six VTEs provides either 12 FICON interface connections or 18 ESCON 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 26 shows the rear view of the VTE with the channel interfaces to the right of center of the unit. DLm960 supports both ESCON and FICON.

FICON channelEach 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 DLM960, the FICON adapter has three light-emitting diode (LED) indicators, listed in Table 3 on page 32, 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 3 FICON adapter LED indicators

Yellow LED4 Gbps

Green LED2 Gbps

Amber LED1 Gbps

Activity

Off Off Off Power off

On On On Power on

Flashing Flashing Flashing Loss of synchronization

Flashing in sequence



Firmware error

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. The EMC Disk Library for mainframe User Guide provides more information.




Reconfigurable non-shared (non-EMIF) mode

CHPID PATH=(0A),REC,TYPE=FC



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. The EMC Disk Library for mainframe User Guide provides more information.

Shared (EMIF) mode

CHPID PATH=(0A),SHARED,TYPE=FC



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. The EMC Disk Library for mainframe User Guide provides more information.

Alternate paths in shared (EMIF) mode

CHPID PATH=(0A),SHARED,TYPE=FCCHPID PATH=(0B),SHARED,TYPE=FC

CNTLUNIT CUNUMBR=EA80,PATH=(0A,0B), +UNITADD=((00,32)),UNIT=3590

IODEVICE ADDRESS=(EA80,32),CUNUMBR=(EA80), +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. The EMC Disk Library for mainframe User Guide provides information.

Configuration for a FICON switch in basic mode

CHPID PATH=((22)),TYPE=FC,SWITCH=02




CNTLUNIT CUNUMBR=300,PATH=(22),LINK=(C2), + UNITADD=((00,32)),UNIT=3590

IODEVICE ADDRESS=(300,32),CUNUMBR=(300),UNIT=3590

ESCON channelEach DLm ESCON interface has a single ESCON MT-RJ connector. If the mainframe uses the older ESCON duplex connectors, the available ESCON converter cable provides a male MT-RJ connector on one end and a female ESCON duplex connector on the other end as shown in Figure 8 on page 35. The male MT-RJ connector fits into the socket on the ESCON controller in the VTE.

Status indicators

Each ESCON interface has a four-character display visible on the back edge of the system adjacent to the interface connector. The display scrolls the status of the interface. Under normal operating conditions, the version of the interface's emulation firmware is displayed.

Figure 8 ESCON converter cable

GEN-000711

ESCONMT-RJ

ESCONduplex




Connect DLm to an ESCON channel

DLm can be connected directly to the mainframe ESCON channel or through an ESCON director. In either case, the following parameters are required to properly define a DLm V348x, 3490, 3480, or 3590 device on a z/OS system:

◆ TYPE must be CNC.

◆ UNIT can be one of the following:

• A virtual control unit: V3480, V3481, V3482, or V3483

• A real 3590

• A real 3490

• A real 3480

◆ CHPID can be:

• 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 ESCON connection

The following output examples show I/O generation.

Basic, dedicated non-shared (non-EMIF) modeCHPID PATH=(0A),DED,TYPE=CNC



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. The EMC Disk Library for mainframe User Guide provides more information.

Reconfigurable non-shared (non-EMIF) modeCHPID PATH=(0A),REC,TYPE=CNC

CNTLUNIT CUNUMBR=EA80,PATH=(0A), +UNITADD=((00,32)),UNIT=3590




IODEVICE ADDRESS=(EA80,32),CUNUMBR=(EA80), +STADET=Y,UNIT=3590

Note: With reconfigurable 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. The EMC Disk Library for mainframe User Guide provides more information.

Shared (EMIF) modeCHPID PATH=(0A),SHARED,TYPE=CNC

CNTLUNIT CUNUMBR=EA80,PATH=(0A), + UNITADD=((00,32)),UNIT=3590IODEVICE ADDRESS=(EA80,32),CUNUMBR=(EA80), + STADET=Y,UNIT=3590


Alternate paths in shared (EMIF) modeCHPID PATH=(0A),SHARED,TYPE=CNCCHPID PATH=(0B),SHARED,TYPE=CNC

CNTLUNIT CUNUMBR=EA80,PATH=(0A,0B), + UNITADD=((00,32)),UNIT=3590



Configuration for an ESCON director in basic modeCHPID PATH=((22)),TYPE=CNC,SWITCH=02

CNTLUNIT CUNUMBR=300,PATH=(22),LINK=(C2), + UNITADD=((00,32)),UNIT=3590

IODEVICE ADDRESS=(300,32),CUNUMBR=(300),UNIT=3590




DLm devices and capacityTable 4 on page 38 provides details of the devices supported on DLm and the minimum and maximum supported capacity.

Table 4 Differences between the DLm models

Capacity DLm960DLm960 with optional DD880

Number of cabinets per system 2 to 13 for 1 TB drives, 2 to 10 for 2 TB drives

2 to 14

Number of virtual tape engines (VTEs) 1 to 6 1 to 6

Number of access control points (ACPs) 2 2

Front-end 4G FICON channels (to the host) 1 2, 4, 6, 8, 10, or 12 2, 4, 6, 8, 10, or 12

Front-end ESCON channels (to the host) 2 3, 6, 12, 15, or 18 3, 6, 12, 15, or 18

Maximum active tape devices3 256 to 1536 256 to 1536

Model and quantity of EMC Network ServersOptional Data Domain system

1 or 2 NS960 1 or 2 NS960 and the optional DD880 NFS server

Number of Data Domain DD880 racks - 1

Data Disk Drive type 1 TB or 2 TB SATA 1 TB or 2 TB SATA

RAID protection RAID 6 (12+2) RAID 6 (12+2)

Number of storage controllers: Celerra Based on capacity.Minimum of two; configured as one active and one hot standbyMaximum of 12; configured as 10 active and two hot standby

Based on capacity.Minimum of two; configured as one active and one hot standbyMaximum of 12; configured as 10 active and two hot standby

Number of storage controllers: Data Domain DD880 NA One active

Replication Supported Supported




Table 5 on page 39 provides details of the front-end ESCON and 4G FICON connections.

Table 5 Details of ESCON and FICON connections

User tape non-deduplicated storage (internal disk array)

Minimum — maximum DAEs 3–122 for 1 TB drives, 1–60 for 2 TB drives

NA

Minimum — maximum terabytes (TB) 28.5–1159 for 1 TB drives, 57.9–1158 for 2 TB drives

NA

User tape deduplicated storage (internal disk array)

Minimum — maximum DD880 32 TB ES20 enclosures (2 TB drives only)

NA 2–64

Minimum — maximum raw storage (TB) in DD880 ES20 enclosures

NA 64–192

Minimum — maximum usable storage (TB) in DD880 ES20 enclosures

NA 47.6–142.5

Logical storage at 10:1 total compression (TB) NA 476–1425

1. The number of channels depends on the number of VTEs: two FICON channels per VTE

2. The number of channels depends on the number of VTEs: three ESCON channels per VTE.

3. The maximum number of tape devices depends on the number of VTEs. There can be up to 256 devices per VTE.

4. For DD880 systems that are part of DLm 2.3.x and are upgraded to 2.4, the maximum ES20 shelf count is 12, if the ES20 shelves contain 1TB drives only.

Capacity DLm960DLm960 with optional DD880

Adapter typeNumber of ports

Number of unique LPARs

Number of control units Number of links

Maximum number of paths supported per VTE

FICON 1 256 16 NA 4096

ESCON 1 16 16 16 64

DLm devices and capacity 39



Tape emulation

DLm VTEs emulate the IBM tape drives to the mainframe and direct the tape data to and from the backend storage arrays. Each VTE, once configured, operates independently of the other VTEs in the VTEC and can be configured with up to 256 tape drives. A DLm configured with two VTEs can emulate up to 512 virtual tape devices, while one with six VTEs can emulate up to 1,536 virtual tape devices at one time.

The virtual tape emulation software:

◆ Receives and interprets channel command words (CCWs) from the host

◆ Sends and receives the tape data records and reads and writes corresponding disk data in response to the CCWs

◆ Presents initial, intermediate, and final status to the host commands and asynchronous status as needed

◆ Sends and receives control information (such as sense and load display data) to and from the host in response to the CCWs

Virtual tape drive 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.

DLm devices and capacity 41



Support for physical tape drivesDLm 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.

DLm960 supports 1-6 Fibre Channel attached tape drives. “Backend storage” on page 29 provides information about the utility.




High availability features of DLm960DLm includes failure recovery mechanisms in various parts of its architecture to ensure optimum availability.

VTEC

A VTEC with more than one VTE delivers enterprise-class availability and scalability through a modular design based on high-performance, highly available VTEs:

◆ VTEs have redundant power supplies, fans, and RAID-protected internal disks. Emulated tape drives on each VTE can mount any cartridge and any logical partition (LPAR) can access any cartridge, delivering enterprise-class availability.

◆ DLm960 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 DLm960, two 10 GbE switches provide a redundant data path, and two 1 GbE switches provide a redundant control path. The redundant data path provides failover to protect against link failures, network card failures, and switch failures.

◆ The 10 GbE ports on the Celerra Server and Data Domain storage controllers of DLm960 are bonded together in failover mode also.

Celerra server

Storage controller failover —

◆ The Celerra 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.

High availability features of DLm960 43



Each Celerra within the DLm960 can have up to six storage controllers, where five are active and one is a standby. The number of active storage controllers is based on the storage capacity of the system.

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 Celerra server against hardware or software failure.

◆ Fail-Safe Network (FSN) — FSN is a high-availability networking feature supported by the Celerra 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. Celerra 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 Celerra 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 Celerra server and DD880 must have:

• Two optical 10 GbE ports to connect the storage controllers or DD880 to the switches in the VTEC (one for each 1 GbE switch)

• Two ports configured together using an FSN failure recovery

◆ Control Station failover — The Celerra server provides a primary and secondary Control Station that ensures uninterrupted file access to users when the primary Control Station is rebooted, upgraded, or unavailable. The Control Station software, which is used to configure and manage the Celerra server, operates independently of the file-access operations and services provided by storage controllers.

The Celerra network server uses the ConnectEMC or E-mail Home utility to notify EMC Customer Support (or your service provider) of the failure. After the primary Control Station is repaired or replaced and the Control Stations are rebooted, either directly or as a result of a powerdown and restart cycle, the first Control Station to start is restored as the primary.

Celerra network server comes with RAID 6 protection to ensure high availability.




Figure 9 VTE to storage controllers — Network topology

Figure 9 on page 45 shows multiple VTEs connected to the storage controllers through two Ethernet switches. This illustrates the high availability of the network storage and FSN.

Data Domain

Because the Data Domain operating system (DD OS) is designed for data protection, the goal of its architecture is data invulnerability. Its design includes:

◆ End-to-end verification

◆ Fault avoidance and containment

◆ Continuous fault detection and healing

01

23

01

23

!

!

Lnk

Tx

Rx

Lnk

Tx

Rx

01

23

01

23

!

!

Lnk

Tx

Rx

Lnk

Tx

Rx

Storage Controllerenclosure 0

Storage Controllerenclosure 1

Storage Controllers Ethernetswitch

Ethernetswitch

VTEs

VTE1

VTE-N

GEN-001931




◆ Filesystem recovery

Figure 10 VTE to DD storage controllers — Network topology

End-to-end verificationWhen the DD OS receives a write request from the backup software, it computes a huge checksum over the data. After analyzing the data for redundancy, it stores only the new data segments and all of the checksums. After the backup is complete and all the data has been synchronized to disk, the DD OS verifies that it can read the entire file from the disk platter through the Data Domain filesystem, and that the checksums of the data that is read back match the checksums written. This ensures that the data on the disks is readable and correct, can be recovered from every level of the system, and that the filesystem metadata structures used to find the data are also readable and correct.

InvalidAddress

0 1 2 3HOST

EXP’N

System

0 1 2 3

X2

X2

I D

0123HOST

EXP’N

System

0123

67 5 4 3 2 11 2 IID

IID

REMOVE

FAULT

POWER

REMOVE

FAULT

POWER

FAULT

REMOVE

POWER

TEST LED

FAULT

REMOVE

POWER

TEST LED

ES20 enclosure 0

DD880 Controller

Data Domain Storage ControllerEthernetswitch

Ethernetswitch

VTEs

VTE1

VTE-N

GEN-001348

Failover




Fault avoidance and containmentThe biggest risk to filesystem integrity is filesystem software errors that occur when writing new data. New data can accidentally write on existing data, and new updates to filesystem metadata can mangle existing structures. Data Domain systems are equipped with a specialized log-structured filesystem that has four important benefits:

◆ New data never overwrites good data

Unlike a traditional filesystem, which will often overwrite blocks when data changes, Data Domain systems write only to new blocks. This isolates any incorrect overwrite (for example, a software defect issue) to only the newest backup data. Older versions remain safe.

◆ Fewer complex data structures

The Data Domain filesystem was built to protect data in backup applications, where the workload is primarily sequential writes of new data. Because the application is simpler, fewer data structures are required to support it. As long as the system can keep track of the head of the log, new writes will not touch old data. This design simplicity greatly reduces the chances of software errors that could lead to data corruption.

◆ NVRAM for fast, safe restart

The system includes a non-volatile RAM write buffer into which it puts all data not yet safely on disk. The filesystem leverages the security of this write buffer to implement fast and safe restart capability. The filesystem includes many internal logic and data structure integrity checks. If any problem is found by one of these checks, the filesystem restarts. The checks and restarts provide early detection and recovery from the kinds of bugs that can corrupt data.

As it restarts, the Data Domain filesystem verifies the integrity of the data in the NVRAM buffer before applying it to the filesystem and so ensures that no data is lost due to the restart. Data Domain systems never update just one block in a stripe. Following the no-overwrite policy, all new writes go to new RAID stripes and those new RAID stripes are written in their entirety. The verification after write ensures that the new stripe is consistent. New writes do not put existing backups at risk.

Continuous fault detection and healingAs a basis of continuous fault detection and healing, the Data Domain system uses RAID 6 protection to protect against double disk faults.




On-the-fly error detection and correction

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

Scrub to ensure data does not go bad

Data Domain systems verify the integrity of all data weekly in an ongoing background process. This scrub process finds and repairs grown defects on the disk before they can become a problem.

The Data Domain storage array includes various recovery mechanisms to ensure optimal availability on the storage controller, network, and DD880 levels. The Data Domain DD OS Administration Guide contains more information about the various DD880 recovery features.

Filesystem recoveryData Domain systems include features for reconstructing lost or corrupted filesystem metadata, as well as filesystem check tools that can quickly bring an ailing system safely back online.

Self-describing data format to ensure metadata recovery

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

Redundant 10 Gb Ethernet data path

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




Redundant 1 Gb Ethernet connectivity for management

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

Redundant 1 GbE ports for replication

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

Redundant backend/drive connectivity

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

Expanded capacity on Data Domain DD880

DLm 2.4.x supports the Expanded Capacity feature provided by Data Domain. This is a licensable feature that allows:

◆ A doubling of usable capacity from 71 TB to 142.5 TB

◆ A doubling of raw capacity from 96 TB to 192TB

For new DLm2.4.0 systems, this is a non-disruptive activity. For DLm2.4.x systems, that are upgraded from an earlier version of the DLm2.3.x system, this is a disruptive activity. In this case, additional hardware needs to be added to the DD880 system. These upgraded systems will require the following hardware changes:

◆ Addition of system memory on the DD880 from 48GB to 64GB

◆ Addition of a 3rd dual ported SAS card

DLm2.4.x systems, upgraded from an earlier version of the DLm2.3.x system, support both 1 TB and 2 TB increments.

Contact EMC Sales for more details, if you need to avail this feature.




Features and benefitsDLm offers many benefits over traditional tape including:

◆ Faster processing of tape mount requests (translating into shorter overall job step processing)

◆ No requirement for physical tapes (reducing the cost, storage, and potential for loss of tapes and data)

◆ Support for data sharing across multiple VTEs (creating a level of data availability not found in previous mainframe virtual tape systems)

◆ Support for low volume access of external physical tapes that allow the mainframe to write to and read physical tapes

◆ Data integrity maintained by storing the tape data on internal storage arrays and using RAID 6 technology to protect the data from physical disk drive failures

◆ Built-in monitoring and reporting technologies, such as Simple Network Management Protocol (SNMP) and ConnectEMC, that raise alerts when attention is needed within the DLm environment

◆ Support for replication of tape data between DLm systems and up to two local or remote DLm systems

◆ No single point of failure of mainframe tape data if the DLm system has more than one VTE

◆ An enhancement to DLm's replication capabilities called Guaranteed Replication (GR) in DLm release 2.2 and later. This feature forces EMC Celerra Replicator™ to completely replicate a tape volume (VOLSER) to the remote site every time the mainframe issues two consecutive write tape marks on a tape and follows it with a tape close

◆ Support for two erase policies for space reclamation (in DLm release 2.3 and later):

• Space: This is the default policy. When a filesystem reaches a specified percentage of space usage (Recovery Percent general parameter), DLm begins erasing the oldest scratch tapes in that filesystem until the amount specified in the Recovery Amount parameter has been recovered.




• Time-to-live: This policy specifies a period of time that scratched tapes will be retained after being scratched, before being automatically erased. Once the period expires, the tapes will automatically be erased regardless of current space utilization. The time-to-live erase options are: Days and Hours.

Note: If the VTE has tape libraries that reside on the Data Domain DD880, the erase policy must be configured to one of the Time-to-live options.

◆ Support for data deduplication in the DLm960 model integrated with DD880:

• Support for the best inline data deduplication technology available in the market that reduces the footprint due to deduplication and reduces power consumption

• Significant cost savings for replication deployments as only the unique data after deduplication is replicated

◆ Support for EMC Secure Remote Support (ESRS) that provides secure, fast, and proactive remote support for maximum information availability. Contact EMC Customer Support to configure ESRS.

Features and benefits 51


CHAPTER 2DLm Operations

This chapter explains the routine DLm operations:

◆ Management access to DLm ............................................................................. 54◆ Access a VTE .................................................................................................... 69◆ Power up DLm .................................................................................................. 72◆ Power down DLm.............................................................................................. 79◆ Start and stop tape devices.............................................................................. 84◆ Support access to DLm..................................................................................... 85

DLm Operations 53

DLm Operations


Management access to DLmThe ACP provides the only user access to the VTEC for management, support, and diagnostics purposes. The ACP resides on an internal network and does not connect directly to the customer's LAN. You can access the ACP only by using a secure connection through the DLm Celerra Control Station. However, during initial setup, you can define an IP address using which you can directly access DLm Console from the customer network.

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 6 on page 54 lists the details that you will need before you access the DLm system.

Table 6 DLm system access details

Item Default Actual

DLm Console

HA IP address

Username dlmadmin

Password password (first login)

Note: The system prompts you to change the password at the initial login.

ACP1

IP address

Username dlmadmin

Password password

ACP2


DLm Operations


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

Access the Control StationThe Control Station is Celerra's dedicated management system. You can connect the Control Stations to a public or private network using their Eth 3 ports for remote administration.

During the initial setup and configuration of DLm, IPs are assigned to the Control Stations. After configuration, you can access the Control Station by:

◆ Using an SSH client (for example, PuTTY) over TCP/IP

◆ Directly connecting a laptop to the serial port. Figure 11 on page 56 explains more about the connectivity.

Remote access to the Control StationYou can remotely access the Control Station by using any SSH client, such as PuTTY. Table 7 on page 55 provides the usernames and the default passwords required to access the DLm Celerra Control Station.

IP address

Username dlmadmin

Password password

Table 6 DLm system access details

Item Default Actual

Table 7 Control Station usernames and passwords

Username Password

nasadmin nasadmin

root nasadmin

Management access to DLm 55

DLm Operations


The Control Station has a serial port (COM 1 port) that connects to an external serial modem. Through the modem connection, the Control Station calls home to EMC for remote support and diagnostics.

Figure 11 on page 56 displays the rear panel of the Control Station provided with DLm version 2.0 and later.

Figure 11 Rear panel of a Gen 2 Control Station and an ACP

A

C S

MGMTB

A B C D E F G

HIK J GEN-001173

A. AC power receptacle B. Mouse

C. COM 1 modem D. Eth 1

E. Eth 2 F. Eth 3

G. COM 2 port H. USB 0-1

I. Eth 0 J. Video

K. Keyboard


DLm Operations


To connect remotely to the Control Station:

1. Start an SSH client terminal session like PuTTY.

2. Select the Connection type as SSH.

3. Type the IP address of the base Celerra's primary Control Station in the Hostname (or IP address) field.

4. [Optional] You can save the session by typing a name for the session in the Saved Sessions field and then clicking Save.

5. Click Open.

Direct access to the Control StationYou can directly access the Control Station by connecting a laptop to the COM 2 port using a serial connection. Once it is connected, you can use PuTTY to log in to the Control Station.

1. Using a USB-to-Serial converter and/or serial cable (DB-9 NULL Modem cable), connect the rightmost serial port on the back of the primary Control Station (CS0) and the COM 1 port on your service laptop.

2. Open a serial PuTTY session.

3. Use the following values:

Serial Line: COM1

Speed: 19200

Data bits: 8

Stop bits: 1

Parity: none

Flow Control: none

4. Press Enter and you will be prompted to log in.


DLm Operations


Access the ACP

The ACP provides the only user access to the VTEC for management, support, and diagnostics purposes. EMC highly recommends that the ACP remain accessible at all times. DLm version 2.0 and later offers a second ACP to ensure high availability. DLm960 has two ACPs. DLm ships with ACPs. Figure 11 on page 56 shows the rear panel of an ACP.

The ACP resides on an internal network and does not connect directly to the customer's LAN. You can access the ACP by using a secure connection through the DLm Celerra Control Station.

Do not modify any network interface on the ACP. Doing so might cause the ACP to lose its connection to the VTEs and Control Stations.

Secure access to the ACPDLm provides two ACPs, ACP1 and ACP2, to ensure high availability. You must configure two separate PuTTY sessions to access ACP1 and ACP2. With PuTTY connected to the Control Station, use TightVNC to initiate contact with the ACP.

Note: EMC recommends that you have only one active VNC session to either ACP1 or ACP2.

To connect to the ACP through a secure connection to the DLm Control Station:

1. Start an SSH client terminal session like PuTTY.

2. Connect to the Control Station:

a. Select the Connection type as SSH.

b. Type the IP address of the base Celerra's primary Control Station in the Hostname (or IP address) field.

c. [Optional] You can save the session by typing a name for the session in the Saved Sessions field and then clicking Save.


DLm Operations


Figure 12 PuTTY session

3. Create a tunnel to the ACP:

a. Select Session > Connection > SSH > Tunnels in the Category of the PuTTY window.

b. Type 5801, the default browser port, in the Source port field.

c. Type the IP address and port number of the desired ACP in the Destination field:

– IP address and port number for ACP1: 128.221.252.40:5801


d. Click Add.

e. Type 5901, the direct VNC port in the Source port field.


DLm Operations


f. Type the IP address and port number of the desired ACP in the Destination field.



g. Click Add.

h. Click Session in the Category (left side) of the PuTTY window.

i. Save the session by typing a name for the DLm session in the Saved Sessions field and click Save.

The ACP desktop opens.

Figure 13 ACP desktop with web browser

Connect to the DLm ConsoleTo connect to DLm Console through the ACP:

1. Connect to the ACP as described in “Access the ACP” on page 58.


DLm Operations


2. On the ACP desktop, double-click the Web Browser icon.

3. On the browser, click the DLm Console link.

The DLm Console login screen opens as shown in Figure 14 on page 62

4. 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 15 on page 63.

Note: At first login, DLm prompts you to change the DLm Console password.

To connect to the DLm Console using the direct access IP address

During initial setup, you can provide an IP address to directly access the DLm Console.

Note: This procedure assumes that, during initial setup, you provided the EMC service personnel with an IP address for direct access to the DLm Console. It also assumes that you have access to and are connected to the Data Center LAN to which the ACP is connected.

1. Open a web browser.

2. Type the additional IP address you provided during setup for DLm Console access 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 14 on page 62.


DLm Operations


Figure 14 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 15 on page 63.

Note: At first login, DLm prompts you to change the DLm Console password.


DLm Operations


Figure 15 DLm Console

Exit DLm ConsoleTo exit the DLm Console, click Logout on the DLm Console menu bar.

Set date and time

The DLm system time is displayed in the status line at the bottom of the VT console. If you need to adjust the system date or time you may do so from the Time tab on the DLm Console:

1. Access the DLm Console as described in “Connect to the DLm Console” on page 60.


DLm Operations


2. Click External.

3. Click the Time tab if it is not already displayed.

Figure 16 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:


2. Click External.

3. Click the Authentication tab.


DLm Operations


Figure 17 User ID creation

4. Select the authentication type:

• Native

“Native” on page 66 provides instructions to add, modify, or delete users of Native authentication type.

• LDAP (including Active Directory)

“LDAP” on page 67 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.

NativeNative user administration stores the usernames and passwords on the VTE and is the default type.


DLm Operations


◆ To modify a user, modify the content of the Name, Password, or Readonly? fields.

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

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

Access a VTE

You can access the VTE through the DLm Console.


The System status tab of the Status menu opens by default (Figure 15 on page 63).

The console displays icons for each configured VTE. From the bottom up, the VTEs in your DLm cabinet are named VTE1, VTE2, VTE3, and so on. Only the icons matching the VTEs installed in the DLm are displayed on the console.

2. In the Console column, click the icon corresponding to the VTE you want to access.


DLm Operations


Figure 19 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) .


DLm Operations


The following navigation keys 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 84 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.


The System status tab of the Status menu opens by default.

2. In the Reboot machine column, click Reboot corresponding to 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. Each Celerra Network Server (including the EMC CLARiiON storage array)

2. Each DD880

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.


DLm Operations


Celerra server power-up

The following steps explain the procedure for powering up the Celerra Network Server and integrated storage arrays:

1. Make sure the power switches for the standby power supplies (SPS), A and B, shown in Figure Figure 20 on page 73, are off (0 position).

The SPS power switches are at the rear of the DLm system and expansion bays.

Figure 20 SPS power switches on DLm960

2. Turn on (Position 1) the left and right cabinet circuit-breaker master switches at the rear of the DLm cabinets:

• Figure Figure 21 on page 74 illustrates the DLm960 bay.

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.

SPS powerswitch B

SPS powerswitch A CIP-000831

Power up DLm 73

DLm Operations


Figure 21 DLm960 bay master power switches

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

Powersource A

GEN-001171

Powersource B

Powersource A

Powersource C

Powersource D

(15 ft extension cables) (15 ft extension cables)

Powersource B

Master switch

Master switch

PDP APDP B PDP APDP B

PDP CPDP D PDP C(optionalfor storageexpansionover 9 DAE)

PDP D(optional

for storageexpansion

over 9 DAE)

Masterswitch

Masterswitch

Masterswitch

Masterswitch

NAS and NAS extension bays VTEC and storage bays


DLm Operations


Note: If the entire VTEC bay is powered down, 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 ACPs or VTEs are started. You must press the Power button on each ACP and each VTE to actually start them when appropriate.

3. Turn on (Position 1) the switches for SPS A and SPS B as shown in Figure 20 on page 73, and wait for the storage array to power up. The storage array can take about 8 minutes to power up.

DD880 power-up

1. Make sure the power switches on the ES20 shelves are in the off position.

2. Power up the DD880 bay.

3. Power on all the ES20s before the DD880 controller.

4. ES20 power: Turn the power switch to on for each of the two power supplies for each ES20 expansion shelf.

Figure 22 ES20 expansion shelf

5. Wait approximately 3 minutes after all expansion shelves are turned on.

6. On the Controller, Push in the power button.

Power up DLm 75

DLm Operations


Figure 23 Controller power buttons.

ACP power-up

To power up the ACP, press the Power button located in the front of the ACP. Figure 24 on page 76 shows the front view of the ACP .

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

Figure 24 Front panel of the DLm960 ACP

CBA D E F G CNS-000979


DLm Operations


VTE power-up

To power up the VTE, press the Power button located in the front of the VTE, as shown in Figure 25 on page 77.

You may hear the fans start and then slow down to adjust the system temperature.

The VTE disk LED starts blinking to indicate the VTE startup.

Normal startup of a VTE takes 5 to 10 minutes. After the VTE starts its network services, you can access the VTE operational desktop from the ACP. As each VTE operates independently, you can power up the DLm VTEs one at a time or all at once.

Figure 25 Front view of the VTE

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

Disk 1Disk 0

L JK

H

I

BA F GEDC

GEN-000718

Power up DLm 77

DLm Operations


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


DLm Operations


Do not press the Reset button while the VTE is online to the host. Follow the hutdown procedure in “Power down DLm” on page 79 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.

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 dwon a VTE.

2. DD880 controller

3. ES20 enclosures

4. Each ACP

5. Each Celerra server

6. The CLARiiON storage array

Note: The powerdown process takes up to 30 minutes after the tape drives are varied offline.

Power down DLm 79

DLm Operations


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.

VTE powerdown

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.

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.

2. Access the VTE desktop as described in “Access a VTE” on page 69.

3. Right-click on the VTE desktop and select Administrator Shell.

4. Type the root password; the shell window appears.

5. To power off the VTE, type poweroff.

6. Press Enter. The system automatically enters the shutdown state.

Note: The virtual tape application automatically restarts the next time you start the system.

After executing the poweroff command, the VTE powers down. Pressing the Power button after a poweroff command will turn the VTE on again.

DD880 powerdown

You can power down the DD880 system from the ACP by executing a CLI command.

To shut down the power to the Data Domain system:


DLm Operations


1. Log in as an administrative user and type this command:

# ssh -l sysadmin 192.168.100.110 system poweroff

2. Type yes and press Enter.

The command automatically performs an orderly shutdown of DD OS processes.

Do not use the chassis power switch to power off the system. Use the system poweroff command instead.

The DD880 controller will power down. This may take a few minutes. After powering down the controller, you can power down the ES20 shelves using the power switches at the back of each ES20 shelf. After powering down all the ES20 shelves in the DD880 bay, you can power off the rack if needed.

ACP powerdown

You can power down and reboot the ACP without affecting the operation of the VTE.

To power down:

1. Right-click on the ACP desktop and select Administrator Shell.


3. To power off the ACP, type poweroff.


Halt the Celerra server

A planned powerdown of the Celerra server and integrated storage array requires access to the Celerra Control Station. Call EMC Customer Support for assistance.

Before you power down the Celerra 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 Celerra server.

3. If you wish to verify the system's health, type:

Power down DLm 81

DLm Operations


/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******************** WARNING! ********************You are about to HALT this Celerra including all of itsControl Stations and storage controllers. DATA will beUNAVAILABLE when the system is halted. Note that thiscommand does *not* halt the storage array.ARE YOU SURE YOU WANT TO CONTINUE? [ yes or no ] : yes

5. Type yes and press Enter.

6. 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 Celerra server. Your connection ends before you get a command complete message.

Verify Control Station powerdown

To verify that the Data Movers have 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 have to remove the front bezel.

2. Wait for 5 minutes, and then login as root at the login prompt.

3. Verify that the Data Movers are shut down using this command:

# /nasmcd/sbin/getreason

This is a sample output for a 6-Data Mover configuration:

6 - slot_0 primary control stationslot_1 secondary control station powered off- slot_2 powered off- slot_3 powered off- slot_4 powered off- slot_5 powered off- slot_6 powered off- slot_7 powered off

After ensuring that the Data Movers are shut down, you can power down the CLARiiON storage array.


DLm Operations


Power down the CLARiiON storage array

To shut down a CLARiiON storage array (SPE and boot DAE), use only the power switches on the SPS.

Failure to follow this procedure can result in the loss of data and extended periods of data unavailability while the array is returned to normal functionality.

SPE chassis and OS-Boot chassis DAEs are plugged into the SPS units. From the rear of the cabinet, the left power supply of each chassis (SPE and OS-boot) is plugged into the left SPS and the right power supplies are plugged into the right SPS. To power down the storage array:

1. Vary off all tape drives, power down all VTEs, and halt the Celerra server to stop all I/O activity.

2. Wait approximately five minutes to allow the write cache to finish writing to the storage system.

3. Use the SPS power switches to power off the storage array. Turn off (0 position) the power switch on the standby power supplies (SPSs). Wait 2 minutes to allow the storage system to write its cache to disk. Ensure that the SPS power indicators are off before continuing.

Never turn off the power directly to the SPE chassis or the OS-boot chassis by using any switches on the power supplies. Never unplug any of the AC cables going to the SPE or OS-boot chassis to disconnect power.

Power down DLm 83

DLm Operations


4. Power off Control Station 0:

# /sbin/halt

Sample output:

# /sbin/halt

Broadcast message from root (ttyS1) (Fri Feb 13 17:53:59 2009):The system is going down for system halt NOW!INIT: Stopping HAL daemon: [OK]Stopping system message bus: [OK]................Halting system...md: stopping all md devices.md: md0 switched to read-only mode.Shutdown: hdaSystem halted.

5. Ensure that the LEDs on all blade management switches are off. When they are off, the Celerra and CLARiiON are completely powered down.

After the CLARiiON storage array has completely powered down, you can power down the cabinets.

ACP Power down

You can power down and reboot the ACP without affecting the operation of the VTE.

To power down:

1. Right-click on the ACP desktop and select Administrator Shell.


3. To power off the ACP, type poweroff.


Start and stop tape devicesTo start or stop the virtual tape devices you must start or stop the VT application. Control of the VT application is through the VT 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.


DLm Operations


◆ 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 VT 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 VT console as described in “Access a VTE” on page 69.

2. In the VT console, type the appropriate command. For example, to start the VT application, type:

STARTVT

The blue bar at the bottom of the VT console displays the changed status of the VT application.

3. Type exit and press Enter to close the console window.

Support access to DLmDLm 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.

Support access to DLm 85

DLm Operations


ESRS

ESRS for Celerra file storage monitors the operation of DLm for error events and automatically notifies your service provider of error events. It also provides a path for your service provider to use to securely connect to your monitored DLm systems.

Figure 26 EMC Secure Remote Support

Modem support

DLm provides an external modem to allow remote access to the ACPs for support and diagnostic purposes. The supplied modem is normally attached to ACP1, the bottom ACP in a DLm960. 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 27 shows the rear panel of the ACP.


DLm Operations


The ACP can be configured to send messages to EMC using the ConnectEMC function when problems are detected within the Celerra Server or the VTEC. The ConnectEMC options include sending the messages via a modem through a customer-supplied analog telephone line.

Support access to DLm 87

DLm Operations




CHAPTER 3DLm Administration

This chapter explains some of the DLm administrative tasks:

◆ Tape libraries ................................................................................................... 90◆ Configure virtual devices .................................................................................. 97◆ Manage configuration files ............................................................................. 111◆ Tape Erase ..................................................................................................... 113◆ Manage VTE and ACP logs .............................................................................. 115◆ Back-end tape support ................................................................................... 118◆ DLm diagnostic reporting ............................................................................... 122◆ AWSPRINT library utility.................................................................................. 126

DLm Administration 89

DLm Administration


Tape librariesThe filesystems offered by DLm 2.x software and the DLm 3.x software are different in many ways. New systems running 3.x software can be made backward compatible with the legacy type of filesystem offered by DLm 2.x. These systems can later be upgraded to support the DLm 3.x enhanced filesystem (EFS). It is very difficult to revert to the 2.x filesystem after you have data in your libraries.

DLm 2.x filesystem (Legacy)

VTEs normally share the virtual tape volumes within a tape library. Each filesystem that provides storage for the tape library filing structure within the DLm system is mounted using a subdirectory named with a two-character VOLSER prefix. For example, if you define and mount a subdirectory BA, that filesystem houses VOLSERs in the range BA0000-BA9999.

When planning for VOLSER ranges, be aware that DLm 2.x supports individual VOLSER ranges only up to 10,000 tape volumes in each filesystem. While DLm holds many times this number, each individual VOLSER range must be restricted to 10,000 tapes, even though it is technically possible to create larger ranges.

EMC service personnel define tape libraries during initial setup.

Note: DLm does not support a configuration where some VTEs use enhanced filesystem and the other VTEs in the configuration use a DLm 2.x (legacy) style filesystem.

DLm 3.x enhanced filesystem (EFS)

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


DLm Administration


the library. When a new filesystem is available, DLm automatically begins using it when creating 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.

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 Celerra Server and/or DD 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.

Tape libraries 91

DLm Administration


Note: DLm does not support a configuration where some VTEs use enhanced filesystem and the other VTEs in the configuration use a DLm 2.x (legacy) style filesystem.

Lock filesystem for EFSIn 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 Celerra Server and DD.

◆ The same lock directory MUST be defined to each VTE accessing a virtual tape library. The same lock directory can be used for more than one virtual tape library.

◆ The lock filesytem is only used during the process of allocating a new scratch volume for output. This filesystem is not used to store tape volumes. (Therefore, the size of the lock filesystem (directory) can be as small as 10 MB).

The lock directory is identified with a global parameter called VOLSERLOCKDIR. This parameter is defined as an additional parameter under the Global options on the Devices panel.

Note: If you do not define a lock directory filesystem, DLm assumes that you want to operate in compatibility mode using an existing virtual library that was created with an earlier version of VTE software.


DLm Administration


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.

Initialize scratch volumes on 2.x filesystemsSince VTEs normally share the virtual tape volumes within a tape library, you need to initialize volumes on only one of the VTEs to make them available to all VTEs sharing the library.

You do not need to initialize all VOLSERs associated with a subdirectory at once. You may initialize the number of VOLSERs you expect to write. For example, assume that you have mounted a 100 GB filesystem using the mount point name BA and you are aware that the average tape volume size is 300 MB. This implies that your disk is capable of holding approximately 335 tape volumes. You may choose to initialize only 500 tapes (for example, BA0000-BA0499, or even BA9000-BA9499). You do not need to initialize all 10,000 VOLSERs (BA0000-BA9999). You can define additional tape volumes later.

Tape libraries 93

DLm Administration


The command to initialize tapes is:

INITIALIZE VOL=volser DEV=devname COUNT=count [CLASS=n][DIR=dirname]

where:

◆ volser is the starting serial number to initialize.

◆ devname is the device name (address) of any tape drive pointing to the tape library.

◆ count is the number of serial numbers to initialize.

◆ n is an optional 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.

Assuming device E980 is a configured device pointing to your tape library then the command to initialize 500 serial numbers to the storage class 0 beginning with VOLSER 000000 would be:

INITIALIZE VOL=000000 DEV=E980 COUNT=500 CLASS=0

This would result with volumes ranging from 000000 to 000499 being created, spreadacross all filesystems in class 0.

If your library has two storage classes defined, class 1 and class 2, the following commands would initialize 1000 VOLSERs per class in the library making both classesready for use:

INITIALIZE VOL=B00000 DEVICE=E980 COUNT=10000INITIALIZE VOL=B10000 DEVICE=E980 COUNT=10000

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 174


DLm Administration


Initialize scratch volumes in EFSIn 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 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 an optional 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.

Note: This parameter is only allowed when the Enhanced Filesystem Architecture option is enabled. Otherwise, the target directory is derived from the first two characters of the VOLSER.

Tape libraries 95

DLm Administration


DIR is an optional parameter. DIR is not a requirement. If DIR is not specified, INITIALIZE places the volumes into the first filesystem it finds within the storage class. During processing, scratch tapes will be automatically moved as needed from one directory (filesystem) to another in the same storage class. However, if you wish to spread scratch volumes across multiple filesystems within a class you may use the DIR parameter to direct a range of tapes to a specific filesystem. CLASS is a required parameter.

Assuming device E980 is a configured device pointing to your tape library then the command to initialize 500 serial numbers to the storage class 0 beginning with VOLSER 000000 would be:

INITIALIZE VOL=000000 DEV=E980 COUNT=500 CLASS=0

This would result with volumes ranging from 000000 to 000499 being created in the first filesystem in class 0.

If your library has two storage classes defined, class 1 and class 2, the following commands would initialize 1000 VOLSERs per class in the library making both classes ready for use:

INITIALIZE VOL=000000 DEV=E980 COUNT=1000 CLASS=1INITIALIZE VOL=001000 DEV=E980 COUNT=1000 CLASS=2

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 in the library with serial numbers ranging from 000000 to 000999. VOL=001000 COUNT=1000 will result in volumes ranging from 001000 to 001999 being created. The result of these two commands is a virtual library with 2,000 volumes whose serial numbers range from 000000 to 001999.

If you are initializing tapes on a Unisys mainframe, include the LABEL parameter telling DLm the tape volume labels will be ANSI format. For example:

INITIALIZE VOL=000000 DEV=E980 COUNT=500 LABEL=A CLASS=0

Note: If your tape devices are defined in a Manual Tape Library (MTL), you must also define them in the mainframe's tape configuration database (TCDB). You must run the DLMLIB utility to do this. Instructions for running DLMLIB are provided in “Locate and upload the DLm utilities and JCL for z/OS” on page 174


DLm Administration


Configure virtual devicesYou can define up to 256 virtual 3480, 3490, or 3590 tape drives on each DLm VTE.

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 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 31 on page 110 allows you to select the configuration file for a VTE. “Manage configuration files” on page 111 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 drives on that VTE’ss.

1. Access the DLm Console using the web browser. “Access the DLm Console” on page 55 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 97

DLm Administration


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


DLm Administration


Note: If the VTE has tape libraries with VOLSERs that reside on DD880, the erase policy must be configured to TTL.

“Tape Erase” on page 113 provides more information about DLm’s erase policy.

• Start space recovery at: Sets the percentage of disk space usage at which DLm starts to recover disk space by deleting the data from scratch volumes. Valid values are 0 to 100. The default is 85%. If the recovery percentage is set to 100, DLm will never automatically delete scratch volume data to recover disk space.

Note: This field is visible only if the Erase policy option, Space or Both, is selected.

• Recover amount (1-100): When DLm starts to recover disk space, it continues erasing data from scratch volumes until this amount of free space has been recovered or until there are no more scratch volumes that can be erased. Valid values are 1 to 100. The default is 5%. Setting recovery amount to 100% causes DLm to erase the data from all scratch volumes on this filesystem once the Start space recovery at value has been reached.

Note: This field is visible only if the Erase policy option Space or Both is selected.

• 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 114 provides more information.


DLm Administration


• 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 independent of any mainframe security programs (such as RACF and ACF/2). By default, these utilities are disabled. Selecting the Tape export enabled option enables the VTE’s export/import utilities.

• Write compatibility: Indicates whether or not the VTE needs backward compatibility with previous generation VTEs. By default, DLm is configured so that it will be backward compatible with the previous version of DLm. This default ensures that a new VTE can be installed into an existing system and share tape volumes with older VTEs. Similarly, volumes written by this VTE can be read by other, older VTEs. For new installations, where there are no existing VTEs, this option can be set to Allow new features but lose backward compatibility. This allows the VTE to take full advantage of all the features of the current generation VTE.

• Guaranteed replication enabled: Select this checkbox to enable Guaranteed Replication.

• GR timeout (seconds) - This is the number of seconds that the VTE should wait for data to be copied to the replica before assuming a replication failure. If the replication does not complete in nnnn seconds, a unit check with equipment check sense is returned to the mainframe's WTM CCW. The default value is 2700 seconds (5 minutes less than the default message interrupt handler (MIH) value of 50 minutes).

Note: The GR Timeout value must be less than the MIH value.

• Additional parameters: In addition to the pre-defined global configuration parameters described above, there are global free-form configuration parameters that can be manually entered into the configuration. To add a free-form parmater, click on the click to add free-form parameters link. The currently available free-form parameter is VOLSERLOCKDIR, seen as a link on the Tape device configuration panel.


DLm Administration


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. “Tape libraries” on page 90 provides more information about tape libraries and filesystems.

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

Control unit Device Type


DLm Administration


In the text box, type the hexadecimal control unit number that you are configuring. For FICON, valid values are 00-FF. For ESCON, valid values are 00-0F.

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

Figure 29 Add devices section


DLm Administration


3. Enter values in the fields of the Add devices section to configure the corresponding parameters for each device:

• Control unit

The hexadecimal control unit number that you are configuring (from the list in the Control units section under Global options).

• Add address range

The starting and ending hexadecimal device unit addresses you wish to add to the VTE. You can define sets of 16 or multiples of 16 (n0—nF).

• Initial device name

Each DLm system must have a unique device name. EMC recommends using the same device name that is defined in the UCB name in the mainframe operating system. The name you type must end in hexadecimal digits, and the configuration program increments the name for the number of devices you are defining. For example, if you are defining 16 devices with an address range of 00 - 0F and you type E900 in the Device Name field, the configurator names the 16 devices E900, E901, E902, ... E90F. The name you type may range from 1 to 8 characters long.

• Tape Library

The library to which this device is connected. To appear in the list of available libraries, the storage must be defined on the Available tab of the Storage panel and be connected to the VTE on the VTE tab of the Storage panel.

Note: The /lockfs entry should never be selected as a tape library.

• IDRC

This parameter turns on or off write compression of the data that 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.


DLm Administration


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.

Note: When writing to VOLSERs stored on Data Domain deduplicated storage, an IDRC setting of YES is ignored. The VTEs do not compress the data before it is written to the deduplicated storage. The deduplication storage server deduplicates and compresses the data before writing to its drives.

IDRC No affects only the writing of data. When IDRC is set to No, the VTE can still read (decompress) virtual tape volumes that it previously wrote with compression on.

IDRC Force configures the DLm virtual tape device to compress the data it writes to a virtual tape disk file regardless of the mainframe's instructions to the VTE regarding the tape file.

Note: Using Force with a deduplicating filesystem can severely limit the ability of the storage system to de-duplicate and will, therefore, use more real disk storage.

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

• FLR active

Select this option to enable the FLR feature. It is unchecked by default. “FLR” on page 158 provides more information.

• FLR retention

The FLR retention option defines a default retention period to be assigned to tape volumes when the mainframe has not indicated an expiration date in the HDR1 record. “FLRRET” on page 159 provides more information.

• FLR mod


DLm Administration


Select this option if you want to allow the tape drive to modify (extend) a tape volume that is in the WORM state. It is unchecked by default. “FLRMOD” on page 159 provides more information.

• FLR extents

FLR extents controls how many times a tape volume in the WORM state can be extended, assuming the FLR mod option is selected. Valid values are from 0 to 10000. If the FLR extents parameter is omitted, the default is 100. “FLREXTENTS” on page 159 provides more information.

• 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 30 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 startes with either "00" or "01". Valid VOLSERs that could be mounted by DLm would include any VOLSER in the range 000000 - 019999; assuming only numeric VOLSERs are in use. If there are no scratch tapes with VOLSERs beginning with "00" or "01" then DLm does not mount a tape and the mount will remain pending.


DLm Administration


If a VOLSER prefix is not defined for a specific scratch synonym then any available scratch tape will be used.

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

ExampleConsider the following definitions of scratch synonyms:

WORKSCRTCH=(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 Configurations panel, click Save Changes to save your configuration to disk.

Figure 31 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 111 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 111 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.

Manage configuration files 111

DLm Administration


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 97• “Add devices” on page 101• “Scratch synonyms” on page 107

5. Save the configuration as described in “Save configuration” on page 110.

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:

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.


DLm Administration


• To delete the configuration file:

Click Delete.

Tape EraseDLm supports a space recovery feature that automatically erases data from scratch tapes on the filesystem based on an erase policy.

The available erase policies are:

◆ Space

◆ Time-To-Live (TTL)

◆ Both (default)

Note: If the VTE has tape libraries with VOLSERs that reside on the Data Domain DD880, the erase policy must be configured for the Time-to-Live options.

The erase policy is a VTE-wide setting. The erase policy can be different on different VTEs. These erase policies affect only AWS-format scratch tapes residing on NFS filesystems. They affect only automatic space recovery erasing. Erase policies have no effect on erase actions performed by mainframe programs such as DLMSCR. You can configure the erase policy using the fields described in “Configure global parameters” on page 97.

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.

Tape Erase 113

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

Note: If the VTE has tape libraries with VOLSERs that reside on the Data Domain DD880, the erase policy must be configured to one of the Time-to-Live options. Data Domain storage does not immediately return the erased storage to the free-space pool, so the SPACE erase policy would result in all scratch VOLSERs being erased once the space threshold is reached.

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.


DLm Administration


Both

DLm starts erasing space if either of the both conditions - Space erase or TTL policy is satisfied.

Manage VTE and ACP logsThe 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 page 60 provides instructions.

The System status tab of the Status menu opens by default.

Figure 32 System status

2. Click the icon in the Logs column corresponding to VTE for which you need the logs.

Manage VTE and ACP logs 115

DLm Administration


Figure 33 VTE 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.


DLm Administration


Figure 34 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. The zip file contains the following directory structure when extracted:

logData-<date collected>- sh.log+ etc - fstab - hosts - mtab - system_params.json + app + snmp - snmptrapd.conf+ linuxsnap - linuxsnap.txt+ opt + webconsole + backup_config

Manage VTE and ACP logs 117

DLm Administration


- last_good_config - last_install - lastInput.json - lastInput.msg + configs - <configuration file name>.json - <configuration file name>.msg - rsaInit.cfg - rsaInitClient.cfg - rsaInitSvc.cfg + logs - apply.log - logAll.txt - status.txt+ proc - mdstat - mounts+ var + log + apache2 - access_log - error_log

Back-end tape supportThe 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.


DLm Administration


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 mappingTo 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 29 on page 102 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 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 28 on page 101.)

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

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.

Back-end tape support 119

DLm Administration


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

STOPVTSTARTVT

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

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 devicesAfter mapping a device as described in “Device mapping” on page 119, 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.


DLm Administration


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.

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

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:


Back-end tape support 121

DLm Administration


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 27 on page 98 opens.)

4. Select the Tape import/export enabled check box. “Configure global parameters” on page 97 provides more information about this field.

5. Save the configuration as described in “Save configuration” on page 110 and install it on the VTE as described in “Activate or install a configuration” on page 111.

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 69 provides instructions.

2. After connecting to the individual VTE, you can type the EXPORT and IMPORT commands in the VT console.

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 212 provides details about how to use the EXPORT command. “IMPORT” on page 215 provides details about how to use the IMPORT command.

DLm diagnostic reportingThe different subsystems of the DLm system generate messages as they operate. The major sources of messages in DLm are:

◆ VTEC

◆ ConnectEMC (reports VTEC and Celerra Server issues)

◆ DataDomain


DLm Administration


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 124 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 198 provides more information.

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


2. Click External.

3. Select the Notify tab.

DLm diagnostic reporting 123

DLm Administration


Figure 35 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 recipientsYou can configure which messages get sent to an SNMP management console or the z/OS master console.


2. Click Messages.

Three tabs appear representing informational, warning, and error messages:

• Error message routing• Warning message routing• Informational message routing

Each tab shows a complete list of all DLm messages in that particular category.

3. Select the tab corresponding to the message type you want to configure.

All messages in the Errors message routing tab are preselected and cannot be deselected.


DLm Administration


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

ConnectEMC

The Celerra ConnectEMC function can automatically notify the EMC service center or other service providers if the VTEC or Celerra system detects a serious problem. ConnectEMC sends messages using email, FTP, or a Celerra 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 445 provides a list of traps that generate ConnectEMC events.

DLm diagnostic reporting 125

DLm Administration


Data Domain DD880 alert notifications

The DD880 generates e-mail alerts when it identifies a problem with either a software component or a hardware component. Not all events generate an immediate e-mail notification.

Alert e-mail (generated immediately)All events of CRITICAL or WARNING severity result in immediate notification to the EMC Data Domain support group. For events with a CRITICAL severity level, the Data Domain DD880 can also be configured to forward the e-mail notification to the e-mail address of the system administrator.

Autosupport e-mails (generated once a day)The Data Domain DD880 generates daily e-mails to the EMC Data Domain support group. These e-mails contain information about all outstanding alerts and the status summary of the general health of the DD880. You an also configure Autosupport emails to be sent to the email address of the system administrator.

AWSPRINT library utilityThe 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 214 provides the details of the command.



CHAPTER 4DLm Replication

This chapter explains the replication concepts and features of a DLm system:

◆ Overview........................................................................................................ 128◆ Replication terminology ................................................................................. 130◆ Celarra replication.......................................................................................... 132◆ DLm Celerra replication and disaster recovery................................................. 134◆ Deduplication storage replication................................................................... 137◆ Replication between DLm3.x and DLm2.x systems ......................................... 142

DLm Replication 127

DLm Replication


OverviewDLm offers IP-based remote replication, which leverages your IP network infrastructure, eliminating the need for channel extension hardware. The replication is storage-based and therefore has no impact on mainframe host operations or performance. DLm replication is asynchronous and only the changes are replicated between the remote sites.

DLm supports unidirectional and bidirectional replication, which means that the source system can also be a target system and vice versa. Celerra replication supports up to four target sites per source system, which means you can replicate data to four different sites. The source and destination DLm systems do not have to be configured with the same capacity.

DLm replication is a separately licensed feature. In the DLm960, Celerra replication and deduplication storage replication are licensed separately. There are some key differences in the way Celerra replication and Data Domain replication work.

Note: A separate license is required for each active storage controller.

Celerra replication in DLm occurs at the filesystem level. A filesystem is a virtual shelf of tapes in which a continuous range of VOLSER are defined. Celerra replication on DLm lets you maintain a remote copy of a collection of virtual tape volumes. Figure 37 on page 129 depicts DLm replication. However, all the filesystems under a tape library should have the same replication state.

Celerra replication is based on EMC Celerra Replicator V2. Using Celerra Replicator (V2) provides more information on Celerra V2 replication. This document and the latest documentation for your specific version of the Celerra operating environment (OE) for file are available at EMC Online Support website.

Data Domain replication occurs on directories corresponding to a tape library and not at the filesystem level. A tape library is a collection of virtual shelves of tapes. In each virtual shelf, a continuous range of VOLSERs is defined. Data Domain replication is based on the EMC Data Domain Replicator. Only unique data with respect to the destination is replicated from the source Data Domain, resulting in large savings in replication bandwidth utilization.


DLm Replication


Figure 37 DLm replication

Data Domain

Primary site Remote site

Data Domain

Data Domain

GEN-001347

VTEC

VTEC

Mainframe

VTEC

Mainframe

Mainframe

Celerra Celerra

Overview 129

DLm Replication


Replication terminologyThe following is some of the terminology used when describing DLm replication:

◆ Replication

The process of sharing information to ensure consistency between redundant resources.

◆ Source object (SO) is also known as:

• The production object (PO)

• The production filesystem (PFS)

• The source filesystem (SFS)

This is the original source collection of data to be replicated.

◆ Destination object (DO) is also known as:

• The destination filesystem (DFS)

• The target filesystem (TFS)

• The secondary filesystem (SDS)

This is the replicated copy of the original data.

◆ Replication session

The relationship that enables replication between the SO and the DO, including two internal checkpoints or snapshots for both SO and DO.

◆ Time-out-of-sync

Defines how closely you want to keep the destination object synchronized with the source object. This is specified in minutes.

◆ Full copy

The complete copy of the source object that is sent to the destination when a replication session is first started, or when a common base is not found.

◆ Differential copy

The changes made to the source object (since the previous replication) that are sent to the destination during replication.


DLm Replication


◆ Snapshot or checkpoint

A point-in-time copy of data. This view of data takes very little space and are just pointers to where the actual files are stored. Snapshots/checkpoints are used when transporting the full copy after first synchronization. Using SnapSure on Celerra provides detailed information on snapshots. This document is available at EMC Online Support website.

◆ Disaster recovery (DR)

The process, policies, and procedures for restoring operations critical to the resumption of business, including regaining access to data, communications, and other business processes after a natural or human-induced disaster.

◆ Recovery point objective (RPO)

A description of the amount of data lost, measured in time. For example, if the last available good copy of data was made 18 hours before an outage, then the RPO is 18 hours. You can define different RPO values for different VOLSER ranges or tape libraries based on information criticality.

◆ Recovery time objective (RTO)

A specified amount of time within which a business process must be restored after a disaster to avoid unacceptable consequences associated with a break in continuity. RPO and RTO form the basis on which a disaster recovery strategy is developed.

◆ Storage controller interconnect is also known as:

• Data Mover interconnect (DMIC)

• DART interconnect (DIC)

The storage controller interconnect is a communication path between two Celerra storage controllers (Data Movers) that is used for all replication sessions between those two storage controllers. This connection defines all interfaces that can be used on each storage controller, and also the bandwidth throttle schedule. This interconnection must be created in both directions.

Replication terminology 131

DLm Replication


Celarra replication Celerra replication is based on EMC Celerra Replicator V2. Using Celerra Replicator (V2) provides more information on Celerra V2 replication. This document and the latest documentation for your specific version of Celerra operating environment (OE) code are available on the EMC Online Support website.

Prerequisites for Celerra replication are:

◆ The required replication licenses are installed in the source and destination DLm systems.

◆ Celerra runs the Celerra OE version 7.0.35.3 or 7.0.40.1 or later.

◆ Celerra runs the Celerra OE version 7.0.40.1 or later.

◆ You have the IP addresses that are assigned to the source and destination storage controllers (Data Movers).

◆ The HTTPS connections between the source and destination storage controllers (port 5085) and between the source and destination Control Stations (port 443) are secure.

◆ Sufficient storage space is available for the source and destination filesystems.

Supported configurations

DLm supports the following configurations for Celerra replication:

◆ Local replication: Between two separate storage controllers located within the same DLm.

◆ Remote replication: Between two separate DLm systems, typically (but not necessarily) in different geographic locations. This includes replicating from a single source to up to four separate destinations.

◆ Bi-directional replication: DLm A replicates to DLm B, while DLm B replicates a different filesystem to DLm A.

Currently, these configurations are not supported:

◆ Replication to more than four separate destinations

◆ Cascading (for example, DLm A replicates to DLm B which in turn replicates to DLm C)


DLm Replication


Celerra replication procedure

DLm uses Celerra Replicator V2 to replicate VOLSERs stored in NFS file systems on the source Celerra. The filesystem on the Celerra corresponds to a VOLSER range in DLm.

The replication environment is initially set up for you at installation by EMC service personnel. They use the DLm tools to create the target filesystems and then connect the source to the target filesystem. The target filesystem must have the same name and size as the source filesystem. To make changes or additions to your replication environment, contact EMC Customer Support.

Celerra replication sessionsDLm allows many Celerra replication sessions to be active simultaneously. Creating a replication session involves these tasks:

1. Ensure that the SO already exists.

2. Create and mount (read only) the DO with the same size and properties as the SO (if it does not already exist).

3. Create internal snapshots at both the source and destination end.

Note: Using SnapSure on Celerra provides detailed information on snapshots. This document is available at EMC Online Support website.

4. Configure and start the replication scheduler that drives the time-out-of-sync policy between the two ends.

5. Establish replication between the source and destination end.

Data replicationThe replication of source data occurs in the following way:

1. An application running under z/OS writes data to one or more virtual tapes (VOLSERs) within a filesystem (VOLSER range) set up for replication on DLm.

2. Replication creates a checkpoint—a point-in-time, block-level copy of the underlying filesystem.

3. Using intelligent scheduling algorithms, checkpoints are transferred to the remote destination asynchronously.

4. Only changed blocks are copied.

Celarra replication 133

DLm Replication


Celerra RepOutOfSyncHours feature

DLm version 2.1 and later provides a replication monitoring feature called the RepOutOfSyncHours feature. The EMC Celerra Replicator monitors the synchronization status of each active replication session. Every time a session goes out of synchronization, a timer starts tracking the duration of the out-of-sync state. If that session does not get synchronized within a specified time period, DLm generates a ConnectEMC alert for an out-of-sync callhome condition. If the session returns to synchronized state before the specified time period expires, the timer is reset.

The default time period before the generation of an out-of-sync callhome alert is eight hours. If you want to change the default time period, contact EMC Customer Service.

Using Celerra Replicator (V2) provides more information about the RepOutOfSyncHours feature. This document and the latest documentation for your specific level of Celerra OE code are available atEMC Online Support website.

DLm Celerra replication and disaster recovery

This section explains the role of DLm replication in a disaster recovery (DR) strategy. “Replication terminology” on page 130 explains terminology relevant to DLm replication in a disaster recovery strategy.

Replication is not a complete disaster recovery strategy, although it provides an essential enabling technology for accomplishing DR. A DR workflow must take into consideration your environment, potential scenarios, and the desired recovery objectives.

The disaster recovery procedure in DLm involve the following steps:

1. Mount the read only copy of the all the filesystems at the target site on the VTEs.

2. Identify the tapes that have been lost due to the disaster event.

3. Perform a failover of the filesystems in the Celerra.

4. Unmount and remount the filesystem as read/write.

5. When the source system becomes available, copy the changes made at the target back to the source system.

6. After all the changes have been copied to the source, change the configuration to the original configuration.

Replication reduces both RPO and RTO. Each filesystem (VOLSER range) maintains a unique and independent value for:


DLm Replication


◆ Time-out-of-sync — This controls how often the destination site is refreshed. Depending upon your load and bandwidth, this can be nearly synchronous. This value is equivalent to the RPO described in “Replication terminology” on page 130.

◆ Quality of service (QoS) — This controls bandwidth throttling by specifying limits on specific days and hours.

Time-out-of-syncDLm replication uses an adaptive scheduling algorithm to determine when to refresh replicated storage. RPO is typically set to less than 10 minutes. The replication scheduler uses best effort to maintain the specified RPO for each range of VOLSERs, and automatically works to catch up after any RPO violation. Advanced capacity planning is required to make sure that RPO violations do not occur. However, events (SNMP traps or email) can be configured in case RPO violations do occur.

Quality of serviceInterconnect QoS defines up to six bandwidth schedules. These are defined in terms of days, hours, and bandwidth.

Identifying lost tapesTo identify tapes that have been lost due to the disaster event:

1. Use the awsprint utility to identify the list of scratch tapes in the file systems that have been disrupted. Compare the output of the utility with the list of scratch tapes for this VOLSER range according to the Tape Management Catalog. Some will appear in the awsprint output but not in the Tape Management Catalog as they were no longer in scratch state when the disaster event occurred. These tapes might not have completed replicating to the target Celerra. “AWSPRINT library utility” on page 126 provides information about the utility.

2. Identify the last snapshot that was transferred successfully to the target using the command processor CP504. The output contains the last successful sync time for a particular file system.

3. Execute GENSTATS with the following options:

a. STILLINUSE

b. PATHNAME=“name of tape library”

Celarra replication 135

DLm Replication


The Genstat report provides a list of VOLSERs that were being trasferred to the destination at the time of the disaster event.

Note: The DATESTART parameter may be used to indicate the start of the search.

An example of param usage in the JCL to generate such the report:

STILLINUSE PATHNAME=tapelib/BB

The sample output:

STILLINUSE PATHNAME=tapelib/BB--------------------------------------------------------------VOLSERS STILL MOUNTED : NODENAME DEVICE VOLSER LAST MOUNTED PATH VTE1 VTE1-01 BB0161 2011/04/29 23:35:14 tapelib/BB VTE1 VTE1-00 BB0180 2011/04/29 23:35:14 tapelib/BB VTE1 VTE1-02 BB0160 2011/04/29 23:35:14 tapelib/BB

This list indicates the VOLSERs that has been lost due to the disaster event and these jobs will need to be re-run.

EMC Disk Library for mainframe Command Processors User Guide contains more information about GENSTATS and command processor CP504.

DR testing from a copy of production dataDR testing is performed without interrupting data replication between the DR and production sites by using a copy of the production data. Disk arrays allow the creation of both read-write snaps and instant read-only copies:

◆ Read-write snaps:

• Confirm operation at the DR site

• Require twice the storage capacity of SO

◆ Read-only copies:

• Confirm that the tapes can be mounted and all required data can be accessed

• Require minimal incremental storage capacity


DLm Replication


Tape catalog considerations

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

Deduplication storage replicationReplication on deduplication storage is executed by the Data Domain Replicator software available with DD880. The replication environment is initially set up for you at installation by EMC service personnel. To make changes or additions to your replication environment, contact EMC Customer Support.

Note: Deduplication storage replication applies only to DLm960 systems equipped with DD880 storage system.

The Data Domain Replicator software includes different replication policies that use different logical levels of the system for different effects. In a DLm environment, the DD880 is configured to only use directory replication, which offers maximum flexibility in replication implementation. With directory replication, a directory (sub-directory, and all files and directories below it) on a source system is replicated to a destination directory on a different system. Directory replication transfers deduplicated changes of any file or subdirectory within a Data Domain filesystem directory that has been configured as a replication source to a directory configured as a replication target on a different system.

In DLm, the directory replication context is established at the directory that corresponds to a virtual tape library. Hence, replication cannot be enabled or disabled for individual VOLSER ranges. Data Domain replication uses a proprietary protocol to transfer only the data that is unique at the destination. Replication transfer for a file is triggered by a file closing. In cases where closes are infrequent, DD Replicator forces data transfer periodically. Once the complete file has been established on the replica, it is made immediately visible to the replica namespace and may be restored or copied at once. The replica at the destination is set to read only. All transfers between the source and the destination use the Diffie-Hellman key exchange. Data Domain Replicator uses its own large checksum to verify the accuracy of all sent data, in addition to the verification that TCP provides.

Deduplication storage replication 137

DLm Replication


Note: The two replication ports on the DD880 are configured in Failover mode to protect against link failures. Failover is the only configuration that DLm supports for the DD880 replication ports. No other configuration is supported for these replication ports.

Prerequisites for DD replication are:

◆ Data Domain Replicator licenses are installed in the source and destination DLm systems.

◆ The software version on the destination VTE must be the same as or higher than the software version on the source VTE.

◆ You have the IP addresses that are assigned to the source and destination DD880 systems.

◆ Cat5 Ethernet cables are available for each DD880 system and all required WAN switches/ports are configures end-to-end.

◆ Sufficient storage space is available in the source and destination filesystems. At initial replication setup, EMC recommends that you plan disk capacity based on a deduplication ratio of zero.

Supported configurations

The following configurations are supported:

◆ Unidirectional from a single source to a single destination

◆ Bidirectional between a single source and destination pair

Note: Data Domain replication is supported only when both the source and target systems are DLm DD systems. Replication from a DD880 to a Celerra is not supported.

Replication session setup

The requirements for the successful setup of a Data Domain directory replication are:

◆ The destination system must be large enough to store all the data replicated from the source.

◆ The network link bandwidth must be large enough to replicate data to the destination.


DLm Replication


◆ The fully qualified domain names FQDN for the source and the destination DD880 systems must be registered in the DNS servers.

If the hostname of the DD880 is DD-1, the FQDN, for example, may be"DD-1.customer.com."

◆ The replication context directory is defined after the directories are created at both the source and the destination. EMC recommends that you set up replication before the system restores backups to the source directory. Erase all files from the destination directory if it is not empty before the initialization of a directory context.

◆ Replication initialization must be executed from the source.

Throttling

As a basic form of quality of service (QoS), times of day during which data may or may not be sent, along with limits to the amount of bandwidth that can be used.

Note: Contact EMC Service if this needs to be configured. By default, no throttling is set.

Recovery point

In a Data Domain system, deduplication is fast and inline, and replication can be simultaneous with backup, so it can finish shortly after backup. The restore image is available immediately from the replica. The recovery point is from the current snapshot before the delay represented by the backup window.

Recovery time

The replica contains only deduplicated data. The recovery time is the same as the restore rate from the deduplication pool in the replica. This should be measured carefully with a large dataset to ensure sustained performance characteristics.

The Data Domain Replicator uses the directory replication feature to support replication at the tape library level.


DLm Replication


Disaster recovery in Data Domain systems

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

In the case of a disaster, the VOLSERs in the tape library accessed after the Sync'd as of time reported for that tape library is lost and cannot be recovered. You can use the GENSTAT utility with the SYNCTIME, DATESTART, DATEEND, and PATHNAME parameters to identify the data that is not replicated. The EMC Disk Library for mainframe Command Processors User Guide contains more information about GENSTATS.

To identify the unreplicated data stored on a Data Domain system:

1. Execute the command processor CP603 with the status option for each replication-enabled tape library that stores its data on a DD880.

2. Note the Sync’d as of time for each replication-enabled tape library on the DD880 system.

3. Execute the command processor 998 to gather statistics .

4. Execute GENSTATS with the following options:

a. STILLINUSE

b. SYNCTIME=hr:mm:sec (the Sync’d as of time)

c. DATESTART=yr:mm:dd (the date to start the search)

d. DATEEND=yr:mm:dd (the date of the Sync’d as of time for this context)

e. PATHNAME="name of tapelibrary" (for example, “tapelibZZZ”)

Note: If you run GENSTATS with the PATHNAME option, the report lists VOLSERs in the tape library that correspond to the specified pathname, the updates of which have not been replicated.


DLm Replication


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

EMC Disk Library for mainframe Command Processors User Guide contains more information about GENSTATS, command processor 998, and CP603.

This GENSTATS report provides a list of VOLSERs that were accessed after the Sync’d as of time and might not have completed replicating the data to the target.

This is an example of how the parameter is used in the JCL:

STILLINUSE DATEEND=10/04/29 SYNCTIME=23:36:00 PATHNAME=tapelibZZZ/

This is the report generated:

VOLSERS MOUNTED AFTER SYNCTIME (10/04/29 23:36:00) 2010/04/29 23:46:36 S10162 2010/04/29 23:46:36 S20181 2010/04/29 23:46:36 S30161 2010/04/29 23:57:59 S10163 2010/04/29 23:57:59 S20182 2010/04/29 23:58:00 S30162 2010/04/30 00:09:25 S10164 2010/04/30 00:09:25 S20183 2010/04/30 00:09:25 S30163 2010/04/30 00:20:49 S10165 2010/04/30 00:20:49 S20184 2010/04/30 00:20:50 S30164 ----------------------------------------------------------------------VOLSERS STILL MOUNTED : NODENAME DEVICE VOLSER LAST MOUNTED PATH VTE1 VTE1-01 S10161 2010/04/29 23:35:14 tapelibZZZ/S1 VTE1 VTE1-00 S20180 2010/04/29 23:35:14 tapelibZZZ/S2 VTE1 VTE1-02 S30160 2010/04/29 23:35:14 tapelibZZZ/S3

The report provides two lists of VOLSERs:

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

◆ VOLSERs that were mounted after the Sync'd as of time

Directory replication flow

This is how DD880 directory replication works:


DLm Replication


◆ The source Data Domain system continuously sends segment references (metadata) to the destination Data Domain system.

◆ Destination Data Domain replica filters them by looking up its index to check which segments it doesn't already have. This could impact replication performance due to the high restore/backup load.

◆ The source periodically asks the replica which segments need to be sent.

◆ The destination responds with list of segment references that it does not have.

◆ The Source reads the requested segments from its filesystem and sends them.

◆ Replication code picks up the logged close records from a queue and begins replication. The maximum amount of time between a write and when replication will start is one hour.

Replication logs the close of a modified file based on the following considerations:

• 10 minutes after the last access, NFS closes the file.

• Every hour (by default), all files are closed regardless of how recently they were written.

• If many files are being accessed or written, files may be closed sooner.

Replication between DLm3.x and DLm2.x systemsDLm 3.1 and later support replication between DLm 3.x and DLm 2.x systems. This section explains the prerequisites and considerations to enable such replication.

Prerequisites

◆ The Gen2 DLm should be a DLm 2.5 system.

◆ The Celerra in a DLm 2.x system should support Replicator V2 for replication.

◆ The target filesystem on the backend Celerra or Celerra must be of the same size or greater than the size of the source filesystem. The DLm 3.x system creates filesystems in TiB increments. You must consider the size of the filesystem created on the DLm2.x if it has to be used for replication with 3.x systems.


DLm Replication


◆ The DLm 3.x system cannot use Enhanced File System when involved in replication with DLm 2.x systems and, therefore, Storage Classes cannot be defined and all file systems will be part of the default Storage Class '0'.

◆ DLm 2.x systems support only static key encryption. Use of RSA Key Manager for key generation is not supported in a DLm 2.x environment. Contact your EMC representative for details about support for replication of encrypted volsers between a DLm 2.x system and 3.x system.

Replication considerations

IMPORTANT

If you want DLm 3.x system to replicate to a 2.x system, you must decide while initially configuring the DLm 3.x system. Once configured, you cannot change the settings and enable or disable replication between 2.x and 3.x systems. These configuration settings must be done by EMC service personnel only.

To enable replication between a DLm 3.x system and DLm 2.x systems, the lock filesystem must be un-mounted from all the VTEs. A standard procedure is followed to mount the Lock filesystem for all DLm systems. This procedure must be skipped. If this is already executed, it must be rolled back.

Note: If the DLm system has been put into use with Lock File system, it cannot be rolled back.

1. In the Storage > Available tab in DLm Console, the entry for /lockfs/LOCK needs to be removed from the list of mount points defined. This list is used to define the list of file systems that need to be mounted on each VTE.

2. The DLm install procedure requires that the Additional parameters dialog to be populated with VOLSERLOCKDIR /lockfs/LOCK. This setting for the VOLSERLOCKDIR must be removed.

3. Both these changes must be saved.

4. The Data Domain DD880 in the DLm2.3.X is shipped with DD OS version 4.7.x. These DLm systems will need to be upgraded to DLm2.5, which supports DD OS version 4.9. The DD880 system in a DLm6960 supports DD OS version 5.1.0.4. Replication between DD OS 4.7.x and the DD OS version 5.1.x is not supported.

Replication between DLm3.x and DLm2.x systems 143

DLm Replication




CHAPTER 5Guaranteed Replication

This chapter provides information about the DLm Guaranteed Replication (GR) feature, an enhancement to DLm's replication capabilities. The major topics include:

◆ Overview of GR............................................................................................... 146◆ GR configuration ............................................................................................ 148◆ Manage GR..................................................................................................... 150

Guaranteed Replication 145

Guaranteed Replication


Overview of GRThe disaster recovery capabilities of DLm include data replication using the Celerra Replicator V2. Chapter 4, “DLm Replication,” provides more information on the regular DLm replication feature.

Celerra Replicator V2 replicates the data periodically and asynchronously. It is configured to periodically create a snapshot of the local DLm storage/filesystems and then asynchronously transfer the data at the time of the snapshot to the remote DLm. The data stored after the last snapshot is not replicated until the replicator takes the next snapshot. Therefore, this data may be lost if connection to the local DLm is suddenly lost.

For most situations and applications, this type of periodic and asynchronous replication is adequate. But, for some critical applications where the data is expected on the remote DLm as soon as it is written to local DLm, this type of asynchronous replication is not adequate.

DLm version 2.2 and later offers an enhancement to DLm's replication capabilities called Guaranteed Replication (GR).

This feature forces Celerra Replicator to completely replicate a tape volume (VOLSER) to the remote site every time the mainframe issues two consecutive write tape marks on a tape (performs a tape close). GR causes the VTE to withhold acknowledgements of tape close from the mainframe until the VTE confirms that the local (or source) Storage Controller (within the DLm) has completed replicating the tape volume to the remote Celerra.

The GR feature is essential for customers and situations where periodic, asynchoronous replication is not adequate. For example, if the DLm at the primary site fails and the processing needs to relocate to the remote site, the data that was being replicated at the time of failure is either completely or partially lost. GR helps to avoid the potential loss of data by ensuring that the tape volume is replicated before it closes.

Note: Since devices enabled for data deduplication do not support GR, select No for GR during device configuration for such devices.




When a tape volume on a replication-enabled filesystem is written to a DLm tape device configured for GR, it is assumed that when the VOLSER is successfully closed, it has been fully replicated to the DR site. Assuming the system log indicates a VOLSER was successfully closed, the VOLSER at the DR site is a completely replicated copy.

Table 8 Behavior of GR and non-GR devices

Filesystem Non-GR device GR device

Non-GR filesystem Read (from a named VOLSER mount) - yes

Read (from a named-VOLSER mount): Yes

Write (to a named VOLSER mount) - yes

Write (to a named-VOLSER mount): Yes, with DLm545W warning message

Mount Scratch - yes Mount Scratch: No; only GR filesystems are searched

GR filesystem Read (from a named VOLSER mount) - yes

Read (from a named-VOLSER mount): Yes

Write (to a named VOLSER mount) - yes

Write (to a named-VOLSER mount): Yes

Mount Scratch - yes Mount Scratch: Yes; only GR filesystems are searched

Overview of GR 147



Tape requirements for GR

Before configuring GR, you must note that not all tapes support GR. Only tapes that use any of the following tape labeling standards support GR:

◆ IBM Standard Labeled tapes (SL)

◆ IBM Non-Labeled tapes (NL)

◆ ANSI Labeled Tapes (AL)

These three standards are implemented in most IBM operating systems as part of the OS data management components (for example, BSAM and QSAM in z/OS). These standards require that tapes must be closed with two consecutive tape marks. These tape marks will trigger GR to start a replication cycle.

GR configurationYou can implement the GR feature on either a single tape drive or multiple tape drives. For example, a VTE, within a DLm that emulates 32 tape drives, might have only 8 or 16 drives configured for GR, while the remaining tape drives can be configured without GR.

There are multiple steps in the GR configuration:

1. Install the replication and GR licenses.

GR is a licensed feature. Contact EMC Professional Services to install GR license.

2. Configure the replication.

GR works only for the filesystems or filesystems that have replication setup. Contact EMC Professional Services to configure replication for the filesystems on which you want GR.

Note: It is not recommended to enable replication on a subset of filesystems in a tape library intended for GR. It should be enabled on all the filesystems in a tape library even if only one (or few of them) is intended to be used for GR.

3. Configure the GR timeout value. “Configuring GR Timeout value” on page 149 describes this task.

4. Configure the devices for GR. “Configuring devices for GR” on page 150 describes this task.




5. Save and install the configuration changes made. This will restart the VTE application.

Note: Every time you make any change to the device configuration or configure replication on any tape library file system, you should save and install the configuration for the change to take effect. This will restart the VTE application.

Restarting the VTE application will result in a temporary outage of any device emulated by the application. You must coordinate the restart operation with the mainframe operations. You must vary all devices being emulated by a VTE to OFFLINE state before you restart the VTE application.

Configuring GR Timeout valueThe GR Timeout parameter must be configured to enable the GR feature. GR Timeout specifies the duration (in seconds), for which the VTE should wait for acknowledgement that the replication refresh has been completed before assuming a failure has occurred. This value prevents the tape drive from remaining in a wait state should replication to the remote DLm not complete. The default value for GR Timeout is 2700 seconds or 45 minutes, which is 5 minutes less than the standard mainframe Missing Interrupt Handler time of 50 minutes.

Note: The GR Timeout value must be less than the mainframe MIH value. If the MIH is less than GR Timeout, the mainframe abends the job when it encounters the MIH.

You can configure the GR Timeout value in the General Parameters section of the DLm configuration file. “Configure global parameters” on page 97 contains instructions to configure this value.

When a tape drive is configured for GR, the VTE performs two functions after it receives two consecutive write tape marks (WTM CCWs) from the mainframe:

◆ It flushes its cache for the filesystem where the VOLSER has been written.

◆ It issues a request asking the replicator to refresh the replication of the filesystem to the remote DLm.

GR configuration 149



Configuring devices for GRThe GR feature is implemented on a device-by-device basis. It is not necessary to configure all the devices in your DLm or all the devices within a single VTE for the GR feature. You can have a subset of your drives configured for GR. Contact EMC Professional services for assistance in configuring devices for GR.

You can configure and view the device configuration for each VTE by clicking on the Devices tab in DLm console. Figure 29 on page 102 shows the Add devices and the Current devices section in the Devices tab of the DLm Console, where GR must be configured.

Note: GR will only work if a device is configured for GR and the tape library file system has been enabled for replication.

“Mainframe configuration for GR” on page 171 provides the instructions for mainframe configuration for GR.

Manage GR Every time a DLm VTE receives two consecutive tape marks from the mainframe on one of its tape volumes, the VTE initiates GR. The VTE requests the Celerra Replicator to refresh the filesystem where the VOLSER is stored and waits for confirmation that the replication refresh is complete. If two consecutive write tape marks occur, the VTE acknowledges tape close after it receives the replication confirmation.

All output tapes written to a device configured with GR trigger replication if the filesystem to which the tape is written is configured for replication.

During a Control Station failover event, the current GR and new host requests for GR, are likely to fail. However, as soon as the failover is complete and the secondary Control Station assumes the primary role, the subsequent requests for GR work as expected.

Note: In the event of a Control Station failover, several minutes may be needed to reach the stage where GR functions are operational again.

Verify GR configuration

In addition to verifying the Celerra configuration, verify the GR configuration by using the query GR command.




The output of the query GR command displays:

◆ The GR Timeout value

◆ The tape devices configured with GR set to YES

◆ The filesystems on the Storage Controllers that have been configured for replication and are eligible for the GR function

MIH considerations for Guarantied Replication

As a best practice, the value chosen for MIH should be several minutes more than that chosen for GR Timeout. In this way, the DLm's actions, in case of replication issues, occur before the actions associated with MIH, giving the user closer control of managing the consequences of replication issues. Compare these situations:

◆ What happens if MIH times out before GR is done or times out:

When GR finishes (either completes or GR Timeout is reached), the VTE will see many attempts from the host to clear the channel and the job will abend.

◆ What happens when MIH forces cancel:

The job eventually clears (abend) on the host. The host may have sent a FORCE after the initial CANCEL accomplished nothing. This is not recommended for the same reasons that a manual FORCE is not recommended (see the MVS Commands User's Guide from IBM). The virtual tape drive remains unresponsive until the GR finishes (either completes or GR Timeout is reached). Attempts to use the drive during this unresponsive time is likely to result in the drive becoming boxed.

◆ What results when manually canceling the job:

When GR finishes (either completes or GR Timeout is reached), the VTE will see many attempts from the host to clear the channel and the job will abend. The CANCEL of the mainframe job will NOT complete until GR releases the Virtual Tape Drive (either GR completes or GR Timeout is reached).

◆ What results from a manual CANCEL and FORCE

The job clears (abend) on the host. Use of FORCE is NOT recommended (see the MVS Commands User's Guide from IBM). The virtual tape drive remains unresponsive until the GR finishes (either GR completes or GR Timeout is reached). Attempts to use the drive during this unresponsive time is likely to result in the drive becoming boxed.

Manage GR 151


CHAPTER 6DLm WORM Tapes

This chapter provides information about defining Write Once Read Many (WORM) filesystems in DLm using the DLm file lock retention (FLR) capability. Topics include:

◆ Overview........................................................................................................ 154◆ Configure WORM ............................................................................................ 157◆ Determine if WORM is enabled ....................................................................... 160◆ Extend or modify a WORM tape ...................................................................... 161◆ Scratch WORM tapes ...................................................................................... 162

DLm WORM Tapes 153

DLm WORM Tapes


OverviewDLm WORM tape is an optional feature which emulates "write-once-read-many" physical tape cartridges. DLm WORM tape allows secure storage of data that is critical for business processes, and for regulatory and legal compliance, by protecting against unintentional or disallowed modification of a virtual tape. You can control the protection status and retention periods at the individual tape level.

Note: The WORM tape feature is only available for tapes which reside in filesystems created on Celerra file storage.

Once you set a tape to the WORM state, the tape’s mode changes to read-only and that tape cannot be modified, deleted, or renamed until the WORM retention period has passed. After the WORM retention period has passed, the file is considered expired. Expired WORM files are not automatically deleted, but once a WORM file is expired it can be deleted. An expired WORM file cannot be changed back to writable mode, nor can it be modified or renamed. However, an expired WORM file can be reset to the protected WORM state by changing the FLR retention details.

Two different types of file-level retention are available: enterprise (FLR-E) and compliance (FLR-C).

◆ FLR-E protects data content from changes made by users, but allows changes to be made by administrators.

◆ FLR-C protects data content from changes made by users, from changes made by administrators, and also meets the requirements of SEC rule 17a-4(f).

While these two types of the underlying Celerra FLR features differ in important ways, management of DLm WORM tapes from the mainframe host is the same in either case.

Note: Filesystems FLR enabled are referred to as WORM filesystems or FLR filesystems in the following sections.

WORM control file

The VTE uses a hidden WORM control file named .FLR to control whether tape volumes written to an FLR-enabled filesystem are put into the WORM state upon close or whether files are left writable. Files will only be set to the WORM state if this file is


DLm WORM Tapes


present. If the ".FLR" file is not present, the VTE will not set files to the WORM state. This feature facilitates development and testing of the preparation of DLm WORM tapes without actually committing those tapes to the WORM state.

Once testing is complete, WORM capabilities can be enabled by adding the control file to the filesystem. Whenever the control file is in place, all future volumes written to the filesystem from a drive configured for WORM will automatically be locked during tape unload processing by the host.

Note: If the .FLR file is deleted, tape volumes that the host unloads after that time will not be put in a WORM state, but tapes already in WORM state are not affected.

Note: The DLm594W system message is generated when the host unloads a tape volume written to an FLR-enabled filesystem but the WORM control file does not exist at that time in that filesystem.

File locking for WORM

The VTE automatically sets a virtual tape file to the WORM state and locks it at tape unload time if:

◆ The DLm_FLR license is installed on the VTE.

◆ The VTE virtual tape drive is configured with FLR=YES.

◆ The filesystem on which the virtual tape file resides:

• Is on an FLR-configured Celerra filesystem

• Is an FLR filesystem

• Contains a ".FLR" control file

◆ The tape's HDR1 label specifies an expiration date, or the virtual drive is configured with a default FLR retention period.

Retention period

Labeled tapesConsiderations for determining the retention period for labeled tapes:

Overview 155

DLm WORM Tapes


◆ For labeled tapes, if the host has specified an expiration date in the HDR1, the retention period is set to 00:00:01 hours on the specified date. For multi-file tapes, only the first HDR1 on the first dataset, is used to determine the entire tape's retention period.

Note: HDR1 dates are specified in the Julian date format YY/DDD or YYYY/DDD.

If the HDR1 does not contain an expiration date, the device's default WORM retention period, FLRRET, is used to determine the action taken:

• If FLRRET is 0, the tape is not placed in the WORM state (that is, "no retention.").

• If FLRRET is positive, its value is added to the current date and time, and the result is used to set the retention period.

• If FLRRET is negative, permanent retention is set.

Several HDR1 expiration dates have special meaning rather than as a specific date:

• 99/365, 1999/365, 99/366, and 1999/366 all mean permanent retention. The VTE sets the file's FLR retention period to 0, which is automatically converted to "infinite retention" by the FLR filesystem when it locks the file.

• 00/000, 0000/000, 98/000, 1998/000, 97/000 and 1997/0000 all mean no retention. The VTE does not set the WORM state for this tape.

• 99/000 and 1999/000 mean today plus 14 days.

◆ If the expiration date is in the past, other than one of the special dates listed above, the file is automatically set to "infinite retention" when the VTE locks the file.

◆ If the HDR1 expiration date is greater than 2038/018, the retention period is set to the maximum value, 2038/018.

Unlabeled tapesConsiderations for determining the retentiom period for labeled tapes:

◆ Unlabeled tapes are always treated as if there was a HDR1 containing no expiration date. Therefore, the device's default WORM retention period, if any, is used. (“FLRRET” on page 159 provides information about the default WORM retention period.)


DLm WORM Tapes


◆ If the default WORM retention period is a negative number, it signifies that the WORM "infinite retention" is desired.

◆ If no default WORM retention period has been configured for the device, the file is not set to the WORM state.

Configure WORM

Note: EMC strongly recommends that you use a storage class other than 0 for WORM-enabled filesystems. Class 0 is the default storage class; therefore, avoid using it for special types of filesystems such as WORM and GR.If you must use class 0 for a WORM-enabled filesystem, explicitly enter 0 in the Storage Class field in the Storage tab of DLm Console. If you leave the Storage Class field empty, DLm will not activate WORM on these filesystems.

1. Double-click the Configure Devices icon on the DLm VTE desktop.

2. Click the Configure Devices link.

3. Click the View or Modify link next to the active configuration file.

4. Scroll down the configuration screen and click the required device index number in the Device Information panel.

5. Enter appropriate values in the following fields:

• FLR

Select this option to enable the WORM feature. It is unchecked by default. “FLR” on page 158 provides more information.

• FLRRET

This option defines a default retention period to be assigned to tape volumes when the mainframe has not indicated an expiration date in the HDR1 record. “FLRRET” on page 159 provides more information.

• FLRMOD

Select this option if you want to allow the tape drive to modify (extend) a tape volume that is in the WORM state. It is unchecked by default. “FLRMOD” on page 159 provides more information.

• FLREXTENTS

Configure WORM 157

DLm WORM Tapes


FLR extents controls how many times a tape volume in the WORM state can be extended, assuming the FLR mod option is selected. Valid values are from 0 to 10000. If the FLR extents parameter is omitted, the default is 100. “FLREXTENTS” on page 159 provides more information.

6. To configure WORM for an individual device, scroll down to the Current devices section. In the FLR column, click the link corresponding to the device you want to configure.

A dialog box opens displaying the FLR fields.

7. Click one of the Submit buttons.

8. Save the changes as described in “Modify or delete a configuration” on page 112.

9. To enable changes to the currently running configuration of the VTE, restart the virtual tape application as described in “Start and stop tape devices” on page 84.

Note: Be sure to vary the devices offline to the mainframe before you restart the VT application.

FLR

Select Yes to enable WORM or No to disable the feature. The default value is No.

If you select No for a tape drive, the VTE does not attempt to set the WORM state for any volume written on this drive, even when the drive is writing to an FLR-enabled filesystem. Any new tape volume written by this drive can be deleted, modified, extended, or renamed just as it could be in any non-FLR-enabled filesystem.

If you select this option for a tape drive, tape volumes written to the drive may be set to the WORM state when written, depending on the following conditions:

◆ The file is written to an WORM filesystem.

◆ The expiration date sent by the mainframe is a date in the future, or if the host does not specify an expiration date, a default retention period is configured for the drive. (See “FLRRET” on page 159.)

◆ A .FLR control file is present in the WORM filesystem.

Note: WORM files can be read by a VTE device even if it does not have FLR configured on it.


DLm WORM Tapes


FLRRET

FLRRET defines a default retention period to be assigned to tape volumes when the mainframe has not indicated an expiration date in the HDR1 record. The FLRRET parameter has no effect on a tape volume unless the FLR active option is selected for the tape drive.

You can set this period in days, months, or years. Enter a numeric value and then select Days, Months, or Years. The default is 0, which indicates there is no default retention period.

Specifying a negative retention number indicates that the WORM "infinite retention" period should be set if the host does not set an expiration date.

When the mainframe writes a tape volume to an FLR drive with no expiration date in the HDR1 label, the VTE adds the default retention period set by FLRRET to the current date to determine the WORM retention period for the tape volume.

If the mainframe does not include an expiration date in the HDR1 and there is no default retention date set then the VTE will leave the volume in a non-WORM state.

FLRMOD

FLRMOD defines whether a tape drive is allowed to modify (extend) a tape volume that is in the WORM state. The default is No; tape volumes in the WORM state cannot be modified.

By default, WORM tape volumes cannot be extended because this would require a modification of the file. However, setting the FLRMOD parameter to Yes for a tape drive causes the VTE to allow WORM tape volumes to be extended by using multiple files in the FLR-enabled filesystem to hold the modified image of the tape volume.

When you set the FLRMOD parameter to Yes, tape volumes in WORM mode are mounted in read-write ("ring-in") mode, so that the host will know that it can write to the volume. The QUERY command will display the device state as "mod".

When you set the FLRMOD parameter to No, tape volumes in WORM mode are always mounted in read-only ("ring-out") mode and writes are not allowed.

FLREXTENTS

FLREXTENTS controls how many times a tape volume in the WORM state can be extended, assuming the FLRMOD parameter is set to Yes. Valid values are from 0 to 10000. If the FLREXTENTS parameter is omitted, the default is 100.

Configure WORM 159

DLm WORM Tapes


The number of extents that make up an extended virtual tape volume is transparent to the mainframe. However, having a large number of extensions can seriously impact the amount of time it takes to open and process all the files involved. FLREXTENTS can be used to limit the quantity of files to a reasonable number.

After the FLREXTENTS limit is reached, the VTE still makes a new extension file and accepts writes, but it responds to every write and write tapemark command with a Logical End of Volume indication (Unit Exception status). It would be expected that the mainframe would close the tape volume and start a new tape soon after receiving a Logical End of Volume, but it is free to continue writing as much data as it wants past the Logical End of Volume indications (up to the normal size limitation).

Determine if WORM is enabledTo determine if WORM is enabled, enter one of these commands:

◆ QUERY CONFIG

If FLR is enabled, the output displays FLR details as follows:

Index Devicename Type CU UA Options------------------------------------ 4A 940A 3590 04 0A PATH=/tapelib/ SIZE=40G FLR=YES FLRRET=1D FLRMOD=YES FLREXTENTS=5

◆ QUERY SPACE

If WORM is enabled, (FLR) is displayed next to the filesystem name.

Tape library space for drives: 9200-92FF

Path Size Active Scratch / Qty Free Filesystem--------- ---- --------- -------------- -------- ----------/tapelib 17G 1017.4M 5% 184 0% 1 5.3G 31% /dev/sda4/tapelib/AA 492.4G 1.6G 0% 12.2K 0% 68 490.8G 99% 10.1.2.219:/tapelib/AA/tapelib/BB 492.4G 4.4G 0% 14.6K 0% 81 488G 99% 10.1.2.219:/tapelib/BB/tapelib/CC 492.4G 896.2M 0% 14.2K 0% 79 491.5G 99% 10.1.2.219:/tapelib/CC/tapelib/DD 492.4G 3G 0% 15.1K 0% 84 489.4G 99% 10.1.2.219:/tapelib/DD/tapelib/FE 98.5G 1.1G 1% 1.3K 0% 7 97.4G 98% 10.1.2.219:/tapelib/FE (FLR)

◆ QUERY

The output displays an ro (read-only) status for a WORM file (unexpired or expired), unless the FLR mod option is selected on the device. If the FLR mod option is selected, it displays the mod status.


DLm WORM Tapes


Devicename VOLSER/L---------- --------9200 AA2222 S R-A2 aws/rw LP9210 FE0023 S R-A2 aws/ro LP9211 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

◆ Drive status

◆ Volume status

“QUERY” on page 218 provides more information.

Extend or modify a WORM tapeNormally, a tape in the WORM state is mounted in write-protect ("ring-out") mode. However, a VTE device can be configured to allow appending of data to the last dataset on an WORM-protected tape, or addition of data sets to the tape by setting the FLRMOD option. (“FLRMOD” on page 159 provides information about setting the FLR mod option.)

Since an WORM file is in read-only mode and cannot be modified, the appended data is maintained in auxillary "segment" files while leaving the original files unchanged. Each time an WORM file is modified, a file named VOLSER_nnnnn is created to hold the modifications. VOLSER is the original filename and nnnnn is a number that is incremented sequentially each time the file is modified.

For example, if the original volume is VTED00, the first modification will create an additional file named VTED00_00001 to hold the modifications. The next modification, if any, would create an additional file named VTED00_00002, and so on.

When a modified WORM tape is unloaded, the new extension file is set to the WORM state with the same retention period as the original VOLSER file. Whenever an extended file is subsequently mounted, all of the segments are opened, concatenated together, and presented to the host as a single tape volume reflecting all the modifications since file creation.

Extend or modify a WORM tape 161

DLm WORM Tapes


The host can only write to a modifiable WORM tape at the end of the last dataset (between the last data block and the tapemark preceding the trailer labels), or between two tapemarks at the end of the existing volume. This corresponds to the host appending to a data set (writing with DISP=MOD) or adding a new file to the tape. Attempts to write at any other location will result in a unit check with sense of command reject, ERPA code x'30' (write protect).

Any VTE can read segmented FLR tapes whether or not the FLRMOD option is selected and whether or not the DLm_FLR license is installed.

Backward compatibility of modified (segmented) WORM tapes

By default, a WORM tape can only be modified 100 times. This is to restrict the number of files that make up a single tape volume, because a large number of segments would have a performance impact on mounting and reading the tape. The default is 100, but can be configured to a different number using the FLREXTENTS option. (“FLREXTENTS” on page 159 provides information about setting the FLR extents option.)

Once the FLREXTENTS number of modifications exist, additional modifications will still be accepted and new segments created as needed, but every write to the tape will result in a unit exception (Logical End of Tape - "LEOT"), signaling to the host that it is approaching physical end of tape. It is expected that the host would close the tape volume and start a new tape volume soon after receiving LEOT, but it is free to continue writing as much data as it wants past the LEOT indications.

Scratch WORM tapesAn unexpired tape in the WORM state cannot be scratched. Attempts to scratch an unexpired tape in the WORM state will result in a ‘file not writable’ error.

An expired tape in the WORM state can be scratched. However, since the only operation that can be performed on an expired WORM tape is to delete it and it cannot be renamed from VOLSER to ~VOLSER, scratching of an expired WORM tape is implemented as a combined scratch-and-erase operation. The existing header labels from the tape are copied to a new ~VOLSER file, then the expired VOLSER file is completely deleted. Scratching an expired WORM tape always erases the data.



CHAPTER 7Mainframe Tasks

This chapter discusses using DLm with z/OS:

◆ Configure devices........................................................................................... 164◆ Real 3480, 3490, or 3590 .............................................................................. 164◆ Manual tape library ........................................................................................ 165◆ MTL considerations for VTE drive selection ..................................................... 167◆ MTL-related IBM maintenance ........................................................................ 169◆ EMC Unit Information Module......................................................................... 169◆ Missing Interrupt Handler............................................................................... 170◆ Mainframe configuration for GR...................................................................... 171◆ Mainframe configuration for deduplicated virtual tapes.................................. 172◆ Dynamic device reconfiguration considerations.............................................. 172◆ DFSMShsm considerations............................................................................. 173◆ Specify tape compaction................................................................................ 173◆ Locate and upload the DLm utilities and JCL for z/OS...................................... 174◆ Initial program load from a DLm virtual tape ................................................... 189

Mainframe Tasks 163

Mainframe Tasks


Configure devicesz/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 3590DLm 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 libraryIf 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 165

Mainframe Tasks


Table 9 on page 166 contains an example of having the same LIBRARY-ID with its unique LIBPORT-IDs.

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

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


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 175 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 175 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 selectionWhen 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 167

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

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 169

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

Mainframe configuration for GRIf you have not configured all the devices on the DLm to support GR, you must perform additional configuration tasks at the mainframe end: you must isolate GR devices from non-GR devices on the mainframe.

MTL

If you configured your DLm devices using a Manual Tape Library (MTL) and not all devices are configured for GR, perform the following steps:

◆ Define two separate MTLs—one for GR-enabled devices and one for non-GR drives.

◆ Update your ACS routines so that you can direct specific VOLSERs to the MTL supporting GR.

Esoterics

You can also define different esoterics for devices using GR and those that do not. For example, you can define two esoterics as follows:

◆ TAPE—To point to devices not enabled for GR

◆ RTAPE—To point to devices enabled for GR

Then, to direct a new VOLSER to GR, you must code JCL to include:

UNIT=RTAPE

Make sure to include UNIT=RTAPE on any DD statement that will write to the VOLSER, even if the VOLSER already exists in the library. Specifically, make sure to include UNIT=RTAPE on any Tape DD Statement that uses DISP=MOD on a volume (VOLSER)

Mainframe configuration for GR 171

Mainframe Tasks


that was originally created with UNIT=RTAPE. Coding DISP=MOD without UNIT=RTAPE might cause the VOLSER to be mounted on a device not supporting GR. Thus, the update does not get replicated to the DR site at the time the volume is closed.

Missing Interrupt Handler

GR will cause significant delay between the time a mainframe issues a close to a tape volume and the time the DLm VTE responds to that close.

By default, the DLm VTE will report a preferred Missing Interrupt Handler (MIH) value of 3000 seconds (50 minutes) to the mainframe for all its devices when the devices are varied online. If a GR device has not received confirmation from Celerra Replicator that replication has been completed before 50 minutes, the mainframe will interrupt the device indicating that the 50 minutes expired without a response from the previously sent CCW (the close).

“MIH considerations for Guarantied Replication” on page 151 provides more information.

Mainframe configuration for deduplicated virtual tapesThe deduplicated virtual tapes/VOLSERs need to be isolated from non-deduplicated virtual tapes. All VOLSERs that reside on the Data Domain DD880 are deduplicated and all VOLSERs that reside on the Celerra are non-deduplicated. This can be done by defining an MTL that contains only deduplicated virtual tapes/VOLSERs. Update your ACS routines so that you can direct specific VOLSERs to the MTL supporting deduplication.

Dynamic device reconfiguration considerations Since DLm is a virtual tape control unit, it cannot benefit from an operator or a system-initiated 'swap' function. Accordingly, following any message 'IGF500I SWAP xxxx TO xxxx - I/O ERROR' for any device, you must reply NO to the subsequent "## IGF500D REPLY 'YES', DEVICE, OR 'NO' ."

If you configured the devices as V348x devices using the UIM, Dynamic Device Reconfiguration (DDR) swap is automatically disabled for those devices, and a swap cannot occur.


Mainframe Tasks


DFSMShsm considerationsIf 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 compactionCompaction of the virtual tape data under z/OS is initiated like it is initiated for a real compression-capable (IDRC) 3480/3490/3590E. The default is NOCOMP for 3480, and COMP for 3490 and 3590E. You can specify the use of compaction in the JCL by using the DCB=TRTCH=COMP or DCB=TRTCH=NOCOMP parameter on the appropriate DD cards for output tapes. No JCL parameter is required for input tapes. The system automatically decompresses the tape data on read requests.

Alternatively, the system programmer can specify the COMPACT=YES parameter in the DEVSUPxx PARMLIB member. This would result in compaction being the default option for all of the virtual drives. The COMPACTION=Y/N option on the SMS DATACLAS definition provides another method for activating and disabling compaction.

It should be noted that while the compaction option significantly reduces the amount of storage required on the DLm library, there is some impact on the data transfer performance compared to uncompressed data. The efficiency of the compaction, as well as the performance impact, varies depending upon the data.

The file-size values reported by the QUERY command and the awsprint utility (using CP503), reflect the compressed data size and not the original uncompressed size.

Note: All data written to the deduplicating storage on the DD880 should be written without IDRC.

DFSMShsm considerations 173

Mainframe Tasks


Locate and upload the DLm utilities and JCL for z/OSEMC 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 9, “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

(satisfy login requirements of the mainframe)

quote site recfm=fb lrecl=80binput 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:


http://Powerlink.EMC.com

Mainframe Tasks


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)

quote site recfm=fb lrecl=80binput 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.

Locate and upload the DLm utilities and JCL for z/OS 175

http://Powerlink.EMC.com

Mainframe Tasks


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

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


Mainframe Tasks


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 175 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. The sample JCL is found in the RUNSCRA and RUNSCRB members of DLMZOS.JCL.CNTL. RUNSCRB illustrates the use of the DEV= parameter. Step 4 on page 175 provides download instructions.


Mainframe Tasks


Table 10 on page 178 lists the DLMSCR parameters that may need to be specified.

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

FREEAFTERSCR

While the FREESPACE parameter requires that a volume already be in a 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


Scratch utility output filesThe 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.

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

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.

Table 10 Parameters in DLMSCR (page 2 of 2)

Parameters Specification


Mainframe Tasks


If an error occurs during a scratch request (such as scratching a non-existent volume), the failure is recorded in the log file. The program continues with the next scratch request and result in a non-zero return code from the program execution.

◆ The DLMCTRL file allocates a DLm tape device for use as a control path to pass the scratch requests. If multiple tape libraries in the DLm filing structure are being used to contain the DLm virtual volumes, you must select a tape device address associated with the library in the DLm filing structure containing the volumes to be scratched.

◆ The DEV=xxxx parameter allows an offline tape device to be used instead of coding the DLMCTRL DD statement. For example, see RUNSCRB in the sample JCL library.

DLMSCR report output messages

Note: ALL messages are proceeded by: mm/dd/yyyy hh:mm:ss VOLUME xxxxxx.

Table 11 DLMSCR report output messages

Hex Code Volume Rejected Message Comments

0x01 REQUEST REJECT - INVALID LOAD/DSPLY

Invalid data length (must be 17, 23, or 40 bytes).

0x02 REQUEST REJECT - ALREADY A SCRATCH

Volume already scratched.

0x05 REQUEST REJECT - INVALID VOLSER

Invalid VOLSER specified - The input volume serial number does not conform to the standard volume naming convention. Check the input TMS report.

0x06 REQUEST REJECT - VOLUME IN USE

Volume in use on the same or different VTE or there is a possibility of a STALE LOCK.

0x07 REQUEST REJECT - VOLUME NOT FOUND

Volume not found in file system; Make sure input tape device 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 LOCKED

File is locked - volume might be in use by another tape drive on this VTE or another VTE or there is a possibility of a STALE LOCK

0x0A REQUEST REJECT - DIRECTORY PROBLEM A

Tape library directory is not accessible - Verify tape unit selected for utility points to correct tape library.


Mainframe Tasks


Note: The hex codes listed are the error codes that the VTE returns to DLMSCR when DLMSCR requests an action on a volume.

Working with the DLm scratch utilityNote 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.

0x0B REQUEST REJECT - DIRECTORY PROBLEM B

Tape library directory is not writeable - Verify that tape library is marked for Read/Write.

0x0C REQUEST REJECT - INVAL/MISSING VOL1

Invalid or missing VOL1 label in volume - Using AWSPRINT verify volume VOL1 record has not been overwritten.

0x0D REQUEST REJECT - VOLSER MISMATCH

The volume serial number from the TMS report and the VOL1 HDR do not match; VOL1 HDR might have been overwritten.

0x0E REQUEST REJECT - INVAL/MISSING HDR1

Invalid or missing HDR1 label in volume - The HDR1 record is not in the correct format; overlayed because of error; use AWSPRINT utility to determine error.

0x0F REQUEST REJECT - MISMATCHING DSNAME

Data Set Name mismatch - The last 17 alphanumerics of 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 DATE PASSED

The TMS input report date does not match the execution date of DLMSCR

0x11 REQUEST REJECT - CREATE DATE=TODAY

Date mismatch - DLMSCR, unless overridden using NODATECHK, defaults to no scratch same day.

0x12 REQUEST REJECT - FILE NOT WRITEABLE

File not writable - The filesystem directory is probably marked as Read Only; This might be target site.

Table 11 DLMSCR report output messages

Hex Code Volume Rejected Message Comments


Mainframe Tasks


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 considerationsObserve the following rules when using DLm with RMM:

◆ Predefine the DLm scratch volumes to RMM. If you have not predefined DLm VOLSERs as scratch in RMM, RMM rejects the new volumes, which results in an unsatisfied mount request on the mainframe. To resolve the unsatisfied mount, define the DLm scratches in RMM, and execute a LOAD command at the appropriate VT console to satisfy a stalled request.

◆ When defining a new DLm scratch tape to RMM, set the initialize option to no. If you select yes and RMM detects that the volume must be initialized (or EDGINERS is run), RMM sends a request to mount a 'blank' VOLSER on a DLm device. DLm is not automatically ready as it cannot recognize which volume to mount. Consequently, you must use the LOAD command at the VT console to manually mount each volume being initialized.

◆ DLMSCR processes two types of RMM scratch reports:

• The scratch report that EGDRPTD creates

• The scratch report that EDGJRPT creates using the EDGRRPTE exec (EDGRPT01)

Use the DATEFORM(I) parameter when running EDGRPTD to create scratch reports to ensure the expected date format is used. When the REXX exec form is used, DLMSCR may not accept a user-tailored version of EDGRRPTE.

TMS considerationsDLMSCR expects Report-05, Report-06, or Report-87 to be used.

TLMS considerationsDLMSCR expects either the TLMS003 or the TLMS043 report as input.


Mainframe Tasks


TSM considerationsDLMSCR expects a Tivoli Storage Manager (TSM) Volume History Report to be used as input to the DLMSCR DD.

ZARA considerationsDLMSCR expects the LIST SCRATCH type of scratch report to be used as input from ZARA.

CA-1 considerationsAlthough 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 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.


Mainframe Tasks


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

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


Mainframe Tasks


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

◆ 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 12 on page 186 lists the possible error codes from DLMCMD.


Mainframe Tasks


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 command2004/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)

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'

Table 12 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.)


Mainframe Tasks


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


Mainframe Tasks


//*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 PARMDLV010I UTILITY VERSIONS (Z/OS R12 ):DLMCMD V 4.06DLMLIB V 4.03DLMSCR V 4.19DLMVER V 1.00GENSTATS V 1.15

DLMVER Messages

The messages related to DLMVER are:

◆ DLV010I UTILITY VERSIONS ( ):

◆ DLV050I LOG FILE FAILED TO OPEN

“DLMVER messages” on page 440 provides the details.


Mainframe Tasks


Initial program load from a DLm virtual tapeSince 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 189

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 8Using DLm with Unisys

DLm systems with FICON interfaces installed can connect to Unisys 2200 mainframes running OS-2200. This chapter discusses issues unique to DLm support for Unisys mainframes.

◆ Unique DLm operations for Unisys mainframes .............................................. 192◆ Configuring for Unisys .................................................................................... 193◆ Initializing tapes for Unisys ............................................................................ 194◆ Configuring the mainframe for DLm ................................................................ 195

Using DLm with Unisys 191

Using DLm with Unisys


Unique DLm operations for Unisys mainframesThis section describes the unique DLm operations required for Unisys mainframe systems.

Autodetection

DLm automatically detects that it is attached to a Unisys host when it receives a Load Display command containing data that is unique to a Unisys mainframe. When this occurs, a message is displayed on the DLm console ("DLm080I: Device devicename UNISYS detected"). You can confirm that DLm has recognized that a drive is attached to a Unisys mainframe by reviewing the messages displayed on the DLm console or by running a QUERY CONFIG command.

Load displays

Unisys does not send the 'M' mount message sent by the z/OS mainframe systems. DLm determines a Unisys mount request by the FCB byte containing x'48', and then moves the VOLSER from the 1st position into the 2nd position of the mount message and inserts an 'M' into the 1st position to form a standard mount message.

Mount "Ready" interrupt

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

Query Config command

The DLm QUERY CONFIG command displays an additional parameter, HOST=UNISYS, for a device that has been determined to be attached to a Unisys mainframe.




Ring-Out Mount request

The Unisys Load Display mount request uses the 8th position of the mount message as a file protect indicator. If that position contains the character 'F', the Unisys mainframe expects to have the tape mounted "ring-out" (read-only). DLm honors the 'F' indicator and mounts the requested volume in read-only mode.

Scratch request

When a Unisys host asks for a scratch tape, DLm ignores the label type (either explicitly requested in the mount request or implied by the LABEL=x configuration parameter) and picks any available scratch tape. This behavior is applicable only to Unisys-attached devices. All non-Unisys devices will continue to honor label type for scratch mount requests.

Configuring for Unisys

Device type

When configuring devices for use by a Unisys mainframe the Device Type should be set to '3490'.

Labels

When the Unisys operating system sends a Load Display mount message, it does not specify a label type. Unisys always expects an ANSI label by default. To accommodate this, you must configure each Unisys-attached device with the LABEL=A parameter. This will change the DLm default for this device to ANSI labels instead of IBM standard labels. Figure 38 shows a sample device definition screen where sixteen tape drives are being defined including the LABEL=A parameter.

Scratch tapes

The Unisys operating system does not send the "MSCRTCH" message to request a scratch tape as an IBM mainframe would. Instead it sends an L-BLNK command. To accommodate the L-BLNK command, you must specify a scratch synonym equal to L-BLNK. Figure 38 shows a properly configured scratch synonym for Unisys mainframes.

Configuring for Unisys 193



Figure 38 Unisys Device Panel

Initializing tapes for UnisysWhen initializing tape volumes to be used with Unisys you must include the LABEL=A option on the initialize command to tell the system that the tape labels will follow the ANSI standard.

For example, to initialize 100 tapes beginning with VOLSER B00000 using tape drive E980, you would enter the following initialize command:

INITIALIZE VOL=B00000 DEV=E980 COUNT=100 LABEL=A




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

The Unisys equipment code for DLm devices is U47M.

Configuring the mainframe for DLm 195


CHAPTER 9z/OS Console Support

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

◆ z/OS Console operation ................................................................................. 198◆ DLMHOST....................................................................................................... 198◆ Using z/OS Console support........................................................................... 201

z/OS Console Support 197

z/OS Console Support


z/OS Console operationDLm 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.

DLMHOSTDLMHOST 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 174 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 199



◆ 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. Step 4 of “Downloading and using the DLm utilities and JCL for z/OS” on page 174 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 TAPECON1VTLNODE2 039E 039F TAPECON1VTLNODE3 03AE 03AF TAPECON1

Using z/OS Console supportIf 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 201



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=NODE1CMD=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=ALLSTOPLOG,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=NODE2STARTLOG,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 CONSNAMENODE1 038E Y 038F Y CON1NODE2 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 203



The commands that DLM000I lists are:

STARTLOG,N=nodename/ALLSTOPLOG,N=nodename/ALLC=Command,N=nodename/ALLSTATUS

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#,STATUSmsg#,C=Q SPACE,N=N1msg#,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,STATUSF DLMHOST,C=Q SPACE,N=N1F DLMHOST,STOPLOG,N=ALL



CHAPTER 10Data Encryption

This chapter discusses using data encryption:

◆ Overview........................................................................................................ 206◆ How RSA Key Manager works with DLm........................................................... 207◆ Configure encryption on DLm ......................................................................... 208

Data Encryption 205

Data Encryption


OverviewEMC Disk Library for mainframe (DLm) includes a data encryption module that allows you to encrypt data using AES-256 encryption as the data is being written. Emulated tape drives in DLm can be configured to perform data encryption by assigning an encryption key class to the drive. When an encryption key class is assigned, the drive will automatically encrypt any tape volume the mainframe writes to the drive. Both the tape header labels and the data blocks are encrypted.

Mixed volumes in the same VTE

Data encryption is configured on a drive-by-drive basis. You can configure one or more drives to perform the data encryption. Each time a tape volume is written to one of the drives, the data is automatically encrypted before it is written to the backend storage.

If you want some tape volumes in the DLm to be encrypted and other tape volumes to be written unencrypted, configure your DLm with some devices supporting encryption and others without encryption..

Figure 39 Configuring for encryption

The Virtual Tape Emulator (VTE) shown in Figure 39 on page 206 is configured with a single library as a backend.

Drives 00 – 0F V3480

Drives 10 – 1F

V3481

B00000 – encrypted

B00003

B00002 – encrypted

B00001

Devices 10 – 1F Encryption = Yes

Devices 00 – 0F Encryption = No


Data Encryption


This implies that all tape volumes are written to the same physical storage whether or not they are encrypted. However, based on the device addresses configured, some tape volumes perform encryption and others do not. In the example in Figure 39 on page 206:

◆ Drives configured with device addresses 00 – 0F are without encryption

◆ Drives configured with device addresses 10 – 1F are with encryption

In the example, EMC's UIM has been installed on the mainframe. UIM provides multiple virtual device types to z/OS. In this example, the devices are assigned to a device type in the following way:

◆ 00 – 0F assigned to V3480

◆ 10 – 1F assigned to V3481

With this configuration, individual jobs can direct whether or not output tapes written to the DLm must be encrypted using any DD statement coded with:

• UNIT=V3480 is allocated to one of the 16 drives (devices 00 – 0F)—not performing encryption and decryption.

• UNIT=V3481 is allocated to one of the 16 drives (devices 10 – 1F)—encrypting data before writing and decrypting data after reading.

Individual jobs can also direct whether or not output tapes written to the DLm must be encrypted by using IBM's Manual Tape Library (MTL) support under system managed storage (SMS). Define two separate MTLs, one with the encrypted devices and one with the non-encrypted devices.

Note: If two separate MTLs of the same type (3490 or 3590) are used on the same VTE, they must be in separate libraries on the DLm (make sure they both do not have /tapelib as their tape library).

How RSA Key Manager works with DLm Each VTE includes the RSA Key Manager client and uses one certificate. During initial setup, EMC personnel install the RSA client, establish the connection between the VTE and the RSA Key Manager, which will use one registration certificate on the RSA server. They also define the encryption key classes to be used.

When the mainframe begins writing a new tape volume:

How RSA Key Manager works with DLm 207

Data Encryption


1. The VTE makes a call over the IP network to the RSA Key Manager to request a key. The encryption key class is passed as an argument with the request.

2. The RSA Key Manager uses the encryption key class to determine how to respond and returns both a cleartext key id and an encryption key to the VTE.

3. The VTE uses the encryption key to encrypt the tape volume's data blocks before writing them to the storage.

4. The VTE stores the cleartext key id on the volume's data file along with the encrypted data.

When the mainframe wants to read a previously encrypted volume:

1. DLm opens the volume's file on the back-end storage.

2. When the VTE recognizes that the data is encrypted, it retrieves the cleartext key id from the file and passes it on to the RSA Key Manager.

3. The RSA Key Manager validates the request and returns the encryption key to the VTE.

4. The VTE then decrypts the data in the file to respond to the mainframe's request.

Configure encryption on DLm For the VTE to communicate with the RSA Key Manager:

◆ The VTE must be connected via TCP/IP to the customer's network via TCP/IP with access to the RSA Key Manager.

◆ Two global configuration parameters must be specified in the Encryption tab under the External menu in the DLm Console:

• The IP address of the RSA Key Manager

• The TCP/IP port that the VTE should use to communicate with the RSA Key Manager

Note: These steps are completed by EMC service personnel during initial setup. Contact EMC customer support for any changes.

After the RSA Key Manager communication is established, you must configure the devices for encryption in the Encryption key class fields under the Devices menu.


Data Encryption


Configure encryption when adding devices


2. Once connected, click Devices. This menu contains a tab for each available VTE.


4. In the Encryption key class field in the Add devices panel shown in Figure 29 on page 102, enter the encryption key class you received from the EMC installation personnel.

5. Enter all the other required details in the Add devices panel and click Add range.

Entering an encryption key in the Encryption key class field instructs the VTE that all data written from this range of devices must encrypt data.

Configure encryption on existing devices


2. Once connected, click Devices. This menu contains a tab for each available VTE.


4. Scroll down to Current devices panel shown in Figure 29 on page 102 and enter the encryption key class you received from the EMC installation personnel in the Encryption key class field against the required device. You can also change the encryption key class used by individual devices.

Configure encryption on DLm 209

Data Encryption




APPENDIX AVirtual Tape Operator Command Reference

This appendix contains the Virtual Tape Operator command reference:

◆ Virtual Tape Operator command reference ...................................................... 212

Virtual Tape Operator Command Reference 211

Virtual Tape Operator Command Reference


Virtual Tape Operator command referenceWhen 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 213



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]

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.

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.

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 /tapelib:

INIT VOL=B00000 DEVICE=E980 COUNT=100

◆ The CLASS parameter directs the new volumes being initialized to a specific storage class within the library. You must initialize scratch tapes into any new storage class before you attempt to allocate a new scratch volume from that class.

◆ The DIR parameter is always optional and allows you to direct the new volumes being initialized to a specific filesytem (directory) within the library. When not specified, new volumes will be initialized into the first filesystem within the storage class. During operation, 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

◆

◆ of the DEV= 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| GR | 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.

The output displays an ro (read-only) status for an FLR file (unexpired or expired), unless the FLRMOD=YES option is set on the device. If FLRMOD=YES is set, the status is mod, indicating the tape is modifiable.

◆ 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 GR shows information about the Guaranteed Replication feature, devices, and filesystems.

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

If FLR is enabled, (FLR) is displayed next to the filesystem name.

◆ 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 output06/01/2010 11:21:44 VTE1 VT: Devicename VOLSER/L06/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 LP06/01/2010 11:21:44 VTE1 VT: 9210 FE0023 S R-A2 aws/ro LP06/01/2010 11:21:44 VTE1 VT: 9211 FE0026 S R-A2 aws/mod LP

The four columns under VOLSER\L are:

◆ Volume currently mounted on the drive

◆ Type of label on the volume:

• S = Standard IBM

• A = ANSI

• N = Unlabeled

◆ Drive status:

• Q = Quiesced

• R = Ready

• NR = Not ready

• NA = Not accessible

• UA = Not currently allocated by a Host

• An = Allocated on n logical channel paths: A1 = allocated on one logical channel path, A2 = allocated on two paths, A3 = allocated to three paths, etc.

(For a non-autoswitched device, An means one Host has varied online n paths and the device; for an autoswitched device, or in a JES3 environment, An means the Host has reserved the device for use on n logical channel paths.)

◆ Volume status:

• aws or flat is the virtual tape file format.

• scsi for a SCSI or Fibre-Channel-attached tape drive.

• rw is read-write.

• ro is read-only.

• lfp is logical file protect set by the Host.

• If a volume is mounted, the current block position or LP (for loadpoint) is displayed, and whether the last operation was a read or write.

Other notations might also be displayed when a volume is being written:




• h-compr or s-compr signifies that the most recent write was compressed by hardware or software, respectively. The total volume size shown is after the compression notation, if any.

• crypt signifies that the most recent write was encrypted.

• AMDD signifies that the AMDD feature has modified one or more blocks being written to this volume.

• GR signifies that the volume is being written to a replicating filesystem and a replication-refresh will be performed when the tape is closed.

If a mount previously failed, the most recently requested VOLSER and the reason for the mount failure are displayed.

QUERY ALL sample outputQUERY ALL sample outputVersion 7.03-9768, build 0, built May 24 2012 13:12:16Licensed Features Enabled: EMC FLR Support SCSI Tape Support Data Exchange (Flat File) Support Encryption Support Import-Export Support EMC DLm Support EMC Encryption Support EMC GR Support AMDD Support AMDD Support for EMCProgram started at Wed Jun 13 10:55:53 2012DLm056I: 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: 000D09137204DLm077I: Interface #0: Firmware emulation type: TRANS, version: 1245 2012/05/17DLm070I: Interface #0: TRANSX emulation version set to 3DLm081I: Interface #0: Current state: running; Desired state: running; Media Down, Loop DownDLm075I: Interface #1: 198144 (0x030600) bus:6 slot:0 type:15 (PEFA-LP) media:3 (FiCon)DLm076I: Interface #1: hardware s/n: 000D09117152DLm077I: Interface #1: Firmware emulation type: TRANS, version: 1245 2012/05/17DLm070I: Interface #1: TRANSX emulation version set to 3DLm081I: Interface #1: Current state: running; Desired state: running; Media Up, Loop UpDLm790I: ST driver version: 1.45DLm841I: System tracelevel is currently set to 1DLm842I: System debuglevel is currently set to 0DLm096I: Erase Policy: retain for 1 day (configured this way)




DLm097I: Maximum continuous erase time set to 30 secondsDLm078I: Disk usage WARNING level set to 88%DLm079I: Disk space RECOVER level is N/ADLm084I: Disk space RECOVERAMT set to 5%DLm120I: Disk RECOVERYUPDATE set to 24 hoursDLm127I: Disk space ERASEPOLICYTTL set to 1D (config)DLm851I: ProtectVOL1 set ONDLm099I: New mount on already-mounted drive will be allowedDLm069I: Resetting Events will not be sent to firmwareDLm112I: Using NEW standard scratch search methodDLm114I: Using DEFAULT method of filesystem allocationDLm109I: Scratch mounts will ignore full filesystems (UseFullFS=FALSE)DLm083I: Compression level set to 1 (0=none,1=faster,9=smaller)DLm010I: Compression hardware availableDLm011I: Compression driver version: 1.1.8DLm012I: Compression card #0: id=0x193F0363 (AHA363) version=0x120 state=00000000DLm013I: Hardware compression set ONDLm013I: Hardware decompression set ONDLm873I: Attention set to PATHGROUPDLm871I: AttentionCount set to 45DLm067I: BusyType set to BusyDLm853I: Pending Mount Fairness (PMFAIR) set to 0DLm892I: Write Sync set to 1GDLm257I: The Maximum Find Volume Display Count is: 1000DLm687I: Enhanced FS move volume method is: RandomDLm688I: Enhanced FS move for volumes in FLR tape libraries: DisabledDLm688I: Enhanced FS move for volumes in GR tape libraries: DisabledDLm256I: Volser Lock Directory set to: /tapelib/.LOCK/DLm957I: Locking with NLM lock manager turned ONDLm111I: Maximum tape block size set to 512000DLm840I: Read-back write verification (non Data Domain) set to DATADLm840I: Read-back write verification (Data Domain) set to OFFDLm116I: Query Space timeout set to 40 minutesDevicename VOLSER/L---------- --------0502 NR-UA6C00 NR-UA6C01 NR-UA6C02 NR-UA6C03 NR-UA6C04 NR-UA6C05 NR-UA6C06 NR-UA6C07 NR-UA6C08 NR-UA6C09 NR-UA6C0A NR-UA6C0B NR-UA6C0C NR-UA6C0D NR-UA6C0E NR-UA6C0F NR-UA




QUERY COMPRESSION sample outputDLm083I: Compression level set to 1 (0=none,1=faster,9=smaller)DLm010I: Compression hardware availableDLm011I: Compression driver version: 1.1.8DLm012I: Compression card #0: id=0x193F0363 (AHA363) version=0x120 state=00000000DLm013I: Hardware compression set ONDLm013I: Hardware decompression set ON

QUERY CONFIG sample outputVTE1 VT: DLm102I: Configuration file is /etc/bti/xmap0VTE1 VT: Current Values Are:VTE1 VT: Index Devicename Type CU UA OptionsVTE1 VT: ------------------------------------VTE1 VT: 00 1D00 3490 00 00 PATH=/tapelib/ SIZE=2GVTE1 VT: 01 1D01 3490 00 01 PATH=/tapelib/ SIZE=2GVTE1 VT: 02 1D02 3490 00 02 PATH=/tapelib/ SIZE=2GVTE1 VT: 03 1D03 3490 00 03 PATH=/tapelib/ SIZE=2GVTE1 VT: 04 1D04 3490 00 04 PATH=/tapelib/ SIZE=2GVTE1 VT: 80 1D80 3490 08 00 PATH=/tapelibGRS2/ SIZE=2GVTE1 VT: GR=YESVTE1 VT: 4A 940A 3590 04 0A PATH=/tapelib/ SIZE=40G FLR=YES FLRRET=1D FLRMOD=YES FLREXTENTS=5

QUERY LABELS sample outputDLm409I: Command received: 'query labels'1D00 S VOL1JJ0031 TCSBT HDR1LL6.DEMO.BACKUP02JJ003100010001 0101520000000000000IBM OS/VS 370 HDR2U000000000000DPHILL6D/DUMP 00000 0000065520

QUERY LOCKS sample outputDLm409I: Command received: 'QUERY LOCKS'===================================dd lock files -- long term filesowner 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 outputDLm409I: Command received: 'query mounted'




Devicename VOLSER/L---------- --------1D00 JJ0031 S R-A2 aws/rw block 2514 (writing 135.6M)

QUERY PATHS sample outputDevice Interface/Path# Port LPAR CU Device PathGroup ID1D00 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 00000000000000000000001D01 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 00000000000000000000001D02 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 outputTape 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 (FLR) ===============================================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.

For filesystems that are recognized as FLR filesystems, the output displays “(FLR)” next to the filesystem device name.

When a Data Domain DD880 is integrated with the DLm system, the following differences appear:

◆ The Size column: The total may not reflect the actual total because the Data Domain storage appliance uses one filesystem for all its exports. In the above example, all the sizes will be equal and the total will be the total of the exports.

◆ Active, Scratch, and Qty remain the same.

◆ Free: All exports reflect the same amount of free space due to the single partition with many exports. The Totals column reflects larger quantity than is really available because it is a total of the 3 individual free spaces.

QUERY SCRATCHNAMES sample outputDLm856I: 2 scratch synonyms: GR,REPL

QUERY STCLASS sample outputDLm409I: Command received: 'QUERY STCLASS'Class Path---------------------------------0 /tapelibREP/CR0 /tapelibREP/R20 /tapelibREP/R10 /tapelibREP0 /tapelib0 /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:52Recover/Recovered 95% / 0% recovered never to neverHighest Usage 29% at 01/30/2011 20:16:35Current Penalty 0%




Last Picked Time at 12/31/1969 19:00:00.000000

QUERY VERSION sample outputVersion 7.03, build 9725, built Apr 12 2012 17:00:33Licensed Features Enabled:SCSI Tape SupportData Exchange (Flat File) SupportImport-Export SupportEMC DLm SupportEMC GR SupportAMDD Support for EMCProgram 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 235.

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] [EFSMOVEFLR=ON/OFF] [EFSMOVEGR=ON/OFF] [QSPACETIMEOUT=nn] [PROTECTVOL1=ON/OFF] [ ERASEPOLICYTTL=[nnn / nnnH / nnnD / OFF] [OFF/nnn/nnnD/nnnH] [DEVICE=devicename|ALL]

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

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

◆ EFSMOVEFLR=ON/OFF indicates if a volume in a FLR tapelib can be moved when EFSMOVE is enabled

◆ EFSMOVEGR=ON/OFF indicates if a volume in a GR tapelib can be moved when EFSMOVE is enabled




◆ QSPACETIMEOUT=nn Sets the number of minutes that QUERY SPACE can run before it is automatically cancelled.

◆ 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 . After the command is executed, a message "DLm127I "Disk space ERASEPOLICYTTL set to Value" 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 235.

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

This appendix provides information on AWSTAPE:

◆ AWSTAPE format............................................................................................. 238

AWSTAPE Information 237

AWSTAPE Information


AWSTAPE formatDLm 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 40 on page 238 illustrates an AWSTAPE disk file.

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

1 2 3 4 5 6 7 8

1 2HDR

HDR

HDR

HDR

3

AWSTAPE-Single Disk File Representing One Physical Tape Volume GEN-001170

Physical Tape Volume data block tapemark

4 5 6 7 8HDR

HDR

HDR

HDR

HDR

HDR

HDR



APPENDIX CLoad Display Command—CCW Opcode x'9F'

This appendix describes the Load Display command (CCW Opdcode x’9F’). Major topics are:

◆ Load display messages .................................................................................. 240◆ Load display data........................................................................................... 242

Load Display Command—CCW Opcode x'9F' 239

Load Display Command—CCW Opcode x'9F'


Load display messagesIBM-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 240 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 241



Load display dataTable 13 on page 242 provides information about load display.

Format Control Byte

Table 14 on page 242 describes the FCB.

Table 13 Load display data

Bits Description

0 Format Control Byte

1–8 Message 0

9–16 Message 1

Table 14 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 110

Reserved.

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




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.

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)

Table 14 Format Control Byte (page 2 of 2)

Bits Value Description

Load display data 243



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 DExtract 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 ......................................................................................... 246◆ Extraction utility ............................................................................................. 246

Extract DLm statistics 245

Extract DLm statistics


DLm statistics filesDLm 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 utilityDLm 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 specifiedNone 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 247



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/hourlystatfmt - DLm statistics extractor, version 5.00-24.Copyright (c) 2007 input file is '/var/bti/stats/hourly'

Date,Hour,Mounts,Drives,BlocksRead,Blockswritten,-BytesRead,BytesWritten09/21/2007,14,4,1,-1,-1,968,009/21/2007,16,7,2,-1,-1,6198537240,110296847709/21/2007,17,4,2,-1,-1,7585128104,110000140009/22/2007,15,1,1,-1,-1,0,009/23/2007,21,3,3,-1,-1,1000480,100040009/23/2007,22,4,4,69,68,1000480,1000400

Example 2

# statfmt --hourly --minutes /var/bti/stats/hourlystatfmt - DLm statistics extractor, version 5.00-24.




Copyright (c) 2007 input file is '/var/bti/stats/hourly'

Date,Hour,Mounts,Drives,BlocksRead,Blockswritten,-BytesRead[00],BytesWritten[00],BytesRead[01],BytesWritten[01],-BytesRead[02],BytesWritten[02],BytesRead[03],BytesWritten[03],-BytesRead[04],BytesWritten[04],BytesRead[05],BytesWritten[05],-BytesRead[06],BytesWritten[06],BytesRead[07],BytesWritten[07],-BytesRead[08],BytesWritten[08],BytesRead[09],BytesWritten[09],-BytesRead[10],BytesWritten[10],BytesRead[11],BytesWritten[11],-BytesRead[12],BytesWritten[12],BytesRead[13],BytesWritten[13],-BytesRead[14],BytesWritten[14],BytesRead[15],BytesWritten[15],-BytesRead[16],BytesWritten[16],BytesRead[17],BytesWritten[17],-BytesRead[18],BytesWritten[18],BytesRead[19],BytesWritten[19],-BytesRead[20],BytesWritten[20],BytesRead[21],BytesWritten[21],-BytesRead[22],BytesWritten[22],BytesRead[23],BytesWritten[23],-BytesRead[24],BytesWritten[24],BytesRead[25],BytesWritten[25],-BytesRead[26],BytesWritten[26],BytesRead[27],BytesWritten[27],-BytesRead[28],BytesWritten[28],BytesRead[29],BytesWritten[29],-BytesRead[30],BytesWritten[30],BytesRead[31],BytesWritten[31],-BytesRead[32],BytesWritten[32],BytesRead[33],BytesWritten[33],-BytesRead[34],BytesWritten[34],BytesRead[35],BytesWritten[35],-BytesRead[36],BytesWritten[36],BytesRead[37],BytesWritten[37],-BytesRead[38],BytesWritten[38],BytesRead[39],BytesWritten[39],-BytesRead[40],BytesWritten[40],BytesRead[41],BytesWritten[41],-BytesRead[42],BytesWritten[42],BytesRead[43],BytesWritten[43],-BytesRead[44],BytesWritten[44],BytesRead[45],BytesWritten[45],-BytesRead[46],BytesWritten[46],BytesRead[47],BytesWritten[47],-BytesRead[48],BytesWritten[48],BytesRead[49],BytesWritten[49],-BytesRead[50],BytesWritten[50],BytesRead[51],BytesWritten[51],-BytesRead[52],BytesWritten[52],BytesRead[53],BytesWritten[53],-BytesRead[54],BytesWritten[54],BytesRead[55],BytesWritten[55],- BytesRead[56],BytesWritten[56],BytesRead[57],BytesWritten[57],-BytesRead[58],BytesWritten[58],BytesRead[59],BytesWritten[59]09/21/2007,14,4,1,-1,-1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-240,0,0,0,0,0,240,0,240,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,248,0,0,-0,0,0,0,0,0,0,0,0,0,0,0,009/21/2007,16,7,2,-1,-1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-0,0,0,0,160,533,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,160,-370400240,0,531456000,176928720,198145160,287040160,82320,-305952000,0,292832800,1016128,305952000,0,291872800,1868096,-306752000,0,305700640,0,308448000,0,306336000,0,308448000,0,-307168000,0,306880000,0,305056000,0,307776480,0,299392000,0,-296288160,0,293440080,0,293056000,0,296480000,0,296737080,009/21/2007,17,4,2,-1,-1,0,0,0,0,0,0,0,0,0,0,160,216416240,248,-516192000,63008720,367393160,305056248,0,293248240,0,-271232000,0,301632008,0,306016000,0,308000000,0,305184000,0,-306884640,0,306656000,0,299744000,0,291392000,0,293248000,0,-




293664000,0,291360000,0,293344640,0,290784080,0,288704080,0,-295904080,0,296832160,0,298144080,0,295968080,0,289984240,0,-291168240,0,295360000,0,297920080,0,114688080,0,0,0,0,0,0,0,0,-0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-0,0,0,0,0,0,0,0,0,0,0,0,0,009/22/2007,15,1,1,-1,-1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-0,0,0,0,0,0,0,009/23/2007,21,3,3,-1,-1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-1000480,1000400,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-0,0,0,0,0,0,0,0,0,0,0,0,0,0,009/23/2007,22,4,4,69,68,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1000480,-1000400,0,0,0,0,0,0,0,0,0,0,0,0

Example 3

# statfmt --mounts /var/bti/stats/vstatsstatfmt - DLm statistics extractor, version 7.03-9725.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,004/16/2012,11:41:13,,,0,0,0,0,37748736,345745915904,0,004/16/2012,12:08:22,,,0,0,0,0,37748736,345745915904,0,0

Example 4

# statfmt --unmount /var/bti/stats/vstatsstatfmt - DLm statistics extractor, version 7.03-9725.Copyright (c) 2012 .input file is '/var/bti/stats/vstats'

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



APPENDIX ESystem Messages

This appendix lists the DLm system, EMCvts, and z/OS system messages. The major topics are:

◆ Message format ............................................................................................. 256◆ DLm system messages ................................................................................... 257◆ Call home messages ...................................................................................... 428◆ EMCvts messages .......................................................................................... 429◆ z/OS system messages .................................................................................. 431◆ VTEC errors that generate ConnectEMC events ................................................ 445

System Messages 255

System Messages


Message formatThe EMC DLm system message format is:

DLmxxxy

where:

xxx = message number

y = message class:

I (Informational)W (Warning)E (Error)


System Messages


DLm system messagesThis section lists the DLm system messages, a description, the system action, and the recommended user action.

DLm000I<debugging message>

Description: Various debugging messages are displayed if the DLm application's debugging level is set to 1 or higher.

System action: None.

User action: You really should not be seeing any DLm000I messages unless you have invoked a debugging mode. For best performance, debugging should be left off unless directed otherwise by EMC Customer Support. Type the command SET DEBUG=0 to turn debugging off.

DLm010ICompression hardware [not] available

Description: Reports the availability of a hardware compression card in the DLm.

System action: If a hardware compression card is present (and is not disabled through configuration or operator command), the card is used for compressing and decompressing virtual tape data.

User action: None.

DLm011ICompression driver version: x.x.x

Description: Displays the version number of the EMC hardware compression card driver.


User action: None.

DLm012ICompression card #n:id=xx version=nnn state=xxxxxxxx

DLm system messages 257

System Messages


Description: Displays information about the hardware compression cards installed in the DLm.


User action: None.

DLm013IHardware compression/decompression set ON/OFF

Description: Reports the status of the DLm hardware compression and decompression features.


User action: None.

Dlm014EUnknown hardware compression card, id=0xXXXX

Description: The identity of the hardware compression adapter cannot be determined.

System action: Hardware compression and decompression will not be available until the problem is resolved and the controller is restarted.

User action: Contact EMC Customer Support for additional assistance.

DLm015EHardware compression driver error

Description: An error has occurred while initializing the DLm hardware compression adapter.

System action: Hardware compression and decompression are not available until the problem is resolved and the DLm is restarted.

User action: Contact EMC Customer Support for assistance.

DLm016EDevice <devicename> Error opening hardware compression driver:

<error message>

Description: An error has occurred when opening the DLm hardware compression adapter.


System Messages


System action: Hardware compression and decompression are not available for this device until the problem is resolved and the DLm is restarted.


DLm017IRemoving all VOLSER locks owned by this system.

Description: During startup and shutdown, all file locks held by this application, if any, are removed.

System Action: All VOLSER locks owned by this system are removed.

User Action: None.

DLm018EError creating <processname> Thread: <error message>

Description: This internal error can only occur during application startup.

System action: Application startup terminates.


DLm019EError allocating memory for <name>: <error message>

Description: An internal memory allocation error has occurred in the DLm application.

System action: Depending on the error, the DLm may abend or need to be restarted to regain some functionality.


DLm020ECannot verify <feature> license: <error message>

Description: The DLm was unable to validate the license for the specified feature.

System action: The specified feature is not available.


DLm021E<parameter=value> incompatible with <license> license


System Messages


Description: The specified parameter is not compatible with the specified licensed feature.

System action: If the error is in the configuaration file, the application startup terminates. If the error is in a SET command the command is rejected.

User action: Contact EMC Customer Support for additional assistance.

DLm022EUnable to find userid 'vtape'

Description: The DLm application must run under the user ID 'vtape,' but this user ID does not exist on the DLm.



DLm023EUnable to switch to user and group 'vtape'

Description: The DLm application must run under the user ID 'vtape,' but the application was unable to switch to this ID.



DLm024EProgram not started with effective userid 'root'

Description: The DLm application must be started under the userid 'root.'



DLm025EInvalid license combination, EMC+OEM.

Description: The combination of license files on the system is not valid.




System Messages


DLm026EPid file <filename> must be full path name. Use -? for Help

Description: The command that starts the DLm virtual tape application contains an invalid argument.



DLm027EFailed to fork daemon: <error message>

Description: The DLm application failed to daemonize itself.



DLm028EInternal Error calling setsid: <error message>




DLm029EInternal Error changing working directory to '/': <error message>




DLm030ITraces are [un]buffered

Description: The DLm application trace files are buffered (saved in memory and written to disk periodically) by default for better performance. If the environment variable DLmTRACEUNBUFFERED has been set to any value when the DLm application starts, trace files are written in an unbuffered manner (every event is written to disk immediately).


System Messages



User action: The buffered default should be sufficient for most tracing needs, unless directed otherwise by EMC Customer Support. When traces are buffered, make sure to type the DLm command Save Trace to write all trace buffers to disk before examining or copying the trace files.

DLm031ECannot Create PID file <filename>: error message

Description: The application failed to to create the process ID file.



DLm032ETrace task error reading pipe, errno=0x<xx> (<nnn>)

Description: An I/O error has occurred during DLm device tracing.

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


DLm033EError writing to <file type> file <filename>:<error message>

Description: An I/O error occurred when writing to the specified file.

System action: The DLm application continues running without writing additional messages to the specified file.

User action: See any earlier messages and the 'error message' portion of this message to determine the cause of the failure. If the problem cannot be corrected, contact EMC Customer Support for assistance.

DLm035EError creating directory 'directory': <error message>

Description: The specified DLm directory did not exist, and the DLm application was not able to create the directory. This error can only occur during application startup.



System Messages



DLm036EError closing <file type> file <filename>: <error message>

Description: The specified file was not successfully closed. The 'error message' text explains the reason for the failure.

System action: None

User action: If you are unable to correct the problem, contact EMC Customer Support for assistance.

DLm037EError creating/opening <feature> message pipe: <error message>

Description: An error occurred while initializing the specified feature. This error can only occur during application startup.

System action: The DLm startup terminates or continues without the specified feature. The 'error message' text explains the reason for the failure.


DLm038ICreating directory 'directory'

Description: The specified DLm directory did not exist, so the DLm is now creating the directory.

System action: The specified directory is created.

User action: None.

DLm039EError opening output <file type> file <filename>: <error message>

Description: The specified output file was not successfully opened. This error can only occur during application startup.

System action: Application startup terminates. The 'error message' text explains the reason for the failure.


System Messages



DLm041EDevice <devicename> error <nnn> going online

Description: The specified device was not able to go online to the channel. This error can only occur during application startup.


User action: Verify in the DLm configuration file that the channel configuration data for the specified device is correct. If the problem recurs, contact EMC Customer Support for assistance.

DLm042EError <nnn> going live to channel. Interface=n, slot=nnnnnn

Description: The channel interface number 'n' was not able to go online to the channel.

System action: This channel interface is out of service until the problem is corrected and the adapter is reset.

User action: Contact EMC Customer Support for more assistance.

DLm044WWARNING: /var filesystem usage at nn%

Description: The specified critical system filesystem is starting to run low in free disk space. If this filesystem were to fill, it might have a detrimental affect on the system operation.

System action: Warning messages will continue to be displayed at every percentage of change in usage as long as the usage exceeds the designated warning level.

User action: Contact EMC Customer Support for assistance in freeing space on the designated filesystem.

DLm045EError getting status of <filesystem> filesystem: <error message>

Description: An unexpected error occurred while trying to get information about the specified filesystem.


System Messages


System action: The system will continue to run, but some features (such as warnings about the capacity limits of certain filesystems) may not be functional.

User action: If this problem recurs, contact EMC Customer Support for assistance.

DLm046W/var has <nnn> remaining bytes, debugging messages turned off

Description: A debugging mode that writes messages to the console log is active, and the /var filesystem, where the messages are stored, is starting to fill.

System action: The debugging mode is turned off to suppress further debugging messages.

User action: Contact EMC Customer Support for assistance in freeing space on the designated filesystem.

DLm047EInternal Error <function>: <error message>

Description: An internal error has occurred.

System action: The function listed cannot be completed.


DLm048EInternal Error <process>: <error message>

Description: An internal error has occurred.

System action: Application terminates.


DLm049EInternal Error <function>: <error message>

Description: An internal error has occurred due to external conditions.

System action: The function listed cannot be completed.



System Messages


DLm050EInvalid command line parameter: <value>. use -? for help

Description: The command line that starts the DLm application contains an invalid argument.


User action: Correct the command line arguments and restart the DLm application.

DLm052EInvalid command line Configuration File Name parameter: <value>.

Use -? for Help

Description: The command line that starts the DLm application contains an invalid argument.


User action: Correct the command line arguments and restart the DLm application.

DLm055EError getting channel driver version number

Description: The DLm application was unable to determine the version of the EMC channel adapter driver.



DLm056IChannel driver version is x.x.x

Description: Displays the version number of the EMC channel adapter driver.


User action: None.

DLm057EThis application requires minimum channel driver version x.x.x!


System Messages


Description: The EMC channel adapter driver is below the minimum release level required by this version of the DLm application. Message DLm056I that precedes this message identifies the channel adapter driver currently loaded.



DLm058IDevice <devicename> MIHn set to nnn seconds

Description: The MIH (Missing Interupt Handler) timeout value that DLm reports to the Host has been set to the specified value. MIHn will be MIH1 or MIH2. MIH1 is the primary or fast MIH value that most Host operating systems use for most CCWs, such as reads and writes. MIH2 is the secondary or slow MIH value that some Hosts use for certain long-running CCWs such as Locate, FSF, and Data Security Erase commands. By default, DLm sets these values to 3000 and 18000 seconds, respectively.

System action: The specified value is reported to the Host on the next Read Configuration Data command.

User action: None.

DLm060EThere is already an instance of <program> running

Description: Another copy of the DLm application is currently running.

System action: The second copy of the DLm application terminates.

User action: Make sure that the application is not already running before starting a second copy.

DLm061ECannot register <function> handler: <error message>




DLm062EError opening Alert FIFO <filename>: <error message>


System Messages


Description: The DLm application was not able to open the pipe over which it receives Alert (error and warning) information from the channel adapter drivers.

System action: The DLm continues to function, but channel adapter alerts are not noted by the DLm.


DLm064EAlert FIFO has been closed

Description: The EMC channel driver has closed the pipe over which it sends alert messages, which are warning and error messages about channel adapter problems, to the DLm application.



DLm065EInvalid data (nn bytes) read from Alert FIFO

Description: The EMC channel driver has sent an unrecognized alert message to the DLm application.



DLm066EError creating/opening Read named pipe <filename>: <error message>




DLm067IBusyType set to Busy/Immediate/Deferred


System Messages


Description: DLm can be configured to send various status codes to hold off the host under busy conditions. The default is to send a true busy signal.

System action: DLm sends a busy status if BusyType is set to "Busy", an immediate command retry for "immediate", and a deferred command retry for "deferred".

User action: None. Do not change this setting unless directed to do so by EMC Customer Support. This setting could cause channel errors.

DLm068IDouble testing of compressed data set ON/OFF

Description: By default, the DLm application performs an extra CRC check of data that has been compressed before writing it to the tape library.

System action: If this option is ON (the default), the data is checked just before it is written to the library. If a discrepancy is found, an error is returned to the Host's write command. If this option is turned OFF, no extra integrity check is performed.

User action: It is recommended that this option always be left ON.

DLm069IResetting 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 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 are not sent to the channel when this option is set OFF.


System Messages


User action: None. Under normal conditions, the low-level channel resetting event indication should NOT be configured OFF. Under rare conditions, a channel may not correctly handle the low-level channel resetting event indicator, and channel errors may occur. In this case, consult EMC Customer Support before configuring this option off.\n". Also see message “DLm082I”.

DLm070I<emulation type> emulation version set to n

Description: The DLm is configured to invoke the specified channel adapter emulation version.


User action: None.

DLm071ENo channel interface cards present!

Description: No channel interface adapters were detected in the system. This error can only occur during application startup.



DLm072EThis 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 DLm application. Message DLm075I that precedes this message identifies the channel adapter in question.



DLm073EInterface #<n> (slot <nnnnnn>) returned bad status = <nnn>

Description: The specified channel interface adapter returned an error status to the application. This error can only occur during application startup.



System Messages



DLm074EInterface #<n> (slot <nnnnnn>) error getting <adapter info>

Description: The specified channel interface adapter returned an error status to the application. This error can only occur during application startup.



DLm075IInterface #n: n (0xxxxxx) bus:n slot:n type:n (adaptertype) media:n

(mediatype)

Description: Displays information about the channel interface adapters in the DLm. This message is displayed at application startup and in response to the QUERY ALL or QUERY CHANNEL ADAPTER command.


User action: None.

DLm076IInterface #n: [hardware s/n | s/n override] xxxxxxxxxxxx



User action: None.

DLm077IInterface #n: Firmware emulation type: XXXX, version: nnnn

yyyy/mm/dd




System Messages


User action: None.

DLm078IDisk usage WARNING level set to nn%

Description: The DLm is configured to warn about tape library disk utilization when usage reaches nn percent full.


User action: None.

DLm079IDisk space RECOVER level [set to nn%]/[is N/A]

Description: The DLm is configured to start erasing scratch tape volumes to recover disk space when disk utilization reaches nn percent full. If is N/A is displayed, the erase policy is set to a Time-to-live policy rather than a space-usage policy, so the RECOVER setting is irrelevant.


User action: None.

DLm080IDevice <devicename> UNISYS detected

Description: The DLm has detected that the specified virtual device is attached to a Unisys Host. This message is displayed once for each virtual device attached to a Unisys.

System action: The DLm automatically makes accommodations for the differences between an IBM and a Unisys Host.

User action: None (unless the Host is not actually a Unisys Host, in which case EMC Customer Support should be contacted for assistance).

DLm081IInterface #n: Current state <state>; Desired state <state>



System Messages



User action: None.

DLm082IResetting 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 are not sent to the Host when this option is set.

User action: None. Under normal conditions, the DLm should NOT be configured to ignore resetting events. Doing so can cause problems when varying on devices to a Host that properly handles, and actually expects, resetting event unit checks. Contact EMC Customer Support for more information.

DLm083ICompression level set to n (0=none,1=faster,9=smaller)

Description: Displays the compression level set by default, in the configuration file, or by the SET COMPRESSION command. The compression level ranges from 0 (no compression at all) to 9 (maximum compression with maximum overhead). The default compression level is 1 (minimum compression with minimum overhead).


User action: None.

DLm084IDisk space RECOVERAMT set to nn%

Description: The DLm is configured to stop erasing scratch tape volumes to recover disk when disk space usage falls to (RECOVER minus RECOVERAMT) percent.


System Messages



User action: None.

DLm085I<feature> support enabled

Description: This message displays if support for an optional feature has been enabled in the configuration file.

System action: The optional feature is enabled.

User action: None.

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.

DLm087IChecking of CRCs from channel set ON|OFF

DLm088ISending of CRCs to channel set ON|OFF

DLm089IUNISYS set ON/OFF for device <devicename> / ALL devices

Description: The SET UNISYS command has been accepted for a device or all devices.

System action: The DLm adjusts the differences between an IBM and a Unisys Host for the specified devices.

User action: None (unless the Host is not actually a Unisys Host, in which case you should not do this).

DLm090IAMDD feature turned ON/OFF [for device devicename]/[for all

devices]


System Messages


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


User action: None.

DLm091IAMDD pad boundary set to <nnn> (0xXX)(SET this way/configured this

way/by default)

Description: The AMDD pad boundary has been set to the designated value.


User action: None.

DLm092ESET AMDD cannot specify a specific device

Description: AMDD is a global setting and cannot be SET by individual device.

System action: The SET command is ignored.

User action: None.

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


User action: None.

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


System Messages


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

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

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


System Messages


DLm097IMaximum 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 stops erasing for a short period before resuming erasing. The default time is 30 seconds.


User action: None.

DLm098IEncryption initialized, <#keys> keys ready

Description: Encryption capability was initialized successfully, with <#keys> keys available for encryption and decryption.


User action: None.

DLm099INew mount on already-mounted drive will be allowed

Description: The DLm system has been explicitly configured to honor a mount request for a drive that already has a virtual tape volume mounted.

System action: If the DLm receives a mount request on a drive that already has a tape mounted, and the drive had received an Unassign command from the host while that tape was mounted, DLm unloads the tape and honors the new mount request.

User action: None. This option is not recommended except in specific circumstances. Contact EMC Customer Support for more assistance.

DLm100IConfiguration file opened: <filename>

Description: The specified input configuration file was successfully opened.


User action: None.


System Messages


DLm101WMissing or invalid file "/etc/bti/btiximl", using config file

"/etc/bti/btixmap0"

Description: The file /etc/bti/ximl should contain the name of the configuration file that the DLm loads at startup. If /etc/bti/ximl does not exist, the DLm loads the default configuration file /etc/bti/xmap0.

System action: The default configuration file, /etc/bti/xmap0, is used.

User action: The /etc/bti/ximl file should normally point to the desired DLm configuration file. Reconfigure the DLm and \Select Configuration for Next Startup\ to identify which of the four DLm configuration files you want to use. Contact EMC Customer Support if this problem recurs.

DLm102IConfiguration file is <filename> [(changed!)]

Description: Displays the name of the configuration file currently in use. (changed!) means that the configuration file has changed since the last DLm startup.


User action: None.

DLm104WDevice <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 DLm application no longer supports this command.

System action: None; the command is ignored.

User action: None.


System Messages


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

DLm108I Guaranteed Replication Timeout set to n seconds

Description: Indicates that the system is configured to wait n seconds for a GR replication refresh to complete. If replication does not complete within this time, an error indication is returned to the host's unload command.


User action: None.

DLm109IScratch mounts will [not] ignore full filesystems

(UseFullFS=TRUE/FALSE)


System Messages


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.

DLm110IChannel adapter firmware tracing by DEVICE/PATH

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


User action: None.

DLm111IMaximum tape block size set to nnn

Description: The DLm has been configured to support a maximum tape block size different from the default of 256K.

System action: The DLm supports the host reads and writes up to the specified block size.

User action: None. Do not change this setting unless directed to do so by EMC Customer Support.

DLm112IUsing NEW/FAST scratch search method


System Messages


Description: The DLm application has been explicitly configured to support either the standard documented scratch tape allocation technique ("NEW") or an alternative faster method that ignores scratch tapes' last-used dates.

System action: The DLm application will use the technique described. The default method is "NEW".

User action: None.

DLm113EUsing 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

DLm114IScratchSearchMethod=OLD is no longer a supported option

Description: The value "OLD" was specified for the ScratchSearchMethod parameter. This value is no longer supported.

System action: The DLm application will use the technique described. The default method is "NEW".

User action: Contact EMC Support for more information.

DLm115EError 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 successfully fsynced.

User action: If you are unable to correct the problem, contact EMC Support for assistance.


System Messages


DLm116IQuery Space timeout set to <nnn> minutes

Description: The system is configured to wait <nnn> minutes for a query space to complete. If query space does not complete within this time, an error indication is displayed on the console.


User action: None.

DLm117IQuery Space <status>

Description: If the Query Space is invoked while it is running, an "already in progress" status will be displayed. If the Query Space exceeds the QSPACETIMEOUT, a "has exceeded the timeout value" status will be displayed.


User action: None.

DLm118ICelerra report interval set to <nn> seconds

Description: The 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.

DLm119EError reading configuration file <filename> line nnn: <error

message>

Description: An I/O error occurred while reading the specified configuration file.


User action: Use the DLm configuration program to reconfigure and save the specified DLm configuration file. If the problem persists, contact EMC Customer Support for assistance.


System Messages


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

System Action: None.

User Action: None.

DLm121ECannot open configuration file <filename>: <error message>

Description: The specified configuration file was not successfully opened.


User action: Use the DLm configuration program to reconfigure and save the specified DLm configuration file. If the problem persists, contact EMC Customer Support for assistance.

DLm122ENo devices defined in configuration file

Description: There were no virtual tape drives configured in the DLm configuration file.


User action: Use the DLm configuration program to reconfigure and save the DLm configuration file. If the problem persists, contact EMC Customer Support for assistance.

DLm123EError in config file, line nn: Unrecognized keyword '<keyword>'

Description: The DLm configuration file contained an error.


User action: Use the DLm configuration program to reconfigure and save the DLm configuration file.


System Messages


DLm124EError in config file, line nn: Incorrect number of <keyword>

parameters




DLm125EError in config file, line nn: Invalid <keyword> value '<value>'




DLm126EMaximum number of devices (nnn) exceeded, terminating

Description: Too many devices have been defined in the configuration file.

System action: Startup terminates.

User action:Use the configuration program to reconfigure with a valid number of devices.

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

DLm128IWatchdog timer set to nnn seconds


System Messages


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

DLm129EError in config file, line nn: <value> is not a valid parameter




DLm130EError in config file, index xx: <value> is not a valid parameter




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




DLm132EError in config file, line nnn: Duplicate <keyword> parameters



System Messages




DLm133EError in config file, line nnn: Too many <keyword> parameters

Description: The virtual tape configuration file contained an error.


User action: Use the configuration program to reconfigure and save the configuration file. If the problem persists, contact EMC Customer Support for assistance.

DLm134EDuplicate INDEX=0xXX in configuration file, line nnn




DLm135EError attaching device index xx




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



System Messages


User action: Correct the configuration file. For more assistance, contact EMC Customer Support.

DLm137WInvalid TRACE= value 'value'


System action: DLm startup continues with the default value of 1.


DLm138E Volser Lock Directory <DIR> is not mounted correctly

Description: An NFS Volser 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.

User Action: Use the configuration program to reconfigure and save the configuration file.

DLm140EError in config file, line nnn: <feature> not supported

Description: The DLm configuration file contains parameters for a feature that is not licensed for use on this DLm.

System action: DLm startup terminates.

User action: Contact EMC for more information on enabling the licensed feature.

DLm144EDuplicate NAME=value in configuration file, line nn




System Messages



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

DLm151EDevice <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 Customer Support for information about obtaining the optional feature license.

DLm155IDevice <devicename> data path='<pathname>' [by default][, volser

prefix=<volid>]

Description: The specified pathname is the base tape library directory for this device; virtual tape volumes for this device resides in this directory and its immediate subdirectories. '[by default]' signifies that PATH= was not specified for the device and it was set to the standard default value; otherwise, PATH=pathname was explicitly set


System Messages


in the device configuration. If a volser prefix is shown, it signifies that virtual tape volumes that begin with the prefix <volid> automatically creates as needed by the DLm, if they have not been pre-initialized.


User action: None.

DLm156WDevice <devicename> Data path <pathname> is not accessible!

Description: The specified virtual tape library directory cannot be accessed.

System action: During system startup, this is a warning message and application startup continues. However, no virtual tape volumes that reside in this directory can be mounted on this drive until the specified directory is made accessible. If this error occurs when processing a SET PATH command, the SET PATH command fails and the current tape library path is not changed.

User action: If the configured directory name is correct, make sure that it is mounted and accessible to the user 'vtape.' If the directory name was misconfigured, correct the PATH= parameter in the DLm configuration file and restart the DLm application.

DLm157WDevice <devicename> tapelib subdirectory 'xxx' is not accessible!

Description: The specified virtual tape library subdirectory cannot be accessed.

System action: During system startup, this is a warning message and application startup continues. However, no virtual tape volumes that reside in this subdirectory can be mounted on this drive until the specified subdirectory is made accessible. If this error occurs when processing a SET PATH command, the SET PATH command fails and the current tape library path is not changed.

User action: Make sure that the proper filesystem is mounted on the specified subdirectory and it is accessible to the user 'vtape.'

DLm160IDevice <devicename> enabled for Guaranteed Replication

Description: Indicates that the device has been enabled for Guaranteed Replication.



System Messages


User action: None.

DLm161ITape library pathname enabled for Replication

Description: Indicates that the tape library directory resides on a filesystem that is enabled for replication.


User action: None.

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

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

DLm164IDevice <devicename> enabled for FLR

Description: This device is configured to support File Level Retention.


User action: None.

DLm165ITape library <pathname> enabled for FLR


System Messages


Description: This tape library directory resides on a filesystem that is enabled for File Level Retention.


User action: None.

DLm166EError 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 Action: Celerra-related features such as Guaranteed Replication and FLR may not function correctly.

User Action: If the error message describes a correctable problem, correct the problem and restart the application. Contact EMC Support if more assistance is needed.

DLm168WInvalid DEBUG= value 'value'

Description: The configuration file or operator SET DEBUG command contained an error.

System action: If a configuration, DLm startup terminates. If a SET DEBUG command error, the SET command is ignored.

User action: If a configuration error, reconfigure the DLm to correct the configuration file. If a SET DEBUG command error, use the HELP command to obtain correct syntax.

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


System Messages


DLm170WCelerra #n report file is over 30 minutes old; check Celerra

control station

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.

User action: Contact EMC Support for assistance.

DLm171EFile <filename> line nnn is too long

Description: The configuration file contained an error.


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

DLm180EError [opening|configuring] <name> communication device <details>

Description: An internal error has occurred within either the SNMP or the IPMI subsystem. The IPMI subsystem is responsible for monitoring and reporting system events other than those occurring within the DLm application, the channel interface adapter, or the adapter device drivers. The SNMP subsystem is responsible for broadcasting all DLm event messages that were selected during DLm configuration to the SNMP management station.

System action: The DLm application continues to function in a degraded state. Data transfer and storage continue to operate normally, but the SNMP and the IPMI subsystem facility is no longer available.

User action: It may be possible to identify the resource that caused the failure and correct the problem. If the problem persists, contact EMC Customer Support for assistance.

DLm181ISNMP data dump file <NAME> has been created


System Messages


Description: This message displays the name of the file that was created to save SNMP diagnostic information.


User action: None.

DLm182WUnable 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 SNMP is 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 DLm application, the channel interface adapter, or the adapter device drivers. The SNMP subsystem is responsible for broadcasting all DLm event messages that were selected during DLm configuration to the SNMP management station.

System action: The error is logged and operation continues. If the failure persists, the subsystem is disabled.

User action: If the SNMP subsystem is disabled as a result of this failure, it can be reenabled from the DLm Console. If the problem persists, or it cannot be corrected, contact EMC Customer Support for assistance.

DLm184EError <number> building SNMP OID. Disabling SNMP

Description: SNMP has detected an internal error and SNMP event messages may have been lost.


System Messages


System action: SNMP is disabled.

User action: It may be possible to restart SNMP from the DLm Console. Contact EMC Customer Support for assistance.

DLm185EError - SNMP <entity> initialization failed (<details>)

Description: Entity is 'thread,' 'library,' or 'IPMI.' A failure has occurred during initialization of the entity. The IPMI subsystem is responsible for monitoring and reporting system events other than those occurring within the DLm application, the channel interface adapter, or the adapter device drivers. The SNMP subsystem is responsible for broadcasting all DLm event messages that were selected during DLm configuration to the SNMP management station.

System action: If the failure occurred within the SNMP subsystem, initialization is aborted and the SNMP services are not available. If the failure occurred within the IPMI subsystem, SNMP continues to function, but no system platform events are reported.


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

DLm188ISNMP is [not] operational

Description: Used to display the current SNMP operating status.


User action: None.

DLm189WSNMP subagent service is unavailable


System Messages


Description: SNMP is not initialized or it has terminated.


User action: None.

DLm190IDLM SNMP terminated

Description: The SNMP subsystem has shut down normally.


User action: None.

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

DLm193IIPMI <informational message>

Description: Describes some event that has occurred within the IPMI subsystem. The IPMI subsystem is responsible for monitoring and reporting system events other than those occurring within the DLm application, the channel interface adapter, or the adapter device drivers.


User action: None.

DLm194WIPMI <warning message>

Description: An internal failure has occurred. The system has recovered, but event messages may have been lost. The IPMI subsystem is responsible for monitoring and reporting system events other than those occurring within the DLm application, the channel interface adapter, or the adapter device drivers.


System Messages


System action: The condition is logged and operation continues. If the condition persists, the subsystem is shut down.

User action: If the problem persists, contact EMC Customer Support for assistance.

DLm195EIPMI <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 events other than those occurring within the DLm application, the channel interface adapter, or the adapter device drivers.

System action: The error is logged and the IPMI subsystem is shut down.

User action: If the cause of the problem cannot be determined and corrected, contact EMC Customer Support for assistance.

DLm196I(System Event) <informational message>

Description: This is an informational message describing a system platform event that was detected by the IPMI subsystem. The IPMI subsystem is responsible for monitoring and reporting system events other than those occurring within the DLm application, the channel interface adapter, or the adapter device drivers.

System action: The message is saved to both the system event log and DLm event log.

User action: None.

DLm197W(System Event) <warning message>

Description: Warns of a system platform event that was detected by the IPMI subsystem. The event should be evaluated to determine if corrective action is needed. The IPMI subsystem is responsible for monitoring and reporting system events other than those occurring within the DLm application, the channel interface adapter, or the adapter device drivers.

System action: The message is saved to both the system event log as well as the DLm event log.


System Messages


User action: The user action varies with the event. In some cases, such as a chassis intrusion warning following the replacement of a system component, the warning may be ignored. In other cases, the message may indicate a failure or loss of redundancy in a power supply, fan, memory device, or other component and the component should be replaced. Contact EMC Customer Support if assistance is needed.

DLm198E(System Event) <error message>

Description: This message indicates that the IPMI subsystem has detected a system platform event that may result in significant functional or security problems. The event should be evaluated to determine if corrective action is needed. The IPMI subsystem is responsible for monitoring and reporting system events other than those occurring within the DLm application, the channel interface adapter, or the adapter device drivers.

System action: The message is saved to both the system event log and the DLm application event log.

User action: The user action will vary with the event. In some cases, such as a chassis intrusion warning following the replacement of a system component, the warning may be ignored. In other cases, the message may indicate a failure or loss of redundancy in a power supply, fan, memory device, or other component and the component should be replaced. Contact EMC Customer Support if assistance is needed.

DLm201IValidating tape library '<pathname>'...

Description: During startup, and any other time a tape library path change is requested, the DLm validates the tape library for various integrity issues.

System action: If any errors are found, subsequent messages report the problems.

User action: If any errors are reported, correct the problems, then SET PATH= to the desired path.

DLm202IDevice <devicename> <nn> subdirectories under tape library

'pathname'

Description: While validating the specified tape library, the DLm displays the number of subdirectories found in that tape library.


System Messages


System action: If any subdirectories exist, they are also validated.

User action: None.

DLm203IDevice <devicename> There is no <volser> directory, using

<pathname>

Description: When attempting to mount, scratch, unscratch, erase, or delete a volume, the DLm found that there was no tape library subdirectory matching the first two characters (\volser prefix\) of the specified volume.

System action: The system searches only in the base tape library directory for the desired volume.

User action: None.

DLm204EDevice <devicename> tapelib directory '<pathname>' is not

browsable!

Description: While validating the tape library, the specified path was found to be not browsable, which means the contents could not be listed.

System action: During system startup, this is a warning message. If this error occurs when processing a SET PATH command, the SET PATH command fails.

User action: Make sure that the tape library is mounted correctly, and that it is owned by user 'vtape' and has the 'x' permission set.

DLm205EDevice <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 describes the error that occurred. Correct the error and retry the SET PATH command to set the tape library path to the desired path.


System Messages


DLm206WDevice <devicename> bypassing full filesystem <pathname>

Description: A filesystem with less than a full tape's worth of free space (based on the current SIZE= value) will be skipped while searching for a scratch tape. This option can be overridden with the "UseFullFS TRUE" configuration option or "SET UseFullFS=TRUE" command.

System action: The specified filesystem is bypassed during this scratch tape search.

User action: None.

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

DLm209ECannot 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


System Messages


DLm210IValidating tape library '<pathname>'...

Description: During startup, and any other time a tape library path change is requested, DLm validates the tape library path.

System action: If any errors are found, subsequent messages will report the problems.

User action: If any errors are reported, correct the problem(s), then SET PATH= to the desired path.

DLm211ITape Library SN '<status>'

Description: During startup DLm determines whether the discovered tape library is supported or not.

System action: During system startup this is an informational message.

User action: If a library is not supported the operator could change the VTL back end to disable this library and enable a supported library instead.

DLm212IVTL <VTL-SN> Volume List <status>

Description: During startup, and at any other time a VTL volume list update is requested, DLm will display the VTL volume list state.


User action: None.

DLm213ISCSI Media Changer Driver version: x.x.x

Description: This message displays the version number of the scsi media changer driver.


User action: None.


System Messages


DLm214EError creating/mapping/opening ATL Volume List file: <filename> :

<error message>

Description: An error occurred while initializing the specified feature. This error can only occur during startup.

System action: startup terminates or continues without the specified feature. The 'error message' text explains the reason for the failure.

User action: If you are unable to correct the problem, contact contact EMC Support for assistance.

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

DLm217WVTL-SN volumes in slots x to y exceed maximum and will not be used

Description: The VTL has defined more slots than the application can support.


User action: Define the number of slots on the back-end VTL to within our maximum of 20,000 slots.

DLm218IScanning tape drive devices...

Description: The SCSI tape drives are being scanned and cataloged.


User action: None.


System Messages


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

DLm220IValidating tapelib subdirectory '<name>'...

Description: During startup, and any other time a tape library path change is requested, the DLm validates the tape library and each of its subdirectories for various integrity issues.

System action: If any errors are found, subsequent messages report the problems.

User action: If any errors are reported, correct the problems, then SET PATH= to the desired path.

DLm221EDevice <devicename> subdirectory name '<name>' is not a valid

volser prefix

Description: During validation of the tape library, the DLm found the specified subdirectory, but the subdirectory name does not conform to a valid volser prefix. Every subdirectory in a tape library must have a two-character name that consists of valid volser characters (A–Z, 0–9).


User action: Either remove the invalid subdirectory from the tape library base directory, or rename the subdirectory to a valid volser prefix.

DLm222EDevice <devicename> subdirectory name '<name>' is not a valid tape

library subdirectory name


System Messages


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.

System action: During system startup, this is a warning message. If this error occurs 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 enhanced filesystem subdirectory name.

DLm224EDevice <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: Make sure the tape library is mounted correctly, and that each subdirectory is owned by user 'vtape' and has the 'x' permission set.

DLm225EDevice <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 describes the error that occurred. Correct the error and retry the SET PATH command to set the tape library path to the desired path.

DLm226WDevice <devicename> file '<filename>' does not belong in

subdirectory '<name>'


System Messages


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.

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

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

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

DLm230WWARNING: Device <devicename> path <dirname> is on root filesystem!

Description: The directory assigned to hold the virtual tape volumes for this device is mounted on the root filesystem. This usually means that the real tape library filesystem was not mounted, since tapes are not expected to be stored on the DLm system disks, but on a high capacity external disk.

System action: The specified directory continues to be used as the tape library for this drive. This message is displayed every time a virtual tape volume is successfully mounted and the tape library is still mounted on the root filesystem.

User action: Make sure that the proper disk filesystem is mounted on the tape library path specified for this drive.

DLm231WUnable to determine <pathname> device name: <error message>


System Messages


Description: The DLm was unable to determine on which disk filesystem the specified directory is mounted.

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


DLm232WDevice <devicename> Unable to determine <pathname> filesystem type:

<error message>

Description: An unexpected error occurred while trying to determine what type of filesystem holds the specified tape library.

System action: The DLm continues to run, but some features (such as warnings about the capacity limits of certain filesystems) may not be functional.


DLm233EDevice <devicename> data path <pathname> is not accessible

Description: During mounting of a tape volume, the DLm was not able to access the specified tape library subdirectory.

System action: This subdirectory is ignored. If there are other tape library subdirectories, they are considered to attempt to fulfill the mount request.

User action: If the configured tape library is correct, make sure that all of its subdirectories are mounted and accessible to the user 'vtape.' If the tape library is misconfigured, correct the PATH= parameter in the configuration file and restart the DLm application, or use the SET PATH command to temporarily change the tapelib path.

DLm234WDevice <devicename> data path <pathname> is not accessible: not

readable

Description: During mounting of a scratch volume, the virtual tape application was not able to access the specified tape library subdirectory.


System Messages


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.

DLm235EDevice <devicename> failed deferred tapelib path change to <path>

Description: A tape library change was previously deferred while a volume was mounted on this drive. Now that there is no longer a volume mounted, an attempt to change the tape library to the new path has failed.

System action: The tape library path is not changed.

User action: This message should have been preceded by one or more messages that explained the problem. See these messages, correct the problems, and then SET PATH= to the desired path.

DLm236WError 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 and restart the application. Contact EMC Support if more assistance is needed.

DLm237WDevice <devicename> Volume <volser> Error reading Celerra Report:

error message

Description: An unexpected error occurred while trying to determine the current state 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.

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.

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

DLm239EError opening Celerra report file <pathname>: error message

Description: An unexpected error occurred while trying to determine the current state 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.

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.

DLm240EUnable to open tape library path <pathname>

Description: A tape library path couldn't be opened.

System action: The search for a particular volser was not completed.

User action: Check to be sure the path exists.

DLm241EDevice <devicename> Unable to read contents of volser' lock file

<volser>: <error>


System Messages


Description: While unlocking a volume, the contents (owner) of a VOLSER lock file could not be read.

System action: The owner of the VOLSER lock could not be determined. The lock remains in place.

User action: Verify that the VOLSER lock directory is mounted and accessible.

DLm242EDevice <devicename> error deleting lock file <filename>: <error>

Description: While unlocking a volume, an error occurred while trying to remove the lock file for this VOLSER.

System action: The status of the VOLSER lock is unknown.

User action: Verify that the VOLSER lock directory is mounted and accessible.

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

DLm244EError reading file <file>: <error>

Description: An error occurred while reading file.

System action: The file could not be read.

User action: Verify the file exists.

DLm245EUnable 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


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

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

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

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

DLm250IDevice <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 Customer Support.


System Messages


DLm251EProblem accessing directory <dirname>: <error>

Description: A problem occurred while accessing the destination directory for the new volume(s).

System action: No volumes will not be created in this directory.

User action: None. If the problem persists, contact EMC Customer Support.

DLm252EWrong storage class. REQ <requested class>, WAS <actual class> for

<dirname>

Description: The IMPORT command specified a storage class for the request directory that was different than the indicated class.

System action: No volumes created.

User action: Retry the command with a different storage class or directory.

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

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

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

DLm256IVolser Lock Directory set to: <directory>

Description: A volser lock directory has been specified for Enhanced Filesystem Architecture operations.


User action: None.

DLm257IThe Maximum Find Volume Display Count is: <count>

Description: This is the maximum number of volumes displayed by the 'find volume' command.

System action: Not more than <count> volumes will be displayed for the find volume command.

User action: None.

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

DLm259ENo storage class <class> directory found

Description: The IMPORT command CLASS= parameter specified a storage class that cannot be found.

System action: The command will not be executed.

User action: Retry the command with valid parameters.


System Messages


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

DLm261EDevice <devicename> Unable to lock volser <volser>: <reason>

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


User action: Verify the VOLSERLOCKDIR setting the configuration file.

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

DLm 263IDevice <devicename> moved <volser path> to <volser path>, <size>

bytes

Description: A device moved a newly acquired scratch volume from one filesystem to another file system of the same class.

System action: None

User action: None.

DLm264EInvalid parameter: <import to>

Description: The IMPORT command TO parameter is not a valid VOLSER name.

System Action: The command will not be executed.


System Messages


User Action: Retry the command with valid parameters.

DLm269IDevice <devicename> forcing CRC storing/large headers for Data

Domain file system

Description: The device is writing to a filesystem that resides on a Data Domain. This type of file system required large headers to be used.


User action: None.

DLm270IDevice <devicename> Volume <volser> writing AMDD optimized volume

Description: During a write operation, the data on this tape volume has been modified by the AMDD feature to achieve better back-end data deduplication. This message will be displayed only once per volume.

System action: None. When the data is read back, the AMDD modifications will be transparent to the host.

User action: None.

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

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


System action: An equipment check error status is returned to the Host I/O request.


DLm273WDevice <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 Customer Support for evaluation.

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

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


System Messages


DLm276IDevice <devicename> Volume <volser> AMDD read <nnnnn> AMDD-modified

blocks

Description: The specified number of blocks read from this tape were found to have been AMDD-modified blocks. This informational message is displayed at unload time whenever any AMDD-modified blocks had been read.


User action: None.

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


DLm278IDevice <devicename> Volume <volser> Suppressing IDRC for <type>

library

Description: The Host has requested that the data it is writing should be compressed, but the data will be written uncompressed because the type of tape library filesystem it is being written to performs better with uncompressed data. <type> may be "EMC DLm Data Domain".

System action:The data being written is not compressed. If desired, compression can be forced, regardless of filesystem, by setting the IDRC=FORCE option on a device-by-device basis. This message will display only once per volume as a reminder.

User action: None.

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


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.

DLm281EEXPORT/IMPORT FROM file not found. EXPORT/IMPORT command aborted.

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


User action: Execute the command with the correct file.

DLm282EEXPORT TO device already in use. EXPORT command aborted.

Description: The TO device specified in the EXPORT command is already in use. The EXPORT command stopped with no action.


User action: Execute the EXPORT command when the device becomes free.

DLm283EEXPORT/IMPORT FROM/TO file already in use. EXPORT/IMPORT command

aborted.

Description: The file specified in the command is currently in use by another device. The command stopped with no action.


User action: Execute the command again after the current operation that is using the file has completed.

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



System Messages


User action: Check for previous error message that may indicate cause of problem. Verify that the physical device is properly attached to the system. If this problem recurs, contact EMC Customer Support for assistance.

DLm285EEXPORT/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: Execute the command again with valid parameters.

DLm287EIMPORT SCSI device is already in use. IMPORT command aborted.

Description: The SCSI device specified in the command is currently in use. The command stopped with no action.


User action: Execute the IMPORT command when the device becomes free.

Note: This message applies to Fibre Channel drives as well. The message mentions "SCSI" because DLm uses SCSI tape drivers.

DLm288EIMPORT 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: Execute the command again with a file that does not exist.

DLm289EEXPORT/IMPORT FROM/TO file is invalid. Scratch file not permitted


System Messages


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 that the IMPORT or EXPORT operation is starting.


User action: None.

DLm291IIMPORT/EXPORT operation finished (successfully/with error):

FROM=file (dev=EXFRxxxx) TO=device (dev=EXTOxxxx)

Description: Message indicating that the operation has completed. If with error, check previous messages for cause of error.


User action: None.

DLm294IEXPORT/IMPORT operation performing rewind or rewind/unload:

FROM=name (dev=EX/IMFROMxxxx) TO=name (dev=IMTOxxxx)

Description: Message indicating that the operation has completed and is now rewinding and unloading the tape device.


User action: None.

DLm295EEXPORT operation reached PEOT. Tape invalid: FROM=name

(dev=EXFROMxxxx) TO=name (dev=EXTOxxxx)

Description: The EXPORT command reached the physical end of tape before completing the export operation. The tape is invalid.


System Messages



User action: Repeat the EXPORT operation with a larger tape.

DLm296EError rewinding tape after PEOT: FROM=name (dev=EXFROMxxxx)

TO=name (dev=EXTOxxxx)

Description: The EXPORT command got an error when rewinding the tape after it reached the physical end of tape.


User action: None.

DLm297EError writing tapemark after PEOT: FROM=name (dev=EXFROMxxxx)

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.


User action: None.

DLm298ESCSI device not ready, operation aborted: FROM=name

(dev=EX/IMFROMxxxx) TO=name (dev=EX/IMTOxxxx)

Description: The SCSI device specified in the command was not in the ready state, and the operation was aborted.


User action: Ready the SCSI device and execute the command again.

Note: This message also applies to Fibre Channel drives. The message mentions "SCSI" because DLm uses SCSI tape drivers.

DLm300WDevice <devicename>, connection n, received pkt 0xXXXX (packettype)


System Messages


Description: The channel interface adapter sent an unexpected message type to the DLm application.

System action: The message from the adapter is ignored.


DLm301WChannel event 'eventtype' (0xXXXX) on device <devicename>

<pathinfo> [XXXX XXXX]

Description: The specified exceptional channel event 'eventtype' has been detected. Some common event types which may occur include:

◆ Halt I/O: Host has issued a Halt I/O command, usually as a result of a Host job being canceled.

◆ System Reset: Host has issued a System Reset, usually as a result of the Host being reset.

◆ Link Error: An error has occurred at the channel link level. This is usually the result of the channel 'dropping light,' most often because the channel cable was unplugged or is faulty. This can also be the result of a channel protocol error caused by a faulty channel, director, or channel adapter hardware or firmware problem.

◆ Selective Reset: The Host has issued a Selective Reset to this device, usually because the device is being varied on or offline, or because a serious I/O error has occurred on this device.

System action: Processing continues normally by the DLm; it is presumed that the Host performs the proper error recovery procedure to which the DLm responds like a real tape drive.

User action: Unless this is an expected occurrence (such as the Host job is being canceled, the Host is being reset, or a channel or device is being varied off or on), check the Host console logs to determine the cause of the problem. Contact EMC Customer Support for assistance if the problem persists.

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


System action: This device is unavailable to the Host until it is brought back online.

User action: None, unless this is an unexpected occurrence, in which case you should investigate the cause at the Host.

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

DLm304EInterface #n exceeded automatic restart limit of <count>, NOT

restarting

Description: The specified channel interface was reset because of an error, or because of an operator action from outside the DLm application. The DLm automatically recovers from this situation <count> number of times, but this count has been exceeded.

System action: This channel interface remains offline to the DLm devices.

User action: The situation causing the channel interface adapter to reset should be investigated; contact EMC Customer Support for more assistance if necessary.

DLm305EActive path(s) on Interface #n, cannot stop adapter

Description: There was an attempt to reset or stop channel interface #n while there were active devices online.

System action: The channel interface remains online without having been stopped or reset.

User action: Before stopping or resetting a channel interface, all channel paths using that channel adapter must be varied offline from the Host.

DLm306WActive path on Interface #n, device <devicename>


System Messages


Description: Channel interface #n is being forcefully stopped or reset while there are active devices online. This may cause I/O errors on the Host channel.

System action: Stopping or resetting of the channel interface continues.

User action: None.

DLm308IRebooting Interface #n, slot=nnnnnn

Description: Channel interface #n is being reset.


User action: None.

DLm309IDevice <devicename> NOT sending a resetting event unit check

Description: A resetting event is any channel event that resets a DLm application device's pathgroup ID or assignment, such as a system or selective reset or restarting of the DLm application. Normally, after a resetting event has occurred, the next command sent by the Host receives a resetting event unit check to notify the Host that the resetting event occurred. The Host should respond appropriately by restoring the device's pathgroup ID and assignment information, and reissue the unit-checked command. Occasionally, especially with older standalone IPL programs, a Host may not handle a resetting event unit check correctly. In this case, the DLm application can be configured to NOT send resetting event unit checks. This message is displayed when the DLm application is so configured and would have normally sent a resetting event unit check to a Host command.

System action: Processing of Host commands continues without the occurrence of a resetting event unit check.

User action: None. Under normal conditions, the DLm application should NOT be configured to ignore resetting events. Doing so can cause problems when varying on devices to a Host that does properly handle, and actually expects, resetting event unit checks. Contact EMC Customer Support for more information.

DLm310E<process> received unexpected packet type 0xXXXX (packettype)


System Messages


Description: An error was returned from the channel adapter. This error can only occur during DLm startup.



DLm311WDevice <devicename> received <info> on path <n> but in chain on

path <n>

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

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


DLm312EDevice <devicename> Error reading from Interface #n: error message

Description: An error was returned from the channel adapter.



DLm313EDevice <devicename> error sending <info>, error = nn (0xXX)

Description: An error was returned from the channel adapter.



DLm314EDevice <devicename> <path> unexpected <type> XX CCW while inccw for

XX

Description: An unexpected packet sequencing error occurred. This is an internal error.


System Messages


System action: A Unit Check is returned to the host.


DLm315WDevice <devicename> selection (ccw XX) on path <n> not assigned

Description: The DLm virtual tape device has been assigned (reserved) by a specific Host LPAR, but it received an I/O command over a channel path on which it is not currently assigned.

System action: The I/O command is ignored.

User action: Check that the DLm configuration for channel paths matches the Host's configuration. Make sure that no other LPARs or Hosts are also trying to talk to the same DLm device.

DLm316EDevice <devicename> received <info> on unexpected connection nn,

path=nn

Description: A message was received from the channel adapter from a path that the DLm does not recognize as a valid path.

System action: The unexpected message is ignored. The application continues to run, but the device may not continue to function properly.


DLm317EDevice <devicename> received data on unexpected connection nn,

path=nn

Description: Data was received from the channel adapter from a path on which the DLm was not currently handling a CCW.

System action: The unexpected data is ignored. The application continues to run, but the device may not continue to function properly.


DLm318EDevice <devicename> received unexpected data on connection nn,

path=nn


System Messages


Description: Data was received from the channel adapter while the DLm was not currently handling a CCW that should return data.

System action: The unexpected data is ignored. The application continues to run, but the device may not continue to function properly.


DLm319EDevice <devicename> <path> invalid data chaining flags (XXX) for XX

CCW

Description: An invalid message was received from the channel adapter. This is an internal error.

System action: The CCW is rejected with a Unit Check.


DLm320IFirmware trace enabled/disabled interface #n, slot nnnnnn

Description: Firmware tracing was enabled or disabled on the specified channel adapter.

System action: Channel adapter tracing remains in this state until the DLm is next restarted.

User action: None. You can use the DLm \ENABLE FIRMWARE TRACE\ or \DISABLE FIRMWARE TRACE\ command to turn tracing on or off.

DLm326EChannel Adapter #n NOT reset/stopped/started

Description: A \RESET/STOP/START CHANNEL ADAPTER\ command was typed, but the specified action could not be performed.


User action: Examine preceding related messages, if any, for additional error messages that explain why the action could not be performed, correct the problem, and try the command again.


System Messages


DLm327IChannel Adapter #n reset/stopped/started

Description: The specified action was taken in response to the DLm \RESET/STOP/START CHANNEL ADAPTER\ command.


User action: None.

DLm331EDevice <devicename> no <type of> paths to send Ready Status

Description: The virtual tape drive has become Ready, but there is no online path to send the Ready Status message to the Host. Most likely the drive, path, or channel was never configured/varied online on the Host, or has been varied offline.

System action: The drive is mounted and ready from the DLm point of view, but since a Ready Status was not presented, the Host most likely reports that the drive is still not ready.

User action: Check that the specified device is varied online on the Host. You can cause the DLm to present another 'Ready' signal to the Host by typing an \Unready\ command, followed by a \Ready\ command. If this problem recurs, contact EMC Customer Support for assistance.

DLm332EDevice <devicename> [pathNumber] Error sending Async Ready Status,

err=nnn

Description: An error has occurred while attempting to send an unsolicited status ('Ready' signal) to the Host.

System action: The DLm attempts to present the status several more times. If the Host never takes the status, the virtual volume remains mounted on the drive, but the Host most likely reports that the drive is still not ready.

User action: You can cause the DLm to present another 'Ready' signal to the Host by typing an \Unready\ command, followed by a \Ready\ command. If this problem recurs, contact EMC Customer Support for assistance.

DLm333EDevice <devicename> failed to send Ready interrupt to Host


System Messages


Description: After several retries, the DLm was unable to present the asynchronous status ('Ready' signal) to the Host.

System action: The application continues without presenting the status to the Host. The virtual volume remains mounted on the drive, but the Host most likely reports that the drive is still not ready.

User action: You can cause the DLm to present another 'Ready' signal to the Host by typing an \Unready\ command, followed by a \Ready\ command. If this problem recurs, contact EMC Customer Support for assistance.

DLm335IDevice <devicename> unassigned while volume <volser> mounted

Description: The host has sent an Unassign command to the device while a tape was mounted on the device.

System action: The Unassign command is processed normally. The tape remains ready and at its current position.

User action: This is a valid but unusual condition. Check that the Host is not having some kind of problem with this virtual device. Contact EMC Customer Support if you need additional assistance.

DLm338INew path established: board=n, path=n, link=xx, lpar=xx, cu=xx

Description: The Host has established a new channel path to the DLm.

System action: This path is available now for channel I/O.

User action: None.

DLm339IPath removed: board=n, path=n, link=xx, lpar=xx, cu=xx

Description: The Host has removed the specified channel path to the DLm.

System action: This path is no longer available for channel I/O.

User action: None.


System Messages


DLm340EDevice <devicename> path <pathname> Incorrect CRC in data received

from channel, failed/retrying...

Description: The DLm application has detected a corruption of written data by the Host.

System action: The DLm application will instruct the Host to retransmit the data up to ten times (displaying “retrying...” each of these times). If the error occurs on eleven consecutive writes, the DLm application will return a unit check error to the Host, with sense of Bus-Out Error (displaying “failed” this time).

User action: A data CRC error may indicate failing hardware, cabling, or a weak data link between the Host and the DLm application. Contact your hardware support personnel for assistance.

DLm341EDevice <devicename> CRC mismatch in data block...

Description: DLm has detected a corruption of data when comparing the CRC value stored in the awsheader from a file with a newly calculated CRC value after reading the data.

System action: DLm will return a unit check to the Host, with sense of Bus Out Error.

User action: A data CRC error may indicate failing hardware. Contact EMC Support for assistance.

DLm342EDevice <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 data has occurred. Contact EMC Support for assistance.

DLm350EUnable to get trace flags for interface #n


System Messages


Description: The DLm is attempting to obtain the current trace options from channel interface number #n, but has failed to do so.

System action: The current trace settings are not available to the DLm. As a result, some subsequent function may not complete.


DLm351EUnable to set trace flags for interface #n

Description: The DLm is attempting to set the trace options in channel interface number 'n,' but has failed to do so.

System action: The current trace settings are not changed.


DLm352IFirmware tracing stopped on interface #n

Description: The DLm has turned tracing off for channel interface #n.

System action: Firmware tracing in channel interface #n remains off until turned back on.

User action: None.

DLm353IFirmware tracing restored on interface #n

Description: The DLm has restored the trace options for channel interface #n.

System action: Firmware tracing resumes in channel interface #n.

User action: None.

DLm354EError saving firmware trace

Description: An error has occurred while attempting to save the firmware trace from channel interface #n.

System action: The trace was not saved.



System Messages


DLm355WDevice <devicename> Attempting to save firmware trace on interface

#n

Description: An error or other unusual event has occurred on channel interface #n, and the DLm attempts to save a firmware trace from that interface.

System action: The DLm attempts to stop the firmware trace and save it to disk. After the trace is saved, firmware tracing resumes.


DLm356EInterface #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 DLm automatically saves a firmware trace 'nn' number of times, but this count has been exceeded for this interface.

System action: The DLm continues running without automatically saving the firmware trace.


DLm357EInterface #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 DLm has been configured to not save a trace for this kind of event.

System action: DLm continues running without automatically saving the firmware trace.


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


System action: If ON (the default) a firmware trace is saved when this type of unexpected event occurs. If set OFF, no firmware trace will be automatically saved.

User action: Contact EMC Customer Support for assistance with this option.

DLm366EDevice <devicename> <function> error, Interface #n, error=0xXX

(nnn)

Description: An error involving channel interface adapter #n has occurred.

System action: This channel interface may not be available to this DLm device until the adapter is reset.


DLm370EUnable to open connection to eslot 0xXXXXXX:err=nn (0xXX)

Description: An error has occurred while opening a channel driver during the DLm application startup.

System action: The DLm application startup terminates.


DLm379E<function>: <error message>

Description: An internal error has occurred in the DLm application during shutdown.

System action: The DLm continues its shutdown.


DLm380ESeverity n Alert Interface #n (XXX:YYY) <type:subtype (additional

parms)>

Description: The DLm has received an alert message from the channel adapter driver, for channel adapter 'n'. XXX:YYY are the alert type and subtype, which are also translated in <type:subtype>.

System action: Depending on the alert severity and type, the DLm may continue to function normally, or it may require service or other attention.


System Messages



DLm381IChannel Interface #n <message>

Description: The DLm has received an informational message from channel adapter 'n.'


User action: None.

DLm390E Invalid encryption key file (rc=n)

Description: The encryption key file has been corrupted.

System action: Encryption or decryption will not be available on this controller until the encryption key file is restored or reconfigured.

User action: Restore the encryption key file from a backup copy, or reconfigure the keys via the encryption key configuration program. Contact EMC Support for more assistance.

DLm391IENCRYPTKEY set to [KEYn|NONE] for device <devicename>

Description: Key #n will be used for encryption on device <devicename>, or if 'NONE' is specified, no encryption will be performedon device <devicename>

System action: The specified encryption key (or none, for 'NONE') will be used for all data written to the specified device.

User action: None.

DLm392EEncryption is not available

Description: Encryption is not set up, or the encryption initialization failed.

System action: Encryption and decryption will not be available for any devices for which encryption was requested.

User action: Verify that the encryption key file is installed, or reconfigure the keys via the encryption key configuration program.


System Messages


DLm393ENo encryption key available for reading encrypted block on

<devicename>

Description: Encryption was not set up at all, or the encryption initialization failed, and then an encrypted block was requested to be read.

System action: The requested block will not be read. A unit check is returned to the host.

User action: The user should check the encryption configuration.

DLm394EDevice <devicename>, invalid encrypted block, block <block#>

Description: An encrypted block was read that did not pass the checks for a valid encrypted block.

System action: A unit check is returned to the host.

User action: If this problem recurs, contact EMC Support for assistance.

DLm395EDevice <devicename>, no matching decryption key, block <block#>

Description: No key currently installed on Virtuent was able to decrypt this encrypted block.

System action: If this error occurs during an I/O initiated by the host, an I/O error (equipment check) will be returned to the host. During an Import or Export operation this is a warning rather than an error; the data will be copied it is original encrypted format to a new location.

User action: Check that Virtuent is configured with the proper encryption keys.

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


System Messages


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

DLm399ESyntax error. Format is 'DRIVE-', not 'DRIVE='.

Description: The correct format for specifying this device is 'DRIVE-'.

System action: The command was invalud and not performed.

User action: Specify the command again with valid syntax.

DLm400EDevice <devicename> Data path <pathname> is not accessible

Description: The specified virtual tape library directory cannot be accessed at the time of a tape mount.

System action: The mount is ignored and the drive remains Not Ready without mounting the virtual tape volume. Virtual tape volumes cannot be mounted on this device until the specified directory is made accessible to the application.

User action: If the configured directory name is correct, make sure that it is mounted and accessible. If the directory name was misconfigured, correct the DLm configuration file PATH= parameter and restart the DLm application. (The path can be temporarily corrected with the SET PATH= command.)

DLm401EDevice <devicename> error opening <filename>, error=nnn; <error

message>

Description: The virtual volume file could not be opened.

System action: The mount is ignored and the drive remains not ready without mounting the virtual tape volume.


System Messages


User action: Examine any preceding related messages and the 'error message' portion of this message for a description of the problem and correct the problem. If the problem recurs, contact EMC Customer Support for assistance.

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

DLm403EDevice <devicename> volume <volser> (filename) invalid AWS block

header at nnnnn (n)

Description: An invalid AWS block header was encountered at offset 'nnnnn' in the specified volume. (n) is one of the following error codes: (1) error reading block header; (2) prvblkl not zero in first block header; (3) unknown bit in flags1; (4) unknown bit in flags2; (5) tapemark record with data length; (6) non-tapemark record with zero data length; (7) prvblkl contains zero past first block header; (8) curblkl or prvblkl contains an invalid length value; (10)–(12) unsupported segmented aws block. The second line of the message shows the block header contents.

System action: The operation reading the volume fails.

User action: Delete and recreate the volume that has the invalid format. If this problem recurs, contact EMC Customer Support for assistance.

DLm404EDevice <devicename> Error deleting unused scratch volume <volser>:

error message

Description: The specified volume was created in response to a scratch tape mount request. Because it was unloaded without ever having been written to, the DLm tried to delete it. An I/O error occurred during the attempt to delete.

System action: The volume may or may not been deleted from the tape library.


System Messages


User action: The 'error message' portion of this message describes the error that occurred. Correct the error.

DLm405IDevice <devicename> Display: 'message1' 'message2' [(blink)]

Description: The Host has sent these messages to be displayed on the virtual tape drive's LED operator display unit.

System action: If the message is a Mount message, and the virtual drive is currently unloaded, and the VOLSER falls within the range managed by the DLm, then the specified volume is mounted.

User action: None.

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

DLm407EDevice <devicename> Rejecting ACLON request - invalid ACLVolser

(value)

Description: The mainframe request for ACLON is rejected because the synonym that was passed is not in the synonym list.

System action: The command is rejected. The current ACL state is not changed.

User action: None.

DLm408IDevice <devicename> ACL turned <ON/OFF> [ACLVolser = 'volser']

[reason]

Description: The ACL (autofill) feature has been turned on or off


System Messages


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.

DLm409ICommand received: 'command'

Description: The specified DLm console command was received from an outside application.

System action: The specified command is processed.

User action: None.

DLm410EDevice <devicename> error nnn initializing Volume <volser>: <error

message>

Description: An error occurred while creating the specified virtual tape volume.

System action: The volume is not mounted.

User action: Examine any preceding related messages and the 'error message' portion of this message for a description of the problem and correct the problem. If the problem recurs, contact EMC Customer Support for assistance.

DLm411EDevice <devicename> AWS block #nnn too large (xxxxxx) to handle

(max=yyyyyy)

Description: The DLm has encountered a tape block in the virtual tape volume that is larger than the maximum tape blocksize ('yyyyyy') it is capable of presenting to the Host. This block in the virtual tape file is 'xxxxxx' bytes and is not compressed in the file.

System action: An I/O error is returned to the Host.


DLm412EDevice <devicename> AWS block #nnn too large to handle (max=yyyyyy)


System Messages


Description: The DLm has encountered a tape block in the virtual tape volume that is larger than the maximum tape blocksize ('yyyyyy') it is capable of presenting to the Host. This block in the virtual tape file is compressed and the exact un-compressed block length, while larger than 'yyyyyy,' is unknown.



DLm413EDevice <devicename> Unexpected EOF in block header at nnnnn, file

<filename>

Description: An error occurred while accessing the specified virtual tape volume. 'nnnnn' is the file offset where the error occurred.

System action: The DLm returns an error status to the current Host I/O request.

User action: Examine any preceding related messages, if any, for additional error information, and correct the problem. If the problem recurs, contact EMC Customer Support for assistance.

DLm414WDevice <devicename> tape full writing <data/TM> at PEOT, file

<filename>

Description: The DLm received a write operation from the Host, but the tape is full.

System action: The write operation fails (Unit Check status, Intervention Required sense), and the virtual drive is put into the 'Not Ready' (Intervention Required) state. The DLm leaves the drive in the Not Ready state until the DLm operator changes the drive to Ready. Most Host systems reports the 'Intervention Required' to the Host operator, pause the current job, and wait for the drive to come ready.

User action: Insert another tape in this drive to resume.

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



System Messages



DLm416EDevice <devicename> not responding.

Description: The tape device is no longer responding to the DLm.

System action: The DLm sets the tape device to NA (Not Accessible).

User action: None.

DLm417EDevice <devicename> I/O error: <function description>; error=nnn;

<error message>

Description: An error occurred while reading a virtual tape file.



DLm418WDevice <devicename> Hardware decompression not available, using

software only

Description: A hardware-compressed block has been read from the virtual tape volume, but a hardware compression card is not available on this DLm to decompress the data.

System action: The data is decompressed with software. This message displays only once per volume as a reminder.

User action: For best performance, data compressed with a DLm hardware compression adapter should be decompressed with a compression adapter as well.

DLm419EDevice <devicename> data read [backwards] returned error

Description: An error occurred while reading a virtual tape file.


System Messages


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.


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

DLm421IDevice <devicename> signaled end of volume to Host on <command>

Description: While writing to a virtual tape volume, logical end of volume (CSW status Control Unit End plus Unit Exception) was signaled to the Host because the capacity of the virtual volume is being approached. Command could be Write, Write Tapemark, or Erase Gap.

System action: The Write command was successful. The logical end of volume condition remains true and signaled for all subsequent writes as long as the virtual tape volume remains positioned past the logical end of volume point.

User action: The Host is expected to close the virtual tape volume and open a new volume.

DLm422WDevice <devicename> <command> at loadpoint

Description: The Host has read or spaced backwards from the virtual tape volume's loadpoint.

System action: The DLm returns an error status (Read Backwards at Loadpoint) to the Host I/O request.


System Messages


User action: This is most likely a Host application error. Correct the application causing the error.

DLm423WDevice <devicename> <command> past <place>

Description: The Host read or positioned past the end of data on the tape volume or physical end of tape on the physical tape volume.

System action: The DLm returns an error status (Data Check, Tape Void) to the Host I/O request.

User action: This is most likely a Host application error. Correct the application causing the error.

DLm424IDevice <devicename> Volume <volser> rewound

Description: The operator REWIND command completed successfully.

System action: The virtual tape volume is now at loadpoint.

User action: None.

DLm425EDevice <devicename> Data block exceeds maximum of yyyyyy bytes

Description: The Host wrote a block larger than the maximum blocksize supported by the DLm.

System action: The block is not written to the virtual tape file, and an I/O error is returned to the Host's write command.

User action: Change the Host application or JCL to write data blocks within the DLm capability ('yyyyyy' bytes or less).

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


System Messages


User action: Clear the options that require expanded headers. Contact EMC Customer Support for assistance.

DLm427WDevice <devicename> write [TM] attempt past end of tape

Description: The Host attempted to write data or a tapemark past the absolute end of tape capacity.

System action: Application returns an error status (Equipment Check, Physical End of Tape) to the Host I/O request.

User action: This is most likely a Host application error, since logical end of tape signal would have been returned for many writes preceding the failing one. Correct the application causing the error.

DLm428IDevice <devicename> possibly lengthy operation (<command> from

<blockid>) begun

Description: The DLm is executing the specified I/O command from the Host. The DLm has determined that this command may take a considerable period of time (more than a few seconds) 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 MAS431I). 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.

DLm429WDevice <devicename> <function description> while device not ready

Description: The operation requested requires a tape to be loaded in the tape drive.


User action: Load the tape drive.


System Messages


DLm430IDevice <devicename> volume <volser> accommodated old-style AWS

header at offset nnnnnn

Description: Earlier DLm releases could write incorrect metadata in a virtual tape block under certain specific rare conditions. Subsequent backwards traversal over such a block would result in an I/O error (Invalid block header). Later DLm releases, including this one, automatically recover from this metadata error without returning an I/O error to the host. This message is displayed strictly for informational purposes.

System action: The virtual tape operation completes successfully. There is no data loss or error indication returned to the host. The invalid metadata in this virtual tape volume is NOT corrected by this action, so this message may be seen in the future as long as this data exists on this volume.

User action: None.

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

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

DLm433IDevice <devicename> is not writing expanded headers.


System Messages


Description: The device is set to write expanded headers, but is currently not honoring the value.


User action: None.

DLm434WWARNING: Path <pathname> disk usage at nn%

Description: The disk usage for the specified tape library has exceeded the current WARNING value.

System action: The DLm continues to warn at every percentage change as long as the usage exceeds the WARNING value.

User action: Consider scratching and erasing unneeded virtual tape volumes to free some disk space.

DLm435I<this is an informational message>

Description: This message is an informational message


User action: None.

DLm436IAttempting to recover space from scratch volumes in <pathname>

Description: The disk usage for the specified tape library directory has exceeded the current RECOVER value.

System action: The DLm erases the data from previously scratched virtual tape volumes until the disk usage falls to (RECOVER minus RECOVERAMT) percent.

User action: Consider scratching and erasing unneeded virtual tape volumes to free some disk space.

DLm437IFinished space recovery, nn bytes recovered from scratch volumes in

<pathname>


System Messages


Description: The DLm has finished attempting to recover space for the specified tape library directory because either (1) the disk space has been reduced by RECOVERAMT, or (2) it has found no more previously scratched volumes to erase. ‘nn’ bytes is the number of bytes erased from scratch volumes and made available for reuse.


User action: None.

DLm438I Finished space recovery, nn bytes recovered from nn scratch volumes

in <pathname>

Description: The DLm application has recovered the specified amount of space from scratch tapes that have surpassed the erase policy retention time.


User action: None.

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

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


System Messages


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

DLm442EDevice <devicename> unable to allocate an SL/AL/NL scratch volume:

<error message>

Description: Loading of a scratch volume was requested, but a scratch volume with the requested label type could not be found. The 'error message' portion of this message explains the reason.

System action: The requested volume is not loaded and the drive remains Not Ready.

User action: Correct the problem preventing the scratch volume allocation and try to reload a scratch tape. If no scratch volumes are available, consider scratching some old, unneeded volumes or INITIALIZE some more scratch volumes.

DLm443EDevice <devicename> unable to create new scratch volume <volser>

Description: Loading of a new scratch volume was requested, but the new virtual tape volume could not be created.

System action: The requested volume is not loaded and the driver remains Not Ready.

User action: One or more previous messages should explain the reason for the problem. Correct the problem preventing the scratch volume allocation, and try to reload a scratch tape. For instance, type the Query Space command to determine if any free space exists on the tape library disk; if no space is available, delete some unneeded volumes to free some disk space. Make sure that a valid, writable directory is specified in the configuration file for this device, and that the directory is currently mounted and accessible. If all possible scratch tapes are already in use, scratch some existing volumes for reuse.

DLm444IDevice <devicename> new scratch volume <volser> created


System Messages


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.

DLm445IDevice <devicename> cannot initialize protected new volume <volser>

Description: The DLm has created the new volume 'volser', but is not able to initialize it because it is read-only. This is only possible when a manual LOAD command with the PROTECTED option is typed for a new (non-existing) volume.

System action: The volume is created and mounted, but it appears to the Host as an empty, un-initialized (and read-only) tape.

User action: Do not do this.

DLm446EDevice <devicename> cannot create volume <volser>, path <pathname>

is read-only

Description: The specified volume does not exist and cannot be opened for writing because the virtual tape library directory 'pathname' is write protected.

System action: The volume is not created, the mount request is ignored, and the device remains not ready.

User action: To write new volumes, make sure that the virtual tape library is correctly mounted and is write-enabled for user 'vtape.'

DLm447WDevice <devicename> invalid volid 'volser', mount request ignored

Description: The Host requested the mounting of a VOLSER that is not a valid IBM VOLSER.

System action: The mount request is ignored and the device remains not ready.

User action: Correct the Host JCL to request a valid IBM VOLSER. An IBM standard VOLSER consists of the uppercase letters A–Z, numbers 0–9, and the hyphen.


System Messages


DLm448WDevice <devicename> volume <volser> already mounted, new mount

request ignored

Description: The Host requested the mounting of a volume, but the specified drive already has a virtual tape volume mounted. The currently mounted tape is not at loadpoint.

System action: The mount request is ignored. The volume already mounted on the drive remains mounted.

User action: Correct the Host JCL that caused a mount request to be sent to a drive that already has a volume mounted. If the Host is finished with the volume that is currently mounted on the drive, you can manually unload that volume and then manually mount the new volume.

DLm449IDevice <devicename> Label request changed from ' ' to default 'X'

Description: The current mount request did not specify a desired label type, so it was set to the default type configured on the DLm for this virtual tape device. The only value which you see for 'X' is 'A' for ANSI labels, because this message does not appear if the default label type is 'S' for IBM standard labels.

System action: The mount process continues, using the default label type configured for this device.

User action: None, unless the default label type is incorrect, in which case the DLm configuration default should be changed or an explicit label type should be requested in the JCL.

DLm450WVolume <volser> file is busy on device devicename1, mount on

devicename2 is ignored

Description: The mounting of a virtual tape volume has been requested, but that volume is currently mounted on another virtual tape drive. A volume can be mounted on only one drive at a time.

System action: The mount request is ignored.

User action: Correct the Host operational issue that resulted in the duplicate request for the same volume. Restart the second job when the virtual tape volume becomes available.


System Messages


DLm451EVolume <volser> file is open elsewhere, mount on <devicename>

ignored

Description: Mounting of the specified virtual tape volume has been requested, but the volume is currently open by another program.

System action: The mount retries several times over several seconds. If the volume does not become free, the mount request is ignored.

User action: Correct the Host operational issue that resulted in the duplicate request for the same volume by two programs at the same time. Restart the second job when the virtual tape volume becomes available.

DLm452WDevice <devicename> is quiesced, mount ignored

Description: Mounting of the specified virtual tape volume has been requested, but the specified drive is in the 'quiesced' state, meaning it does not accept any tape mounts until it is 'unquiesced' (or until the DLm is restarted).


User action: UNQUIESCE the drive, or use a different drive.


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

DLm454EDevice <devicename> volume <volser> not found

Description: The DLm was requested to load a virtual tape volume that does not exist in the DLm tape library.


System Messages


System action: The drive remains unloaded and Not Ready.

User action: Verify that the correct volume is being requested. Also check that the tape library directories are properly mounted and are accessible to the DLm. If the requested volser is for a scratch tape, make sure that there are scratch volumes, initialized with the correct label type, available.

DLm455EError 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 of this message for a description of the problem and correct the problem. If the problem recurs, contact EMC Customer Support for assistance.


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 Customer Support for additional assistance.

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


System action: The mount request is ignored. The volume already mounted on the drive remains mounted.

User action: Consider correcting the Host JCL or Host operating system that allowed a mount request to be sent to a drive that already had a volume mounted. Contact EMC Customer Support for additional assistance.


request deferred

Description: The Fujitsu Host requested the mounting of a volume, and the specified drive already has a virtual tape volume mounted.

System action: The mount request will be honored after the Host unloads the volume currently mounted on the drive.

User action: If possible, correct the Host JCL that caused a mount request to be sent to a drive that already has a volume mounted.

DLm459WDevice <devicename> volume <volser> has a corrupted IBM/ANSI label

set

Description: During opening of an existing virtual tape volume, the DLm has determined that the volume contains a valid VOL1 label, but the rest of the header label set is missing, incomplete, invalid, or corrupted in some way.

System action: This is a warning message only. The mount completes successfully and is available for normal use by the Host.

User action: The Host most likely complains about the invalid labels; take the appropriate action required by the Host. If the Host refuses to use the corrupted volume as is, perform a reinitialization of the virtual tape volume using the standard Host initialization procedures. Try to determine the reason the Host previously wrote invalid labels to this tape volume. This condition is most often caused by an error on the Host during volume initialization or at some other time when the Host is writing the volume labels. In particular, this problem has been seen when a Host job is cancelled while it is opening an output tape.

DLm460IDevice <devicename> volume <volser> file renamed to <filename>


System Messages


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.

DLm461IDevice <devicename> performing deferred mount request

Description: The Fujitsu Host requested the mounting of a volume while the specified drive already had a virtual tape volume mounted. The drive is now unloaded and the mount request will be reevaluated.

System action: The mount request will be attempted at this time.

User action: If possible, correct the Host JCL that caused a mount request to be sent to a drive that already had a volume mounted.

DLm462WMount error renaming volume <volser> (filename to filename): <error

message>; retrying...

Description: The host has asked for a previously scratched volume by specific volser. DLm was unable to rename the scratch volume (~VOLSER) to an active volume (VOLSER).

System action: The rename will be retried several times over several seconds. If the rename does not succeed during this time the mount request will be ignored.

User action: Refer to any earlier messages and the 'error message' portion of this message to determine the cause of the failure.

DLm463WVolume <volser> file is open elsewhere, retrying...

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 will be ignored.

User action: Correct the Host operational issue that resulted in the duplicate request for the same volume by two programs at the same time. Restart the second job when the virtual tape volume becomes available.


System Messages


DLm464EDevice <devicename> volser \volser\ prefix differs from existing

volser “volser”

Description: The Host is attempting to write a VOL1 label with a different VOLSER onto the virtual tape volume, but the new volser does not start with the same two character volser prefix as the existing VOLSER.

System action: The DLm rejects the Host's write, returning a Unit Check status and Command Reject sense.

User action: You can only write over an existing volser with a new VOLSER of the same two character prefix. Correct the JCL or operator procedure that attempted to rename the volume.

DLm465EDevice <devicename> invalid volser 'volser' in VOL1 label

Description: The Host is attempting to write a new VOL1 label to the virtual tape volume, but the VOLSER in the VOL1 label is invalid.


User action: Correct the Host job that is attempting to write the invalid VOLSER to the DLm.

DLm466EDevice <devicename> volser 'volser' from VOL1 already exists [as

scratch]

Description: The Host is attempting to write a VOL1 label with a different VOLSER onto the virtual tape volume, but the new volser is the same as a volume that already exists in the DLm tape library.


User action: Correct the Host job that is attempting to write the duplicate VOLSER to the DLm, or delete the existing volume on the DLm before rerunning the job.

DLm467EDevice <devicename> error renaming volume <volser1> (filename) to

<volser2> (filename); <error message>


System Messages


Description: The Host is attempting to write a VOL1 label with a different VOLSER onto the virtual tape volume, but the DLm is failing in its attempt to rename the mounted volume to the new volume name.


User action: See any earlier messages and the 'error message' portion of this message to determine the cause of the failure. If the problem cannot be corrected, contact EMC Customer Support for assistance.

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

DLm469IDevice <devicename> volume <volser1> renamed to <volser2>

(filename)

Description: The Host has written a VOL1 label with a different VOLSER onto the virtual tape volume.

System action: The virtual volume file was successfully renamed to the new VOLSER.

User action: None.

DLm470EMOUNT volume 'volser' failed

Description: Mounting of the specified virtual tape volume was unsuccessful.

System action: The mount request is ignored and the drive remains Not Ready.

User action: This message are preceded by one or more messages that explain the reason for the mount failure. Correct the error indicated in the preceding messages.


System Messages


DLm471EDevice address xxxx on GROUP n doesn't exist

Description: Mounting of a virtual tape volume on OSADDR 'xxxx' was requested by the EMC mount program, but the specified device does not exist in the specified GROUP.

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 EMC mount program and DLm to use the proper device addresses.

DLm472IVolume <volser1> is currently on <devicename>, cannot mount

<volser2>

Description: Mounting of volume 'volser2' on the specified drive was requested by the EMC mount program, but the specified device already has the virtual tape volume 'volser1' mounted.


User action: Correct the operational issues that resulted in the attempt to mount on a busy drive.

DLm473EInvalid mount request x'xx' 'aaaaaaaa' 'bbbbbbbb'

Description: Mounting of a virtual tape volume was requested by the EMC mount program, but the second word of the request ('bbbbbbbb') did not contain a proper drive designation.



DLm474ENo free device in default GROUP n to mount 'volser'

Description: Mounting of a virtual tape volume on any available drive address was requested by the EMC mount program, but there is no free drive in this GROUP.


System Messages



User action: Retry the Host mount when a virtual drive becomes available.

DLm475ENo free device in GROUP n to mount 'volser'

Description: Mounting of a virtual tape volume on ANY available drive address was requested by the EMC mount program, but there is no free drive on this LPAR and GROUP.


User action: Retry the Host mount when a virtual drive becomes available.

DLm476WWARNING: Device <devicename> OSADDR is 000

Description: Mounting of a virtual tape volume was requested by the EMC mount program, but the device upon which the volume is being mounted has an OSADDR of 000.

System action: The mount proceeds, but the mount device address of 000 is reported back to the Host program. If the mount request was for a specific device address, this probably would not be of any consequence, but if the request was for 'Any' drive, the Host program is not able to determine on which drive the volume was mounted.

User action: Reconfigure the DLm and add the correct OSADDR parameter for each DLm device that is attached to a VSE system.

DLm477EMount requested on <devicename1> by <devicename2> failed

Description: Mounting of a virtual tape volume on any available drive address was requested by the EMC mount program, but the volume could not be mounted on <devicename2>. This message is preceded by one or more messages that explain the reason for the mount failure.



System Messages


User action: See any preceding messages for the reason for the mount failure and correct the problems.

DLm478IDevice <devicename> Requesting mount 'volser' on 'device'

Description: Mounting of a virtual tape volume was requested by the mount program or a tape manager on the host.

System action: The DLm attempts to mount the requested volume on the requested drive.

User action: None.

DLm479WDevice <devicename> volume <volser> is completely empty!

Description: The specified tape volume was successfully mounted, but contains no data or tape marks.

System action: The specified volume is mounted as requested, but any attempts to read from the volume results in an I/O error (Unit Check status, Tape Void sense) being presented to the Host.

User action: Be certain that the correct volume is being requested. If necessary, delete and reinitialize the virtual tape volume.

DLm480EBoth active and scratch volser volumes exist in <pathname>, mount

ignored

Description: While mounting a volume, the DLm found both active (VOLSER) and scratch (~VOLSER) copies of the volume in the same tape library.

System action: The mount request is ignored, and the drive remains not ready.

User action: Determine which, if any, of the volumes is valid and should be kept, and delete the invalid volume.

DLm481EMount error renaming volume <volser> (filename to filename): <error

message>


System Messages


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

User action: See any earlier messages and the 'error message' portion of this message to determine the cause of the failure. Contact EMC Support for assistance.

DLm482IScratch tape <volser> made active

Description: The Host has asked for a previously scratched volume by specific volser.

System action: The DLm returns the requested volume to active status by renaming it from ~VOLSER to VOLSER, then mounts the volume.

User action: None.

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

User action: See any earlier messages and the 'error message' portion of this message to determine the cause of the failure.

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


System Messages


DLm485WDevice <devicename> Mount of unlabeled [SCRTCH/PRIVAT] volume

ignored

Description: The Host requested the mounting of an unlabeled scratch tape. The DLm does not support the mounting of unlabeled scratch tapes because there is no way to track the volume by volser after the Host writes unlabeled data.

System action: The mount request is ignored and the device remains Not Ready.

User action: Specify a specific VOLSER for unlabeled usage, or specify a labeled tape for scratch usage.

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

DLm487IDevice <devicename> volume 'filename' mount will be retried

Description: The specified virtual tape file mount request automatically retries.

System action: The load request is retried.

User action: None.

DLm488IDevice <devicename> Unused scratch volume <volser> deleted

Description: The specified volume was created in response to a scratch tape mount request, but it was unloaded without ever being written to.

System action: The volume is deleted from the DLm disk.

User action: None.


System Messages


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

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

DLm491IDevice <devicename> on SMB filesystem, max volume size changed to

2G

Description: The DLm has detected that the tape library for the specified virtual tape drive is on a CIFS/SMB filesystem and the current maximum volume setting for this drive was greater than 2 GB.

System action: The maximum volume size for this drive is adjusted to 2 GB. If the tape library path is ever changed back to a non-SMB filesystem, the maximum volume size automatically changes back to the previous value.

User action: None.

DLm492IDevice <devicename> not on SMB filesystem, max volume size changed

back to size

Description: The DLm has detected that the tape library for the specified virtual tape drive is no longer on a CIFS/SMB filesystem, and the maximum volume setting for this drive was previously adjusted to 2 GB.

System action: The maximum volume size for this device is adjusted back to the previous value.


System Messages


User action: None.

DLm493WDevice <devicename> write [TM] attempt to protected volume

Description: The Host attempted to write data or a tapemark to this read-only tape volume.

System action: The DLm returns an error (Command Reject, File Protected) to the Host application.

User action: Correct the JCL, program or operational procedure that caused the Host to try to write to a protected volume, or mount the volume in read-write mode.

DLm494WDevice <devicename> disk full writing data/TM at nnnnnnn, file

<filename>

Description: The DLm received a write operation from the Host, but the tape library disk is full. 'nnnnnnn' is the number of bytes written 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 DLm leaves the drive in the Not Ready state until the DLm operator changes the drive to Ready. Most Host systems reports the 'Intervention Required' to the Host operator, pause the current job, and wait for the drive to come ready.

User action: When space is available on the tape library disk, execute the READY command to this drive to resume.

DLm495EDevice <devicename> disk full writing data/TM at nnnnnnn, file

<filename>

Description: The DLm received a write operation from the Host, but the tape library disk is full. The DLm cannot recover and continues because the tape library is on an NFS filesystem. 'nnnnnnn' is the number of bytes written so far.

System action: The write operation fails (Unit Check status, Equipment Check sense). The contents of the volume being written is unpredictable.

User action: Rerun the job after more space is made available on the target tape library filesystem.


System Messages


DLm496WDevice <devicename> write compression suppressed by IDRC=NO /

forced by IDRC=FORCE>

Description: Either the Host requested compression of the output data but the DLm virtual tape drive is currently set to IDRC=NO, or the Host did not request compression but the drive is currently set to IDRC=FORCE. This message is only displayed once per volume.

System action: If IDRC=NO is set, the data is written uncompressed to the DLm tape library. If IDRC=FORCE is set, the data is compressed.

User action: None, unless you truly wanted the data to be compressed or not compressed in a different way. In that case, reconfigure the DLm virtual tape drive with the correct IDRC parameter, or type the DLm console command SET IDRC=ON/OFF/FORCE [DEV=devicename] to temporarily override the DLm configuration.

DLm497WDevice <devicename> Hardware [de]compression configured off, using

software only

Description: The DLm has hardware compression/decompression capability but is currently configured to not use the hardware facility for compression/decompression. This message displays once per volume whenever this condition is true.

System action: The data is compressed or decompressed with software rather than with the compression hardware.

User action: None, unless you truly wanted the data to be compressed or decompressed with the compression hardware (which is much faster than software compression/decompression). In that case, type the DLm command SET HWCOMPRESSION=ON or SET HWDECOMPRESSION=ON to reactivate the hardware compression/decompression feature.

DLm498EDevice <devicename> Volume <volser> error uncompressing data block

#nnnnn: nn (error message)

Description: An error occurred while reading compressed data from the tape file.

System action: The DLm returns an error (Data Check) to the Host.


System Messages


User action: If possible, recreate the corrupted volume. If this problem recurs, contact EMC Customer Support for assistance.

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


DLm500IScratchsing/Unscratching/Erasing of volume <volser> requested by

host via device <devicename> [dsn='datasetname']

Description: Scratching, unscratching, or erasing of the specified virtual tape volume was requested by the Host. If the request is further qualified by a data set name, it is shown in the message.

System action: The DLm attempts to scratch, unscratch, or erase (delete the data of a scratch volume) the specified volume on the DLm tape library disk. If a data set name is specified, the volume is first checked to confirm that it contains the specified dataset.

User action: None.

DLm501IVolume <volser> (filename) scratched/unscratched/erased/deleted

Description: Scratching, unscratching, erasing, or deletion of the specified virtual tape volume as requested by the Host was successful.

System action: The specified virtual tape volume was scratched, unscratched, erased (data deleted), or deleted (file deleted) from the DLm tape library disk as requested. A return code of 0 (success) was returned to the Host application.

User action: None.

DLm502WVolume <volser> is currently on <devicename>, cannot

scratch/unscratch/erase


System Messages


Description: Scratching, unscratching, or erasing of the specified virtual tape volume was requested by the Host, but the specified volume is in use.

System action: The virtual tape volume status is not changed. A return code of 0x06 is returned to the Host application.

User action: Change the tape status later when it is not in use.

DLm503EError scratching/unscratching/erasing volume <volser> (filename);

<error message>

Description: An error occurred during the scratching, unscratching, or erasing of the specified virtual tape volume requested by the Host.

System action: The volume is in an undefined state. It may have been scratched or it may still be active, depending on the error that occurred. A return code of 0x07 (volume does not exist) or 0x08 (any other error) is returned to the Host application.

User action: Consult any preceding related messages and the 'error message' portion of this message for a description of the problem and correct the problem. If the problem recurs, contact EMC Customer Support for assistance.

DLm504EScratching/unscratching/erasing of invalid volume 'volser'

requested by host via device <devicename>

Description: Scratching, unscratching, or erasing of the specified virtual tape volume was requested by the Host, but the requested volser is an invalid VOLSER.

System action: The scratch, unscratch, or erase request is ignored. A return code of 0x05 is returned to the Host application.

User action: Correct the VOLSER being sent by the Host program.

DLm505EDevice <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 DLm console command, was requested by the Host, but the data sent by the Host was of an incorrect length.


System Messages


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.

DLm506EBoth active and scratch <volser> volumes exist in <pathname>!

Description: Scratching or unscratching of the specified virtual tape volume was requested by the Host, but the DLm found that the files VOLSER (not scratch) and ~VOLSER (scratch) both exist in the same tape library.

System action: The scratch or unscratch request is ignored. A return code of 0x03 is returned to the Host application.


DLm507EScratch/Unscratch Error renaming volume <volser> (filename); <error

message>

Description: Scratching or unscratching of the specified virtual tape volume was requested by the Host, but the DLm encountered a problem while renaming the volume to the specified filename.

System action: The scratch or unscratch request is ignored. A return code of 0x08 is returned to the Host program.

User action: See the error message portion of this message to determine the reason for the error.

DLm508IVolume <VOLSER> (filename) erased

Description: The specified virtual tape volume was erased because the length of time since it was scratched has surpassed the erase policy retention time.

System Action: The specified virtual tape volume was erased (its data deleted) and its storage space returned to free space for reuse.

User Action: None.

DLm510WDevice <devicename> data path <pathname> is not accessible


System Messages


Description: Scratching, unscratching, or erasing of a virtual tape volume was requested by the Host, but the specified tape library directory is not currently accessible.

System action: The scratch, unscratch, or erase request is ignored. A return code of 0x0A is returned to the Host program.

User action: Make sure that the device through which scratch/unscratch/ erase requests are sent by the Host application is assigned to the correct tape library directory, and that the directory is read-write accessible by the user 'vtape'.

DLm511WDevice <devicename> data path <pathname> is not writable

Description: Scratching, unscratching, or erasing of a virtual tape volume was requested by the Host, but the specified tape library directory is not currently writable.

System action: The scratch, unscratch, or erase request is ignored. A return code of 0x0B is returned to the Host program.

User action: Make sure that the device through which scratch/unscratch/ erase requests are sent by the Host application is assigned to the correct tape library directory, and that the directory is read-write accessible by the user 'vtape.'

DLm512EDevice <devicename> Scratching/Erasing/Unscratching/Deleting not

allowed on <drive>

Description: Scratching, unscratching, or erasing of a virtual tape volume was requested by the Host, but the DLm virtual device is currently assigned to a physical tape drive.

System action: The scratch, unscratch, erase, or delete request is ignored. A return code of 0x0A is returned to the Host program.

User action: Make sure that the device through 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.

DLm515WVolume <volser> file is open elsewhere, cannot

scratch/unscratch/erase


System Messages


Description: While considering the specified virtual tape volume for scratching, unscratching, erasing, it was found that the specified volume was currently being accessed on another program.

System action: The scratch/unscratch/erase request is ignored. If the action was requested by the Host, a return code of 0x09 is returned to the Host application.

User action: Scratch/unscratch/erase the volume later when it is not in use.

DLm516EError locking volume <volser> (filename); <error message>

Description: While considering the specified virtual tape volume for scratching, unscratching, erasing, an I/O error occurred while trying to lock the file for exclusive access.

System action: The scratch/unscratch/erase request is ignored. If the action was requested by the Host, a return code of 0x08 is returned to the Host program.

User action: Make sure that the specified volume exists, is owned by the user 'vtape,' is writable, and is not in use by any other program. Scratch/unscratch/erase the volume later when it is not in use. If the problem recurs, contact EMC Customer Support for assistance.

DLm517EInvalid VOL1 label in volume <volser> (filename)

Description: While considering the specified virtual tape volume for scratching, unscratching, erasing, it was found that the specified volume does not contain a valid VOL1 label.

System action: The scratch/unscratch/erase request is ignored. If the action was requested by the Host, a return code of 0x0C is returned to the Host program.

User action: Specify a valid standard labeled tape in the request. If the volume has somehow been overwritten with incorrect contents, delete and reinitialize the volume.

DLm518EMismatched volser <volser1> found in <volser2> (<filename>)

Description: While considering the specified virtual tape volume for scratching, unscratching, erasing, it was found that the VOLSER (volser1) found in the VOL1 label on the volume does not match the one expected (volser2).


System Messages


System action: The scratch/unscratch/erase request is ignored. If the action was requested by the Host, a return code of 0x0D is returned to the Host program.

User action: If the volume has somehow been overwritten with incorrect contents, delete the volume manually and reinitialize the volume.

DLm520EInvalid HDR1 label in volume <volser> (<filename>)

Description: While considering the specified virtual tape volume for scratching, unscratching, erasing, it was found that the volume does not contain a valid HDR1 label.

System action: The scratch/unscratch/erase request is ignored. If the action was requested by the Host, a return code of 0x0E is returned to the Host program.

User action: If the volume has somehow been overwritten with incorrect contents, delete and reinitialize the virtual tape volume.

DLm521EVolume <volser> (filename) has data set 'dataset1', not 'dataset2'

Description: While considering the specified virtual tape volume for scratching, unscratching, erasing, it was found that the volume contains the data set 'dataset1,' not the data set specified by the Host request ('dataset2').

System action: The scratch/unscratch/erase request is ignored. A return code of 0x0F is returned to the Host program.

User action: Correct the data being sent by the Host application.

DLm522EInvalid 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 action: The scratch/unscratch/erase request is ignored. A return code of 0x10 is returned to the Host program.



System Messages


DLm523EVolume <volser> (filename) created too recently (nnnnnn) to scratch

today (nnnnnn)

Description: Scratching of a virtual tape volume was requested by the Host, but the date found in the virtual tape volume's HDR1 label shows that the file was created on the same date that (or later than) the scratch request is being made. A volume can only be scratched one or more days later than the day on which it was created.

System action: The scratch request is ignored. A return code of 0x11 is returned to the Host program.

User action: Resubmit the scratch request to the DLm at least one day after the file on the volume was created.

DLm524WVolume <volser> (filename) already scratched/unscratched/erased

Description: Scratching, unscratching, or erasing of a virtual tape volume was 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 is returned to the Host program.

User action: Be careful not to submit duplicate scratch/unscratch/erase requests to the DLm.

DLm525EVolume <volser> (filename) not a scratched/erased tape

Description: Erasing or deleting a scratch volume was requested by the Host, but the specified virtual tape volume is not in the scratched (for erase) or erased (for delete) state.

System action: The erase or delete request is ignored. A return code of 0x04 is returned to the Host program.

User action: Be careful to submit erase requests for previously scratched volumes only, or delete requests for previously erased volumes only.

DLm526EVolume <volser> (filename) cannot un-scratch, already erased


System Messages


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.

DLm532EDirectory at <pathname> is not a DLM filesystem

Description: An OCFS/2 support license is installed, but the Distributed Lock Manager directory doesn't exist.

System action: OCFS/2 support is disabled until the problem is corrected and the DLm is restarted.


DLm534EOCFS/2 DLM initialize failed, error: error message

Description: OCFS/2 Distributed Lock Manager initialization failed.

System action: OCFS/2 support is disabled until the problem is corrected and the controller is restarted.


DLm535EError opening DLM log file 'filename', error:error message

Description: An error occurred while attempting to open the Distributed Lock Manager log file.

System action: OCFS/2 support is disabled until the problem is corrected and the controller is restarted.

User action: If the error messages describes a correctable problem, correct the problem and restart the controller. Contact EMC Customer Support if more assistance is needed.


System Messages


DLm539EDevice <devicename> volser <volser> write verification error: error

message

Description: An error occurred while verifying the data just written to disk.

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.

DLm540WUnexpected 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 application. Contact EMC Support if more assistance is needed.

DLm541IDevice <devicename> Volser <volser> GR device writing to

replicating filesystem

Description: Indicates that the device is configured to use Guaranteed Replication and the volume is written on a Guaranteed Replication-enabled filesystem.

System action: When the tape is closed, a replication-refresh will be performed on the filesystem.

User action: None.

DLm542IDevice <devicename> Volser <volser> preparing GR replication (nn

second delay)


System Messages


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.

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

DLm544IDevice <devicename> Volser <volser> GR replication-refresh complete

Description: Indicates that the GR replication refresh has completed successfully.

System action: The tape volume will be unloaded, with normal unload status returned to the host's unload command.

User action: None.

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


System Messages


DLm546IDevice <devicename> Volser <volser> retrying replication through

'csname'

Description: Indicates that the refresh is being retried on the specified Control Station after GR replication refresh failed once due to a communication error.

System action: Retries GR replication refresh.

User action: Check the Celerra configuration to make sure that the Celerra Control Station is properly configured.

DLm547WDevice <devicename> Volser <volser> ssh error with control station

'csname'

Description: Indicates that GR replication refresh has failed due 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 Station is properly configured.

DLm548EDevice <devicename> Volser <volser> Guaranteed Replication error:

error message

Description: A GR replication refresh has encountered an error.

System action: Unloads the tape volume, with an error status returned to the host's unload command. The file is intact, but replication is not guaranteed.

User action: Check the error message for a description of the problem, correct the problem, check the replication status, or force a manual replication of the filesystem. If necessary, contact EMC Support for more assistance.

DLm549EDevice <devicename> Guaranteed Replication cannot locate info for

'pathname'


System Messages


Description: Attempts to refresh GR replication, but cannot obtain detailed replication information about the filesystem.

System action: The GR replication refresh is not performed. An error status is returned to the host's unload command. The file is intact, 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.

DLm550ICommand received from Host: device <devicename>: cmd = 'command'

Description: The specified DLm console command was sent from the Host through the specified virtual tape device.

System action: The command is executed. Depending on the results of the command, a return code returns to the Host program.

User action: If the command is successful, none. Otherwise, determine the reason for the DLm console command failure and correct the problem.

DLm551EHost-initiated commands not allowed

Description: A DLm console command was sent from the Host, but the DLm is not configured to allow Host-initiated commands.

System action: The command not be executed. A failure code be returned to the Host program.

User action: If you want the Host to be able to initiate DLm console commands, correct the DLm configuration to allow for this feature.

DLm552EUnable to locate script <scriptname>: <error msg>

Description: A DLm RUN console command was sent from the Host, but the DLm is not able to locate the specified script.

System action: The command is not executed. A failure code returns to the Host.

User action: Check that the correct script name was specified in the RUN command, and that the script file has the proper permissions to be executed by the DLm user 'vtape.'


System Messages


DLm553EUnable to execute script <scriptname>

Description: A DLm RUN console command was sent from the Host, but the DLm is not able to execute the specified script.


User action: Check that the correct script name was specified in the RUN command, and that the script file has the proper permissions to be executed by the DLm user 'vtape.'

DLm555ERUN command not allowed

Description: A DLm RUN console command was sent from the Host, but the DLm is not configured to allow the RUN command.


User action: If you want the Host to be able to initiate DLm RUN commands, correct the DLm configuration to allow for this feature.

DLm556WRUN process #nnnnn has not finished in nn seconds

Description: A DLm RUN console command was sent from the Host and executed by the DLm, but the specified script did not complete within the specified time limit.

System action: The DLm cancels the process identified by process ID #nnnnn. A failure code returns to the Host.

User action: If the specified script normally takes longer than the time specified, specify a longer time on the RUN command.

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


System Messages


User action: If the preceding error message(s) describe a correctable problem, correct the problem and retry mounting the tape volume. Contact EMC Support if more assistance is needed.

DLm561EDevice <devicename> Missing or invalid AWSMAP in <filename>

Description: An error has occurred while opening a previously extended virtual tape volume on a WORM filesystem. The format of the specified file is invalid.



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


DLm563EDevice <devicename> Info in file <filename> doesn't match previous

segment

Description: An error has occurred while opening a previously extended virtual tape 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.



DLm564EDevice <devicename> Invalid segment number in segment <n>


System Messages


Description: An error has occurred while opening a previously extended virtual tape 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>.



DLm565EDevice <devicename> Illegal volume mod attempt, volume <volser>,

offset <nnnnnn>, block <nnn>

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.

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

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


System Messages



User action: None.

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

User action: None.

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


User action: If the preceding error message(s) describe a correctable problem, correct the problem and retry the failing job. Contact EMC Support if more assistance is needed.

DLm570WHDR1 has invalid expiration date `xxxxxx'

Description: During opening of an existing virtual tape volume, or when the Host wrote a new HDR1 label, DLm determined that the expiration date in the HDR1 label (xxxxxx) was invalid.

System action: Processing continues. DLm 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 DLm is if the file is being written to a WORM filesystem. In this case, if DLm 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.


System Messages


DLm571WDevice <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, DLm determined that the expiration date in the HDR1 label (yyyy/ddd) was outside of the range that can be converted to a retention period by DLm. DLm can process HDR1 expiration dates in the range Jan. 1, 2003, through Jan. 18, 2038.

System action: Processing continues. If the HDR1 date was prior to Jan. 1, 2003, DLm regards the volume's expiration date to be Jan. 1, 2003. If the HDR1 date was after Jan. 18, 2038, DLm regards the volume's expiration date to be Jan 18, 2038. The only time a volume's expiration date is of any consequence to DLm 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.


DLm572EUnable 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, DLm was unable to convert the HDR1 expiration date (xxxxxx) to a retention period, for an unknown reason.

System action: Processing continues. DLm 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 DLm is if the file is being written to a WORM filesystem. If DLm 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.


DLm573EError while validating directory <directory>: <error message>

Description: During the directory validation process a problem was discovered.

System action: The specified directory cannot be used for the intended purpose.

User action: Verify the existence and properties of the directory. Contact EMC Customer Support for assistance.


System Messages


DLm580EError getting <volser> file status; <error message>

Description: While closing a virtual tape file, an error occurred in reading the file's current status information.

System action: Processing continues. There may be problems in accessing this file later.

User action: The error message portion of this message identifies the reason for the error. Correct the reason if possible. If the problem recurs, contact EMC Customer Support for assistance.

DLm581EDevice <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 Customer Support for assistance.

DLm582IDevice <devicename> volume <volser> made/left read-only

Description: This message is displayed when an output virtual tape volume written to a write-once filesystem is unloaded and the volume has been made a read-only volume.

System action: The virtual tape volume is now permanently read-only.

User action: None.

DLm590EDevice <devicename> Unable to calculate retention time for nD/M/Y

(out of range?)


System Messages


Description: While closing a volume that has no valid HDR1 expiration date, written to a WORM filesystem, DLm was unable to calculate a valid retention period based on the configured default retention period.

System action: Processing continues. DLm 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.

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 persists, contact EMC Customer Support for assistance.

DLm591EDevice <devicename> Unable to set access time: <error message>

Description: While closing a volume written to a WORM filesystem, DLm was unable to set the retention period in the file's last access time.

System action: Processing continues. DLm 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 `error message' portion of this message to determine the cause of the problem. If this problem persists, contact EMC Customer Support for assistance.

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

DLm595WDevice <devicename> configured SnapLock and .SNAPLOCK found but

<pathname> is not a SnapLock directory


System Messages


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.

User action: Be sure that the correct tape library is configured and the correct external filesystem is mounted for this device.

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

System action: Processing continues. The virtual tape volume just written is not SnapLock'ed.

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 SnapLock'ed, you must create a file called .SNAPLOCK in each SnapLock directory.

DLm597WDevice <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 application has determined that the target directory is not an FLR filesystem, 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.

User action: Be sure that the correct tape library is configured and the correct external filesystem is mounted for this device.

DLm607EDevice <devicename>, Volume <volser>: error while setting scratch

state

Description: An error occurred while trying to scratch or unscratch a virtual tape file.


System Messages




DLm612EDevice <devicename>, Volume <volser>: <message>

Description: The DLm experienced an internal error, and outputs a detailed error message.



DLm614EDevice <devicename>, Volume <volser>: could not get hint for block:

nnnn

Description: The DLm was unexpectedly unable to find an entry in an index of block IDs while performing a LOCATE.

System action: The DLm returns an error status to the Host's LOCATE request.


DLm631EDevice <devicename>, Volume <volser>: could not find block nnnn

Description: The DLm was unable to locate a block specified in a LOCATE request.

System action: The DLm returns an error status to the Host's LOCATE request.


DLm636IDatabase timeout set to N seconds


System Messages


Description: Normal response to an operator 'SET DBTIMEOUT=N' command.

System action: The specified database timeout was changed.

User action: None.

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

DLm660IDevice <devicename>, Volume <volser>: For Unisys only, trying again

as SCRTCH

Description: The Host requested that the DLm mount volume <volser>, but the volume does not exist. For Unisys devices only, the DLm now performs a SCRTCH mount request.

System action: The DLm attempts to mount a scratch volume.

User action: None.

DLm671EDevice <devicename>, Volume <volser>: error while closing tape

Description: An error occurred while unmounting a virtual tape.



DLm674EDevice <devicename>, Volume <volser>: Bad path specified: full

path(<filename>)

Description: An internal error occurred while the DLm was attempting to construct a path name.


System Messages




DLm676EDevice <devicename>, Volume <volser>: internal I/O error

Description: The DLm experienced an internal I/O error.



DLm677EDevice <devicename>, Volume <volser>: error while renaming tape to

'xxxxxx'

Description: An error occurred while changing a tape's volser.



DLm678EDevice <devicename>, Encryption/decryption failed

Description: An error occurred while encrypting or decrypting data.

System action: The DLm application returns an error status to the current Host I/O request.

User action: Examine any preceding related messages, if any, for additional error information, and correct the problem. If the problem recurs, contact EMC Support for assistance.

DLm679ECannot set FIPS mode for encryption


System Messages


Description: The initialization of FIPS-mode-certified encryption failed.

System action: The DLm application initialization terminates.

User action: Examine any preceding related messages, if any, for additional error information, and correct the problem. If the problem recurs, contact EMC Support for assistance.

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



DLm681EDevice <devicename> <path-type> path 'path' specified, but no valid

<path-type> license file exists.

Description: A Centera path was encountered, but the DLm is not licensed for Centera support.

System action: The DLm does not accept mount requests using Centera Paths.

User action: If the DLm should be licensed to support Centera usage, contact EMC Customer Support for assistance.

DLm682EDevice <devicename> unable to initialize VirtualFile path 'path'

Description: An error occurred while X.

System action: The DLm does not accept mount requests using the indicated Centera Path.

User action: Ensure that the indicated Centera Path is correctly configured. If the problem persists, contact EMC Customer Support for assistance.


System Messages


DLm683WNothing to recover for tape <volser>; cleaning up.

Description: A previous I/O failure caused recovery of a partially-written tape to be attempted, but no recovery was possible.

System action: The DLm cleans up the remnants of the unrecoverable tape.

User action: None.

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



DLm685Eunable to initialize path 'pathname': error message

Description: An error occurred while setting the specified path.

System action: The path is not changed.


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


DLm687IEnhanced FS move volume method is: <method>

Description: The enhanced FS will use the displayed method when moving a volume.


User action: None.

DLm688IEnhanced 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 ifselected as disabled or will use the efsmove method chosen for all file systems when selected as enabled


User Action: None.

DLm701EDevice <devicename> Data Exchange Feature not licensed, mount

'volser' ignored

Description: Mounting of a flat file (data exchange) volser was requested, but this DLm is not licensed for flat file support.


User action: Only flat files can start with the volser prefix \BFL\. If you want to use the DLm flat file/data exchange feature, you must obtain a license for this feature. Contact EMC Customer Support for assistance.

DLm704EDevice <devicename> Error deleting unused flat volume <volser>:

error message

Description: The specified volume was created in response to a flat tape mount request. Because it was unloaded without ever having been written to, the DLm tried to delete it. An I/O error occurred during the attempt to delete.

System action: The volume may or may not been deleted from the tape library.


System Messages


User action: The 'error message' portion of this message describes the error that occurred. Correct the error.

DLm711IDevice <devicename> Unused flat volume <volser> deleted

Description: The specified volume was created in response to a flat tape mount request, but it was unloaded without ever being written to.

System action: The volume is deleted from the DLm disk.

User action: None.

DLm714EDevice <devicename> too many trailer labels!

Description: The DLm received too many labels to store (more than legally allowed for standard label processing) while processing the trailer labels for a standard labeled flat file.

System action: The Host write is canceled with a unit check.

User action: Correct the condition that is causing too many labels to be written.

DLm715EDevice <devicename> data in trailer labels!

Description: The DLm received a non-label data record while processing the trailer labels for a standard labeled flat file.

System action: The Host write request is canceled with a unit check.

User action: Correct the condition that is causing the invalid label or data to be written within the trailer labels.

DLm720EDevice <devicename> command in flat file

Description: The DLm application received a tape positioning command from the Host while positioned within the data area of a flat file.

System action: The Host command is canceled with a unit check.

User action: Spacing commands are not allowed within flat files; correct the condition that is causing the spacing within the file.


System Messages


DLm724EDevice <devicename> read backwards/previous in flat file

Description: The DLm application received a Read Backwards or Read Previous command from the Host while within the data area of a flat file.

System action: The Host command is canceled with a unit check.

User action: Reading backwards is not allowed in a flat file; correct the condition that is causing the backwards read within the file.

DLm766EDevice <devicename> file 'filename' already exists [as scratch]

Description: The Host wrote a HDR1 label to a flat file volume, and the DLm attempted to change the volume's filename from VOLSER.FLAT to VOLSER.DATASETNAME.FLAT (where DATASETNAME is the data set name from the HDR1 label), but the file VOLSER.DATASETNAME.FLAT already exists in the tape library.


User action: Either delete or rename the existing file in the tape library before writing a flat file with the same name, or use a different data set name in the JCL for the new output file.

DLm767EDevice <devicename> error renaming volume <volser> (oldfilename) to

newfilename; <error message>

Description: The Host wrote a HDR1 label to a flat file volume, and the DLm attempted to change the volume's filename from VOLSER.FLAT to VOLSER.DATASETNAME.FLAT (where DATASETNAME is the data set name from the HDR1 label), but an error occurred while renaming.


User action: See the 'error message' portion of this message to determine the reason for the error.

DLm770ECannot set RSA mode for encryption

Description: The initialization of RSA mode encryption failed.


System Messages


System action: Startup terminates.

User action: Examine any preceding related messages, if any, for additional error information and correct the problem. If the problem reoccurs contact EMC Support for assistance.

DLm771E Cannot get RSA key from 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, that the Key Manager is accessible from the controller, and that the access certificates are valid.

DLm772ECannot 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, that the Key Manager is accessible from the controller, and that the access certificates are valid.

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

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

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

DLm776ECannot stop RSA key module

Description: The attempt to stop the RSA key module failed.



DLm777ERSA 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 either is an initialization error, contact EMC Support for assistance.

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


System Messages


User action: None

DLm779INot encrypting on device <devicename>

Description: The tape has prior unencrypted data set(s), so this new appended data.

System action: The new data set is written unencrypted.

User action: None

DLm780ERestarting 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

DLm781WDevice <devicename> is open as a read only tape

Description: The volume on the specified device is mounted in read-only mode.

System action: The tape is mounted in read-only mode.

User action: To write new volumes, make sure the tape is correctly mounted and is write-enabled.

DLm782ECommand <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 execute this command at the physical tape device.

DLm783WDevice <devicename> tape door is open


System Messages


Description: The tape door is open.

System action: The system cannot mount the tape.

User action: Physically close the tape door.

DLm785WDevice <devicename> Read Buffer too small

Description: The data block read from the tape is larger than the maximum supported by DLm.

System action: The DLm returns an error status (equipment check) to the Host.

User action: The tape is not compatible with the DLm because of the large blocks it contains.

DLm786EDevice <devicename> Failed to Open <device path>

Description: The physical tape device is not accessible.

System action: Application does not communicate with this tape device.

User action: The tape most likely requires manual intervention.

DLm787EDevice <devicename> Unable to set Compression ON/OFF errno <error

message>

Description: The physical tape device did not accept the compression command.

System action: Data written to this tape device is not compressed.


DLm788EDevice <devicename> SCSI block #nnn too large (xxxxxx) to handle

<operation> (max=yyyyyy)

Description: The DLm has received a tape block with size ('xxxxxx') that is larger than the maximum tape blocksize ('yyyyyy') that can be presented to the SCSI Tape Device.



System Messages


User action: Correct the Host application to send a blocksize that can be handled by the tape drive.


DLm789IDevice <device name> does not support the SCSI <cmd> command

Description: The physical tape drive does not support the specified command.

System action: DLm will continue, but the specified command cannot be performed.

User action: Determine that the attached device is a supported device type.


DLm790IST driver version info: <description>

Description: Displays the version number of the st (SCSI tape) driver.


User action: None.


DLm791IBTISMC driver version info: <description>

Description: This message displays the version number of the btismc (SCSI Media Changer) driver.


User action: None.


System Messages


DLm795IDevice <devicename> ready

Description: Displays when a SCSI tape drive assigned to a DLm virtual tape device transitions from not ready to ready.

System action: A "Ready" interrupt is sent to the host.

User action: None.


DLm796IDevice <devicename> offline and not ready

Description: Appears when a SCSI tape drive assigned to a DLm virtual tape device transitions from ready to not ready.

System action: None. The drive appears not ready to the host.

User action: None.


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

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


System Messages


User action: None.

DLm804IWriting corefile to 'filename.gz' ...

Description: Normal response to the ' SAVE COREFILE' command.

System action: A diagnostic core file of the virtual tape application will be saved to the specified file.

User action: None.

DLm805Icorefile 'filename.gz' saved to disk

Description: Normal response to the 'SAVE COREFILE' command.

System action: A diagnostic core file of DLm has been written to the specified file.

User action: None.

DLm810ECommand failed: command: <error message>

Description: The DLm received an error while trying to execute the specified command in an external shell.

System action: The system continues running without executing the specified external command.


DLm812E<command> feature is not licensed

Description: The specified command requires a feature that is not licensed for use on this DLm.



DLm813ECommand <command> is not permitted


System Messages


Description: The specified command is not permitted by the DLm configuration.


User action: Refer to the EMC Disk Library for mainframe User Guide for instructions about how to activate this command.

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

DLm815EParameter n 'value' is not a valid VOLSER or synonym




DLm816ENo free device available to mount volume <volser>

Description: The operator LOAD command specified any drive ('*'), but there was no free drive.


User action: Wait for a drive to be free, then retype the command.

DLm817EParameter n 'keyword=value' is not a valid parameter





System Messages


DLm818EInvalid device name 'value' specified (too long)

Description: The <devicename> specified in an operator command is invalid.



DLm819EUnknown device name 'value' specified

Description: The <devicename> specified in an operator command is invalid.



DLm820ENo devicenames match 'devicenames'




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

DLm822IGuaranteed Replication refresh on Sync set ON/OFF


System Messages


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.

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

DLm826WDevice <devicename> is already Ready/NotReady, READY/UNREADY

command ignored

Description: The operator Ready or Unready command specified a drive that is currently in that state.


User action: Specify the correct device and desired state in the command.

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


System Messages


DLm829EDevice <devicename> is Ready, UNLOAD/REWIND/SET PATH command

ignored

Description: The operator Unload or Rewind or SET PATH command specified a drive that is in the Ready state.


User action: If you want to manually unload or rewind or change the path of a device you must make it UNREADY first.

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

DLm831EInvalid <parameter> value specified




DLm832EInvalid <parameter> value specified

Description: Syntax error on an operator command. Cannot set the same SCSI path to all devices.





System Messages


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

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

DLm839Eunable to assess space for <path> (nnn)

Description: The DLm was unable to obtain status information about the specified tape library subdirectory, in response to the \Query Space\ command.

System action: This tape library subdirectory is skipped in the \Query Space\ output.

User action: Make sure that a valid tape library directory is specified in the configuration file for this device, that the directory is currently mounted and accessible, and that all subdirectories with in the tape library are mounted and accessible. If the problem persists, contact EMC Customer Support for assistance.

DLm840IRead-back write verification set to ON/DATA/OFF

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.


System Messages


DLm841ISystem tracelevel is currently set to n

Description: The tracelevel is displayed in response to the Query All command.


User action: None.

DLm842ISystem debuglevel is currently set to n

Description: The debuglevel is displayed in response to the Query All command.


User action: None.

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

DLm844IDevice <devicename> OSADDR set to 'XXXX'

Description: The OSADDR value for this device has been changed. The OSADDR value is used with the VSE DLmMOUNT program to identify the name by which VSE knows a DLm application virtual device.

System action: The new OSADDR value will be used to find a virtual device when DLmMOUNT requests a mount on a specific drive by name, and DLm will report the OSADDR value to DLmMOUNT when it completes a mount on ANY drive.


System Messages


User action: None.

DLm845IDevice <devicename> GROUP set to 'n'

Description: The GROUP value for this device has been changed. The GROUP value is used with the VSE DLmMOUNT 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 DLmMOUNT requests a mount on ANY drive.

User action: None.

DLm846IAWS maps usage default value set to OFF

Description: An AWS map will not be written to an AWS file.


User action: None.

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

DLm848IDevice <devicename> maximum volume size changed from <oldsize> to

<newsize>

Description: The operator SET SIZE= command was accepted for the specified device.

System action: The maximum volume size was changed for the specified device. The SIZE is changed effect immediately.

User action: None.


System Messages


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

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

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

DLm852IFull-erase set ON

Description: The DLm has been configured to perform a more extensive erasure of data when a erasing of a virtual tape volume is requested. Most tape managers expect to find the complete original header label set on every scratched tape, but under some circumstances (for example, on a Unisys system), the full label set is not desirable.


System Messages


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.

DLm853IPending Mount Fairness (PMFAIR) set to <nnn>

Description: The PMFAIR option allows the DLm to be configured to delay read and write I/Os while a tape mount operation is in progress. This can speed up tape mounts on a heavily loaded system, at a slight expense to overall throughput during tape mount operations. This option is off by default.

System action: Every read and write I/O is delayed by <nnn> milliseconds while a tape mount is in progress.

User action: None.

DLm854WRequested path already assigned to device <devicename>

Description: The device path requested is already assigned to this device.

System action: The path is not changed from the previous value.


DLm855ESCSI Tape Device <device path> does not exist

Description: The device path requested does not exist.





System Messages


DLm856Inn scratch synonyms: volser,volser,...

Description: Displays any scratch synonyms that are defined in the configuration file.


User action: None.

DLm857EError Invalid Path

Description: The Operator selected a path that requires a feature that is not licensed for use on this DLm.



DLm858IDevice <devicename> Data path deferred change from 'oldpath' to

'newpath'

Description: The operator SET PATH= command was accepted, but the specified device currently has a volume mounted.

System action: The new data path takes effect immediately after the current volume is unmounted.

User action: None.

DLm859IDevice <devicename> Data path changed from 'oldpath' to 'newpath'

Description: The operator SET PATH= command was accepted.

System action: The new data path takes effect immediately on the specified virtual tape drive.

User action: None.

DLm860EPATH= is no longer supported; use DEV= to specify the tape library


System Messages


Description: The operator INITIALIZE command specified the obsolete PATH= parameter. Older versions of the DLm supported a choice between using PATH= or DEVICE= to designate the tape library where the volumes would be initialized. The PATH= parameter is no longer supported, and DEV= is required.

System action: The INITIALIZE command is ignored.

User action: Do not specify PATH=, but use the required DEVICE= parameter on the INITIALIZE command. See HELP INITIALIZE for more information.

DLm861ETape library path not changed

Description: The SET PATH command has failed.



DLm862EInvalid volser <volser> for volume initialization

Description: The INITIALIZE command specified a VOLSER of 'SCRTCH' or 'PRIVAT,' or beginning with 'BFL.' BFLxxx volsers are reserved for Data Exchange (\flat\) volumes, which cannot be pre-initialized on the DLm. Scratch volumes should be initialized with the actual volser desired, not by using the word 'SCRTCH' or 'PRIVAT.'


User action: Specify a valid volser that does not start with the prefix 'BFL' or ‘SCRTCH’ or ‘PRIVAT’.

DLm863ESCSI Tape path already in use

Description: The SET PATH command has failed.


User action: Set PATH= to a valid SCSI tape path that is not already in use.


System Messages



DLm864EYou can only create <nnn> volumes starting from <volser>

Description: The INITIALIZE command COUNT= parameter was too big for the specified starting volser.

System action: The INITIALIZE command is rejected.

User action: Use the HELP INIT command for more information about using the INITIALIZE command. Make sure that the specified COUNT value would not cause the numeric portion of the volser to overflow or the first two characters of the volser to change.

DLm865EFile '<filename>' [non-]scratch volume already exists

Description: While processing the INITIALIZE command, the DLm found that the volume it is attempting to create already exists in the tape library, as either a scratch or non-scratch volume.

System action: The new scratch volume is not created, and the original volume is not changed.

User action: Be careful to not create new scratch volumes in the range of existing volumes.

DLm866EFile/Directory '<filename>' open failed, err=<nnn>: <error message>

Description: An I/O error occurred while attempting to create a new scratch volume.

System action: The specified new scratch volume has not been created.

User action: Se the `error message' portion of this message for an explanation of the error. Correct the error and try initializing the volumes again.

DLm867EError writing to <filename>: <error message>


System Messages


Description: An I/O error occurred while attempting to create a new scratch volume.

System action: The specified new scratch volume has not been created.

User action: See the `error message' portion of this message for an explanation of the error. Correct the error and try initializing the volumes again.

DLm868EToo many errors have occurred, terminating

Description: Multiple errors have occurred during processing of the operator INITIALIZE command.

System action: One or more new scratch volumes may have been created before the maximum number of errors occurred.

User action: Review the messages prior to this one to determine the nature of the errors, and correct the errors and retype the correct INITIALIZE command.

DLm869Inn Standard/ANSI-labeled volumes initialized

Description: The DLm has completed an INITIALIZE command.

System action: The specified number of new scratch volumes have been created.

User action: None.

DLm870EDevice <devicename> Initializations not allowed in <tapelib>

Description: The tape library type assigned to this device does not support tape initialization. Volumes can be initializedonly in tape libraries on direct-access filesystems.


User action: Specify a DEVICE=device that has a tape library defined on a valid direct-access filesystem.

DLm871IAttentionCount set to <value>

Description: The configurable ATTENTIONCOUNT parameter has been set as shown.


System Messages


System action: The ATTENTIONCOUNT parameter defines how many times the DLm should retry sending an asynchronous \Ready\ interrupt should it be rejected by the channel or Host. The default number of retries is 45.

User action: None.

DLm872EInvalid SNn= value <value> (incorrect length)

Description: The operator SET command contained an incorrect serial number. The new serial number must be exactly 12 characters long.

System action: The SET command is ignored.

User action: Specify a valid value in the SET command. Use the HELP command to see the proper command syntax.

DLm873IAttention set to <value>

Description: The configurable ATTENTION parameter has been set as shown.

System action: The ATTENTION parameter defines which channel paths the DLm should send a \Ready\ interrupt to when a virtual tape drive comes ready. The possible values are:

◆ ALL — The interrupt is sent to every channel path established for this device.

◆ NONE — No interrupt is sent to any Host when a drive comes ready.

◆ ASSIGNED — The interrupt is sent to every channel path which has an Assignment in effect. An Assignment is typically made when a Host VARYs a drive online. This is the default action.

◆ PATHGROUP — The interrupt is sent to every channel path which currently has a Path Group ID (PGID) set. A PGID is typically set when a Host VARYs a path online.

◆ REQUESTER— The interrupt is sent only to the path from which the Load Display mount request was received.

User action: None.

DLm874ESetting <parameter> requires a DEVICE= parameter too


System Messages


Description: The operator SET command was typed without specifying a specific device to be set.

System action: The <parameter> specified is ignored.

User action: This particular SET command <parameter> requires that a DEVICE= parameter be specified; retype the SET with a specific DEVICE specified. Use the HELP command to see the proper command syntax.

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

DLm876IUnknown volumes will be treated as Scratch requests

Description: Normally, a request for a non-existent volume results in message DLm454E and the drive remains Not Ready. However, this DLm has been configured to treat mount requests for non-existent volumes as if the request were for a scratch volume. This option only applies for devices connected to a Unisys mainframe.

System action: The DLm proceeds as if a SCRTCH volume was requested when a non-existent volume is requested, but only if the device is connected to a Unisys mainframe at the time.

User action: None.

DLm877ISupport for VSE Host Utilities disallowed/allowed

Description: The DLm 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.


System Messages


User action: User Action: If you want to use the supplied VSE Utilities, enable this option; otherwise, leave this feature off by default.

DLm878I<debugging feature enabled / disabled / not enabled: message>

Description: A special DLm debugging feature was enabled through configuration or with the SET commandor 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 Customer Support.

DLm879I[Device <devicename> / ALL devices / TAPELIB path]

quiesced/unquiesced

Description: The QUIESCE or UNQUIESCE command was typed.

System action: A quiesced device is in a state where it does not accept any new tape mounts until it is explicitly unquiesced (or until the DLm is restarted). If a drive has a volume mounted at the time it is quiesced, it continues to function completely normally; it does not accept another mount after the current volume is unloaded.

User action: None.

DLm880IGroupAccess set to 'R'

Description: By default, virtual tape files created by the DLm are only accessible by the 'vtape' user. This message signifies that the DLm is currently configured to allow other members of the 'vtape' user group to have Read access to the virtual tape files created by the DLm.

System action: All tapes created while this option is set to have group accessibility.

User action: Reconfigure the DLm if you do not want other members of the 'vtape' group to have access to virtual tape files. Files that were created while this option was set to continue to be accessible by all members of the 'vtape' group unless the file permissions are manually changed by the administrator.


System Messages


DLm881IOtherAccess set to 'R'

Description: By default, virtual tape files created by the DLm are only accessible by the 'vtape' user. This message signifies that the DLm is currently configured to allow any user to have Read access to the virtual tape files created by the DLm.

System action: All tapes created while this option is set to have global accessibility.

User action: Reconfigure the DLm if you do not want everyone to have access to virtual tape files. Files that were created while this option was set to continue to be accessible by anyone unless the file permissions are manually changed by the administrator.

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

DLm884IDisk 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


DLm885EEXIT[!] 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.

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

DLm887IChannel adapter <n> serial number override set to <xxxxxxxxxxxx>

Description: The operator SET SNn= command was accepted.

System action: The hardware serial number reported by the DLm to the Host for channel adapter <n> has been set to the specified override value. If <xxxxxxxxxxxx> is blank, the override has been removed and the DLm reports the actual hardware serial number once again.

User action: None. Use the SET SNn= command to remove the override.

DLm888WWarning: New serial number contains lower case letters!

Description: The operator SET SNn= command was accepted, but the serial number specified contained one or more lowercase alphabetic characters.

System action: The specified serial number is accepted, and is reported to the Host EXACTLY as you specified.

User action: None, unless you really meant to type uppercase letters in the serial number. In that case, type the command again with the proper value.


System Messages


DLm889EEncryption key n is not available

Description: The specified encryption key is not installed.

System action: The ENCRYPTKEY value is not changed from the previous setting.

User action: Specify a valid, installed key in the SET ENCRYPTKEY command.

DLm890EHelp has no additional information for 'something'

Description: The DLm command 'HELP something' was typed, but 'something' is not a valid DLm command or message number.


User action: Use the HELP command alone to see a summary of the DLm commands available.

DLm891EInvalid command syntax

Description: The preceding operator command was invalid.



DLm892IWrite 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 is also displayed periodically if not set to 0.

System action: The virtual tape application will flush the data to disk storage every <nnnnnn> bytes, or not at all if the <nnnnnn> is set to 0.

User action: For best performance, this option should be set to 0 (the default).

DLm893E<feature> feature not yet supported


System Messages


Description: The preceding operator command used a DLm feature that is not supported.



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

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


DLm897EUnexpected keyword parameter n 'keyword=value'

Description: Syntax error on an operator Load command.



DLm898EUnknown parameter n 'something'

Description: Syntax error on an operator Load command.



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 MAS900I 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 MAS899I). This message is displayed when the task is no longer in that state.


User Action: None.

DLm901EError reading Keyboard Data: <error message>

Description: An I/O error has occurred while reading a command from the keyboard.


System Messages


System action: The DLm application terminates.


DLm902EZero Bytes read from Keyboard

Description: An I/O error has occurred while reading a command from the keyboard.



DLm908EError formatting message for SNMP trap: error message

Description: An error has occurred while formatting a message before evaluation by the SNMP agent.

System action: The message is sent to the SNMP agent as is, but might not be perfectly formatted.


DLm910WDevice <devicename> <deliberate error message>

Description: This message immediately precedes a deliberate error caused by the DLm, caused by setting a debugging mode on the DLm for testing purposes.

System action: A deliberate error of some kind follows this message.

User action: None. Do not be surprised by the error that follows. If you get this message unexpectedly, contact EMC Customer Support for assistance.






System Messages






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

DLm921ISet ProtectVol1=OFF to enable VOL1 overwrites

Description: This message follows MAS920E 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> 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.

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

DLm950IMessage from Host

Description: A Host program has sent this message to be displayed on the DLm Console.


User action: None.

DLm951IMessage from another program

Description: An external program has sent this message to be displayed on the DLm Console.


User action: None.


System Messages


DLm952EUnable to get hostname : <error message>

Description: The application was unable to get the hostname of the system

System action: Unable to continue.

User action: Verify that the hostname of the system is set correctly.

DLm953WLocking 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 the tape library filesystem is mounted with automatic 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 lock file feature is NOT recommended. Contact EMC Support for more information before turning off file locking.


System Messages


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

DLm958WDevice <devicename> not setting lock for <filename>

Description: The specified virtual tape volume is on a read-only filesystem mounted with the -onolock option. The virtual tape volume will NOT be locked against concurrent access from other system(s).

System action: The tape mount continues without locking the file. If another system writes to the tape file while this system has it mounted results will be unpredictable for this system.

User action: Mounting a filesystem in this manner is not recommended if there is any chance that another system might be writing to this filesystem at the same time. Contact EMC Support for more information.

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

DLm971EError closing input/output fifo: <filename>


System Messages


Description: The DLm received an error while closing the specified file. This error can only happen during program termination.

System action: The DLm continues to shut down.


DLm972EError deleting input/output fifo: <filename>

Description: The DLm received an error while closing the specified file. This error can only happen during program termination.

System action: The DLm continues to shut down.


DLm975IDiagnostic data written to file '<file>' (<num> bytes)

Description: The diagnostic data was written to <file>.


User action: None.

DLm976EError writing diagnostic data dump file '<file>': open error <error

detail>

Description: The diagnostic data could not be written to <file>.



DLm979EError writing diagnostic data dump file '<file>': open error <error

detail>

Description: The diagnostic data could not be written to <file>.




System Messages


DLm980EProgram Check error in thread nnnn (processname), state=XXXXXXXX

Description: An internal program error has occurred.

System action: The DLm attempts to shut down all virtual devices. All devices are taken offline to the Host, and the DLm application terminates.


DLm981EProgram Check type 'error type'

Description: An internal program error has occurred.



DLm990IShutting down this application...

Description: The DLm application is terminating.


User action: None.

DLm991EError shutting down device <devicename>

Description: An error occurred while attempting to shut down a virtual device.

System action: The DLm application continues to shut down.


DLm992W<n> volumes mounted; use vtd to force shutdown

Description: The operator 'EXIT' or 'RESTART' command was entered while one or more virtual tape drives had a volume mounted.



System Messages


User action: Before shutting down, wait for all Host applications to finish and unload their tapes. If for some reason the Host cannot unload all of the DLm devices, manually unload all virtual tape volumes with the DLm 'UNLOAD' command. If, for some other reason, the DLm 'UNLOAD' command cannot unload all the DLm devices, the vtd force command will force a shutdown even while tapes are mounted.

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

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

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

DLm997ENMI Detected

Description: A NMI has been reported in the /var/log/messages file.



System Messages


User Action: Determine why the NMI occurred and correct it. For more assistance, contact EMC Support.

DLm999ETerminating 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 Customer Support.


System Messages


Call home messagesThis section lists the EMC Call home messages.

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

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


System Messages


EMCvts messagesEMCvts 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 yyyyNot 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 yyyyLoading 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 yyyyNo need to reload firmware

The script has determined that there is no need to update the firmware on the channel adapter card.

EMCvts: EMC directory "directory" does not exist!The directory containing the EMC DLm executable files cannot be located. Contact EMC Customer Support if you need additional assistance in determining the cause of this problem.

EMCvts: Error loading firmware into slot nnnnnn (Interface n)!An error occurred while attempting to load new firmware into the channel adapter card. Contact EMC Customer Support if you need additional assistance in determining the cause of this problem.

EMCvts: Error occurred. Press Enter to exit.This message follows all other EMCvts error messages. Press Enter to terminate the DLm application. Correct the preceding error, or contact EMC Customer Support for additional assistance in determining the cause of the problem.

EMCvts messages 429

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 foundInformation message to display the number of channel interfaces found in the system.

EMCvts: No channel adapters installed, or drivers not presently loadedNo 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.


System Messages


z/OS system messagesThis 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.

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

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

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

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

z/OS system messages 431

System Messages


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

DLH000ICOMMANDS ARE:STARTLOG,N=nodename/ALLSTOPLOG,N=nodename/ALLSTARTCMD,N=nodename/ALLSTOPCMD,N=nodename/ALLN=nodename/ALL,C=commandHELPSTATUS

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.


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 LOG FILE FAILED TO OPEN

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.

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

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

DLS012IUNEXPECTED 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


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

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

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

DLS040ICONTROL PATH FAILED TO OPEN

The DLMSCR control tape failed to open. Make sure the controller is up and running and the unit address used for the DLMSCR control tape is a valid controller device and has been varied online to the mainframe.

DLS050I LOG FILE FAILED TO OPEN

DLMSCR maintains a log file with all the error and informational messages from any DLMSCR runs. Check the mainframe job log to determine why it did not open properly.

DLS060ISORTIN FILE FALED TO OPEN

DLMSCR requires a sortin file when processing a Tivoli Storage Manager (TSM) report.

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

DLS081IFREExxxxx NOT ALLOWED WITH TYPE RMMDV

RMMDV has its own format, See the documentation on RMMDV.

DLS100INO INPUT PARAMETERS FOUND

DLMSCR requires at least the TYPE= parameter be configured. Check the format of your input parameters.

DLS110INO type FOUND IN INPUT PARAMETERS

DLMSCR requires the TYPE= parameter. Check your input parameters.

DLS111IUNKNOWN type FOUND IN INPUT PARMS

DLMSCR has found an incorrect TYPE= parameter. Check your input parameters.

DLS120I Freespace not confirmed - terminating


System Messages


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

DLS140ISORT 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 LOG FILE FAILED TO OPEN

The file that the DLMLOG DD card points to failed to open, or no DLMLOG DD card was present. Check the JOBLOG and JCL for the reason, and resubmit the job. If no logfile is required, use parm=’WTO’ to send the result to the operator instead of the logfile.


System Messages


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

DLmT03ESSH Keys Check Failed.

DLmT04E NFS Mounts Status Check Failed.

DLmT05E DLm ACP Required Services Status Check Failed.

DLmT06E GR Status Check on Celerra Failed.

DLmT07EVNX Capacity Check Failed.

DLmT10E VTE Failed to Respond to System Health Check Request.

Healthcheck messages 441

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.

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

DLmT23EOne-GbE Management Switch Connection Check Failed.

DLmT30E Ten GB Data Switch is not Responsive.


System Messages


DLmT31E Ten GB Data Switch Status Check Failed.

DLmT32EAll Ten-GbE Data Switche(s) are not Responsive.

DLmT33ETen_GbE Data Switch Connection Check Failed.

DLmT40E Data Domain System is not Responsive.

DLmT41E Data Domain System Status Check Failed.

DLmT42EAll Data Domain System(s) are not Responsive.

DLmT43EDD Management Path Connection Check Failed.

DLmT44EDD Data Path Connection Check Failed.

DLmT45EDD Capacity Check Failed.

DLmT50E Celerra System is not Responsive.

Healthcheck messages 443

System Messages


DLmT51E Celerra System Status Check Failed.

DLmT52EAll VNX system(s) are not Responsive.

DLmT53EVNX System Connection Check Failed.

DLmT98EUnexpected Error.


System Messages


VTEC errors that generate ConnectEMC eventsDLm errors that generate ConnectEMC events are:

DLm015E DLm119E DLm326E DLm498E






















DLm055E DLm226W DLm471E DLm812E






VTEC errors that generate ConnectEMC events 445

System Messages






DLm074E DLm319E DLm991E


INDEX


Numerics3480, 3490, or 3590

configure devices 97, 164Direct Tape 119IDRC 173Load Display command 240Manual Tape Library 165real 164, 169size range 106UIM 169, 170

AACP

controls and indicators 27, 77power down 81status indicators

FICON 32awsprint library utility 126, 135AWSTAPE 238

CCelerra

power down 83Channel Command Words 240Command

DFSMShsm 173DISABLE 212EXPORT 212HELP 214IMPORT 215INITIALIZE 215LOAD 217poweroff 79reboot 79REWIND 227SAVE TRACE 228SET 228SHOW 232SNMP 232statfmt 246

Syntax 212UNLOAD 234UNQUIESCE 234UNREADY 235z/OS operator 170

connectESCON channel 35FICON channel 31

considerationsDDR 172DFSMShsm 173RMM 182TLMS 182TMS 182TSM 183ZARA 183

DDirect Tape 118DLm

ASCII data/labels 241command 174, 175, 184compression 121ENTER command 186label type 105power down 79power up 72replication 128tape drive mapping 119utility version reporting 175

DLMCMD utility 184DLMSCR utility 177documentation, related 15Dynamic Device Reconfiguration considerations (DDR)

172

EEMC publications 15EMC support website 15ESCON


Index


connection 35

FFICON

connection 31status indicators 32

formatAWSTAPE 238Control Byte 242EMC DLm message 256Load display data 242statfmt command 246

GGENSTAT utility 176

Iindicators

FICON 32

LLibrary utility, awsprint 126

Mmessage

class 256DLm system 257DLMCMD 431DLMLIB 436DLMSCR 436EMC DLm 256EMCvts 429format 256Format Control Byte 240number 256z/OS system 431

Ppassword

system 72power down

ACP 81Celerra 83

Powerlink website 15

Rreplication

copy 130creating 133disaster recovery 134disastory recovery 134overview 128supported configurations 132terminolgy 130

TTape

direct 118, 119export command 212export/import utilities 121import command 215

Tape Library unaccessibleDLm156W 289DLm400E 334

Uutility

DLm scratch 179DLMCMD 184DLMSCR 177DLMVER 174GENSTAT 176

VVTE

configuring virtual device 97controls and indicators 24

Zz/OS

compaction of the virtual tape data 173configuring the devices 164Load display message 240Missing Interrupt Handler 170operator command 170utilities 174


EMC Disk Library for mainframe DLm960 - Dell EMC Spain · IPL from the stand-alone IPL tape........

Documents

Transcript of EMC Disk Library for mainframe DLm960 - Dell EMC Spain · IPL from the stand-alone IPL tape........