Dell EMC Disk Library for mainframe

Version 5.1

User Guide for DLm8500 with PowerMax

302-005-775
Rev 03
February 2020
 Copyright © 2020 Dell Inc. or its subsidiaries All rights reserved.

Dell 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.” DELL 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 DELL SOFTWARE DESCRIBED
IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.

Dell Technologies, Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property
of their respective owners. Published in the USA.

Dell EMC
Hopkinton, Massachusetts 01748-9103
1-508-435-1000 In North America 1-866-464-7381
www.DellEMC.com

2 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
CONTENTS

Figures 7

Tables 9

Preface 11

Chapter 1 Overview of Dell EMC Disk Library for Mainframe 13

Introduction to Disk Library for mainframe........................................................ 14
DLm architecture...............................................................................................14
VTEC Overview.................................................................................... 15
Backend storage...................................................................................19
Mainframe channel interfaces...............................................................19
Tape emulation................................................................................................. 20
Virtual tape drive states....................................................................... 20
Data formats.........................................................................................21
High availability features....................................................................................21
VTEC.................................................................................................... 21
Network connectivity failure checks.....................................................21
Benefits............................................................................................................ 22

Chapter 2 DLm Operations 23

Management access to DLm............................................................................. 24
License activation............................................................................................. 24
Overview of the activation procedure.................................................. 24
Receiving the LAC and activating the license.......................................25
Installing the license on DLm Console.................................................. 29
Starting and stopping tape devices...................................................................30
Key Management Interoperability Protocol .......................................................31

Chapter 3 DLm Administration 33

Tape libraries.................................................................................................... 34
Storage class recommendation............................................................ 34
Initializing DLm scratch volumes.......................................................... 35
Defining tape libraries...........................................................................37
Configuring virtual devices................................................................................37
Planning considerations........................................................................37
DLm configuration files........................................................................ 37
Configuring global parameters............................................................. 38
Adding devices.....................................................................................40
Scratch synonyms ...............................................................................45
DLm Long term retention..................................................................................46
LTR file systems...................................................................................47
Defining LTR Filesystems..................................................................... 47
Parameters for LTR policies................................................................. 48
Configuring LTR policies...................................................................... 49

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 3
Contents

Configuring Migration Policies on the Migration Policies tab in DLm Console....51

DLm Console Migration Policies tab fields........................................................ 53
Managing configuration files............................................................................. 54
Activating or installing a configuration on selected VTEs..................... 54
Creating a new configuration............................................................... 56
Editing a configuration......................................................................... 58
Saving a configuration file ...................................................................58
Deleting a configuration....................................................................... 58
Installation history................................................................................58
Tape erase........................................................................................................ 59
Space erase policy............................................................................... 59
Time-to-Live erase policy.....................................................................59
Both.....................................................................................................60
VTE logs and DLm statistics............................................................................. 60
VTE logs...............................................................................................60
Viewing the latest VTE logs..................................................................60
Support data.........................................................................................61
VOLSER Listing................................................................................... 62
Capacity statistics............................................................................... 63
Performance statistics......................................................................... 64
Downloading a replication report..........................................................65
System health check............................................................................66
Virtuent command interface..............................................................................67
DLm diagnostic reporting..................................................................................68
VTEC................................................................................................... 68
ConnectEMC........................................................................................72
AWSPRINT library utility...................................................................... 72

Chapter 4 SRDF Replication 79

SRDF replication overview................................................................................ 80
SRDF Synchronous (SRDF/S).............................................................80
Prerequisites for SRDF replication....................................................... 80
SRDF connections and configuration.................................................................81
SRDF replication capabilities................................................................ 81
SRDF/S active-passive configuration................................................... 81
Configuration files on source and target systems.................................82
Disaster recovery capabilities............................................................................82
SRDF benefits...................................................................................................82

Chapter 5 GDDR and Supported Configurations 85

GDDR Introduction........................................................................................... 86
GDDR Control Systems........................................................................86
Workload location.................................................................................87
GDDR Processes.................................................................................. 87
SRDF/Star with AutoSwap GDDR Configuration.............................................. 87
DLMDRD...........................................................................................................88
DLMDRC...........................................................................................................88

Chapter 6 Mainframe Tasks 89

Device configuration......................................................................................... 90
3480, 3490, and 3590 tape drives.................................................................... 90
Manual Tape Library (MTL).............................................................................. 90
Defining DLm devices with HCD.......................................................... 90
MTL considerations for VTE drive selection......................................................92

4 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Contents

Enabling a Dell EMC batch utility to communicate with a specific VTE....

92
MTL-related IBM maintenance......................................................................... 93
Dell EMC Unit Information Module....................................................................93
Missing Interrupt Handler................................................................................. 94
MIH command......................................................................................94
Dynamic device reconfiguration considerations................................................ 95
Critical considerations for operator-initiated swap functions .............. 95
DFSMShsm considerations............................................................................... 95
Identifying esoteric tape unit names to DFSMShsm.............................95
Specifying tape compaction..............................................................................96
DLm z/OS components.................................................................................... 96
Initiating an initial program load from a DLm virtual tape...................................96
Creating a stand-alone IPL tape on DLm.............................................. 97
Mounting and IPLing from the stand-alone IPL tape............................ 97
IPL considerations for DLm.................................................................. 97
DR logging........................................................................................................ 98
Preparing z/OS for IPv6................................................................................... 99
Enabling IPv6....................................................................................... 99
Configuring IPv6.................................................................................100
Configuring Virtual Telecommunications Access Method (VTAM)...... 101

Chapter 7 Using DLm with Unisys 103

Unique DLm operations for Unisys mainframes................................................104
Autodetection.....................................................................................104
Load displays...................................................................................... 104
Mount "Ready" interrupt.................................................................... 104
Query Config command...................................................................... 104
Ring-Out Mount request.....................................................................104
Scratch request..................................................................................104
Configuration for Unisys..................................................................................105
Device type........................................................................................ 105
Labels................................................................................................. 105
Scratch tapes..................................................................................... 105
Initializing tapes for Unisys.............................................................................. 105
Configuring the Unisys mainframe for DLm..................................................... 105

Appendix A Virtual tape operator command reference 107

Syntax............................................................................................................. 108
CLOSE VSTATS.............................................................................................. 108
DETAIL MOUNT.............................................................................................. 108
FIND................................................................................................................ 109
HELP............................................................................................................... 109
INITIALIZE........................................................................................................110
KMRESTART................................................................................................... 112
LOAD............................................................................................................... 112
LTR.................................................................................................................. 113
MIGRATE......................................................................................................... 114
QUERY.............................................................................................................115
QUERY SPACE sample output.............................................................117
QUIESCE..........................................................................................................117
READY............................................................................................................. 118
REWIND...........................................................................................................119
ROTATE...........................................................................................................119

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 5
Contents

SAVE TRACE................................................................................................... 119

SCRATCHNAME............................................................................................. 120
SET.................................................................................................................. 121
SNMP..............................................................................................................127
STARTVT........................................................................................................ 128
STOPVT.......................................................................................................... 128
UNLOAD..........................................................................................................128
UNQUIESCE....................................................................................................129
UNREADY........................................................................................................130

Appendix B SMP/E Installation 131

Introduction to SMP/E Installation ................................................................. 132
Loading DLMSxyz.XMITLIB to disk..................................................................132
Preparing DLMSxyz.XMITLIB(#EXTRACT).....................................................134
Customizing the RIMLIB JCL ..........................................................................135
Running the installation jobs ........................................................................... 138
Performing a cleanup.......................................................................................139
Applying maintenance .....................................................................................139
Authorizing DLm LINKLIB and Recycle DLMHOST.......................................... 139
Shutting down and restarting DLMHOST ....................................................... 140

Appendix C AWSTAPE Information 141

AWSTAPE format............................................................................................142

Appendix D Volume Handling 143

Volume serial numbers..................................................................................... 144
Scratch volumes.............................................................................................. 144
Delete (erase) scratch volume data ................................................... 145
Mount volumes ............................................................................................... 146
Mount a specific volume by VOLSER .................................................146
Mount a scratch volume .................................................................... 146

Appendix E Load Display Command — CCW Opcode x'9F' 149

Load display messages.................................................................................... 150
Load display data.............................................................................................150

6 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
FIGURES

1 DLm8500 Multiple Rack Solution for PowerMax Architecture...........................................15

2 VTE front — right control panel........................................................................................ 16
3 VTE front — left control panel.......................................................................................... 16
4 Rear Panel of DLm 5.1 VTE for OCFS2 and NFS operations.............................................. 17
5 Dell S3048 switch..............................................................................................................18
6 Dell S4048-ON switch....................................................................................................... 18
7 Brocade DS-6510R-B switches..........................................................................................19
8 Sample LAC mail .............................................................................................................. 25
9 Confirming site details ..................................................................................................... 26
10 Reviewing the selection ....................................................................................................27
11 License activation complete ............................................................................................. 28
12 Viewing the license key..................................................................................................... 29
13 License installed on DLm Console..................................................................................... 30
14 Last Installation.................................................................................................................38
15 Global options................................................................................................................... 39
16 Control units......................................................................................................................41
17 Adding devices.................................................................................................................. 42
18 LTR feature activation...................................................................................................... 48
19 Configuring LTR ...............................................................................................................48
20 Configuring LTR policies .................................................................................................. 50
21 Migration feature activation..............................................................................................52
22 DLm Console Migration Policies tab .................................................................................52
23 DLm Console Migration Policies tab options..................................................................... 52
24 Configuration operations — Activating or installing a configuration................................. 55
25 Upload configurations....................................................................................................... 57
26 Installation history.............................................................................................................59
27 Gather logs........................................................................................................................ 61
28 VOLSER listing..................................................................................................................63
29 Capacity statistics............................................................................................................ 64
30 Performance statistics......................................................................................................65
31 System health check.........................................................................................................67
32 Virtuent command interface............................................................................................. 68
33 Notification tab.................................................................................................................69
34 SNMPv3 configuration......................................................................................................70
35 Configuring messages....................................................................................................... 72
36 SRDF Synchronous (SRDF/S)..........................................................................................80
37 SRDF/S active/passive configuration...............................................................................82
38 DR Logging Overview....................................................................................................... 98
39 Scratch synonym for Unisys............................................................................................ 105
40 AWSTAPE single disk file.................................................................................................142

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 7
Figures

8 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
TABLES

1 Typographical conventions................................................................................................ 12
2 Ports used by the DLm 5.1 VTE for OCFS2 and NFS operations........................................ 17
3 Status Indicators...............................................................................................................20
4 VTE OS licenses for DLm models...................................................................................... 24
5 Storage class considerations.............................................................................................34
6 Example of LIBRARY-ID and LIBPORT-ID..........................................................................91
7 Help command — option description .............................................................................. 110
8 Initialize command — option description..........................................................................110
9 Load command — option description...............................................................................112
10 LTR command - option description...................................................................................113
11 MIGRATE option description............................................................................................115
12 Query command — option description............................................................................. 116
13 QUIESCE option description............................................................................................ 118
14 SCRATCHNAME command - option description..............................................................120
15 Set command—option description.................................................................................. 122
16 SNMP command—option description............................................................................. 127
17 Unquiesce command — option description..................................................................... 129
18 RIMLIB File Contents.......................................................................................................135
19 Load display data.............................................................................................................150
20 Format Control Byte ....................................................................................................... 151

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 9
Tables

10 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
PREFACE

As part of an effort to improve its product lines, Dell EMC periodically releases revisions of its
software and hardware. Therefore, some functions described in this document might not be
supported by all versions of the software or hardware currently in use. The product release notes
provide the most up-to-date information on product features.
Contact your Dell EMC technical support professional if a product does not function properly or
does not function as described in this document.
Note: This document was accurate at publication time. To ensure that you are using the latest
version of this document, go to Dell EMC Online Support (https://www.dell.com/support).
Purpose
Dell 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 DLm8500 with PowerMax and ECS. It also
includes configuration information that is required for ongoing operation.
Audience
This guide is part of the Dell EMC DLm documentation set, and is intended for use by system
operators to assist in day-to-day operation. Configuration, and maintenance tasks must be
accomplished by qualified Dell EMC service personnel only.
Readers of this document are expected to be familiar with tape library operations and the
associated tasks in the mainframe environment.
Related documentation
The following Dell EMC publications provide additional information:
l Dell EMC Disk Library for mainframe Physical Planning Guide for DLm8500 with PowerMax and
ECS
l Dell EMC Disk Library for mainframe Release Notes
l Dell EMC Disk Library for mainframe Command Processors User Guide
l Dell EMC Disk Library for mainframe System Messages Guide
l Dell EMC Disk Library for mainframe DLMDR Software Release Notes
Special notice conventions used in this document
Dell 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 Indicates a hazardous situation which, if not avoided, could result in minor or
moderate injury.
NOTICE Addresses practices not related to personal injury.

Note: Presents information that is important, but not hazard-related.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 11
PREFACE

Typographical conventions
Dell EMC uses the following type style conventions in this document:

Table 1 Typographical conventions

Bold Used for names of interface elements, such as names of windows,

dialog boxes, buttons, fields, tab names, key names, and menu paths
(what the user specifically selects or clicks)

Italic Used for full titles of publications referenced in text

Monospace Used for:
l System code
l System output, such as an error message or script
l Pathnames, filenames, prompts, and syntax
l Commands and options

Monospace italic Used for variables

Monospace bold Used for user input

[] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means “or”

{} Braces enclose content that the user must specify, such as x or y or

z

... Ellipses indicate nonessential information omitted from the example

Where to get help

Dell EMC support, product, and licensing information can be obtained as follows:
Product information
For documentation, release notes, software updates, or information about Dell EMC products,
go to Dell EMC Online Support at https://www.dell.com/support.

Technical support
Go to Dell EMC Online Support and click Service Center. You will see several options for
contacting Dell EMC Technical Support. Note that to open a service request, you must have a
valid support agreement. Contact your Dell EMC sales representative for details about
obtaining a valid support agreement or with questions about your account.

Your comments
Your suggestions will help us continue to improve the accuracy, organization, and overall quality of
the user publications. Send your opinions of this document to [email protected].

12 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
CHAPTER 1
Overview of Dell EMC Disk Library for Mainframe

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

l Introduction to Disk Library for mainframe.............................................................................14

l DLm architecture................................................................................................................... 14
l Tape emulation......................................................................................................................20
l High availability features........................................................................................................ 21
l Benefits.................................................................................................................................22

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 13
Overview of Dell EMC Disk Library for Mainframe

Introduction to Disk Library for mainframe

The Dell 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 tape-less 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 (formerly known as CopyCross™) and CA Vtape. However, these solutions utilize
expensive host CPU cycles to perform the tape operations, and direct access storage device
(DASD) space to store 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.
All DLm models are built using a common tape-on-disk software package known as Virtuent. The
Virtuent software runs on a base hardware controller which provides four FICON connections to
the mainframe.
DLm works seamlessly with the mainframe environment, including the major tape management
systems, such as 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 because 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.
The DLm8500 with PowerMax provides a disaster recovery option that uses Symmetrix-based
remote replication technology (SRDF) for restarting the production workload at the disaster
recovery site.
l In a disaster recovery configuration, there are two sites: one site is active and serves as the
production workload site, and the other site is the dormant site, also referred to as the passive,
standby, or inactive site. The DLm configuration, capacity, and features are identical at both
the active and dormant sites. The sites are identical, except that the active site is the
production site.
A swap refers to the process of making the active site dormant, and the dormant site active.
The swap process is always the same, irrespective of the direction of the swap (that is,
whether the swap is from Site A to Site B, or Site B to Site A). The time it takes to perform a
swap is also the same, irrespective of direction. The benefits of this configuration are that it
achieves parity between the sites, and that the swap procedure and swap procedure times are
always the same, irrespective of direction.
This feature is ideal for customers who want their data centers (DC) to be completely
identical. Due to the parity between the sites, this DR configuration is ideal for customers who
want their production sites to be at either the active or dormant site for extended periods of
time.
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 architecture
This section describes the major components of a DLm.
The major components of a DLm8500 system are the virtual tape emulation controller (VTEC) and
the PowerMax backend storage system.

14 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Overview of Dell EMC Disk Library for Mainframe

VTEC Overview
The VTEC is a 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:
l 3 to 8 virtual tape emulators (VTEs) for Multiple Rack Solutions for PowerMax
Note: VTEs 3 - 6 are standard. The 7th and 8th VTEs are available by RPQ only.

l A pair of 1 GbE switches for the management network in Multiple Rack Solutions
l A pair of 10 GbE switches for the data network in Multiple Rack Solutions
l A pair of 16 Gb Fibre Channel switches in Multiple Rack Solutions for PowerMax
Note: You can also configure NFSv3 access to a remote ECS system to use as a target of LTR
offload from the DLm system.
The following figure illustrates how the various components of the DLm8500 Multiple Rack
Solution for PowerMax system are connected to each other.
Figure 1 DLm8500 Multiple Rack Solution for PowerMax Architecture

VTE
This section describes the VTE panels.
The mainframe virtual tape emulation software, Virtuent, runs on the VTEs. The VTEs emulate IBM
tape drives and interface to the mainframe and direct tape data to and from the back-end storage
arrays. This data is written to the storage arrays and stored in NFS file systems over a redundant
10 GbE data network.
The following figure shows the right control panel on the front panel of the VTE:

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 15
Overview of Dell EMC Disk Library for Mainframe

Figure 2 VTE front — right control panel

Label Component
1 Power Button w/ Integrated LED
2 USB port (2)
3 iDRAC Direct port
4 iDRAC Direct LED
5 VGA port

The following figure shows the left control panel on the front panel of the VTE:
Figure 3 VTE front — left control panel

Label Component
1 Drive indicator
2 System health and system ID indicator
3 iDRAC Quick Sync 2 wireless indicator

16 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Overview of Dell EMC Disk Library for Mainframe

Label Component
4 Temperature indicator
5 Electrical indicator
6 Memory indicator
7 PCIe indicator

The following figure shows the rear view of the VTE:

Figure 4 Rear Panel of DLm 5.1 VTE for OCFS2 and NFS operations

The following table lists the ports that are used by the DLm 5.1 VTE for NFS operations.

Table 2 Ports used by the DLm 5.1 VTE for OCFS2 and NFS operations

Port Function

Eth0 and Eth1 Bonded for failover - Customer external network (For VTE1 and VTE2
only). The Eth0 and Eth1 ports can handle either 10 GbE or 1 GbE
throughput.

Eth2 and Eth3 Bonded for failover - DLm internal management network.

Intel X710 (Ethernet to support file storage Bonded for LACP - Connect OM-4 cables from these ports to the
mounted over NFS protocols) Eth4, Eth5, DLm internal ethernet data network.
Eth6, and Eth7

QLE2672 (mainframe FICON) Channel 1, 2, Connect FICON channel cables from the mainframe to these ports
3, and 4 (link speeds of 4 Gb, 8 Gb, and 16 Gb).

QLE2692 (Fibre Channel to support block Connect OM-4 cables from these ports to the DLm internal Fibre
storage mounted over OCFS2 protocols) Channel data network. (link speeds of 4 Gb, 8 Gb, and 16 Gb).
FC0, FC1, FC2, and FC3

iDRAC iDRAC is connected to the internal management network for remote

management of the VTE.

USB Plug in a USB drive to upload or download data from/to the VTE.

Power Supplies Two 750 Watt power supplies. Connect a black cord and a gray cord.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 17
Overview of Dell EMC Disk Library for Mainframe

Each VTE supports four FICON channel ports (two ports each from two QLE2672 FICON
adapters). The FICON interfaces can be single-mode or multimode. Single-mode or multimode SFP
transceiver modules are pre-installed in the FICON channel interface adapters. These transceivers
receive the FICON channel interface connectors. The FICON channel cable mode must match the
SFP module mode.
Eth4, Eth5, Eth6, and Eth7 are 10 Gigabit Ethernet ports (two ports each from two Intel X710 10
GbE adapters).
FC0, FC1, FC2, and FC3 are 16 Gb Fibre Channel ports (two ports each from two QLE2692 16 Gb
FC adapters).

DLm8500 management network

This section describes the management network in a DLm8500 system.
The DLm has an internal Gigabit Ethernet network for management purposes. In a DLm8500, the
management ports of the VTE and PowerMax systems are connected to a pair of 1 Gb Dell S3048-
ON switches to protect against a single switch failure.
Figure 5 Dell S3048 switch

External management network

DLm provides support for the IPv6 protocol. Each external network interface in the DLm will be
configurable for IPv6-only, dual IPv4/IPv6, or IPv4-only addressing. To configure IPv6 support on
your DLm, contact Dell EMC Customer Service.

DLm8500 Ethernet data network

In a DLm8500, the data from the mainframe is transferred to the DLm8500 back-end storage
systems such as Data Domain or ECS over 10-Gigabit Ethernet connections.

Figure 6 Dell S4048-ON switch

DLm8500 fibre channel data network

In a DLm8500, the data from the mainframe is transferred to the PowerMax back-end storage
systems over 16 Gigabit Fibre Channel connections.

18 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Overview of Dell EMC Disk Library for Mainframe

Figure 7 Brocade DS-6510R-B switches

Backend storage
The DLm8500 uses two Fibre Channel switches to connect to a PowerMax 8000 storage array to
serve as the back-end storage.
One of the benefits of a DLm8500-based system is the use of SRDF for replicating data to remote
systems thereby allowing customers to take advantage of the associated Disaster Recovery (DR)
capabilities and applications of SRDF. The DLm Disaster Recovery Dummy (DLmDRD) software
runs on the management VTE in a DLm8500 configuration. DLm Disaster Recovery is the
mechanism for communication between GDDR, which runs on the mainframe, and the DLm.
16 Gb Brocade DS6510B Fibre Channel switches
A pair of 16 Gb Brocade DS6510B 48-port Fibre Channel switches connect to the PowerMax 8000.
PowerMax storage
The PowerMax 8000 has a minimum of 7 FC drives (three RAID1 pairs plus a spare). The data
drives are 4TiB NVMe using FBA 6RAID6. The Control Devices are 300GB 10K RPM Fibre Channel
4 Gbps.

Mainframe channel interfaces

A VTE contains mainframe channel interfaces. Each VTE contains four Fibre Connectivity (FICON)
interfaces. The FICON interfaces can be either single mode or multi-mode.
A DLm8500 system can be configured with 1 to 8 VTEs, providing a maximum of 32 FICON
interface connections.

FICON Channel
You must attach at least one mainframe channel to each VTE you intend to configure to be
operational. Any VTE not attached to a mainframe channel will not be operational.
Each DLm VTE FICON interface has a single LC-type fiber-optic connector. The type of cable you
must use depends on the following:
l The type of connector on the mainframe (either LC or SC)
l The type of fiber-optic cable (single mode or multimode) supported by the mainframe channel
DLm FICON interfaces are available either with single mode or multimode fiber-optic cable
support. The core size micron ratings for the cables are as follows:
l Single mode fiber-optic cable: 9/125
l Multimode fiber-optic cable: either 50/125 or 62.5/125

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 19
Overview of Dell EMC Disk Library for Mainframe

FICON and Fibre cards status indicators for DLm

Each FICON interface has LED status indicators visible through its backplate. These indicate which
speed the link is running 4, 8, and 16 Gbps. When the link is up, the LED remains steadily on and, if
there is traffic, it blinks. The numbers stamped into the faceplate correspond to the speed. The
following table describes the FICON status indicators for DLm:

Table 3 Status Indicators

Amber LED16 Gbps Green LED 8 Gbps Amber LED 4 State

Gbps

Off Off Off Power off (before

firmware
initialization)

On On On Power on (after
firmware
initialization)

Flash Flash Flash Loss of

synchronization

Flash in sequence Flash in sequence Flash in sequence Firmware error

On for link up or Flash if I/O Off Off 16 Gbps link up/

activity activity (UP/ACT)

Off On/flash Off 8 Gbps link up/

activity (UP/ACT)

Off Off On/flash 4 Gbps link up/

activity (UP/ACT)

Flash Off Flash Beacon

Tape emulation
DLm VTEs emulate the IBM tape drives to the mainframe and direct the tape data to and from the
back-end storage arrays.
Each VTE, once configured, operates independently of the other VTEs in the VTEC.
A DLm system that is configured with one VTE can emulate up to 512 virtual tape devices, while
one with six VTEs can emulate up to 3,072 virtual tape devices.
The virtual tape emulation software performs the following functions:
l Receives and interprets channel command words (CCWs) from the host.
l Sends and receives the tape data records and reads and writes corresponding disk data in
response to the CCWs.
l Presents initial, intermediate, and final status to the host commands and asynchronous status
as needed.
l 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:

20 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Overview of Dell EMC Disk Library for Mainframe

l Not Ready — The virtual tape drive appears online to the host 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.
l Ready — 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, Virtuent, the virtual tape emulation 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-display Mount 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 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.

High availability features

DLm includes failure recovery mechanisms in various parts of its architecture to ensure optimum
availability.

VTEC
DLm delivers enterprise-class availability and scalability through a modular design based on high-
performance, highly available VTEs.
l 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.
l DLm8500 configured with two VTEs or more has a shared IP address to ensure high availability
for management functions. If the primary Management VTE (VTE1) fails, the secondary
Management VTE (VTE2) takes over as the primary, and the shared IP address moves over to
that Management VTE (VTE2).
l The configuration files are saved on the Management VTEs to allow quick and easy restoration
if a VTE is replaced.
l VTEs provide redundant data and control paths. The redundant data path provides failover to
protect against link failures, network card failures, and switch failures.
l In DLm8500, two 10 GbE switches provide a redundant data path, and two 1 GbE switches
provide a redundant management path.

Network connectivity failure checks

DLm provides the Data Network Packet Monitor to detect faulty ports or cables in the private
network.
The monitor is installed on the primary management VTE and runs once every hour. Using this
hourly data, it calculates the packet loss percentage for each data network port. If any one of

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 21
Overview of Dell EMC Disk Library for Mainframe

these ports exceeds the packet loss threshold of 5%, a call home is generated. The call home has
details about the exact port and the component that is affected. This data enables Dell EMC
customer Support personnel to troubleshoot the issue and resolve it.
The default threshold is 5%. If your data traffic warrants adjustments to the threshold, contact
Dell EMC customer Support.

Benefits
DLm offers many benefits over traditional tape including:
l Faster processing of tape mount requests (translating into shorter overall job step processing)
l No requirement for physical tapes (reducing the cost, storage, and potential for loss of tapes
and data).
l Support for data sharing across multiple VTEs (creating a level of data availability not found in
previous mainframe virtual tape systems).
l Support for low volume access of external physical tapes that allow the mainframe to write to
and read physical tapes.
l 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.
l 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.
l Support for replication of tape data between DLm systems and up to two local or remote DLm
systems.
l No single point of failure of mainframe tape data if the DLm system has more than one VTE.
l Support for two erase policies for space reclamation:
n Space — This is the default policy. When a file system reaches a specified percentage of
space usage (Recovery Percent general parameter), DLm begins erasing the oldest scratch
tapes in that file system until the amount specified in the Recovery Amount parameter has
been recovered.
n Time-to-live (TTL) — 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 TTL erase
options are: Days and Hours.
l Support for Secure Remote Services that provides secure, fast, and proactive remote support
for maximum information availability. Contact Dell EMC Customer Support to configure Secure
Remote Services.
Note: With DLm 5.0 and later, you can leverage the Dell EMC Usage Intelligence solution
included with Secure Remote Services. Usage Intelligence provides the capability to
collect, transfer, analyze, and report software usage and entitlement data across Dell EMC
products. Contact [email protected] for more information.

22 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
CHAPTER 2
DLm Operations

This chapter explains the routine DLm operations.

l Management access to DLm................................................................................................. 24

l License activation..................................................................................................................24
l Starting and stopping tape devices....................................................................................... 30
l Key Management Interoperability Protocol ........................................................................... 31

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 23
DLm Operations

Management access to DLm

The first two VTEs in a multi-VTE DLm (VTE1 and VTE2) provide management and support access
to the DLm system. These VTEs are called Management VTEs. If the DLm has only one VTE, that
VTE functions as the Management VTE. The Management VTEs also connect to the management
LAN of the DLm system. They act as the gateway, providing access to the . Management VTEs
also function as the firewall isolating the internal DLm networks from your LAN.
This VTE provides a user-friendly GUI called DLm Console to execute various setup, monitor, and
configuration tasks.

License activation
DLm 5.0 and later require license installations for the VTE OS. Each DLm has its own basic license
called the VTE OS license, which covers the generic DLm functionality. You must activate the
license and provide the activated license certificate (eLicense file) to the Dell EMC service
personnel during installation.
The following table lists the VTE OS licenses for different DLm models.

Table 4 VTE OS licenses for DLm models

DLm Model Model Number of License Description

DLm8500 with PowerMax 458-002-368 (DLm5-VTEOS) DLm8500 – VTE OS License

456-113-436 DLm5 VTEOS Storage Group 8:

(ECS)

GDDR Tape license: 458-002-370 DLm5 GDDR Tape (456-113-447:

DLm5 GDDR Tape License)

DLm 5.x feature licenses: 458-002-374 DLm Long-Term Retention

(456-113-455 DLm Long-Term
Retention License)

458-002-375 DLm Encryption (456-113-456 DLm

Encryption License)

458-002-377 DLm Guarantee Replication

(456-113-458 DLm Guarantee
Replication License)

Overview of the activation procedure

An overview of the process to activate a license for DLm.
About this task
Do this to activate a license and install it on DLm:
Procedure
1. Receive the License Authorization Code (LAC) by email.
2. Follow the instructions in the LAC to activate software.
3. Save one or more license files.
4. Provide the license files to the Dell EMC service personnel during installation.

24 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Operations

Receiving the LAC and activating the license

This section describes the procedure to receive the LAC and activate the license.
Before you begin
You will receive an email with the LAC and a link that enables you to activate the software.
About this task
The following figure shows a sample email.
Figure 8 Sample LAC mail

Procedure
1. In the email, click the Click here link under Activating Your Software.
This takes you to the Dell EMC Software Licensing Central portal.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 25
DLm Operations

Figure 9 Confirming site details

2. The registered company name and address is listed in the Step 1: CONFIRM COMPANY &
SITE page.
l If the details are correct, click NEXT: REVIEW.
l If the details are not correct, click Change Site, edit the details, and then click NEXT:
REVIEW.

26 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Operations

Figure 10 Reviewing the selection

3. In the Step 2: REVIEW YOUR SELECTIONS page, the default email ID to which the license
keys should be sent is displayed. Click Email to more people if you want to add more email
IDs.
4. Click Add notes to this transaction to enter any remarks pertaining to this activation
transaction.
5. Click ACTIVATE.
The license is activated.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 27
DLm Operations

Figure 11 License activation complete

6. Save the certificate in your local drive by clicking SAVE TO FILE.

You will need to upload this certificate in DLm Console later.
7. You can print the certificate by clicking PRINT CERTIFICATE or view the certificate by
clicking VIEW CERTIFICATE.
8. You can also view a copy of the license key by clicking View license key.

28 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Operations

Figure 12 Viewing the license key

9. Provide the license file to the Dell EMC service personnel for installation.

Installing the license on DLm Console

Perform these steps after activating the software and saving the license.
Procedure
1. Log in to the DLm Console.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 29
DLm Operations

2. Navigate to the External > Licensing tab.

3. Click Browse... and select the license file that you saved after activation.
4. Click Install.
On successful installation, DLm Console displays the message: "Upload completed
successfully".
5. Click OK.
6. The newly installed license is listed when the page refreshes.
Figure 13 License installed on DLm Console

7. You can delete a license by clicking the corresponding X button.

Starting and stopping tape devices

About this task
To start or stop the virtual tape devices you must start or stop Virtuent. You can control Virtuent
through the VT Console.
Note: Before Virtuent is restarted, you must vary all DLm devices offline to the host.

The commands for starting and/or stopping tape emulation on a VTE are:
l STARTVT to start Virtuent and activate devices in the installed configuration file.
l STOPVT to stop Virtuent. Once Virtuent stops, the channel links are disabled and all virtual
drives cease to respond to the host until Virtuent restarts. Any I/O from the host while
Virtuent 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 Virtuent.
STOPVT will not terminate Virtuent if any virtual drives currently have volumes loaded.
l STOPVT! to terminate Virtuent while volumes are loaded. Any virtual tapes currently loaded
will be immediately unloaded without any further processing.

30 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Operations

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 VTEs must be brought down
immediately. Any virtual tape volumes currently being written should be considered invalid.
When Virtuent is active, the VT Console shows the VT status as "Running." Informational,
warning, and error messages from Virtuent scroll on the console.
To start or stop the virtual tape devices:
Procedure
1. Access the DLm Console :
a. Open a web browser and type the Management VTE's HA IP address as follows:
https://<IP address>

b. Type the DLm Console user name and password in the login page.
2. Open the VT Console from the System status tab for the appropriate VTE.
3. Type the appropriate command: STARTVT, STOPVT, or STOPVT!
Note: Before Virtuent is stopped or restarted, you must vary all DLm devices offline to
the host.
For example, to start Virtuent, type:
STARTVT
The blue bar at the bottom of the VT Console displays the changed status of Virtuent.

4. Type quit and press Enter, then click on X to close the VT Console window.

Key Management Interoperability Protocol

Key Management Interoperability Protocol (KMIP) is an industry-standard protocol allowing
encryption clients to access any industry key manager which supports the KMIP standard. DLm
supports KMIP to enable third party key managers for obtaining keys to encrypt and decrypt
virtual tape volumes.
Dell EMC customer support personnel configure and initialize KMIP on the VTEs and define
channel devices for KMIP encryption.
You must provide the following to enable the support personnel to configure KMIP:
l CA certificate (.pem file)
l CA revocation list (CRL)
l Client certificate/key (.p12 file)
l Password for the client certificate/key .p12 file
l IP Address and port for the KMIP server
KMIP certificates may have an expiration set on them. New certificates must be uploaded
preferably prior to the expiration date.
Note: If you know the expiration dates of any of the certificates, contact Dell EMC customer
Support personnel on time to get new certificates installed before the old ones expire.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 31
DLm Operations

32 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
CHAPTER 3
DLm Administration

This chapter explains the DLm administrative tasks.

l Tape libraries......................................................................................................................... 34
l Configuring virtual devices.................................................................................................... 37
l DLm Long term retention...................................................................................................... 46
l Configuring Migration Policies on the Migration Policies tab in DLm Console........................ 51
l DLm Console Migration Policies tab fields............................................................................. 53
l Managing configuration files................................................................................................. 54
l Tape erase.............................................................................................................................59
l VTE logs and DLm statistics.................................................................................................. 60
l Virtuent command interface.................................................................................................. 67
l DLm diagnostic reporting...................................................................................................... 68

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 33
DLm Administration

Tape libraries
This section provides a description about Tape libraries.
A virtual tape library is controlled by a top-level directory that is stored on the system disks of a
VTE. Each file system 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 file systems that are mounted under
the top-level directory to store tape volumes.
For example, /tapelib<string>/DD1_P1_FS1,
where /tapelib<string> is the top-level directory and /DD1_P1_FS1 is the subdirectory.
DLm stores any number of VOLSERs in the file systems within the library until space within the file
systems is depleted. More file systems can be added to the library at any time without disrupting
the operation of the library. When a new file system is available, DLm automatically begins using it
when creating tape volumes. Each tape volume (VOLSER) is stored as a single file on one file
system.
Like real tape volumes, virtual volumes are written, read, and scratched. Once a VOLSER has been
scratched within the library, it can be reused during a future tape allocation process.
Tape libraries enable multiple storage classes to be defined. Each file system defined to a virtual
library is assigned to only one storage class. The storage classes are identified by numbers; for
example: 0, 1, 2, and so on, If you do not define a class, the file system you define is assigned to
the default storage class 0.
Note: Valid storage classes are 0-100.

Storage class recommendation

Storage classes are numeric classes that enable you to define groups (classes) of tape volumes
(VOLSERS) within a tape library.
Note: It is recommended that you use a Virtuent class other than 0 for LTR file systems. Class
0 is the default storage class; therefore do not use it for special types of file systems.
If you must use Class 0, then enter 0 explicitly in the Storage Class field on the Storage >
Available tab in DLm Console instead of leaving it empty.
The following table describes the classes and when to use them.

Table 5 Storage class considerations

Storage Class Meaning Notes

0 Default storage class. l Assign all LOCK file systems to Storage

Class 0
l It is strongly recommended, as a best
practice, that you do not use Storage
Class 0 for special type file systems
l If you must use Storage Class 0, enter 0
explicitly in the Storage Class field on
the Storage > Available tab of the DLm
Console

34 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Administration

Table 5 Storage class considerations (continued)

Storage Class Meaning Notes

1-100 Defines special storage l It is recommended, as a best practice, to

classes. assign special file systems to storage
classes other than 0 (classes 1-100).
l Use the range 1-100 to define classes. in
which the customer will assign VOLSERs
that must meet specific requirements
(for example, replication), or other
customer-defined special classes

Blank (none Same as class 0. l Do not leave the Storage Class field
defined) blank (empty) for special file systems

Example - Replication file system storage classes, for example, using storage classes, you can
isolate data recovery (DR) tapes that are replicated to a remote location from work tapes that are
stored only locally.
l You might create Storage Class 2 for data recovery (DR) tapes that are replicated to a remote
location.
l You might create Storage Class 3 for work tapes that are stored only locally.

Initializing DLm 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.
About this task
Run at least one INITIALIZE command in a VT Console before you start any tape drives on DLm.
Otherwise, no scratch tapes are available for use within the DLm system.
A DLm tape library is made up of one or more file systems.
Note:
l DLm supports a maximum of 275 concurrent NFS file system mounts at startup.
l DLm supports a maximum of 80 K tapes per NFS file system mounts at startup.
If you exceed this concurrent mounts threshold at startup, you might see errors during VTD start
that indicate problems while attempting to verify all the tapelib directories.
If all the VTEs have the same /etc/fstab (in the same order), they may all fail to mount the same
file systems. You will not have access to tapes in file systems that failed to mount to the VTEs.
Exceeding the maximum tapes per file system can impact:
l Mount Performance, Internal Virtuent checks
l Tapelist and space reporting
l Configuration of install timeouts
The tape library 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.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 35
DLm Administration

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.
Use the INITIALIZE command to initialize tapes:
INITIALIZE VOL=volser DEV=devname COUNT=count CLASS=n DIR=dirname
where:
l volser is the starting serial number to initialize.
l devname is the device name (address) of any tape drive pointing to the tape library.
l count is the number of serial numbers to initialize.
l n is the class these volumes are to be added to. CLASS is a required parameter unless the DIR
parameter is used.
l dirname optionally specifies the subdirectory to create the volumes in. 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.
This parameter is only allowed when the Enhanced File system Architecture option is enabled.
Otherwise, the target directory is derived from the first two characters of the VOLSER.
Under the Enhanced File System Architecture, if DIR is not specified, INITIALIZE spreads the
tapes between all the file systems it finds within the storage class. However, if you want to
initialize the scratch tapes only in a specific directory, use the DIR parameter to specify that
directory.
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 file systems
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=1
INITIALIZE VOL=001000 DEV=E980 COUNT=1000 CLASS=2
Note: Since the INITIALIZE program automatically generates VOLSERs starting with the
VOLSER specified with VOL=, ensure you do not overlap VOLSER ranges when entering these
commands.
In the example above, VOL=000000 COUNT=1000 will result in 1,000 tape volumes being created in
the library with serial numbers ranging from 000000 to 000999. VOL=001000 COUNT=1000 will
result in the creation of volumes ranging from 001000 to 001999. 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 are 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 DLm z/OS components.

36 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Administration

Defining tape libraries

This section describes how to define a tape library.
About this task
Dell EMC service personnel define tape libraries during initial setup.
Note: At least one file system must be defined for each virtual tape library you intend to
define. It is also mandatory to define one small (10 MB) file system to use as a lock directory.
To provide the best overall performance, multiple file systems in each library are desirable. While
there is no strict limitation, a minimum of four file systems is recommended to enable the VTE to
balance output across all file systems in the library.
Note: DLm does not support a configuration where some VTEs use enhanced file system and
the other VTEs in the configuration use a DLm 2.x (legacy) style file system.
Dell EMC service personnel use the following steps to define a tape library:
Procedure
1. Create the file system on the back-end storage system using DLm tools.
2. Define the lock file system and other file systems in the 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.
The list of available libraries can be viewed in the Storage > Available tab of DLm Console.
Note: Make sure you do NOT delete the special purpose file systems, dlmconfig and
dlm_lock_fs.

Configuring virtual devices

You can define up to 512 virtual 3480, 3490, or 3590 tape drives on each DLm VTE.
During initial setup, Dell EMC service personnel define your devices based on the details that are
provided by your system administrator.

Planning considerations
This section describes the planning considerations.
l For z/OS systems, for each VTE, plan for one virtual device that will always be offline and can
be used by DLm utilities to communicate with the VTE.
l If you plan to run the DLm z/OS started task (DLMHOST), this requires two devices offline:
one to remain offline and be used by DLMHOST to communicate with the VTE, and one virtual
device if DLMHOST logging is requested.
Refer to the Dell EMC Disk Library for mainframe Command Processors and Utilities for z/OS Guide
for more details on DLMHOST.

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 file, you
will be working with this default configuration file. Optionally, you can create and use your own

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 37
DLm Administration

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 Configurations page allows you to select the configuration file for a VTE. You must save your
configuration 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.
Figure 14 Last Installation

Configuring global parameters

This section describes how to configure global parameters.
About this task
The DLm Console allows you to configure the virtual tape drives on a VTE.
Procedure
1. Access the DLm Console using the web browser:
a. Open a web browser and type the Management VTE's HA IP address as follows:
https://<IP address>

b. Type the DLm Console username and password in the login page.
2. Once connected, click Configurations. In the Configurations operations tab, make sure
the correct configuration is selected in the drop-down list in the upper left corner of the tab.
3. Click Devices to display the Tape device configuration panel.
This panel contains a tab for each available VTE.

38 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Administration

Figure 15 Global options

4. Click the tab pertaining to the VTE you want to configure.

5. Enter values in the fields under Global options at the top of the Devices panel:
a. In Warn at, select the percentage of disk space usage at which DLm will begin to warn
about usage.
Each time the contents of a file system changes, the VTE checks the space used against
this value. If the used space in the file system is at or above this value, a warning will be
issued. The valid range is 0 to 100. The default is 88%.

b. In Erase policy, select the erase policy you want the VTE to use when recovering space
on scratched tapes: Space, Time-to-Live (TTL) in days or hours, or Both.
Erase policies cannot be changed by a SET command. This is a global parameter which
applies to all tape library directories of a VTE.
Note:
Tape erase provides more information about DLm’s erase policy.

c. In Start space recovery at, select the percentage of disk space usage at which DLm
starts to recover disk space by deleting the data from scratch volumes.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 39
DLm Administration

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.

d. In Recover amount, select the percentage of free space to recover.

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

e. In Erase scratched tapes after, enter the maximum duration in hours or days for which
the data of a scratched tape will be retained before automatic space recovery starts, and
select hours or days.
Note: This field is visible only if the Erase policy option TTL or Both is selected.
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 provides more information.

f. Select the Use default lock FS check-box to use the default DLm lock directory.
g. Under Additional parameters, click on the Add free-form parameters link or the
parameters next to Additional parameters to specify any global free-form configuration
parameters you want.
In addition to the pre-defined global configuration parameters described in the previous
steps, you can manually enter global free-form configuration parameters into the
configuration.
Note: Global additional parameters must be entered using the format:
PARAMETER<space>VALUE. For example, AMDD OFF.

Adding devices
This section describes how to add devices.
Each Devices > VTEx tab contains Add devices and Current devices fields.
In the Add devices fields, you can define virtual tape devices (drives) to be emulated by this VTE.
Current devices lists the currently-configured virtual tape devices for the VTE. You can add new
devices to the existing tape libraries or create new tape libraries and allocate devices to them.
Note: Contact Dell EMC Customer Support to have a file system created for the new tape
libraries.

Adding virtual devices

About this task
Define the virtual tape devices (drives) to be emulated to the mainframe by this VTE starting with
the Control Units (CUs) section.
Note: File systems must be created by Dell EMC personnel during initial setup before you add
devices.

40 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Administration

Procedure
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:
a. In the Control Units text box, type the hexadecimal control unit number that you are
configuring.
Valid values are 00–FF.

b. From the Type drop-down list, select the device type to be emulated: 3480, 3490, or
3590.
Note: All devices on the same Control Unit must be the same type.

c. From the Subsystem drop-down list, select the subsystem number.

Figure 16 Control units

2. Click the + button to complete the addition.

The Control Unit is added to the list and an Add devices configuration section is displayed
as follows:

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 41
DLm Administration

Figure 17 Adding devices

3. Enter values in the fields of the Add devices section to configure the corresponding
parameters for each device:
a. In Control Unit, enter the hexadecimal control unit number that you are configuring
(from the drop list that is provided of the Control Units section defined).
b. In Unit address (UA) range, enter the starting and ending hexadecimal device unit
addresses that you wish to add to the VTE.
You can define sets of 16 or multiples of 16 (n0—nF).

c. In Initial device name, enter a unique name of 1–8 characters for the address.
Each DLm system must have a unique device name. Dell EMC recommends using the
same device name that is defined in the UCB name in the mainframe operating system.
The name that 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 this field, the
configurator names the 16 devices E900, E901, E902, ... E90F.

d. From the drop-down menu in Tape Library, select a tape library to which this device is
connected.
For example: /tapelib.
To be displayed 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.

42 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Administration

e. In IDRC (Improved Data Recording Capability), specify whether to turn on or off write
compression of the data that DLm writes to the library.
The available values are Yes, No, and Force. The default value is IDRC=Yes.
When IDRC is set to Yes, 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 JCL. DLm only
compresses data with a block size of 100 bytes or more.
When IDRC is set to No, the VTE does not compress the data that it writes to a virtual
tape disk file, despite instruction from the mainframe. When IDRC is set to No, the VTE
still reports to the host that it supports compression but it does not perform any
compression on the data it writes to the disk. This is because some host operating
systems or tape managers do not use drives that do not support compression.
IDRC=No affects only the writing of data. When IDRC is set to No, the VTE can still read
(decompress) virtual tape volumes that it previously wrote with compression on.
IDRC=Force configures the DLm virtual tape device to compress the data it writes to a
virtual tape disk file regardless of the mainframe's instructions to the VTE regarding the
tape file and regardless of whether the tape resides on a deduplicating file system.

f. [For ECS file systems only] In the Encryption key class field, enter a valid KMIP class to
enable the drives to do encryption.
When this option is configured, the tape drive makes a call to the KMIP Key Manager
using this key class each time the drive opens a tape volume for output.
Note: Key class must correspond to the one specified on External > Encryption
page. Key class always starts with "KMIP_" prefix to enable KMIP keys encrypted
tapes on a device.

g. In Additional parameters, code any optional keyword parameters you want assigned to
the devices being created:
l GROUP=nn—nn is any decimal number. GROUP should be coded whenever DLm is to
be used with VSE systems. When the VSE utility DLMMOUNT or a VSE tape manager
requests a mount on “any” drive, only virtual drives in the same GROUP as the
requesting drive are considered for the mount. All virtual tape drives attached to the
same VSE system or guest should have the same GROUP, and each VSE system
should use a different GROUP number. When not coded, all drives default to
GROUP=0.
l LABELS=S/N/A — Most operating system mount requests specify a label type, but for
those that do not, the LABELS parameter sets the default label type for the drive.
The label types are:
S = IBM standard (EBCDIC) labels (the default)
N = Unlabeled
A = ANSI (ASCII) labels.
The label type affects only the 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.
l SIZE=maxvolumesize — This parameter limits the maximum size of an individual
tape volume. The maximum volume size can be specified in any of the following:
- bytes (SIZE=nnnnnn)
- kilobytes (SIZE=nnnK)
- megabytes (SIZE=nnnM)

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 43
DLm Administration

- 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).
If omitted, the maximum volume size defaults to 2G (2 gigabytes) for 3480 or 3490
tape devices, and 40G (40 gigabytes) for 3590 tape devices. The maximum allowable
tape size for 3480 or 3490 or 3590 tape devices is 32T but is limited to the amount of
available storage in the file system. The minimum tape size is 15M (15 megabytes).
l TRACE=n — This parameter allows you to set the trace option for this specific device.
Available trace levels are:
0 — No tracing (default)
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)
l 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 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. You can change the configuration of individual devices in the Current
devices section.

Deleting a device range

Procedure
1. After connecting, click Configurations. In the Configuration operations tab, make sure the
correct configuration is selected in the drop down list in the upper left corner of the tab.
2. Select the Devices menu at the top of the page and select the correct VTE tab.
3. Scroll down to the Current devices section.
4. Scroll to the range of devices that you want to delete and click the X button on the right
side of the control unit box.

44 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Administration

5. Select the Configurations tab at the top of the screen.

6. On the Configurations panel, click Save Changes to save your configuration to disk.

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 scratch tape. Then, on a mount
request the TMS will request a scratch tape by sending its pool name (rather than by requesting
SCRTCH or PRIVAT). In support of scratch tape requests by pool name, 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.
The field in the Scratch Synonyms section under Global options of the device tab lets you
include whatever names your installation uses to request scratch tape mounts. DLm recognizes
these synonyms, along with SCRTCH andPRIVAT, as a request for a scratch volume when they are
in a load display CCW. A scratch synonym is defined for each storage class. To allocate tapes to a
storage class, a scratch synonym must be associated with that storage class.

Adding scratch synonyms

About this task
To add scratch synonyms (tape pool names):
Procedure
1. Define a scratch synonym in the following format in the Scratch Synonyms section under
Global Options:
synonym=(prefix1,prefix2,…CLASS=(CLASSn,CLASSn,…))
where:

l 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. DLm Console converts the synonyms to
upper case.
l prefixn is a set of VOLSER prefixes that may be associated with a scratch synonym.
Each prefix can be from 1 to 6 characters in length. prefixn defines the prefix
characters of the VOLSERs that can be assigned in response to a scratch request made
with this synonym. For example, SCRTCH=(00,01)would indicate that any load request
received for SCRTCH must be satisfied with a VOLSER that starts with either "00" or
"01". Valid VOLSERs that could be mounted by DLm would include any VOLSER in the
range 000000–019999, assuming only numeric VOLSERs are in use. If there are no
scratch tapes with VOLSERs beginning with "00" or "01" then DLm does not mount a
tape and the mount will remain pending. If a VOLSER prefix is not defined for a specific
scratch synonym then any available scratch tape will be used.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 45
DLm Administration

l CLASSn defines the storage class or classes associated with this scratch synonym. For
example, PRIVAT=CLASS=CLASS1 would indicate that any load request received for
PRIVAT must be satisfied by allocating a scratch VOLSER in storage class 1. DLm
normally selects which storage from which to allocate a scratch tape based on free
space and frequency of file system use. When a synonym specifies a specific class of
storage be used, DLm first identifies all file systems assigned to the storage class (or
classes) and then selects a file system from those file systems 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.

Scratch synonyms example

Consider the following definitions of scratch synonyms:
WORK
SCRTCH=(00,01)
PRIVAT=CLASS=CLASS1
In this example any mount requested with the synonym WORK will be assigned any available scratch
tape in the default storage class 0.
A request for SCRTCH will also go to default storage (class 0), but will only be assigned a volume
with a serial number beginning with 00 or 01. If no scratch tapes with these prefixes are available
the mount will not be satisfied and will remain pending.
PRIVAT tapes will be allocated from 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:
l DRTAPE=(00,01),CLASS=(CLASS1,CLASS2) defines two synonyms, DRTAPE and CLASS.
DRTAPE will use volume serial numbers beginning with 00 or 01 in Class 0 storage. CLASS will
use only VOLSERS of CLASS1 and CLASS2.
l 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.
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.

DLm Long term retention

The DLm Long Term Retention (LTR) feature moves virtual tape files that have not been accessed
by the host through Virtuent for a configurable, policy-based period of time from normal tapelib
storage to LTR storage. The assumption is that LTR storage will be second-tier, cheaper, possibly
“lights out” storage, and could be offsite (for example, in the cloud). DLm8500 offers low cost
ECS solution for LTR.
LTR storage resides outside of “normal” tapelibs; but a tape that resides on LTR storage will be
accessible by Virtuent if a migrated tape is requested by the host.
Dell EMC service personnel initialize each of the LTR source tape libraries during initial setup.
Note: Whenever new storage is added after the initial setup, contact Dell EMC Professional
Services to initialize tape libraries for LTR.

46 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Administration

LTR file systems

LTR storage is defined and created in the same manner that other file systems are defined and
created. You must enable LTR for the file systems in DLm Console.
The following are the special characteristics of LTR storage:
l LTR storage will be mounted outside of the normal tapelib mount points. They are not
physically a part of any tapelib directory tree, and no devices will be allowed to point to them
with a PATH parameter, either in the configuration or with the SET command.
l All LTR file systems will be mounted in subdirectories that reside under a common grandparent
directory named /ltr, which resides on the VTE “/” file system.
l To be used for LTR storage, each LTR file system will be associated with a single DLm tape
library.
l Virtuent will recognize the association between tape libraries and LTR file systems solely based
on LTR mount point naming convention. Under the common /ltr grandparent directory, there
will be directories that exactly match (“shadows”) the names of associated tape libraries. For
example, the LTR storage /ltr/tapelibPROD would be associated with the tape library /
tapelibPROD.
l Once moved to LTR storage, tapes never migrate back to tape library storage until they are
scratched.
l Tapes that have been migrated to LTR storage can be accessed (mounted) by Virtuent when
requested by explicit VOLSER. They can be read and written to just as if they resided on
regular tape library storage (with a possible reduction in throughput, depending on the LTR
storage type).
l The Virtuent FIND command does not search LTR storage because it is not part of any active
tape library. However, it does indicate that the volume is on LTR storage. No other
characteristics will be printed.
l The Virtuent QUERY SPACE command does not see LTR storage because it is not part of any
active tape library. A new LTR option can be specified for the QUERY SPACE command that
lists information about LTR storage.
l The Guaranteed Replication and Replication on RUN features are not supported on LTR
storage.
l Tapes in quiesced tape libraries will not be moved to LTR storage.

Defining LTR Filesystems

Procedure
1. Log in to DLm Console.
2. Ensure that the LTR feature is activated on DLm Console External > Features page.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 47
DLm Administration

Figure 18 LTR feature activation

3. Navigate to Storage > Available.

Figure 19 Configuring LTR

4. To designate a file system as LTR target storage, check the LTR checkbox.
5. Enter the class for the LTR file system in the Storage class field. Storage class becomes a
mandatory field when you select LTR.
Note: The Class value must be unique for each LTR file system associated with the same
tape library.
DLm Console automatically adds “/ltr” to the front of the Mount Point name when LTR is
selected. When a previously checked LTR checkbox is un-checked DLm Console removes “/
ltr” from the front of the Mount Point name.

6. Click the VTEn tab.

7. Under Active, select the LTR file systems that you intend to use as LTR target storage.
These file systems will be mounted on the VTE.

Parameters for LTR policies

You must specify the following parameters to define a policy for migration to LTR storage:
l The “from” tape library and class
l The age, specified in number of days, at which time a tape should be migrated to LTR storage
l The minimum file size specified in Kb/Mb/Gb
l Optional limits as to the day(s) of the week and time(s) of day to perform the moves

48 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Administration

l Type of modification for moved tape (compressed/uncompressed)

l The length of time, specified in number of hours, between when a tape is migrated to LTR
storage and when it is deleted from the tape library storage
l The VTE(s) on which the LTR migration tasks should run
l The Max Tasks number of tasks to be started on each of the VTEs specified. This is the
maximum number of tapes that will be moved concurrently for this policy on each of the
specified VTEs.

Configuring LTR policies

About this task
The target LTR file system is not explicitly specified in the policy; it is implicitly defined as the LTR
file system with the same name as the tape library (for example, /ltr/tapelibPROD for /
tapelibPROD) and the same class.
Procedure
1. Log in to DLm Console.
2. Navigate to Storage > LTR Policies.
3. Under LTR Policies configuration, click Add next.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 49
DLm Administration

Figure 20 Configuring LTR policies

4. Specify valid values in the following fields:

l Enabled: Select Enable to switch on LTR policy. If it is unchecked, the policy is disabled
but all the parameters of the policy will be saved.
l Name: Enter a name for the LTR policy. It can contain only alphanumeric characters,
dashes, and underscores. It can have a maximum length of 30 characters and cannot be
empty. The name value is not case sensitive.
Note: The name of a policy must be unique.

l Source Tapelib: Choose one of the tape library names from the drop-down box as a
source for moving to LTR storage. Selecting a tape library enables the Source Storage
Class field.
l Source Storage Class: Choose the storage class for which this policy is being defined.
l Move after: Enters the age at which tapes under this policy will be moved to LTR
storage. This value must be specified in number of days from last access (last Virtuent
unload of the tape). Any positive number is valid. The maximum value is 730 days (2
years) and the minimum is 0 day.
l Move/Do not move during:

50 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Administration

Specify when the filesystems should or should not be moved to LTR storage. Move is
selected by default.
n The first checkbox on each line allows selecting the days where moving will be started
if the Move option has been selected or will not be started if the Do not move option
has been selected.
n Specify the time periods for each day of the week using the start and end fields.
n The All day checkbox allows you to specify hours from 00:00 to 23:59.
l Delete after: Specify the number of hours that Virtuent should leave the original file in
the tape library after moving it to LTR.
The valid values are 0 - 24 hours. The default is 0, which deletes the information
immediately after the VOLSER is moved.
l Minimum tape size: Specify the minimum size of tape for which moving will be
performed. You can specify the size in Kilobytes (Kb), Megabytes (Mb) and Gigabytes
(Gb) by choosing appropriate unit from drop-down list. The minimum value is 0 Kb which
is the default.
l Tape modification: Select the type of tape modification when it is stored in the LTR
filesystem: Uncompressed or Compressed. Uncompressed is selected by default.
l Apply to VTE’s: Select the VTE(s) on which the move policy tasks should run. The
number of tasks specified in Max Tasks will be started on each of the VTEs specified.
Only the VTE(s) on which filesystems with the particular storage class was marked as
active are displayed.
l Max tasks: Select the maximum number of concurrent tapes that should be moved at
the same time under this policy on each of the specified VTEs. The maximum value is 5
tasks and the minimum is 1 task. The default is 1 task.
Note: Specifying too many concurrent moves may impact the overall VTE or DLm
performance.

Configuring Migration Policies on the Migration Policies tab in

DLm Console
Procedures for defining and configuring DLm Data Migration Policies in DLm Console.
About this task
To configure DLm Data Migration policies in DLm Console:
Procedure
1. Ensure that the migration feature is activated on DLm Console External > Features page.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 51
DLm Administration

Figure 21 Migration feature activation

2. Go to the Storage tab.

Figure 22 DLm Console Migration Policies tab

3. Select the Migration Policies tab.

4. To create a Migration policy, click Add next. The following illustration shows the fields to be
defined for each policy:
Figure 23 DLm Console Migration Policies tab options

52 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Administration

DLm Console Migration Policies tab fields

A list of the available fields on the DLm Console Migration Policies tab.
The Migration policies configuration page contain the following fields:
Enabled:
If checked, this policy is enabled automatically upon Virtuent startup. If not checked, the
policy does not start automatically, but can be enabled at any time with the MIGRATE
ENABLE command.

Name:
Defines a unique name for this Migration policy. The policy name can contain only
alphanumeric characters, dashes, and underscores, up to 30 characters. The name value is not
case sensitive (for instance - “PROD-AllDays-vte2” and “prod-alldays-vte2” are the same
names). The policy name is used as an input parameter for various Virtuent MIGRATE
commands, and is displayed in various messages about the policy.

Source Directory:
A drop-down box displays all defined tape library directories. Choose one of the tape library
directories as a source that this policy should migrate tapes from.

Target Directory:
A drop-down box displays all defined tape library directories. Choose one of the tape library
directories as a target that this policy should migrate tapes to.

Move after:
Defines the age at which tapes under this policy will be eligible to be migrated. Age is defined
as the number of days since Virtuent last unmounted the tape. Any positive number between
0 and 730 days is valid. Zero means that an age criteria is not applied, and a tape of any age is
eligible for migration at any time.

Move/Do not move during:

Specifies when moves should be performed (with the “Move” option, which is the default) or
moves should not be performed (with the “Do not move” option).

Tape modification:
There are two choices for the Tape modification field, Compressed and Uncompressed. If
Compressed is selected, all migrations will compress the target tape during the move (even
those written with AMDD to Data Domain filesystems). If Uncompressed is selected, all target
tapes will be written without compression.

Migrate scratch tapes

If checked, scratch tapes will be migrated.

Apply to VTE’s:
A check box to select which VTE(s) should use this policy. Multiple VTEs can be selected to
run the same policy. Check boxes are only displayed for VTE(s) that are configured to use the
Source and Target Directories selected above.

Max tasks:
Sets the maximum number of concurrent tapes copies that should be performed at the same
time under this policy on each of the specified VTEs. The minimum number is 1 (the default
value) and the maximum number is 5. Specifying a larger number will ensure that more tapes

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 53
DLm Administration

will get migrated in a shorter time, but the VTE will expend more resources doing so, and
could impact overall VTE or DLm performance.

Managing configuration files

The DLm Console lets you manage configurations in the following ways:
l Activating or installing a configuration on selected VTEs
l Creating a completely new configuration
l Editing a configuration
l Saving a configuration file
l Deleting a configuration

Activating or installing a configuration on selected VTEs

Saving a configuration does not automatically install it on the VTEs. 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.
About this task
Installing a configuration may often require a Virtuent restart, which may result in boxed devices.
DLm provides fields that enable you to check if a Virtuent restart is required. You can also ensure
that Virtuent is not restarted unless you specifically select the option to allow a restart.
Note: If Virtuent must be restarted when the configuration is installed, you must vary all DLm
devices offline before installing the configuration.
Ensure that all VTEs that this configuration will be installed on are powered up and running before
clicking Install on nodes.
To install (and activate) your configuration on selected VTEs:
Procedure
1. Click Configurations > Configuration operations tab and select the configuration to install.
The Configuration field at the upper right corner of the screen identifies the current
selected configuration. If necessary, select the configuration from the drop-down box.

54 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Administration

Figure 24 Configuration operations — Activating or installing a configuration

2. At the bottom of the page, select the VTEs on which you want to check if installing the
configuration will require a Virtuent restart.
3. Click Check on nodes.
This shows you if a Virtuent restart is required for any of the selected VTEs.
4. If any changes were made to the configuration and they are not yet saved, you can save or
discard the changes by clicking the Save changes button or the Discard changes button,
respectively.
5. Select the Restart Virtuent if required check box, if you want to proceed with installing
the configuration even if it requires a Virtuent restart. If it does not require a restart, you
need not select the check box.
Leaving it unselected will result in the following:
l If no restart is required for a particular VTE, the configuration is installed.
l If a restart is required for a VTE, No changes are applied. The process stops.
6. Click Install or Install basic settings.
This enables the Install on nodes button.
l Click Install basic settings if you want to install only the basic settings such as Network,
Messages, NTP, Encryption, and DLMAUT.
l Click Install if you want to install all settings including Storage, File systems, Tape
libraries, Tape devices, and LTR policies.

7. Select the VTEs on which to install the configuration file.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 55
DLm Administration

8. Click Install on nodes.

The configuration is installed on the selected VTEs.
The Apply log window opens, showing the status and results of the configuration
installation.
On the Configurations tab, the Last Installation field identifies the active, installed
configuration file.

Results
Note: In multiple-VTE configurations, all VTEs must be powered on and running when you click
Install.
CAUTION When you click Install, Virtuent may restart if the Restart Virtuent if required box
is checked. If your VTE is currently online to the mainframe, Dell EMC strongly recommends
that you idle all tape drives and vary them offline before installing the new configuration.
If your DLm system has multiple VTEs, Virtuent on every VTE detects a change to its current
configuration and automatically restarts. 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.

Creating a new configuration

You can create a new configuration using one of the following method:
Note: The configuration name should only contain Latin ASCII characters. White spaces,
periods (.), commas (,), and non-ASCII characters are not supported.
l Copy an existing configuration to a new file — Use this method to create a new config file that
would need a few changes from the copied one. You can make needed edits to the new file and
save the new config file.
or
l Create a completely new configuration — Use this method to create a completely new file
containing only some default values. You may need to edit all of the tabs.
Note: Make sure you edit the Network address with the correct customer IP network
address for the HA, VTE1, and VTE2 (if the DLm has more than one VTE).

Creating a completely new configuration

Procedure
1. Select the Configurations tab in 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.

Copying a configuration
Procedure
1. Select the Configuration menu in the DLm Console.
2. At the upper left corner of the page, select the configuration you want to copy.
3. From the list box near the Copy to field select the configuration to which the configuration
file must be copied.
You can also copy to a new file by selecting new file from the list and specifying a name.

56 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Administration

4. Click Copy to.

5. Make the necessary changes for the configuration.
6. Click Save changes.

Uploading a configuration
About this task
You can upload an existing configuration to configure the installation. To upload a configuration:
Procedure
1. Click Configurations > Configuration operations on the DLm Console.
2. Click Upload configuration button.
A pop-up opens asking you to browse.
3. Click Browse to search for a configuration on your local disk.
Figure 25 Upload configurations

4. Click Upload to upload the selected configuration.

Downloading a configuration
About this task
To save a copy of your configuration on your local storage:
Procedure
1. Click Configurations > Configuration operations on the DLm Console.
2. Select the configuration you want to download from the drop-down box.
3. Click Download configuration button.
A pop-up opens asking you to browse a location where you want to save the file.
Results
The configuration file is downloaded in the selected location.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 57
DLm Administration

Editing a configuration
When you select a specific configuration on the Configurations tab, all changes made to that
configuration on any tab will apply only to that selected configuration. For example, if you have
two configuration, config which is the default and a configuration named config1, and you
select config1, all changes that you make on any tab, for example, Devices, will apply only to
config1.
About this task
The name of the configuration that you are currently editing displays in the heading area at the top
right corner of the DLm Console window. For example, Configuration: config1.
To edit a configuration:
Procedure
1. Select the Configurations tab at the top of the DLm Console.
2. Select the configuration you wish to modify from the drop down list on the left.
Select the Devices tab at the top of the DLm Console and make the required changes.
3. Return to the Configuration menu and click Save changes.

Saving a configuration file

Procedure
1. Select the Configurations tab at the top of the screen.
2. On the Configurations panel, click Save Changes to save your configuration to disk.
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.

Deleting a configuration
Procedure
1. Select the Configurations tab at the top of the DLm Console.
2. Select the configuration you wish to delete.
3. Click Delete.
4. In a pop up window that appears, verify the deletion.

Installation history
To see the history of recent configuration changes, click Configurations > Installation history
tab.

58 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Administration

Figure 26 Installation history

Tape erase
DLm supports a space recovery feature that automatically erases data from scratch tapes on the
file system based on an erase policy.
The available erase policies are:
l Space
l Time-To-Live (TTL)
l Both (default)
The erase policy is a VTE-wide setting. The erase policy can be different on different VTEs. Dell
EMC recommends that the erase policy to be different on each VTE, so that all the VTEs do not
contend for the same volume. These erase policies affect only AWS-format scratch tapes (not flat
tapes nor physical tape cartridges). 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 Configuring global parameters.

Space erase policy

When a file system reaches a specified percentage of space usage, DLm begins erasing data in
that file system 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.

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

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 59
DLm Administration

tapes will automatically be erased regardless of current space utilization. The default TTL value is
365 days.
You can specify the time in:
l Days
l Hours
Note: 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 value starts recovering space. If that VTE cannot complete erasing
the scratched tapes before the next higher Time-to-Live value, the next VTE joins in and helps
to complete the space recovery.
For example, in a four-VTE system, if you set the Time-to-Live value of VTE4 to 48 hours, set
that of VTE3 to 36, that of VTE2 to 24 hours, and that of VTE1 to 12 hours.
In the case of this example, VTE1 starts erasing tapes that were scratched 12 hours ago. If it
cannot complete the recovery, VTE2 starts at the end of the twenty fourth hour. Both VTEs
recover space until all the tapes are cleaned up. If VTE1 and VTE2 cannot complete the space
recovery at the end of the thirty sixth hour, VTE3 joins VTE1 and VTE2 in recovering space.

Both
DLm starts erasing scratch data if either of the conditions — Space erase or TTL policy is
satisfied.

VTE logs and DLm statistics

The DLm Console allows you to view and gather the most recent VTE logs for diagnostic purposes.
It also provides statistics such as capacity or performance of the system.

VTE logs
VTEs maintain a log of all messages issued by Virtuent. 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.

Viewing the latest VTE logs

About this task
To view the latest VTE logs:
Procedure
1. Access the DLm Console using the web browser :
a. Open a web browser and type the Management VTE's HA IP address as follows:
https://<IP address>

b. Type the DLm Console username and password in the login page.
The System status tab of the Status menu opens by default.

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

60 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Administration

The logs appear in a new window or a new tab. Use Previous and Next to navigate through
the logs.

3. The Search Logs field enables you to search for the logs containing a particular search
string generated during a particular period.
a. Click on the Since first record link. A calendar widget pops up.
b. Select the date from which you want to see log details.
c. Select the time from which you want to see log details.
d. Click OK to close the widget. The date and time appear as a link.
e. Enter a search string in the text box. You can use an asterisk as a wildcard in the search
string. Search strings are case-sensitive; for example, "Scratch" will only find entries
containing the word "Scratch" with a capital 'S'.
f. Click Go. Clicking Go without a search string will list all the log entries since the specified
date and time.

Support data
About this task
To gather VTE details for diagnostic purposes:
Procedure
1. On the Status menu, click the Gather logs menu.
The VTEs are listed in the Machine name column.
2. In the Support data column, 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.
Figure 27 Gather logs

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 61
DLm Administration

VOLSER Listing
About this task
DLm Console provides a searchable list of tapes. The tapes listed can be filtered by library and
VOLSER. You can sort the columns of the table.
The columns are:
l VOLSER name
l Filename
l Scratch status
l Size
l Last modification date/time
l Last access date/time
To view the list of tapes:
Procedure
1. Access the DLm Console using a web browser.
2. Select the Status menu.
3. Click the Tape list tab. Sorted list of tapes and fields for search are displayed as shown in
the following figure.
Note: The VOLSER Listing database is updated on an hourly basis.

62 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Administration

Figure 28 VOLSER listing

Click on an item in the Directories field or the Volser field. The tapes in the directory are
listed. If you select a tape in the list, the details of that tape are displayed on the right.

Capacity statistics
About this task
The DLm Console displays capacity statistics of attached storage. It provides following features:
l The ability to download the graph data in comma separated value (CSV) format,
l The ability to select a new date and time range,
l A warning indicator indicating that the used storage is close to the maximum for the DLm
system, and,
l Indicators on how much storage in each area grew or shrank over the graph period
Procedure
1. Access the DLm Console:
a. Open a web browser and type the Management VTE's HA IP address as follows:
https://<IP address>

b. Type the DLm Console username and password in the login page.
2. Select the Status menu.
3. Click the Space tab.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 63
DLm Administration

4. Select the mount points for which you want to see the status.
5. Select specific date and time range by clicking on the Showing from date and time on the
screen and select a date and time range from the pop-up box to view the capacity used in
that time frame. Alternatively, you can also click and drag a range on the graph to zoom into
that selected area.
Figure 29 Capacity statistics

6. You can download the statistics in CSV format for use with spreadsheet programs by
clicking Download CSV. When prompted, select a location to store the resulting file.
Results
The capacity statistics displayed include the following metrics for the selected mount points:
l Capacity used
l Capacity free
l Number of active tapes
l Number of scratch tapes
l Percentage of tapes that is active
l Percentage of tapes that are scratch
l Percentage of capacity used by active tapes
l Percentage of capacity used by scratch tapes.
l Storage Limit Warning Indicator
l Trend Indicator

Performance statistics
DLm Console provides Performance statistics in the form of graphs with parameters like time,
channel, VTE, tapelib, and file system. You can select a date range to view statistics in that time
frame.
About this task
You can individually enable or disable the following change values:
l throughput

64 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Administration

l reads
l writes
l tapes mounted in period
l mount time
Procedure
1. Access the DLm Console using a web browser:
a. Open a web browser and type the Management VTE's HA IP address as follows:
https://<IP address>

b. Type the DLm Console username and password in the login page.
2. Select the Status menu.
3. Click the Performance tab.
The Performance statistics are displayed as shown in the following figure. You might only
see part of the data on the screen. To zoom into the entire data, hold down the left mouse
key and select you area. For example, if the last date on initial display of the chart is 21 April,
you can hold down the left mouse key and drag it to see data until the current date.
Figure 30 Performance statistics

4. To download a comma-separated values file (.CSV) for use with spreadsheet programs,
click the Download CSV link on the page. A prompt will appear asking you to select a
location to store the resulting file.

Downloading a replication report

About this task
DLm provides a report of the replication sessions in the system.
Procedure
1. Access the DLm Console:
a. Open a web browser and type the Management VTE's HA IP address as follows:
https://<IP address>
b. Type the DLm Console username and password in the login page.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 65
DLm Administration

2. Click Storage > Management.

System health check

DLm Console provides a Health check section under the Status > System status tab which allows
you to perform a full DLm health check.
About this task
The DLm system is configured to automatically run health check every hour unless automatic
health checks have been disabled. The results shown on the screen are from the most recent
health check that was completed, either automatically or through a manual user input.
Procedure
1. Access the DLm Console using a web browser.
a. Open a web browser and type the Management VTE's HA IP address as follows:
https://<IP address>

b. Type the DLm Console username and password in the login page.
2. Select the Status menu.
3. Click System status tab.
4. Click the Run DLm Health Check button to initiate health check.
Note: Health check initiates immediately, but the results from this may not be available
for some time, as health checks on very complex installations can take some time to
complete.

You can see the system status for each DLm component in the System status table. The
possible states reported after the health check are:
l OK
l Warning
l Check
l Error
Check and Error are both FAILED health check conditions that will send call home alerts. If
the health check summary is not available, DLm Console displays "Health check summary is
unavailable:" followed by the specific reason.

66 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Administration

Figure 31 System health check

Virtuent command interface

About this task
The DLm Console provides a menu-type interface to execute Virtuent commands. This interface
eliminates the need to remember the command set or refer to related documentation.
Procedure
1. Access the DLm Console:
a. Open a web browser and type the Management VTE's HA IP address as follows:
https://<IP address>

b. Type the DLm Console username and password in the login page.
2. Select the Status menu.
3. Click the Command tab.
The Virtuent Command Interface screen appears as shown in the following figure.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 67
DLm Administration

Figure 32 Virtuent command interface

4. From the System drop-down box, select the VTE for which you want to execute the
Virtuent command.
5. Select the command from the Command drop-down box.
Note: The Command drop down box provides the frequently used commands. Use the
VT Console if the required command or option is not listed.

6. Enter command option(s) in the Options text box. The syntax is displayed in the Options
Format field.
7. Click Execute to run the command.
Results
The output is displayed in the Command Output box.

DLm diagnostic reporting

The different subsystems of the DLm system generate messages as they operate. The major
sources of messages in DLm are:
l VTEC
l ConnectEMC

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:

68 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Administration

l An SNMP management console

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

Sending messages to SNMP

To send messages to SNMP:
Procedure
1. Configure the message destinations.
2. Configure which messages to send.
In the Messages menu of DLm Console, under the following tabs, select the SNMP check
box for each of the messages you want sent to SNMP:
l Error message routing
l Warning informational message routing
l Informational message routing
Configuring messages and recipients provides more information.

Configuring VTEC to send SNMP alerts

The VTEC contains SNMP MIBs that monitor the system and report events. Once configured, the
VTEC can send SNMP alerts to a designated SNMP manager. SNMP alerts are sent either as
SNMPv2c traps on port 162 using the community name 'public', or using SNMPv3.
About this task
To configure the VTEC to send SNMP alerts:
Procedure
1. Access the DLm Console:
a. Open a web browser and type the IP address as follows: https://<IP address>
b. Type the DLm Console username and password in the login page.
2. Once connected, click Configurations. In the Configurations operations tab, make sure
the correct configuration is selected in the drop down list in the upper left corner of the tab.
3. Click External.
4. Click the Notification tab.
Figure 33 Notification tab

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 69
DLm Administration

5. In SNMP manager fields, type the host name or IP address of one or two systems to which
you want SNMP management messages sent.
For more information, see Configuring messages and recipients.
If either of the SNMP manager 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.

6. You can select either v2c (default) or v3 as SNMP protocol version from the drop-down list.
a. If you select v2c, you can edit the Community field. The default string is public.
Note: The Community field accepts alphanumeric string with a maximum length of
31 characters.

b. If you select v3, additional fields are displayed, as shown in the following illustration.
Figure 34 SNMPv3 configuration

The following table lists the SNMPv3 parameters:

Parameter Description

Engine ID Engine ID of the SNMP agent. Default value is

local EngineID, auto-generated by the system.
This field accepts hexadecimal octet
characters. Range: 10 to 64

Security name Enter a name with a maximum length of 31

characters.

Authentication Select the authentication protocol (SHA or

MD5) from the drop-down list, and enter a
password. The minimum length of password
must be eight characters.

Privacy Select the privacy protocol (AES or DES) from

the drop-down list, and enter a password. The
minimum length of password must be eight
characters.

Sending messages to z/OS

For z/OS messages, you must install the z/OS started task and then configure which messages
you want sent.

70 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Administration

In the Messages menu of DLm Console, under the following tabs, select the Mainframe check box
for each of the messages you want sent to the mainframe:
l Error message routing
l Warning informational message routing
l Informational message routing
The next section, Configuring messages and recipients, provides detailed instructions.
The DLMHOST section in the Dell EMC Disk Library for mainframe Command Processors and Utilities
for z/OS Guide also provides information.

Configuring messages and recipients

You can configure which message gets sent to an SNMP management console or the z/OS master
console.
About this task
Note: 'E' level error messages cannot be configured. They are always selected to be sent to
SNMP and the mainframe.
'E' level error message configuration is disabled in the DLm Console by default. If you need to
configure a particular 'E' level message, contact Customer Support.
Procedure
1. Access the DLm Console :
a. Open a web browser and type the IP address as follows: https://<IP address>
b. Type the DLm Console username and password in the login page.
2. Once connected, click Configurations. In the Configurations operations tab, make sure
the correct configuration is selected in the drop down list in the upper left corner of the tab.
3. Click Messages.
Three tabs appear representing informational, warning, and error messages:
l Error message routing
l Warning message routing
l Informational message routing
Each tab shows a complete list of all DLm messages in that particular category.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 71
DLm Administration

Figure 35 Configuring messages

4. Select the tab corresponding to the message type you want to configure.
5. Select the check boxes in the following columns to send alerts to the corresponding
recipient:
l SNMP
l Mainframe
6. Select the toggle all check boxes to reverse the selection.

ConnectEMC
The ConnectEMC function can automatically notify the Dell EMC service center or other service
providers when the VTEC or the back-end storage system detects a serious problem.
ConnectEMC sends messages using email.
The email connection requires the DLm to have access to your company's LAN.
ConnectEMC is configured by Dell EMC personnel during initial setup. You can have them
configure the VTEC to generate ConnectEMC events for error-level SNMP traps.

AWSPRINT library utility

The awsprint utility enables you to produce lists of the tapes in the virtual tape library within the
DLm. You can use the command processor CP503 to obtain the awsprint output from the
mainframe. The Dell EMC Disk Library for mainframe Command Processors User Guide provides
information about CP503.
You must establish a CLI session on a DLm VTE to use awsprint. awsprint is a virtual tape library
utility that the mainframe user can run from the shell on the VTE to review the contents of the
virtual tape library. awsprint enables you to produce lists of the tapes in the virtual tape library.

72 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Administration

The output is either displayed directly on the VTE Linux shell or written to a FLAT file. You can
view the file using any text editor.
awsprint syntax
The syntax to run the awsprint utility in a VTE Shell is:

awsprint -p/tapelib -sBT00* -N -d

The following examples illustrate the syntax and parameters available.

Example 1

Executing awsprint with no options specified. A report is generated with awsprint

syntax and a description of its options.

vte1:~ # awsprint
awsprint Version 7.40-15840, Compiled Jul 2 2015 14:12:01

Usage: awsprint directory [-s pattern] [-NDVHIS] [-dar] [--less]

directory Specifies the path where the AWS tapes are stored.
This is a required parameter. For backwards
compatibility,
directory can be specified with a "-p" switch.
-s pattern Option to select files by filename, up to six
characters;
or to select files by scratch filename, up to seven
characters;
an optional ending '*' can be used as a wildcard.
The default is to select all files in the directory.
-N Sort output by fileName.
-D Sort output by Date,
-V Sort output by VOL1 Volser.
-H Sort output by HDR1 dataset name.
-I Sort output by fileName, interspersing scratch and
non-scratch
files (which normally would collate into separate
groups).
-S Sort output by file Size.
Only one sort option can be specified.
The default sort sequence is -N, by fileName.
-r --recurse Specifies that all directories should be recursed.
-a --all Specifies that all (scratch and non-scratch) volumes
are to be printed regardless of selection pattern.
-h --help Displays this help information.
-V --version Displays version number.
-d --details Specifies that tape details should be printed.
-l --less Specifies that tape label information (VOL1 label,
label
type, DSN) are not to be displayed. Using this option
will
greatly speed up the program as awsprint does not need
to open, read, and close every file in the directory.
Output is written to the console. You can use redirection (">") to
write the awsprint output to a file.

Usage example:
awsprint /tapelib -sBT00* -H >tapelist.txt
Selects all tapes starting with BT00 in path /tapelib, sorted by the
HDR1 dataset name. The output is redirected to the file
tapelist.txt.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 73
DLm Administration

Example 2

Executing awsprint with tapelib folder specified. Note that BFL FLAT files are
stored in this folder.

vte1:~ # awsprint /tapelibFLR/CEL1_FLRP_FS1

awsprint Version 7.40-15840, Compiled Jul 2 2015 14:12:01

Sorted by Name 09/14/2015 02:30:08 PM

Path: /tapelibFLR/CEL1_FLRP_FS1
Selection Criteria: All Tapes Without Details

NO. NAME VOLSER DATE TIME LBL TAPE INFO TAPE SIZE FLR EXP

1 BG0301 BG0301 08/26/15 15:19 S HDR1MCMD.TEMPFILE.H01 32.7K

2 BG0302 BG0302 08/26/15 15:21 S HDR1MCMD.TEMPFILE.H01 32.7K
3 BG0304 BG0304 08/27/15 11:01 S HDR1MCMD.TEMPFILE.H01 32.7K
4 BG0306 BG0306 08/28/15 15:41 S HDR1P499.TEMPFILE.H01 32.7K
5 BG0308 BG0308 08/28/15 15:42 S HDR1P499.TEMPFILE.H01 32.7K
6 BG0310 BG0310 08/28/15 15:42 S HDR1P499.TEMPFILE.H01 32.7K
7 BG0312 BG0312 08/28/15 15:42 S HDR1P499.TEMPFILE.H01 32.7K
8 BG0314 BG0314 08/28/15 15:43 S HDR1P499.TEMPFILE.H01 32.7K
9 BG0316 BG0316 08/28/15 15:43 S HDR1P499.TEMPFILE.H01 32.7K
10 BG0318 BG0318 08/28/15 15:44 S HDR1P499.TEMPFILE.H01 32.7K
11 BG0320 BG0320 08/28/15 15:44 S HDR1P499.TEMPFILE.H01 32.7K
12 BG0322 BG0322 08/28/15 15:45 S HDR1P499.TEMPFILE.H01 32.7K
13 BG0324 BG0324 08/28/15 16:05 S HDR1MGDLMTL1.TEMP.H01 32.7K
14 BG0326 BG0326 08/28/15 16:11 S HDR1MGDLMTL1.TEMP.H01 32.7K
15 BG0328 BG0328 08/31/15 09:56 S HDR1MGDLMTL1.TEMP.H01 32.7K
16 BG0330 BG0330 08/31/15 10:01 S HDR1MGDLMTL1.TEMP.H01 32.7K
17 BG0332 BG0332 08/31/15 10:02 S HDR1MGDLMTL1.TEMP.H01 32.7K
18 BG0334 BG0334 08/31/15 10:04 S HDR1MGDLMTL1.TEMP.H01 32.7K
19 BG0336 BG0336 09/01/15 10:08 S HDR1MGDLMTL1.TEMP.H01 32.7K
20 BG0338 BG0338 09/01/15 10:21 S HDR1MGDLMTL1.TEMP.H01 32.7K

Example 3

Executing awsprint with the recursive option.

vte1:~ # awsprint /tapelibFLR -r

awsprint Version 7.40-15840, Compiled Jul 2 2015 14:12:01

Sorted by Name 09/14/2015 02:31:35 PM

Path: /tapelibFLR
Selection Criteria: All Tapes Without Details

NO. NAME VOLSER DATE TIME LBL TAPE INFO TAPE SIZE FLR EXP
1 BFL499 08/28/15 15:45 F FLAT FILE 2.3K
2 BFL500 08/20/15 14:01 F FLAT FILE 2.2K
3 BFL501 09/01/15 10:14 F FLAT FILE 18.0K
4 BFL502 09/14/15 13:16 F FLAT FILE 144K
5 BFL503 09/02/15 11:07 F FLAT FILE 145K
6 BFL504 09/02/15 10:22 F FLAT FILE 2.6K
7 BFL601 09/02/15 10:23 F FLAT FILE 4.9K
8 BFL602 09/02/15 10:23 F FLAT FILE 8.0K
9 BFL603 09/02/15 10:23 F FLAT FILE 9.5K
….
awsprint Version 7.40-15840, Compiled Jul 2 2015 14:12:01

Sorted by Name 09/14/2015 02:31:35 PM

74 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Administration

Example 3 (continued)

Path: /tapelibFLR/CEL1_FLRP_FS1
Selection Criteria: All Tapes Without Details

NO. NAME VOLSER DATE TIME LBL TAPE INFO TAPE SIZE FLR EXP
1 BG0301 BG0301 08/26/15 15:19 S HDR1MCMD.TEMPFILE.H01 32.7K
2 BG0302 BG0302 08/26/15 15:21 S HDR1MCMD.TEMPFILE.H01 32.7K
3 BG0304 BG0304 08/27/15 11:01 S HDR1MCMD.TEMPFILE.H01 32.7K
4 BG0306 BG0306 08/28/15 15:41 S HDR1P499.TEMPFILE.H01 32.7K
5 BG0308 BG0308 08/28/15 15:42 S HDR1P499.TEMPFILE.H01 32.7K
6 BG0310 BG0310 08/28/15 15:42 S HDR1P499.TEMPFILE.H01 32.7K
7 BG0312 BG0312 08/28/15 15:42 S HDR1P499.TEMPFILE.H01 32.7K
8 BG0314 BG0314 08/28/15 15:43 S HDR1P499.TEMPFILE.H01 32.7K
9 BG0316 BG0316 08/28/15 15:43 S HDR1P499.TEMPFILE.H01 32.7K
10 BG0318 BG0318 08/28/15 15:44 S HDR1P499.TEMPFILE.H01 32.7K
11 BG0320 BG0320 08/28/15 15:44 S HDR1P499.TEMPFILE.H01 32.7K
12 BG0322 BG0322 08/28/15 15:45 S HDR1P499.TEMPFILE.H01 32.7K
13 BG0324 BG0324 08/28/15 16:05 S HDR1MGDLMTL1.TEMP.H01 32.7K
14 BG0326 BG0326 08/28/15 16:11 S HDR1MGDLMTL1.TEMP.H01 32.7K
….
awsprint Version 7.40-15840, Compiled Jul 2 2015 14:12:01

Sorted by Name 09/14/2015 02:31:35 PM

Path: /tapelibFLR/CEL1_FLRP_FS2
Selection Criteria: All Tapes Without Details

NO. NAME VOLSER DATE TIME LBL TAPE INFO TAPE SIZE FLR EXP
1 BG0300 BG0300 08/26/15 15:11 S HDR1G20A.GDG.G0068V00 1.2M
2 BG0303 BG0303 08/26/15 15:20 S HDR1MCMD.TEMPFILE.H01 32.7K
3 BG0305 BG0305 08/27/15 11:00 S HDR1RGREEN7.TEMPX 32.7K
4 BG0307 BG0307 08/28/15 15:41 S HDR1P499.TEMPFILE.H01 32.7K
5 BG0309 BG0309 08/28/15 15:42 S HDR1P499.TEMPFILE.H01 32.7K
6 BG0311 BG0311 08/28/15 15:42 S HDR1P499.TEMPFILE.H01 32.7K
7 BG0313 BG0313 08/28/15 15:43 S HDR1P499.TEMPFILE.H01 32.7K
8 BG0315 BG0315 08/28/15 15:43 S HDR1P499.TEMPFILE.H01 32.7K
9 BG0317 BG0317 08/28/15 15:44 S HDR1P499.TEMPFILE.H01 32.7K
10 BG0319 BG0319 08/28/15 15:44 S HDR1P499.TEMPFILE.H01 32.7K
11 BG0321 BG0321 08/28/15 15:45 S HDR1P499.TEMPFILE.H01 32.7K
12 BG0323 BG0323 08/28/15 15:59 S HDR1MGDLMTL1.TEMP.H01 32.7K
13 BG0325 BG0325 08/28/15 16:08 S HDR1MGDLMTL1.TEMP.H01 32.7K
14 BG0327 BG0327 08/28/15 16:12 S HDR1MGDLMTL1.TEMP.H01 32.7K
15 BG0329 BG0329 08/31/15 09:59 S HDR1MGDLMTL1.TEMP.H01 32.7K
16 BG0331 BG0331 08/31/15 10:01 S HDR1MGDLMTL1.TEMP.H01 32.7K
….

Example 4

Executing awsprint with tapelib specified along with recursive and detail options. A
report of all tape volumes in a tapelib is generated.

vte1:~ # awsprint /tapelibFLR -r -d

awsprint Version 7.40-15840, Compiled Jul 2 2015 14:12:01

Sorted by Name 09/14/2015 02:32:05 PM

Path: /tapelibFLR/CEL1_FLRP_FS1
Selection Criteria: All Tapes With Details

NO. NAME VOLSER DATE TIME LBL TAPE INFO TAPE SIZE FLR EXP
********************************************************************
*****
1 BG0301 BG0301 08/26/15 15:19 S HDR1MCMD.TEMPFILE.H01 32.7K

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 75
DLm Administration

Example 4 (continued)

********************************************************************
*****
DETAILS OF /tapelibFLR/CEL1_FLRP_FS1/BG0301

<EBCDIC LABELS>
VOL1BG0301
HDR1MCMD.TEMPFILE.H01BG030100010001 0152380000000000000IBM OS/VS 370
HDR2U000000000000RGDLMCMD/STEP3 P 0004B1
...Tape File #1: 3 x 80-byte blocks
0 Blocks Compressed 3 Blocks not Compressed
<TM>
<TM>
EOF1MCMD.TEMPFILE.H01BG030100010001 0152380000000000000IBM OS/VS 370
EOF2U000000000000RGDLMCMD/STEP3 P 0004B1
...Tape File #3: 2 x 80-byte blocks
0 Blocks Compressed 2 Blocks not Compressed
<TM>
<TM>
<1 x 32500-byte AWSMAP>
End of tape.

********************************************************************
*****
2 BG0302 BG0302 08/26/15 15:21 S HDR1MCMD.TEMPFILE.H01 32.7K
********************************************************************
*****
DETAILS OF /tapelibFLR/CEL1_FLRP_FS1/BG0302
<EBCDIC LABELS>
VOL1BG0302 TCSBT
HDR1MCMD.TEMPFILE.H01BG030200010001 0152380000000000000IBM OS/VS 370
HDR2U000000000000RGDLMCMD/STEP3 P 0004B1
...Tape File #1: 3 x 80-byte blocks
0 Blocks Compressed 3 Blocks not Compressed
<TM>
<TM>
EOF1MCMD.TEMPFILE.H01BG030200010001 0152380000000000000IBM OS/VS 370
EOF2U000000000000RGDLMCMD/STEP3 P 0004B1
...Tape File #3: 2 x 80-byte blocks
0 Blocks Compressed 2 Blocks not Compressed
<TM>
<TM>
<1 x 32500-byte AWSMAP>
End of tape.
********************************************************************
*****

Example 5 Example 5

Executing awsprint with recursive and fewer options.

vte1:~ # awsprint /tapelibFLR -r -l

awsprint Version 7.40-15840, Compiled Jul 2 2015 14:12:01

Sorted by Name 09/14/2015 02:32:19 PM

Path: /tapelibFLR
Selection Criteria: All Tapes Without Details

NO. NAME VOLSER DATE TIME LBL TAPE INFO TAPE SIZE FLR EXP
1 BFL499 08/28/15 15:45 2.3K
2 BFL500 08/20/15 14:01 2.2K

76 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 DLm Administration

Example 5 Example 5 (continued)

3 BFL501 09/01/15 10:14 18.0K

4 BFL502 09/14/15 13:16 144K
5 BFL503 09/02/15 11:07 145K
6 BFL504 09/02/15 10:22 2.6K
7 BFL601 09/02/15 10:23 4.9K
8 BFL602 09/02/15 10:23 8.0K
9 BFL603 09/02/15 10:23 9.5K
10 BFL999 09/02/15 11:27 593K
11 BFLABC 08/25/15 11:01 3.4K
12 BFLBG1 09/01/15 10:29 18.0K
13 BFLBG6 08/24/15 14:33 320
14 BFLBG9 08/24/15 16:20 320
15 BFLBGA 08/25/15 11:05 5.7K
16 BFLGR1 08/27/15 11:01 145K
17 BFLM10 08/26/15 09:27 15.5K
18 BFLMT1 08/25/15 13:38 0
19 BFLMT2 08/25/15 14:00 0
20 BFLMT3 08/25/15 14:03 0
21 BFLMT4 08/25/15 14:04 0
22 BFLMT5 08/25/15 14:05 0
23 BFLMT7 08/25/15 14:17 0
24 BFLXXX 08/25/15 11:03 9.5K
25 CEL1_F 09/14/15 14:27 10.0K
26 CEL1_F 09/13/15 23:02 10.0K
********************************************************************
*****
awsprint Version 7.40-15840, Compiled Jul 2 2015 14:12:01

Sorted by Name 09/14/2015 02:32:19 PM

Path: /tapelibFLR/CEL1_FLRP_FS1
Selection Criteria: All Tapes Without Details

NO. NAME VOLSER DATE TIME LBL TAPE INFO TAPE SIZE FLR EXP
1 BG0301 08/26/15 15:19 32.7K
2 BG0302 08/26/15 15:21 32.7K
3 BG0304 08/27/15 11:01 32.7K
4 BG0306 08/28/15 15:41 32.7K
5 BG0308 08/28/15 15:42 32.7K
6 BG0310 08/28/15 15:42 32.7K
7 BG0312 08/28/15 15:42 32.7K
8 BG0314 08/28/15 15:43 32.7K
9 BG0316 08/28/15 15:43 32.7K
10 BG0318 08/28/15 15:44 32.7K
11 BG0320 08/28/15 15:44 32.7K
12 BG0322 08/28/15 15:45 32.7K
13 BG0324 08/28/15 16:05 32.7K
14 BG0326 08/28/15 16:11 32.7K
15 BG0328 08/31/15 09:56 32.7K
16 BG0330 08/31/15 10:01 32.7K
17 BG0332 08/31/15 10:02 32.7K
18 BG0334 08/31/15 10:04 32.7K
19 BG0336 09/01/15 10:08 32.7

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 77
DLm Administration

78 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
CHAPTER 4
SRDF Replication

This chapter provides information about the SRDF Replication (SRDF) feature of DLm8500 with
PowerMax. The major topics include:

l SRDF replication overview.................................................................................................... 80

l SRDF connections and configuration..................................................................................... 81
l Disaster recovery capabilities................................................................................................ 82
l SRDF benefits....................................................................................................................... 82

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 79
SRDF Replication

SRDF replication overview

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

SRDF Synchronous (SRDF/S)

The SRDF Synchronous Mode maintains a real-time mirror image of the data of the remotely
mirrored volumes. The data is written in the global memory of both the systems, before the
application I/O is completed. The data on the source volumes and the target volumes are fully
synchronized at the completion of an I/O sequence through a first-in, first-out queue (FIFO)
model. The data movement is managed at the block level with synchronized mirroring. Using
SRDF/S, the system pairs can be located up to 200 km apart in a campus environment.
About this task
The following figure describes the I/O process in SRDF/S.
Figure 36 SRDF Synchronous (SRDF/S)

Procedure
1. The local system containing the primary volumes (Source) receives a write option from the
host.
2. The write I/O is transmitted to the remote Symmetrix system (secondary target volume).
The local Symmetrix system does not accept other write options to the primary volume.
3. An acknowledgment from the remote Symmetrix system is sent to the local Symmetrix
system.
4. An I/O completed message is sent to the local host from the local Symmetrix system. The
additional host writes are accepted to the primary volume by the local Symmetrix system.

Prerequisites for SRDF replication

l VNX software must be installed on both the source and destination systems.
l SRDF links must be operational between the two systems.

80 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 SRDF Replication

l All SRDF/S volumes must be synchronized.

SRDF connections and configuration

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

SRDF replication capabilities

SRDF offers the following capabilities:
l Switched SRDF: Enables the Symmetrix system to be connected through any SAN switches.
l Dynamic SRDF devices: Provides the capability to change SRDF Groups and device pairings as
needed
l Concurrent SRDF: Concurrent SRDF offers the capability to maintain multiple, host-
independent, remotely mirrored copies of data.
l Campus implementations: There are several SRDF Campus implementations available that
enable units to be up to 66 kilometers apart.
l Metropolitan area networks implementations: Allows the customer to use the entire bandwidth
on the "dark fibre ". This depends on the ability of the customer or the carrier for the dark fibre
installation.

SRDF/S active-passive configuration

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

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 81
SRDF Replication

Figure 37 SRDF/S active/passive configuration

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

Configuration files on source and target systems

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

Disaster recovery capabilities

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

SRDF benefits
SRDF offers several benefits:
l It protects against local and regional site disruptions.

82 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 SRDF Replication

l It helps in maintaining continuous data availability and multiple remote recovery sites.
l It assists in meeting regulatory requirements.
l SRDF provides near-instant recovery.
l It migrates, consolidates, or distributes data across storage platforms which helps in data
center consolidations and technology refreshes.
SRDF enables non-stop operations and provides application restart across volumes.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 83
SRDF Replication

84 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
CHAPTER 5
GDDR and Supported Configurations

This chapter introduces GDDR and its configuration. It also provides details about DLMDRD and
DLMDRC.

l GDDR Introduction................................................................................................................ 86
l SRDF/Star with AutoSwap GDDR Configuration...................................................................87
l DLMDRD............................................................................................................................... 88
l DLMDRC............................................................................................................................... 88

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 85
GDDR and Supported Configurations

GDDR Introduction
Dell EMC Geographically Dispersed Disaster Restart (GDDR) is a software product that runs on
the IBM z/OS operating system to automate business recovery following both planned outages
and disaster situations, including the total loss of a data center.
GDDR does not provide replication and recovery services itself, but rather monitors and automates
the services provided by other Dell EMC products, as well as third-party products, required for
continuous operations or business restart.
While GDDR is not required for SRDF in general, in the mainframe environment, GDDR is a
requirement for 3-site star SRDF configurations. GDDR can manage environments that are
comprised of the following elements:
l Multiple z/OS systems
l Multiple Sysplexes
l Multiple Symmetrix controllers
l Intermix of CKD and FBA/FBAM DASD and Business Continuance Volumes (BCVs)
Since GDDR manages production systems following disasters, it does not reside on the same
mainframe host that it is seeking to protect. GDDR resides on separate z/OS systems from the
mainframe hosts that run your application workloads.
GDDR is installed on a control LPAR at each site. These control LPARs are referred to as GDDR
nodes, Control Systems, or C-Systems. Each GDDR control system is aware of the other GDDR
control systems through network connections between each site. This multi-site awareness allows
GDDR to detect disasters and identify survivors.
GDDR can distinguish normal operational disruptions from disasters and respond accordingly. This
awareness is achieved by periodic exchange of dual-direction heartbeats between the GDDR
control systems.
In any GDDR installation, one control system (C-System) is designated as the Master C-System.
In three-site configurations, GDDR can nominate a control LPAR to assume the leadership role for
GDDR and recover business at one of the surviving sites. If a local or regional disaster occurs,
GDDR can determine which of the surviving sites will execute the recovery.

GDDR Control Systems

The GDDR control systems are more commonly referred to as GDDR C-Systems. One GDDR C-
System is located at each site in a separate z/OS System. Each GDDR C-System runs in monoplex
mode from local DASD. GDDR C-Systems do not run any production workload. Dell EMC
recommends that GDDR is installed on dedicated C-System DASD on separate controllers from
the production DASD.
The main functions of a GDDR C-System are as follows:
1. Controlling the recovery after an outage
2. Controlling a planned site swap
One of the C-Systems is designated as the Master C-System. During normal operations, the
Master C-System is the central control point for all GDDR activities.
Some GDDR functions can only be carried out by the Master C-System, for example:
l Running planned processes
l Updating GDDR parameters

86 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 GDDR and Supported Configurations

Workload location
In a GDDR complex with AutoSwap, the business or production workload can run as either a single
site workload, or as a multi-site workload, where the production workload runs at both the primary
and secondary sites.
Contingency or standby systems are typically located at the same location as the secondary DASD.
l Managed workloads—GDDR can trigger the stop and restart of production workloads on z/OS
systems and Distributed systems.
l External workloads—External workloads run on mainframe systems which do not have their
DASD in the managed Symmetrix units. GDDR can coordinate stop and start of the workload
on these non-managed mainframe systems with the workload stop and start actions for
managed systems.
l Excluded systems—GDDR can be configured to exclude certain z/OS systems from workload
management, although these systems have their DASD in the managed Symmetrix arrays.

GDDR Processes
A GDDR process or script is a dynamically determined sequence of function calls to achieve a
predetermined result.
l Planned process
A GDDR planned process is initiated through the GDDR interface to perform a planned task.
l Unplanned process or takeover process
The GDDR unplanned process or takeover process can only be initiated following an error that
results in a possible takeover situation. Takeover processes are initiated as a result of certain
messages being issued or specific events occurring.
l GDDR process restart
After the cause of the original failure has been identified and resolved, the GDDR process can
be rerun.

SRDF/Star with AutoSwap GDDR Configuration

The three-site SRDF/Star with AutoSwap configuration provides for near-continuous availability
through device failover between DC1 and DC2 as well as disaster restart capabilities at DC3.
In this environment, GDDR can perform the following tasks:
l Manage planned site swaps
l Manage recovery after unplanned site swaps
l Manage reconfiguration of the SRDF/Star environment between the concurrent and cascaded
topologies
l Manage reconfiguration of the SRDF/Star environment from cascaded to concurrent with a
primary processing site move
l Ensure continuous operation of SRDF/Star in the event of loss or removal of the primary MSC
server when SRDF/Star High Availability is configured
l Perform standard operational tasks:
n IPL, system reset, activate, deactivate
n Trigger stop/start of business workloads
l Actively monitor for unplanned/failure events, including:

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 87
GDDR and Supported Configurations

n Sites
n Systems
n ConGroup trip
n Loss of SRDF/S
n Loss of SRDF/A
n Inter-site communication failure
n AutoSwap events
l Configure/reconfigure:
n Couple datasets
l Manage coupling facilities:
n Policies

DLMDRD
DLm Disaster Recovery Dummy (DLMDRD) is a software module in DLm which assists in the DLm
disaster recovery process. DLMDRD provides several commands used for DLm disaster recovery
or disaster recovery testing operations. It provides a mechanism for communication between the
customer's mainframe LPAR (using GDDR or DLMDRC) and the DLm so that disaster recovery
operations can be initiated and controlled by the customer (using DLMDRC) or Dell EMC GDDR.
The communication between the DLMDRD and GDDR/DLMDRC (running on the customer's
mainframe LPAR) is based on a Client/Server model using the TCP/IP protocol. All systems have
the DLMDRD software running on the primary management VTE at all times.
GDDR issues commands to DLMDRD to manage the functions of the DLm during the following
Disaster Recovery events:
l Planned swap from the primary site to a secondary site.
l Unplanned swap from a primary site to the secondary site.
For more information, see Dell EMC Disk Library for mainframe Release Notes.

DLMDRC
DLMDRC is the DLm Disaster Recovery Client. While GDDR issues commands to DLMDR to
manage DLm functions during planned and unplanned swap events, DLm also supports Stateless
Site Swap disaster recovery configurations without the use of GDDR. DLm does this through
DLMDRC.

88 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
CHAPTER 6
Mainframe Tasks

This chapter explains how to use DLm with z/OS.

l Device configuration............................................................................................................. 90
l 3480, 3490, and 3590 tape drives.........................................................................................90
l Manual Tape Library (MTL)...................................................................................................90
l MTL considerations for VTE drive selection.......................................................................... 92
l MTL-related IBM maintenance.............................................................................................. 93
l Dell EMC Unit Information Module........................................................................................ 93
l Missing Interrupt Handler...................................................................................................... 94
l Dynamic device reconfiguration considerations.....................................................................95
l DFSMShsm considerations................................................................................................... 95
l Specifying tape compaction.................................................................................................. 96
l DLm z/OS components.........................................................................................................96
l Initiating an initial program load from a DLm virtual tape....................................................... 96
l DR logging.............................................................................................................................98
l Preparing z/OS for IPv6....................................................................................................... 99

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 89
Mainframe Tasks

Device configuration
z/OS uses the Hardware Configuration Definition (HCD) utility to define devices on the system.
HCD provides an interactive interface that allows you to define the system's hardware
configuration to both the channel subsystem and the operating system.
The three alternatives for configuring DLm devices on the mainframe are:
l Configure the devices as real 3480, 3490, or 3590 tape drives.
l Configure the devices as MTL devices.
l Configure the devices with a unique device type using the Dell 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 the 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.

3480, 3490, and 3590 tape drives

DLm can emulate 3480, 3490, and 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 ensure that they are writing or reading to a known tape device. These
applications typically do not work with the Dell EMC UIM.

Manual Tape Library (MTL)

Dell EMC recommends that you use the MTL to define DLm devices. If you plan to use DLm
devices with OAM or any application that verifies device type, you cannot use the Dell 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.

Defining DLm devices with HCD

Procedure
1. Configure DLm devices as either 3490 or 3590 tape devices using HCD.
Note: Dell EMC recommends that you do not use Dell EMC UIM due to cautions and
limited function described in EMC Unit Information Module. 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.

90 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Mainframe Tasks

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, when you want
to configure more than 16 drives, you must configure multiple control units on the same
channel using different logical control unit addresses.
5. Make sure that each control unit's devices have the same LIBRARY-ID, but a unique
LIBPORT-ID per control unit.
6. If you want more than 512 tape drives defined in an MTL, define a second MTL.
Note: The maximum number of tape drives defined in an MTL is 512.

The following table contains an example of having the same LIBRARY-ID with its unique
LIBPORT-IDs.

Table 6 Example of LIBRARY-ID and LIBPORT-ID

Dev Add CU Log CU LIBRARY-ID LIBPORT-ID

E800 CU800 00 12345 01

E801 CU800 00 12345 01

E80F CU800 00 12345 01

E810 CU810 01 12345 02

E811 CU810 01 12345 02

E81F CU810 01 12345 02

Results
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". 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.
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. Dell EMC provides an example of the
JCL required for linking DLMLIB. The sample JCL file is found in the LNKLIB member of
EMC.DLMS400.SAMPLIBU. Dell EMC Disk Library for mainframe Command Processors and
Utilities for z/OS Guide provides download instructions.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 91
Mainframe Tasks

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 IBM
DFSMSdfp Diagnosis.

MTL considerations for VTE drive selection

When a request is made for a tape drive defined in an MTL, the ACS routines select the
appropriate tape storage group for the library. Allocation subsequently chooses any available drive
in that library. This is not a problem if only one VTE is defined as part of the library. However, an
MTL can span multiple VTEs for performance and failover considerations. In this case, targeting a
specific VTE for batch utilities is required.
Note: Prior to z/OS 1.11, 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. In installations running z/OS 1.11 or more recent releases, MTL
devices can be specified using the SMSHONOR clause in the UNIT specification. Refer to the
z/OS JCL Reference Manual for more information.

Enabling a Dell EMC batch utility to communicate with a specific VTE

Use one of these methods to enable a Dell EMC batch utility (DLMCMD, DLMSCR) to
communicate with a specific VTE in an MTL defined with multiple VTEs:
l Omit a single drive from the MTL in each VTE's device group.
l Define a separate MTL for each VTE to enable VTE selection.

Omitting a single drive from the MTL in each VTE’s device group
About this task
To enable an Dell EMC batch utility to communicate with a specific VTE in an MTL defined with
multiple VTEs, you can omit a single drive from the MTL in each VTE’s device group. Dell 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.
As an alternative to varying the device online, executing the utility, and varying the device offline,
the DLMCMD, and DLMSCR batch utility programs support the use of the EXEC statement
parameter, DEV=xxxx, which allows access to an offline tape device. Installations running z/OS
1.11 or later can also use the SMSHONOR parameter in the UNIT specification as an alternative to
the use of the DLMCMD PARM DEV=xxxx parameter. Refer to the z/OS JCL Reference Manual for
more information.
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.
Note: 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. If the DLMCMD, or DLMSCR utility is
used with the DEV= parameter when the specified device is online, DLm displays the
corresponding DLm0182I message and terminates the operation.
For DLMCMD and DLMSCR steps, this parameter eliminates the need to code a DLMCTRL DD
statement.

92 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Mainframe Tasks

Consider an MTL defined with two VTEs, each configured with 64 devices. To omit a single drive
from the MTL in each VTE’s device group:
Procedure
1. In each VTE, define 63 devices as MTL=YES in the HCD.
One device would be MTL=NO in the HCD.

2. Subsequently, use demand allocation in JCL to select the specific drive address that is
outside the MTL.

Defining an MTL for a device to be used with a Dell EMC batch utility
Procedure
1. Similar to the previous method for omitting a single drive, define only 63 devices on each
VTE as part of the same MTL.
2. For each VTE, define a separate MTL (different LIB-ID) for the remaining device, as well as
a new esoteric.
3. Use ACS routines to select the appropriate library that limits the available drive selection to
that one drive.

MTL-related IBM maintenance

The program temporary fix (PTF) for each of the following APARs must be applied when using
DLm in an MTL environment:
l APAR OA03749 — More than one device fails to vary online.
l APAR OA06698 — Replacement tape drives get MSG IEA437I in an MTL environment.
l APAR OA07945 — Mount hangs or times out using MTL with OEM Automated Library.
l APAR OA08963 — Tape volume capacity is incorrect for OAM object support users.
l APAR OA10482 — MTL scratch volume mount error occurs.
Note: These APARS are generally found in z/OS 1.11 and above.

Dell EMC Unit Information Module

As an alternative to defining real 3480s, 3490s, or 3590s or using an MTL, Dell EMC provides a
user UIM that allows DLm tape devices to be configured to HCD using a unique device type. Using
the Dell EMC UIM prevents the operating system from allocating DLm virtual tape drives to jobs
requesting a mount of a real tape cartridge. However, using the UIM to define VTE devices is not
the recommended choice; Dell EMC recommends that you use OAM or another application that
checks device types. OAM and other applications that check device types will fail when allocated
to a UIM-defined device. Information regarding user UIM can be found in IBM's document, z/OS
MVS Device Validation Support (SA22-7586-0).
You must install the Dell EMC UIM and associated Unit Data Table (UDT) into SYS1.NUCLEUS
before you configure 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 DLm z/OS components.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 93
Mainframe Tasks

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 Dell EMC Customer
Support for a different module name to use.
After installing the UIM, you can configure DLm devices in HCD. The UIM provides the following:
l Four control unit types: V3480, V3481, V3482, and V3483.
l 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 Dell 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 (/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, you should define that drive with a
separate generic name (for example, V3481).
Once 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 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.
Note: Some applications may not work with this device type.

Missing Interrupt Handler

DLm reports a preferred Missing Interrupt Handler (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.
If the MVS, OS/390, or z/OS MIH timer value is set too low for the occasional lengthy operations
that can occur on a large tape cartridge and 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 that you do not set an MIH time value for any device that
establishes its own primary or secondary time interval (such as the DLm). Overriding the DLm-
supplied primary MIH timeout value might adversely affect MIH recovery processing for the device
or device class.

MIH command
To determine the current MIH timer value, you can use the following z/OS operator command:
D IOS,MIH,DEV=xxxx
where xxxx is any DLm virtual tape drive address.
You can temporarily change the MIH value for DLm devices by typing the following z/OS operator
command:
SETIOS MIH,DEV=(xxxx-xxxx),TIME=mm:ss
where xxxx-xxxx is the range of DLm virtual tape drive addresses.
The IBM manual, 3490 Magnetic Tape Subsystem Introduction and Planning Guide (GA32-0297),
provides more information about the MIH timer and tape drives.

94 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Mainframe Tasks

Dynamic device reconfiguration considerations

The swap function allows you to move volume access from one VTE to another. DLm supports
operator-initiated swap functions. This is useful during FRUs or upgrades when the VTE needs to
be rebooted. You no longer have to wait for allocated drives on a VTE to be de-allocated and taken
offline. Using the SWAP command, you can move volume access from the VTE to be serviced to
another VTE that has the same attributes as the swapped source device.
DLm only supports operator-initiated swaps.
Make sure you follow the considerations under Critical considerations for operator-initiated swap
functions when you use the operator-initiated z/OS SWAP command to move virtual volumes to
drives on different VTEs on the same DLm to permit VTE FRU changes or for other reasons.
The system-initiated (DDR) swap function is not supported. A system-initiated swap indicates a
permanent I/O error, and additional recovery attempts are not appropriate.
Note: In the case of a system-initiated swap, following a 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' message.
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.

Critical considerations for operator-initiated swap functions

These are the considerations that you must observe before using the operator-initiated SWAP
command:
l Do not attempt to swap between different class tape drives. That is, 3490 to 3590 or 3590 to
3490.
l Make sure the drive being swapped from and the drive being swapped to are configured to the
same library (for example, /tapelib_ETCxxxx).
l Make sure the drive being swapped from and the drive being swapped to have the same
attribute (for example, if the 'from' device specifies NO GR the 'to' device cannot specify GR).
l When writing to deduplicating storage, the DLm may not perform maximum deduplication
optimization on the remainder of the tape after moving to the "to" drive. The DLm
deduplication optimization algorithms in some cases recognize data from specific mainframe
backup programs based on the first few blocks written to the tape. Since the "to" drive
resumes writing in the middle of the tape, it may not recognize and optimally deduplicate in this
case.

DFSMShsm considerations
If you plan to use DLm with HSM, the various SETSYS tape parameters do not accept V348x
generic names as valid. In that case, it is necessary to define esoteric names that are unique to the
various V348x devices.

Identifying esoteric tape unit names to DFSMShsm

About this task
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.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 95
Mainframe Tasks

Procedure
1. Define these esoteric tape unit names to z/OS during system I/O generation (HCD).
2. Include the esoteric tape unit names in a DFSMShsm SETSYS USERUNITTABLE
command.

Specifying tape compaction

Compaction of the virtual tape data under z/OS is initiated like it is initiated for a real
compression-capable (IDRC) 3480/3490/3590E. The default is NOCOMP for 3480, and COMP
for 3490 and 3590E. You can specify the use of compaction in the JCL by using the
DCB=TRTCH=COMP or DCB=TRTCH=NOCOMP parameter on the appropriate DD cards for output
tapes. No JCL parameter is required for input tapes. The DLm 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.
While the compaction option significantly reduces the amount of storage required on the DLm
library, some impact occurs 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.

DLm z/OS components

Dell EMC provides a set of utilities and a UIM for the z/OS environments. The utilities are:
l DLMSCR — A scratch utility that sends VOLSER scratch requests to DLm.
l DLMCMD — A utility that enables the mainframe to send DLm commands.
l DLMLIB — A utility that is required to define scratch volumes on an MTL.
l DLMVER — A utility that reports the versions of all DLm mainframe utilities on the mainframe
and the z/OS release.
l DLMHOST — A host utility that provides z/OS Console Operation support.
l DLMWTOR — A utility enables a WTOR to be issued to the z/OS Console with up to 10 lines of
user-defined text. This provides a means to require z/OS operator confirmation of a DLm-
related change such as halting all DLm Tape activity.
Note: The DLm Command Processors and Utilities for z/OS Guide provides more information
about the DLm z/OS utilities.

Initiating an initial program load from a DLm virtual tape

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

96 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Mainframe Tasks

Creating a stand-alone IPL tape on DLm

About this task
To create a stand-alone IPL tape:
Procedure
1. On the DLm Console, initialize a non-labeled tape on DLm. For example:
init vol=SAIPL label=nl dev=E980 scratch=no CLASS=0
OR
init vol=SAIPL label=nl dev=E980 scratch=no DIR=D0
The examples create 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 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. For example:
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, being sure to explicitly specify the VOLSER you mounted in the
previous step.
Once the stand-alone IPL tape has been created, it is ready to use.

Mounting and IPLing from the stand-alone IPL tape

About this task
The mainframe will perform the IPL from the stand-alone IPL tape mounted on DLm.
Procedure
1. 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.

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

IPL considerations for DLm

The considerations for initiating an IPL on a mainframe host from DLm are:

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 97
Mainframe Tasks

l 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.
l 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, Rewind, and Ready commands
at the VT Console.
l Tapes on which stand-alone programs exist typically are not automatically unloaded. You may
need to manually execute the Unready and Unload commands using DLm Console to unload
the stand-alone IPL tape when you are done.

DR logging
Introduction to DR logging
In z/OS environments, DLm controllers provide a service referred to as “DR Logging”, which logs
tape volume mounts and un-mounts to a log file on the virtual tape library. When DR Logging is
enabled, each DLm controller defined as part of the virtual tape library creates a log file on each of
the file systems. The controller writes a single record to the log file for each tape volume
(VOLSER) it mounts and un-mounts from the file system.
Figure 38 DR Logging Overview

These log files are hidden from view so that they cannot be mistaken for tape volume (VOLSER)
files.
If a controller outage should occur, a DLm “Still in Use” report can be generated using the CP988
or CP989 command processors utility. This report will read all the log files in the virtual tape
library and report those tape volumes which were mounted and never unmounted.
The purpose of this report is to help determine which tape volumes may be incomplete following a
controller failure.

98 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Mainframe Tasks

By placing the DR log files in the virtual tape library rather than writing them on the controller’s
internal storage, the log files can be replicated to a secondary disaster recovery site along with the
tape volumes. Then, in the unlikely event there is a complete loss of the primary processing facility,
the DLm "Still in Use" report can be used to help identify all tape volumes that were in use at the
primary site at the time of the failure.
Enabling DR logging
The DR logging feature is not enabled by default in DLm. To enable DR logging, a hidden control
filed named “.vstats”, must be present in each file system where logging is to be performed.
The .vstats file may be empty. DLm does not look at the contents of the file. It only uses the
presence of the file to determine whether or not to perform DR logging for that file system.
The procedure to create the .vstats file in a file system varies depending on the DLm controller
model. Please refer to the hardware installation guide that accompanied your system for
information on how to create this control file.
Retrieving the Still In Use Report
The "Still In Use" report is part of the standard DLm general statistics command processor
CP988 or CP989.
Execute CP988 command processor with the STILLINUSE parameter to produce the Still In Use
report from available DR Logs.

Preparing z/OS for IPv6

IPv6 is supported by the z/OS Communications Server. In DLm, you have the option to use either
IPv6 or IPv4 addresses. The default is IPv4. If you want to use IPv6 addresses, and your z/OS
system does not currently support IPv6, then z/OS installation changes are required.

Enabling IPv6
About this task
Enable IPv6 by performing the following procedure:
Procedure
1. Uncomment and activate an IPv6 NETWORK statement in SYS1.PARMLIB(BPXPRMxx).
There are two of these: one for INET, one for CINET. Uncomment the one you're already
using for IPv4. The following is a commented CINET statement:

/*NETWORK DOMAINNAME(AF_INET6) DOMAINNUMBER(19) */ /* For IPv6 */

/* TYPE(CINET) */

2. Test the activated change by entering the following commands on ISPF Command Shell:
netstat up

ping ::1

For example:
ISPF Command Shell
Enter TSO or Workstation commands below:

===> netstat up

MVS TCP/IP NETSTAT CS V1R12 TCPIP Name: TCPIP

Tcpip started at 14:52:42 on 04/29/2014 with IPv6 enabled
***

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 99
Mainframe Tasks

ISPF Command Shell

Enter TSO or Workstation commands below:

===> ping ::1

CS V1R12: Pinging host ::1

Ping #1 response took 0.000 seconds.
***

Configuring IPv6
About this task
Configure IPv6 by performing the following procedure:
Procedure
1. Add an IPCONFIG6 statement to your TCPIP profile. This example includes the optional
SOURCEVIPA parameter:

IPCONFIG6 SOURCEVIPA

2. Add an INTERFACE statement to your TCPIP profile that is appropriate to your environment
for an IPv6 interface. INTERFACE is used for IPv6 in place of the DEVICE, LINK, and HOME
statements.
The following example is an INTERFACE — IPAQENET6 OSA-Express QDIO interfaces
statement:

INTERFACE OSAQDIO15 DEFINE IPAQENET6 PORTNAME OSAQDIO1

where:

OSAQDIO15 is an interface name of your choice.

OSAQDIO1 is a port name of your choice.

3. Add a START statement for your new interface:

START OSAQDIO15

4. If you are not already doing so, convert the GATEWAY statement in your TCPIP profile to a
BEGINRoutes statement. The GATEWAY statement is not supported for IPv6 and will
eventually be dropped for IPv4. GATEWAY and BEGINRoutes statements may not co-exist,
so, to combine the two in a single stack, IPv4 must be converted to BEGINRoutes and IPv6
added to it. See “Steps for converting from IPv4 IPAQENET DEVICE, LINK, and HOME
definitions to the IPv4 IPAQENET INTERFACE statement” in the z/OS Communications Server
IP Configuration Guide.
l Sample GATEWAY statement for IPv4:

GATEWAY
;
; Direct Routes - Routes that are directly connected to my interfaces.
;
; Network First Hop Link Name Packet Size Subnet Mask Subnet Value
;
10 = OSA01Al 1500 0.255.255.0 0.242.29.0
DEFAULTNET 10.242.29.1 OSA01Al 1500 0
l Corresponding BEGINRoutes statement:

BEGINRoutes
ROUTE 10.242.29.0 255.255.255.0 = OSA01AL MTU 1418

100 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Mainframe Tasks

MAXImumretransmittime 120 MINImumretransmittime 0.5

ROUNDTRIPGain 0.125 VARIANCEGain 0.25 VARIANCEMultiplier 2
DELAYAcks NOREPLaceable
ROUTE DEFAULT 10.242.29.1 OSA01AL MTU 1418
MAXImumretransmittime 120 MINImumretransmittime 0.5
ROUNDTRIPGain 0.125 VARIANCEGain 0.25 VARIANCEMultiplier 2
DELAYAcks NOREPLaceable
ENDRoutes

l To this, add the second and fourth ROUTE statements as follows for IPv6:

BEGINRoutes
ROUTE 10.242.29.0 255.255.255.0 = OSA01AL MTU 1418
MAXImumretransmittime 120 MINImumretransmittime 0.5
ROUNDTRIPGain 0.125 VARIANCEGain 0.25 VARIANCEMultiplier 2
DELAYAcks NOREPLaceable
ROUTE 2001:DB8:0:0:10:0:0:1/32 = OSAQDIO15 MTU 1418
MAXImumretransmittime 120 MINImumretransmittime 0.5
ROUNDTRIPGain 0.125 VARIANCEGain 0.25 VARIANCEMultiplier 2
DELAYAcks NOREPLaceable
ROUTE DEFAULT 10.242.29.1 OSA01AL MTU 1418
MAXImumretransmittime 120 MINImumretransmittime 0.5
ROUNDTRIPGain 0.125 VARIANCEGain 0.25 VARIANCEMultiplier 2
DELAYAcks NOREPLaceable
ROUTE DEFAULT6 2001:DB8:0:0:10:0:0:1 OSAQDIO15 MTU 1418
MAXImumretransmittime 120 MINImumretransmittime 0.5
ROUNDTRIPGain 0.125 VARIANCEGain 0.25 VARIANCEMultiplier 2
DELAYAcks NOREPLaceable
ENDRoutes

where:
n OSAQDIO15 matches the interface name designated on the INTERFACE statement.
n 2001:DB8:0:0:10:0:0:1/32 is the IPv6 address for the desired VLAN interface at
your installation.
n 2001:DB8:0:0:10:0:0:1 is the gateway address for the desired VLAN interface at
your installation.

5. Activate the above changes.

Configuring Virtual Telecommunications Access Method (VTAM)

About this task
Configure VTAM by performing the following procedure:
Procedure
1. Add and activate a TRLE statement to VTAMLST using available OSA device numbers.

TRLOSA VBUILD TYPE=TRL

TRL01 TRLE LNCTL=MPC,READ=0004,WRITE=0005,DATAPATH=(0006), X
PORTNAME=OSAQDIO1,MPCLEVEL=QDIO
TRL01B TRLE LNCTL=MPC,READ=0008,WRITE=0009,DATAPATH=(000A), X
PORTNAME=OSA01A,MPCLEVEL=QDIO

where:

PORTNAME is the one designated on the INTERFACE statement.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 101
Mainframe Tasks

2. Test the activated changes by pinging a host with a known IPv6 address:
For example:

ISPF Command Shell

Enter TSO or Workstation commands below:

===> ping 2001:DB8:0:0:10:0:0:1

CS V1R12: Pinging host 2001:DB8:0:0:10:0:0:1

Ping #1 response took 0.001 seconds.
***

102 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
CHAPTER 7
Using DLm with Unisys

This chapter describes how to use DLm with Unisys.

l Unique DLm operations for Unisys mainframes.................................................................... 104

l Configuration for Unisys...................................................................................................... 105
l Initializing tapes for Unisys.................................................................................................. 105
l Configuring the Unisys mainframe for DLm......................................................................... 105

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 103
Using DLm with Unisys

Unique DLm operations for Unisys mainframes

This section describes the unique DLm operations required for Unisys mainframe systems.

Autodetection
DLm automatically detects that it is attached to a Unisys host when it receives a Load Display
command containing data that is unique to a Unisys mainframe. When this occurs, a message is
displayed on the DLm Console (DLm0080I: 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.

104 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Using DLm with Unisys

Configuration for Unisys

This section describes what you need to consider about device type, labels, and scratch tapes
when you configure DLm 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.

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 message. To accommodate the L-BLNK
message, you must specify a scratch synonym equal to L-BLNK. The following figure shows a
scratch synonym configured for Unisys mainframes.
Figure 39 Scratch synonym for Unisys

Initializing tapes for Unisys

When initializing tape volumes to be used with Unisys, include the LABEL=A option on the initialize
command to tell the system that the tape labels will follow the ANSI standard.
About this task
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 CLASS=0

Configuring the Unisys mainframe for DLm

Configure DLm devices 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.
About this task
The Unisys equipment code for DLm devices is U47M.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 105
Using DLm with Unisys

106 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
APPENDIX A
Virtual tape operator command reference

This appendix describes the virtual tape operator command reference.

l Syntax................................................................................................................................. 108
l CLOSE VSTATS...................................................................................................................108
l DETAIL MOUNT...................................................................................................................108
l FIND.................................................................................................................................... 109
l HELP................................................................................................................................... 109
l INITIALIZE............................................................................................................................ 110
l KMRESTART........................................................................................................................ 112
l LOAD.................................................................................................................................... 112
l LTR.......................................................................................................................................113
l MIGRATE............................................................................................................................. 114
l QUERY................................................................................................................................. 115
l QUIESCE.............................................................................................................................. 117
l READY..................................................................................................................................118
l REWIND............................................................................................................................... 119
l ROTATE............................................................................................................................... 119
l SAVE TRACE........................................................................................................................119
l SCRATCHNAME..................................................................................................................120
l SET.......................................................................................................................................121
l SNMP.................................................................................................................................. 127
l STARTVT............................................................................................................................. 128
l STOPVT...............................................................................................................................128
l UNLOAD.............................................................................................................................. 128
l UNQUIESCE........................................................................................................................ 129
l UNREADY............................................................................................................................ 130

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 107
Virtual tape operator command reference

Syntax
Virtual tape operator commands use the following syntax rules:
Note: The commands and associated syntax listed in this appendix refer to the full set of
commands available through the VT Console. If you are viewing or executing commands in the
DLm Console's Command tab (on the Status page), the available commands are only a subset
of the full commands available through the VT Console.
l UPPERCASE words are keywords and must be spelled as shown. You can type the keywords in
either uppercase or lowercase.
l 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.
l Values in square brackets [] are optional.
l When multiple values are separated by a pipe symbol (|), enter only one of the choices.

CLOSE VSTATS
Syntax

CLOSE VSTATS PATH=xxx

Description
The CLOSE VSTATS PATH=xxx command closes the DR logging vstats file in the path
specified to allow a mount point to be unmounted.
Note: A closed vstats file will automatically re-open if a tape is mounted in or moved to a
directory with a closed vstats file, or if the ROTATE DRLOG command is executed. To prevent
a vstats file from automatically reopening, take the directory out of service with the QUIESCE
TAPELIB command before closing its vstats file.

Example
close vstats path=/tapelib/BT

DETAIL MOUNT
Syntax

DETAIL MOUNT

Description
The DETAIL MOUNT command returns detailed information about currently mounted tapes.
Example
DETAIL MOUNT

108 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Virtual tape operator command reference

Sample Output

Devicename VOLSER Load Time Duration Requestor Path

Last I/O Time Tape Library Path
---------- ------ ------------------- -------- -----------------
F400 D30321 2016/04/24 09:50:50 2.0 m [intfc 2/#1141100:link 114:lpar 11]
2016/04/24 09:52:48 /tapelib/DD1_BPOOL_FS3/
F401 D10322 2016/04/24 09:52:03 45.0 s [intfc 1/#1001100:link 100:lpar 11]
2016/04/24 09:52:48 /tapelib/DD1_BPOOL_FS4/
F402 D40324 2016/04/24 09:52:38 10.0 s [intfc 1/#1001100:link 100:lpar 11]
2016/04/24 09:52:48 /tapelib/DD1_BPOOL_FS1/
F403 D10318 2016/04/24 09:50:42 2.1 m [intfc 1/#1001100:link 100:lpar 11]
2016/04/24 09:52:43 /tapelib/DD1_BPOOL_FS1/
F404 D20318 2016/04/24 09:50:42 2.1 m [intfc 2/#1141100:link 114:lpar 11]
2016/04/24 09:52:32 /tapelib/DD1_BPOOL_FS1/
7C0C LMA100 2016/05/05 09:27:23 21.0 m [Manual Mount]
2016/05/05 09:38:23 /ltr/tapelibA/FS1/

FIND
Syntax

FIND VOL=volser [DEV=devicename]

Description
The FIND command finds a specific volume (VOLSER) in the DLm tape library and reports the
current status of that volume.
If the DEV= parameter is specified, the search is limited to the PATH set for that device.
Note: For compatibility, this syntax is allowed:
FIND VOLUME volser [DEV=devicename]

Example
FIND VOL=000001
The example returns the current status of the tape volume with the serial number 000001.
Sample Output

DLm0409I: Command received: 'FIND VOL=D40316 DEV=F400'

find volume(s) 'D40316' Fri Apr 24 10:02:50 2015 (Julian 114)
Volume Type DSN Size Modified Mounted St Class Path
====================================================================================
D40316 S VTC01263.M5120B32 5.3G 114/2015 9:57 [0] /tapelib/DD1_BPOOL_FS4
find volume(s) 'D40316' -- command complete

HELP
Syntax

HELP [command|message number|ABOUT]

Description
The HELP command displays the following information about Virtuent commands and messages:

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 109
Virtual tape operator command reference

Options
The following table provides the descriptions for the command options.

Table 7 Help command — option description

Value Description

HELP or ? Displays summary of all commands. HELP and ? are

synonymous.

HELP [command] Displays a detailed description of the specified command.

HELP [message number] Displays an explanation of the message. HELP 0489

displays information about message DLm0489E. (Typing
the message number as DLm0489E, DLm0489, or 0489
gives the same result.)

HELP [About] Displays information about Virtuent.

Note: The Help information pertains to Virtuent only.

Example
HELP DLm0489
HELP SET

INITIALIZE
Syntax

INITIALIZE VOL=volser DEVICE=devname

[COUNT=count]
[CLASS=n]
[DIR=subdirectory]
[LABEL=S|A|N]
[SCRATCH=Y|N]
[EPIC=N|Y]
[ERRORS=nnnnn]
[VIRTUALSCRTCH=NO|YES]

Description
Creates and initializes one or more AWS-format virtual tape volumes in the tape library.
Note: In DLm command syntax, you can use DEVICE and DEV interchangeably.

Options
The following table provides the descriptions for the command options.

Table 8 Initialize command — option description

Value Description

VOL=volser It is the starting serial number to initialize. If VOLSER is specified without a count, only the
volume specified is created.

COUNT=count It is the number of serial numbers to initialized. If count is not specified, only the single
VOLSER specified will be initialized. If count is specified, volser becomes a template for

110 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Virtual tape operator command reference

Table 8 Initialize command — option description (continued)

Value Description

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.

ERRORS=nnnnn If ERRORS=nnnnn is specified, up to nnnnn errors are tolerated and initializations continue
until <nnnnn> have occurred. If the ERRORS parameter is not specified, initializations
terminate after encountering five errors (such as volser already exists). Any existing volume
in the range is skipped. It will not be altered in any way.

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 when using
EFS:
INIT VOL=B00000 DEVICE=E980 COUNT=100 CLASS=0

CLASS=n The CLASS parameter directs the new volumes being initialized to a specific storage class
within the library. You must initialize scratch tapes into any new storage class before you
attempt to allocate a new scratch volume from that class. CLASS is a required parameter
when using Enhanced File System (EFS), and is not valid when EFS is not being used. Unless
DIR is also specified, the new tapes will be spread across all subdirectories of the specified
CLASS.

DIR=subdirector The DIR parameter is always optional and allows you to direct the new volumes being
y initialized to a specific file system (directory) within the library.
Note: This parameter is only allowed when the Enhanced File System (EFS) architecture
option is enabled.

LABEL=[S/A/N] 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.

SCRATCH=[Y/N] 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=N. Unlabeled tapes are initialized only with SCRATCH value N, and this parameter
is mandatory for creating unlabeled tapes.

EPIC=[N/Y] Specifying EPIC=Y places an identifier on the VOL1 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=N.

VIRTUALSCRTCH=N Specifying VIRTUALSCRTCH=YES places the identifier VirtualSCRTCH on the System

O/YES Code field of the HDR1 label for SL-labeled tapes. This identifier may signify to the host that
this volume resides in a virtual tape library. This option is required under certain rare
circumstances, such as with RMM when a VOLSER that was previously cataloged on the
host has been re-initialized on the DLm. This prevents the host from rejecting the tape due
to an incorrect dataset name. VIRTUALSCRTCH is only valid when initializing SL tapes. The
default is NO.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 111
Virtual tape operator command reference

Example
INITIALIZE VOL=S20000 DEV=3800 COUNT=100 CLASS=2

KMRESTART
Syntax

KMRESTART

Description
This command restarts the keymanager daemon. It is used to reinitialize new certificates and
parameters.
Dell EMC Customer Support personnel upload the new certificate in DLm Console and then
initialize the keymanager daemon.
Note: This command is NOT disruptive and does not require a restart of Virtuent.

LOAD
Syntax

LOAD [VOL=volser] [ON] [DEVICE=devicename|*] [UNLABELED|LABELED|NL|SL|AL]

[PROTECTED]

Description
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.
Note: The label option applies only to scratch mount requests. Virtuent ignores the label
specification when a specific VOLSER is specified.
Options
The following table provides the descriptions for the command options.

Table 9 Load command — option description

Value Description

VOL=volser Specifies the VOLSER to be loaded.

DEVICE=devicename|* Specifies the virtual tape drive to be loaded. * loads the first available device.

[UNLABELED|LABELED| LABELED/SL specifies that the scratch volume must be initialized with standard IBM
NL|SL|AL] (EBCDIC) labels. The LABELED and SL options are synonymous. This option has no
effect when a specific VOLSER is requested.

UNLABELED/NL specifies that the scratch volume must be initialized as an unlabeled

tape. The UNLABELED and NL options are synonymous. This option has no effect when
a specific VOLSER is requested.

112 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Virtual tape operator command reference

Table 9 Load command — option description (continued)

Value Description

AL specifies that the scratch volume must be initialized with standard ANSI (ASCII)
labels. This option has no effect when a specific VOLSER is requested.

PROTECTED The PROTECTED option loads the tape as read-only. Otherwise, the volume is loaded in
normal read-write mode.

Example
LOAD VOL=S20000 DEV=3800

LTR
Syntax

LTR [ENABLE | DISABLE] policyname

FAILURES [CLEAR|LIST] policyname
REVERT VOLSER=volname MODIFICATION={COMPRESSED|UNCOMPRESSED}
{TAPELIB=tapelibname
[CLASS=nn] | POLICY=policyname}
MIGRATE POLICY=policyname [VOLSER=volname]
[START={NOW|NEXT}]
KILL

Description
The LTR command enables you to manage LTR policies configured on VTE, perform on-demand
migration of any tape volume to LTR target storage, and bring back the previously migrated tape
volume to the primary storage.
Options
The following table provides the descriptions for the command options:

Table 10 LTR command - option description

Value Description

LTR [ENABLE|DISABLE] policyname Enables or disables the specified LTR policy.

Wildcards are allowed in the policy name
parameter. The policy name is not case-
sensitive.

LTR FAILURES [CLEAR|LIST] l CLEAR—Removes all tapes from the list

policyname | * of failures to retry migration.
l LIST—Prints all tapes from the list of
failed migrations.

LTR REVERT VOLSER=volname Brings back the specified volser from LTR
MODIFICATION={COMPRESSED| target of specified tape library. Wildcards are
UNCOMPRESSED} allowed in VOLSER parameter.
{TAPELIB=tapelibname [CLASS=nn] |
l MODIFICATION={COMPRESSED|
POLICY=policyname}
UNCOMPRESSED}— This parameter

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 113
Virtual tape operator command reference

Table 10 LTR command - option description (continued)

Value Description

specifies compression state of tape

volume after reversion.
l CLASS=nn —Brings back volsers located
on LTR targets with class nn.
Note: This option is valid only when
VOLSER parameter is specified as a
wildcard.
l POLICY=policyname—Brings back
volsers located on LTR targets of
specified LTR policy.

LTR MIGRATE POLICY=policyname Adds volser to the migration request for

[VOLSER=volname] [START=NOW | specified LTR policy. If START option is
NEXT] specified, filelists for specified LTR policy
source tapelibs are refreshed, and then LTR
migration is initiated for requested volumes.
l START=NOW—migration starts
immediately.
l START=NEXT—migration starts on
schedule.

LTR KILL Immediately stops all LTR migrations in

progress, and disables the LTR feature.

MIGRATE
Syntax

MIGRATE
[ENABLE policyname[*]]
[DISABLE policyname[*]]
[STATUS]
[FAILURES LIST policyname [*]]
[FAILURES CLEAR policyname [*]]
[KILL]

Description
Use the MIGRATE ENABLE or MIGRATE DISABLE command to enable or disable one or more
specified migration policies. Besides, you can use the MIGRATE KILL command to disable the
Migration feature, disable all migration policies, and terminate all migrations in progress. MIGRATE
STATUS command displays the status of Migrate feature. MIGRATE FAILURES LIST prints all
tapes from list of failed migrations, while MIGRATE FAILURES CLEAR removes all tapes from list
of failures.
Options
The following table provides the descriptions for the command options:

114 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Virtual tape operator command reference

Table 11 MIGRATE option description

Value Description

MIGRATE ENABLE policyname[*] Enables one or more specified migration policies. The
policy name can be terminated with a ‘*’ wildcard
character to specify multiple policies, or a ‘*’ alone
specifies all migration policies.

MIGRATE DISABLE policyname[*] Disables one or more specified migration policies until a
MIGRATE ENABLE command is entered or until Virtuent
is restarted. Any migrations in progress when the
MIGRATE DISABLE command is entered continues to
normal completion. The policy name can be terminated
with a ‘*’ wildcard character to specify multiple policies,
or a ‘*’ alone to specify all migration policies.

MIGRATE STATUS Displays information about the Migrate feature and its
policies.

MIGRATE FAILURES LIST policyname[*] Prints all tapes from list of failed migrations.

MIGRATE FAILURES CLEAR policyname[*] Removes all tapes from list of failures to retry the
migration process.

MIGRATE KILL Disables the Migration feature, disables all migration

policies, and terminates all migrations in progress. Any
migrations in progress are treated as if the operator
interrupted them with an UNLOAD command. The
original source file is left in place, and the partial target
file is deleted.

QUERY
Syntax

QUERY [[DEV=]devicename[+]|ALL|MOUNTED]
[CONFIG]|[CRITICAL]|[PATHS [ASSIGNED]]|[EFS]|[LABELS]
[[DEV=]devicename]
[VERSION]|[SPACE [BYCLASS][LTR][WIDEFORMAT]]|[SCRATCHNAMES]|[COMPRESSION]|[GR]
[STATISTICS|STATS]
[STCLASS]
[WARNING|RECOVER|RECOVERAMT]
[CHANNEL ADAPTERS]
[DRIVE LIST]
[REJECTED PATHS][LOCKS]
[LTR]

[MIGRATE]

Description
Use the QUERY command to display the system information. The following is a description of the
values within the command:
Options
The following table provides the descriptions for the command options.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 115
Virtual tape operator command reference

Table 12 Query command — option description

Value Description

QUERY [[DEV=] device With no operands, displays the current status of all virtual tape drives, while
name] DEVICE=devicename displays a single drive or range of drives. Use * as a
wildcard character to display a range of drives. For example, Q E98* displays
all the devices E980–E98F.

QUERY ALL Displays information about Virtuent, the channel interface cards, and all virtual
tape devices.

QUERY MOUNTED Displays information only about the drives that currently have virtual tape
volumes mounted.

QUERY CONFIG Shows detailed configuration information for all devices, or a single device if
DEV= is specified.

QUERY CRITICAL Shows information about the critical usage thresholds and behaviors.

QUERY PATHS [ASSIGNED] Shows all the channel paths established for the VTE devices, or a single device
if DEV= is specified. If ASSIGNED is specified, only channel paths with a current
host assignment (typically those varied online) are displayed.

QUERY EFS Displays information about the Enhanced File System (EFS) states.

QUERY LABELS Shows the header labels, if any, for all mounted tapes.

QUERY VERSION Displays Virtuent release number.

QUERY SPACE [LTR] Shows a summary of the disk space used and available in all the tape libraries.
[WIDEFORMAT] Note: You can enter additional commands while the QUERY SPACE
command is being processed.

If the BYCLASS option is used, the subdirectories are listed and totaled for each
class.
The LTR option displays information only about LTR storage.
The WIDEFORMAT option prints all the information on one line for each tape
library directory, regardless of the length of the tape library path names. The
column positioning will be adjusted to accommodate the longest path name.

QUERY SCRATCHNAMES Displays all the scratch VOLSER synonyms currently in effect.

QUERY COMPRESSION Lists the status of a VTE's AHA compression adapters.

QUERY GR Displays the tape library directories configured for replication and are eligible
for GR or Replication on RUN. It also displays the GR timeout value, and the list
of shared GR directories for each storage.

QUERY WARNING WARNING, RECOVER, and RECOVERAMT are effectively the same, and display
the space usage warning percent, space recovery percent, space recover
QUERY RECOVER
amount, recovery update time, and erase policy TTL time. File-size values
QUERY RECOVERAMT reported by the QUERY command reflect the compressed data size, not the
original uncompressed size.

QUERY STATISTICS or QUERY Displays the current state of the Virtuent statistics collection system.
STATS

QUERY STCLASS Displays the storage classes of the tape libraries.

QUERY CHANNEL ADAPTERS Displays information about all channel adapters in the VTE.

116 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Virtual tape operator command reference

Table 12 Query command — option description (continued)

Value Description

QUERY REJECTED PATHS Displays connections that the host has attempted to establish with the VTE,
but which are not configured.

QUERY LOCKS Displays two kinds of VOLSER locks currently set:

l Short term locks set by Enhanced File System (EFS) when searching for or
moving files between file systems.
l Long term locks set by Virtuent to reserve a VOLSER for the duration it is
used.

QUERY LTR Displays information about the Long Term Retention feature and policies
configured on this VTE.

QUERY MIGRATE Displays information about the Migration feature and all configured policies.

QUERY SPACE sample output

l Tape library space for drives — All devices sharing the same tape library are grouped together.
l 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.
l Size — This is the size of the entire file system.
l Active — This is the amount of space being used by non-scratch tape volumes.
l Scratch — This is the amount of space that scratch tape volumes use. The system can reclaim
scratch tape space at any time as needed.
l Qty — This is the number of scratch tape volumes in this directory.
l Free — This is the amount of free space currently available on the entire file system. Note that
if the file system 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.
l Filesystem — The file system device name, typically a hard drive partition name or an NFS or
SMB mount point.

QUIESCE
Syntax

QUIESCE [[DEVICE=]devicename|ALL|*] [SCRATCH PATH=path] [TAPELIB PATH=path]

Description
The QUIESCE command sets one or all of the virtual devices, or a tape library directory, into the
'quiesced' state. Quiesced drives will not accept any future Load requests until UNQUIESCE'd (or
until the system is restarted). Other than not accepting new loads, quiesced drives remain On-
Line, Ready and fully functional; any volume already loaded on the drive can be accessed normally
until it is unloaded.
Mount requests issued by the host while a drive is quiesced remain pending and will be performed
when the drive is unquiesced.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 117
Virtual tape operator command reference

Options
The following table provides the descriptions for the command options:

Table 13 QUIESCE option description

Value Description

ALL or * Are synonymous and quiesces all drives

QUIESCE SCRATCH PATH=path Quiesced SCRATCH tape library directories will be

bypassed when searching for or mounting a scratch tape.
In addition, a quiesced directory will not be eligible to
move scratch volumes into. Usage of the directory will
return to normal once it is UNQUIESCE'd.

QUIESCE TAPELIB PATH=path Quiesced TAPELIB 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.

Example
QUIESCE TAPELIB PATH=/tapelib/FS1
QUIESCE DEVICE=4000

READY
Syntax

READY [DEVICE=]devicename

Description
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 UNREADY command was entered.
Example
READY DEVICE=9200
READY CD05

118 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Virtual tape operator command reference

REWIND
Syntax

REWIND [DEVICE=devicename]

Description
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.
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 to not be in use by a host application, but needs to be rewound to
load point immediately.
Example
REWIND DEVICE=940A

ROTATE
Syntax

ROTATE [LOCAL|DRLOG]

Description
The ROTATE command rotates the local statistics file (LOCAL) or the DR Logging files (DRLOG) in
each of the tape library directories.
The current data will be zipped and the specified log will be cleared.

SAVE TRACE
Syntax

SAVE [TRACE]

Description
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. It also saves channel adapter
trace files to disk.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 119
Virtual tape operator command reference

SCRATCHNAME
Syntax

SCRATCHNAMES [ADD synonym[=(prefix,prefix,...,CLASS=CLASSn)]] [DELETE

synonym]

Description
The SCRATCHNAMES ADD command adds a new scratch synonym. The SCRATCHNAMES DELETE
command deletes an existing synonym. synonym is a 1-8 character scratch synonym (poolname).
SCRATCH is the minimum abbreviation for the SCRATCHNAMES command.
Options

Table 14 SCRATCHNAME command - option description

Value Description

ADD synonym[=(prefix,prefix,...,CLASS=CLASSn)] Adds a new scratch synonym.

For ADD, synonym must not exist as a current scratch
synonym. Otherwise, the command is rejected. Prefix(es)
and class are optional (default is no VOLSER prefix, class 0).
Valid prefixes are 1-6 valid VOLSER values. Any number of
prefixes may be specified, separated by commas, and must
precede any optional CLASS parameter.

DELETE synonym Deletes a scratch synonym.

For DELETE, synonym must exist as a current scratch
synonym. Otherwise, the command is rejected. DEL is the
minimum abbreviation for DELETE.

Example
The following are examples of valid SCRATCH ADD commands:
l SCRATCH ADD POOLFOUR=(D0,D1,D2,D3,D4)
The synonym POOLFOUR is added. POOLFOUR allocates scratch tapes with the VOLSER
prefixes “D0”, “D1”, “D2”, “D3”, and “D4” from CLASS 0 directories
l SCRATCH ADD SCRTCH1=(CLASS=CLASS1)
The synonym SCRTCH1 is added. SCRTCH1 allocates scratch tapes with any VOLSER prefix
from CLASS 1 directories.
l SCRATCH ADD SCRTCH3=(M0,CLASS=CLASS3)
The synonym SCRTCH3 is added. SCRTCH3 allocates scratch tapes with the VOLSER prefix
“M0” from CLASS 3 directories.
l SCRATCH ADD SCRTCH4=(ABA,ABB,ABC,CLASS=CLASS4)
The synonym SCRTCH4 is added. SCRTCH4 allocates scratch tapes with the VOLSER prefixes
“ABA”, “ABB”, and “ABC” from CLASS 4 directories.

120 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Virtual tape operator command reference

The following is an example of a valid SCRATCH DELETE command:

SCRATCH DEL SCRTCH4

SET
Syntax

SET [AMDD=ON|OFF]
[CRITICALPERCENT=nn]
[CRITICALSCRATCH=YES|NO]
[CRITICALEFSMOVE=YES|NO]
[CRITICALRO=YES|NO]
[CRITICALLEOT=YES|NO]
[DDWRITEVERIFY=ON|OFF|CRC|DATA|HEADERS]
[DEVICE=devicename|ALL]
[EFSMOVE=SPACE|RANDOM|NEVER]
[EFSMOVEFLR=ON/OFF]
[EFSMOVEDDRL=ON/OFF]
[EFSMOVEGR=ON/OFF]
[ENCRYPTKEY=[n|KEYn|NONE]
[ERASEMOVE=SPACE|COUNT|RANDOM|NEVER]
[ERASEPOLICYTTL=nnn|nnnH|nnnD|OFF]
[FILELISTREFRESHINTERVALDDREMOTE=OFF|nnn|nnnM|nnH]
[FILELISTREFRESHINTERVALVNXREMOTE=OFF|nnn|nnnM|nnH]
[FSALLOCATION=RR|SPACE]
[GR=YES | NO | SYNC | RUN [DEVICE=devname]]
[CELERRAREPORTINTERVAL=n]
[DDREPORTINTERVAL=n]
[GRREPORTINTERVAL=n]
[GRTIMEOUT=n]
[HWCOMP=ON|OFF|FORCE]
[HWDECOMP=ON|OFF|FORCE]
[IDRC=ON|OFF|FORCE]
[KEYCLASS=key_class|NONE]
[LEOT=xxx]
[MIGRATE=ON/OFF]
[NONTRUNCATEWRITE=YES|NO]
[PATH=pathname [NOCHECK]]
[PROTECTVOL1=ON|OFF]
[QSPACETIMEOUT=nn]
[RDC256K=ON|OFF]
[RECOVER=nn]
[RECOVERAMT=nn]
[RECOVERUPDATE=nn]
[RESCRATCHIFREAD=NO|YES]
[SIZE=xxx]
[TESTCOMPRESSEDDATA=TRUE|FALSE|CRYPT]
[TIMESTAMPS=NO|YES]
[TRACE=n]
[VOL=prefix]
[WARNING=nn]
[WRITEVERIFY=ON|OFF|CRC|DATA|HEADERS]
[LTR=ON/OFF]
[MIGRATE=ON/OFF]
[VIRTUALSCRTCH=NO/YES]
[FLRLOCKIFEXPIRED=YES/NO]

Description
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 Virtuent is started. To make permanent changes, make the changes in the VTE
configuration file.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 121
Virtual tape operator command reference

Options
The following table provides the descriptions for the command options:

Table 15 Set command—option description

Value Description

CRITICALSCRATCH=[YES|NO] These parameters enable setting of the critical usage threshold and
CRITICALPERCENT=nn behaviors.
CRITICALEFSMOVE=[YES|NO]
l CRITICALPERCENT is the percentage threshold at which the critical
CRITICALRO=[YES|NO]
space behaviors are invoked. The default is 97%. Valid values are 0–
CRITICALLEOT=[YES|NO]
100, inclusive.
l CRITICALSCRATCH controls the critical-space scratch allocation
behavior. YES, the default, prevents a scratch allocation from any file
system that is at or above the critical space threshold. NO specifies
that a scratch is allocated regardless of critical space.
l CRITICALEFSMOVE controls the critical-space EFS move behavior.
YES, the default, prevents moving of a scratch tape into a file system
that is at or above the critical space threshold. NO specifies that a
scratch tape may be moved into a file system regardless of critical
space.
l CRITICALRO controls the critical-space read-only behavior. YES, the
default, causes all tapes that are mounted from a file system that is
at or above the critical space threshold to be mounted read-only. NO
specifies that a tape is mounted normally regardless of critical space.
l CRITICALLEOT controls the critical-space LEOT behavior. YES, the
default, causes writes to all tapes mounted from a file system that is
at or above the critical space threshold to receive immediate LEOT
(logical end of tape - tape full) indication. NO specifies normal
behavior regardless of critical space.

DEVICE=[devname|ALL] Specifies which device name (or all devices) to set the specified value
for.

EFSMOVE=[SPACE|RANDOM|NEVER] Indicates whether files will be moved based on free space, randomly or
never when the EFS feature is in use.

ERASEMOVE=SPACE|COUNT|RANDOM| Indicates whether erased scratch files will be moved based on free space,
NEVER scratch count, random or never.

ERASEPOLICYTTL=[nnn|nnnH| Sets the Erase Policy TTL value to OFF or sets the Erase Policy TTL to a
nnnD|OFF] value in days (default) or hours. For example, the SET
ERASEPOLICYTTL=10D command results in setting the TTL
ERASEPOLICY to 10 days. SET ERASEPOLICYTTL=OFF turns off TTL
ERASEPOLICY.

FLRLOCKIFEXPIRED=YES|NO Controls whether the tape is locked when unloading if the determined
retention period is a past date (meaning the tape would already be
expired). The default for this parameter is YES, which will set the
retention period to the date specified. This results in a past date and FLR
sets permanent retention on the tape. If the value is NO, Virtuent does
not lock the file. This parameter only affects the initial writing of the
tape, not when extending (modifying). FLRLOCKIFEXPIRED=NO has an
effect if HDR1 includes a past date.
This is a global parameter; it affects all virtual devices on the VTE.

122 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Virtual tape operator command reference

Table 15 Set command—option description (continued)

Value Description

FSALLOCATION=[RR|SPACE] Sets the method for choosing a file system for a scratch tape mount. The
default is RR (Round Robin); Virtuent cycles to the least-frequently used
eligible file system to fulfill a scratch tape mount request. RR is the
recommended setting as it tends to allocate scratch tapes evenly from all
the file systems over time. The SPACE setting instructs Virtuent to use
the file system with the most available free space, and is not
recommended as it tends to allocate scratch tapes from a limited number
of file systems rather than spreading them out more evenly.

GR=YES|NO|SYNC|RUN Enables or disables the Guaranteed Replication or Replication on RUN for

[DEVICE=devname] one or more devices. If no device is specified, the option is changed for
every device.

CELERRAREPORTINTERVAL=n Specifies the frequency in seconds at which Virtuent checks if the

Celerra report written by the Control Station in /opt/DLm/VNX-n/
dlmconfig/ has been updated, and reloads the report if it has changed.
Any positive number, including 0, is valid. The default is 33 seconds.

DDREPORTINTERVAL=n Specifies the frequency in seconds at which Virtuent checks if the DD

report written by the Data Domain in /opt/DLm/DD-n/dlmconfig/ has
been updated, and reloads the report if it has changed. Any positive
number, including 0, is valid. The default is 33 seconds.

GRREPORTINTERVAL=n GRREPORTINTERVAL sets both CELERRAREPORTINTERVAL and

DDREPORTINTERVAL values. Any positive number, including 0, is valid.

GRTIMEOUT=n Sets the number of seconds that Virtuent waits for a replication refresh
to complete before sending an error to the host. Any positive number,
including 0, is valid. Changing the GRTIMEOUT value affects any
replication refreshes that are already in progress. GRTIMEOUT is a global
option, and cannot be set by individual device.

HWCOMP=[ON|OFF|FORCE] Indicates whether the VTE uses the hardware compression adapter to
perform data compression. 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. Normally, hardware compression is switched off if any error
occurs during hardware compression. If HWCOMP=FORCE is specified,
hardware compression remains on even if a hardware compression error
occurs. DLm only compresses data with a block size of 100 bytes or more.

HWDECOMP=[ON|OFF|FORCE] Indicates whether the VTE uses the hardware compression adapter to
perform data decompression. By default, the VTE uses hardware
decompression (HWDECOMP=ON) whenever the compression hardware is
present and decompression is required. If you set HWDECOMP=OFF, the
VTE uses software decompression when decompression is needed.
Hardware decompression is switched off if any error occurs during
hardware decompression. If HWDECOMP=FORCE is specified, hardware
decompression remains on even if a hardware decompression error
occurs.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 123
Virtual tape operator command reference

Table 15 Set command—option description (continued)

Value Description

IDRC=[ON|OFF|FORCE] 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. If you set IDRC=OFF, the VTE still reports to
the host that it supports compression, although it does not perform any
compression when it writes data to disk. This is because some host
operating systems or tape managers will not use drives that do not
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. DLm only compresses data with a block size of 100
bytes or more.

LEOT=xxx Sets the distance from Physical End of Tape (PEOT) at which Virtuent
starts returning Logical End of Tape (LEOT) signals to the host. LEOT is a
global value; all tape devices use the same value. LEOT can be specified in
bytes ("SIZE=1234500000") kilobytes ("SIZE=1234500 K"), megabytes
("SIZE=1234.5M"), GB ("SIZE=1.2345G"), or terabytes ("SIZE=2T").
Valid values are 0 (bytes) to 32T. The new size value takes effect
immediately. The default value is 10M.

LTR=ON/OFF Controls the LTR feature. The default is ON.

MIGRATE=ON/OFF Enables or disables the migration feature. If the migration feature is

turned off with the SET MIGRATE=OFF command, any migrations in
progress continue to normal completion, but no new migrations are
started until the feature is re-enabled. The default is ON.

NONTRUNCATEWRITE=[YES|NO] Controls the non-truncate first-write feature. The default is YES. Non-
truncate first write is a performance feature that deletes the tape and re-
creates it when writing at loadpoint, as this is faster than truncating a
large existing file.

PATH=pathname[NOCHECK] 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 or drive is not waiting for specific mount, 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 in DLm. Always specify the tape library base directory, that is, /
tapelib, not a subdirectory of the tape library (such as /tapelib/
BA). Virtuent 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.

124 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Virtual tape operator command reference

Table 15 Set command—option description (continued)

Value Description

PROTECTVOL1=[ON|OFF] ON prevents accidental overwriting of a VOL1 label. Any attempt to

overwrite a VOL1 label with one of the following will be blocked with a
write-protect error, with message DLm0920E displayed:
l Data
l A tapemark after data has been written elsewhere on the tape during
the same usage
Message DLm0921I will also be displayed each time, as a reminder that
the feature can be turned off if required. This feature is ON by default.
Note: ON does not protect the VOL1 label against intentional
overwrites by utilities like IEHINITT.

QSPACETIMEOUT=nn Sets the number of minutes that QUERY SPACE can run before it is
automatically canceled.

RDC256K=[ON|OFF] Can be used to disable the default behavior of setting the"256 K writes
supported" bit in the 3490 Read Configuration Data. The default is ON.

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 0–100.
Note: If the recovery percentage is set to 100, the VTE never
automatically deletes scratch volume data to recover disk space.

RECOVERAMT=nn Sets the maximum amount of space (in percentage of disk space) that
Virtuent attempts to recover once the recovery threshold is reached.
Valid values are 1–100.

RECOVERUPDATE=nn Sets a forced space recovery attempt to occur every nn hours when the
amount of space that is used in a given tape library directory is above the
RECOVER threshold, but has not changed in percentage value since the
last space recovery attempt ended. The valid range is 1 hour to 8760
hours (365 days). The default is 24 hours.

RESCRATCHIFREAD=[NO|YES] Changes Virtuent behavior regarding the returning of scratch tapes back
to scratch status when they are unloaded. The default is NO, which is the
original behavior: If a scratch tape is read, it stays in the active state
when unloaded. If set to YES, a scratch tape that has been read (but not
written) is returned to scratch status when unloaded.
Note: This parameter is applicable only to tapes mounted by a scratch
request. If you mount a scratch volume explicitly by requesting a
specific VOLSER, the host ignores the RESCRATCHIFREAD=YES
option.

SIZE=xxx Sets the maximum volume size for virtual tape volumes. The valid range is
15M (15 megabytes) to 32T (32 terabytes). The maximum allowable tape
size is limited to the amount of available storage in the file system. You
can specify a single DEVICE, or ALL devices simultaneously (the default).
You can specify the size in bytes, kilobytes (K), megabytes (M),
gigabytes (G), or terabytes (T). For example: "SIZE=16000000",
"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 SIZE is changed and the position on the tape is

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 125
Virtual tape operator command reference

Table 15 Set command—option description (continued)

Value Description

already past the new SIZE value, Virtuent sends logical end-of-volume
warnings on all subsequent write/write tapemark commands. Virtuent
signals the physical end of the volume approximately LEOT bytes past the
current position.

TESTCOMPRESSEDDATA=[ON|OFF| Controls the integrity check of data after compression. If this option is
CRYPT] set to CRYPT (the default), data that is compressed by Virtuent is
decompressed, and if encrypted it is also decrypted, then compared to
the original data from the host before it is written to the virtual tape
library. If this option is set to ON, data that is compressed by Virtuent is
decompressed to test compression integrity but the test does not
perform data decryption. In either case, if a discrepancy is found, an error
is returned to the Host's write command. If the Test Compressed Data
feature is turned OFF, no extra integrity check is performed after
compression before writing the data to the tape library. The Test
Compressed Data value is shown in message DLm0068I when configured,
SET, or with the QUERY ALL command .

TIMESTAMPS=[NO|YES] Indicates whether the date and time should be included in each message
that is sent to the VT Console. The default is NO to reduce the amount of
data being displayed on the VT Console. Messages written to the logfiles
are always timestamped. This parameter affects only messages to the VT
Console.

TRACE=n Sets the trace level for a specific device when you specify a
DEVICE=devicename. If ALL is specified, the trace level is set for all
devices plus the general system trace simultaneously. The default is ALL
if no DEVICE is specified. This option affects only Virtuent traces.

VIRTUALSCRTCH=NO/YES Specifying VIRTUALSCRTCH=YES places the identifier VirtualSCRTCH

on the System Code field of the HDR1 label of any newly initialized (never
used) tape. This identifier may signify to the host that this tape resides in
a virtual tape library. This option is required under certain circumstances,
such as with RMM when a VOLSER that was previously cataloged on the
host has been reinitialized on the DLm. This prevents the host from
rejecting the tape due to an incorrect dataset name. VIRTUALSCRTCH
option has no effect when reading AL and NL tapes. The default option is
NO.

VOL=prefix Sets an extra filter for scratch volume selection for a given device. After
meeting all other scratch selection criteria, the candidate VOLSER is
checked against this VOL parameter and is selected only if it matches this
prefix.

WARNING=nnn Sets the percentage of disk space usage at which Virtuent begins to warn
about usage. The valid range is 0–100.

WRITEVERIFY=[ON|OFF|CRC|DATA| Controls the degree of data verification Virtuent performs following

HEADERS] writing of data to the tape library.
l CRC reads the data from the disk, checks the disk CRC, but doesn't
decrypt or decompress the data. This is the default option when ON is
selected.

126 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Virtual tape operator command reference

Table 15 Set command—option description (continued)

Value Description

l ON is synonymous with CRC. After writes, the data will be read back
and checked against the CRC generated when it was written.
l OFF turns off all read-back verification of data written to the tape
library.
l DATA configures the write verification feature to perform full
verification of the data blocks. Full verification entails reading,
checking the data against the CRC generated when it was written,
decrypting, decompressing, and checking the CRC of the block
against the original CRC written by the host.
l HEADERS configures the write verification feature to only check the
AWS headers of each block. When HEADERS is set, the full data
blocks are not read or checked

Example
SET HWDECOMP=OFF
SET HWCOMP=OFF
SET ERASEPOLICYTTL=1D

SNMP
Syntax

SNMP [TEST] [ENABLE|DISABLE] [SHOW | STATUS]

Description
Use the SNMP command to enable or disable the SNMP feature on a VTE, or to display its status.

Table 16 SNMP command—option description

Value Description

TEST Tests sending SNMP traps for different types of

messages (info/warning/error)

[ENABLE | DISABLE] Enables or disables usage of SNMP feature on current

VTE.

[SHOW | STATUS] Displays status of SNMP feature on current VTE.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 127
Virtual tape operator command reference

STARTVT
Syntax

STARTVT

Description
This command starts Virtuent on the VTE.
This command is only valid when the VT Console window indicates that the VT status is Not
Running.
Once the VT status is Running, tape devices on this VTE may be varied online on the mainframe.
Note: The STARTVT command works only when entered directly through the VT Console. It
does not work when sent from the mainframe through the DLMHOST or when used with
CP501.

STOPVT
Syntax

STOPVT [!]

Description
This command stops Virtuent on the VTE.
This command is only valid when the VT 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: The STOPVT and STOPVT! commands work only when entered directly through the VT
Console. They do not work when sent from the mainframe through the DLMHOST or when
used with CP501.

UNLOAD
Syntax

UNLOAD [[DEVICE=]devicename]

Description
Use the UNLOAD command to perform a manual unload of the specified virtual tape drive.

128 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Virtual tape operator command reference

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.
The UNLOAD command is run 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 to not be in use by a host
application, but needs to be unloaded immediately.
You can also use the UNLOAD command to interrupt a specific migration that is in progress. If
either a migration “from” device or “to” device is specified in the UNLOAD command, the
migration is terminated with a DLm2661I “migration interrupted” message displayed. Both the
original source file and the partial target file are left in place. Migration “from” and “to” device
names can be seen in various migration messages as well as with the QUERY command.
Example
UNLOAD DEVICE=9200

UNQUIESCE
Syntax

UNQUIESCE [[DEV=]devicename|ALL|*] [SCRATCH PATH=path] [TAPELIB PATH=path]

Description
The UNQUIESCE command removes one or all of the virtual devices, or a tape library directory, or
a scratch tape library directory from the quiesced state. After being unquiesced, drives once again
accept mount requests. Pending load requests issued by the host while a drive was quiesced will
be automatically retried and performed when the drive is unquiesced. Once unquiesced, the tape
library directory becomes eligible for searches and mounting scratch volumes.
Unquiescing a drive does not send any signal to the host.
Options
The following table provides the descriptions for the command options:

Table 17 Unquiesce command — option description

Value Description

ALL or * Unquiesces all drives at once

UNQUIESCE SCRATCH PATH=path Unquiesces quiesced scratch tape library directories

UNQUIESCE TAPELIB PATH=path Unquiesces quiesced tape library directories

Example
UNQUIESCE DEVICE=4000
UNQUIESCE TAPELIB PATH=/tapelib/FS1

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 129
Virtual tape operator command reference

UNREADY
Syntax

UNREADY [DEVICE=]devicename

Description
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 no host application is using it.
Example
UNREADY DEVICE=9200
UNREADY CD05

130 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
APPENDIX B
SMP/E Installation

This appendix provides detailed instructions for the SMP/E installation process.

l Introduction to SMP/E Installation ......................................................................................132

l Loading DLMSxyz.XMITLIB to disk...................................................................................... 132
l Preparing DLMSxyz.XMITLIB(#EXTRACT)......................................................................... 134
l Customizing the RIMLIB JCL .............................................................................................. 135
l Running the installation jobs ................................................................................................138
l Performing a cleanup........................................................................................................... 139
l Applying maintenance ......................................................................................................... 139
l Authorizing DLm LINKLIB and Recycle DLMHOST...............................................................139
l Shutting down and restarting DLMHOST ............................................................................140

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 131
SMP/E Installation

Introduction to SMP/E Installation

About this task
DLm supports SMP/E-based installation procedures for DLm Utilities and JCL for z/OS.
Note: In this chapter, x.y.z is used to denote the release number. For example, for DLm release
5.0.0, x.y.z refers to 5.0.0 and xyz refers to 500.
The DLm kit consists of a flattened file (DLMSxyz.XMITFILE) that contains a PDS of TSO
TRANSMIT images of files, and the JCL needed to perform an SMP/E indirect-library installation
on the product. The PDS is packaged as a TSO TRANSMIT file on a CD or in an open systems zip
file, DLMSxyz.zip, for an electronic download from Dell EMC's Online Support Downloads section.
Also included on the CD, or within the zip file, is a ReadMe_DLMSxyz.txt text file which contains
installation instructions.
The steps for installation are:
Procedure
1. Load DLMSxyz.XMITLIB to disk.
2. Prepare DLMSxyz.XMITLIB(#EXTRACT).
3. Customize the RIMLIB JCL
4. Run the installation jobs.
5. Perform cleanup.
6. Apply maintenance.
7. Shut down and restart DLMHOST.

Loading DLMSxyz.XMITLIB to disk

About this task
You can choose to load the software in one of two ways:
l Installing DLm from a CD
l Installing DLm from the online Dell EMC Support web page
To install DLm from a CD:
Procedure
1. If you are installing DLm from a CD:
a. Mount the CD on an open systems host. The host must have FTP installed.
b. Allocate a working directory on the open system for the installation.
c. Copy the contents of the CD to that working directory.
2. If you are installing DLm from the online Dell EMC Support web page, perform the following
steps:
a. Log in to a privileged account on an open systems host (root on UNIX or administrator on
Windows).
b. Allocate a working directory on the open system for the installation.
c. Log on to the Dell EMC Support home page: https://www.dell.com/support.

132 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 SMP/E Installation

d. Click on Downloads. In the Type a Product Name field, type Disk Library for
mainframe immediately followed by the applicable DLm model (for example, DLm8500)
for which you are searching. Select the text that automatically displays for the
appropriate DLm model and click the Search button.
e. Click on DLm 5.x.x SMP/E z/OS base pkg (500) to download. This zip file contains the
installation kit and the installation instructions.
f. Download the installation kit into the working directory you selected above.
g. If your current host is a Windows system, unzip the file in the working directory. If your
current host is a UNIX system, unzip and untar the file in the working directory.
h. Locate the DLMSxyz.XMITFILE. This file is in the TSO TRANSMIT format and contains a
flattened copy of DLMSxyz.XMITLIB, a PDS that holds other TRANSMIT images, the
JCL to extract them, and necessary SMP/E installation files.
i. On the target mainframe, allocate a file to which you can FTP the DLMSxyz.XMITFILE.
Use the Data Set name prefix you intend to use for product installation. For example, if
you intend to install the product with the recommended Data Set name prefix of
EMC.DLMSxyz, name the file EMC.DLMSxyz.XMITFILE.
j. Allocate the Data Set with the following characteristics:
l LRECL=80
l BLKSIZE=3120 (This value is required)
l DSORG=PS
l SPACE=(CYL,(5,2)) (Assumes 3390 devices)
l RECFM=FB
Note: The SPACE parameter here and elsewhere assumes that you are allocating the
dataset on a 3390 device.

k. FTP the DLMSxyz.XMITFILE to the mainframe in binary format (as-is without translation
or encoding).
Your FTP session may look similar to:

ftp> binary
200 Representation type is Image
ftp> put DLMS500.xmitfile 'emc.dlms500.xmitfile'
200 Port request OK.
125 Storing data set EMC.DLMS500.XMITFILE
250 Transfer completed successfully.
ftp: 1401360 bytes sent in 2.70Seconds 519.21Kbytes/sec.
ftp>

Note: If you use another method, such as IND$FILE, ensure that you use the
equivalent of the ftp binary format.

l. Use TSO RECEIVE to receive the file into a PDS. The PDS is created by the RECEIVE
command and does not have to be pre-allocated. However, you must specify a Data Set
name using the DA[taset] parameter; otherwise the file is allocated using your TSO prefix
(usually your logon id). Use the Data Set prefix that you intend to use for the product
libraries.
For example:

Menu List Mode Functions Utilities Help

------------------------------------------------------------------------------

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 133
SMP/E Installation

ISPF Command Shell

Enter TSO or Workstation commands below:

===> receive INDA('EMC.DLMS500.XMITFILE')

INMR901I Dataset EMC.DLMS500.XMITLIB from LLINKE1 on NODENAME

INMR906A Enter restore parameters or 'DELETE' or 'END' +
DA('EMC.DLMS500.XMITLIB')
IEBCOPY MESSAGES AND CONTROL STATEMENT
S PAGE 1
IEB1135I IEBCOPY FMID HDZ1C10 SERVICE LEVEL UA56546 DATED 20100830 DFSMS 01.
12.00 z/OS 01.12.00 HBB7770 CPU 2818
Û}
IEB1035I RGUSER7 IKJACCNT IKJACCNT 10:08:19 THU 09 APR 2015 PARM='WORK=4M,SIZE
=1M'
COPY INDD=((SYS00081,R)),OUTDD=SYS00080
IEB1013I COPYING FROM PDSU INDD=SYS00081 VOL=Z1CWK9 DSN=SYS15099.T100819.RA000
.RGUSER7.R0103201
IEB1014I TO PDS OUTDD=SYS00080 VOL=W54753 DSN=EMC.DLMS500.XMITLIB
IEB167I FOLLOWING MEMBER(S) LOADED FROM INPUT DATA SET REFERENCED BY SYS00081
IEB154I $$README HAS BEEN SUCCESSFULLY LOADED
IEB154I $$VER HAS BEEN SUCCESSFULLY LOADED
IEB154I #EXTRACT HAS BEEN SUCCESSFULLY LOADED
IEB154I RIMLIB HAS BEEN SUCCESSFULLY LOADED
IEB154I SETUP HAS BEEN SUCCESSFULLY LOADED
IEB154I SMPMCS HAS BEEN SUCCESSFULLY LOADED
***

IEB154I XEXELIB HAS BEEN SUCCESSFULLY LOADED

IEB154I XJCLLIB HAS BEEN SUCCESSFULLY LOADED
IEB154I XMITJCL HAS BEEN SUCCESSFULLY LOADED
IEB154I XMTWIN1 HAS BEEN SUCCESSFULLY LOADED
IEB154I XOBJLIB HAS BEEN SUCCESSFULLY LOADED
IEB154I XPNLLIB HAS BEEN SUCCESSFULLY LOADED
IEB154I XSAMLIB HAS BEEN SUCCESSFULLY LOADED
IEB1098I 13 OF 13 MEMBERS LOADED FROM INPUT DATA SET REFERENCED BY SYS00081
IEB144I THERE ARE 16 UNUSED TRACKS IN OUTPUT DATA SET REFERENCED BY SYS00080
IEB149I THERE ARE 5 UNUSED DIRECTORY BLOCKS IN OUTPUT DIRECTORY
IEB147I END OF JOB - 0 WAS HIGHEST SEVERITY CODE
INMR001I Restore successful to dataset 'EMC.DLMS500.XMITLIB'
***

Note: If you did not specify "DA(…)" as above, the Data Set would be allocated as
user ID.XMITLIB.

Preparing DLMSxyz.XMITLIB(#EXTRACT)
About this task
Prepare DLMSxyz.XMITLIB(#EXTRACT) to extract ds-prefix.RIMLIB and the SMP/E indirect
libraries by completing the following steps:
Procedure
1. Edit the #EXTRACT member of the newly RECEIVED library. You can edit the #EXTRACT
job by running the SETUP REXX program in the XMITLIB Data Set. The SETUP REXX
program prompts you for all of the information needed to edit the JOB. For example:

Menu Functions Confirm Utilities Help

------------------------------------------------------------------------------
DSLIST EMC.DLMS500.XMITLIB Row 00001 of 00013
Command ===> Scroll ===> CSR
Name Prompt Size Created Changed ID
________ $$README 287 2006/08/31 2015/02/11 11:09:02 DLMS500

134 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 SMP/E Installation

________ $$VER 1 2010/11/11 2015/02/11 11:09:23 DLMS500

________ #EXTRACT 103 2015/02/11 2015/02/11 14:28:15 DLMS500
________ RIMLIB 1441 2015/02/11 2015/02/11 14:28:15 DLMS500
EX______ SETUP 21 2015/02/11 2015/02/11 14:28:15 DLMS500
________ SMPMCS 131 2015/02/11 2015/02/11 14:28:15 DLMS500
________ XEXELIB 9702 2015/02/11 2015/02/11 14:28:15 DLMS500
________ XJCLLIB 82 2015/02/11 2015/02/11 14:28:15 DLMS500
________ XMITJCL 254 2006/08/31 2014/06/10 16:32:28 DLMS500
________ XMTWIN1 48 2006/08/31 2015/02/11 11:17:39 DLMS500
________ XOBJLIB 1667 2015/02/11 2015/02/11 14:28:15 DLMS500
________ XPNLLIB 1258 2015/02/11 2015/02/11 14:28:15 DLMS500
________ XSAMLIB 2278 2015/02/11 2015/02/11 14:28:15 DLMS500
**End**

In the above example, the received dataset is listed in an ISPF 3.4 member list, EX has been
entered next to the SETUP member, and Enter is pressed.
The following is a sample of the SETUP Customization panel:

+---------------------- EMC JCL Customization Utility ----------------------+

| COMMAND ==> _____________________________________________________________ |
| |
| Type EXEC on the command line and press ENTER to proceed, or PF3 to exit. |
| |
| CLIST library ==> 'EMC.DLMS500.XMITLIB' |
| Edit macro name ==> XMIT |
| XMITLIB dsname prefix ==> EMC.DLMS500 |
| |
| |
| Install-to disk volser==> ______ Disk unit name ==> SYSDA |
| |
| Enter your job card below ('%MEMBER%' will be replaced by member name): |
| => //RGREEN7X JOB MSGCLASS=A,CLASS=A,MSGLEVEL=(1,1) |
+---------------------------------------------------------------------------+

2. Specify the job card and install-to VOLSER and change any defaults as required. Then press
Enter to update the #EXTRACT member with the correct JCL customization.
3. If you wish to edit the #EXTRACT manually, make the following changes:
a. Change the job card to one that conforms to your standards.
b. Globally change ds-prefix to the Data Set prefix of this library (to be the Data Set prefix
for the product libraries).
c. Globally change DVOL to a disk VOLSER that can be used to hold the extracted libraries.
d. Globally change DISK-UNIT to a site-appropriate unit name.
4. Submit #EXTRACT. All step completion codes must be 0, except for the DELETE step,
which has a step completion code of 8, unless the job is a rerun. The #EXTRACT JOB
creates all the data sets needed to do an SMP/E install.

Customizing the RIMLIB JCL

About this task
Continue the installation process by editing the JCL in the RIMLIB created by the #EXTRACT JOB.
Table 18 RIMLIB File Contents

Contents Description

#U1ALLOC Allocate product and SMP/E datasets (Upgrade install only)

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 135
SMP/E Installation

Table 18 RIMLIB File Contents (continued)

Contents Description

#U4DDDEF Adds required DDDEF and other required UCLIN to SMP/E

CSI (Upgrade install only)

#01ALLOC Allocate product and SMP/E datasets

#02DFZON Defines SMP/E CSI cluster

#03REPRO Initializes SMP/E CSI cluster with

SYS1.SAMPLIB(GIMZPOOL)

#04DDDEF Adds required DDDEF and other required UCLIN to SMP/E

CSI

#05RECEV Receives DLM V5.0.0 functions

#06APPLY Applies DLM V5.0.0 functions

#07ACCPT Accepts DLM V5.0.0 functions

#08CLEAN Removes unneeded DDDEF entries and deletes unneeded

datasets.

#99MAINT Boilerplate JCL to receive and apply maintenance

DLMJCL Recommended optional JCL customization REXX exec.

DLMWIN1 ISPF panel definition used by DLMJCL exec.

SETUP REXX program to run DLMJCL directly from the RIMLIB

The RIMLIB library (ds-prefix.RIMLIB) is a PDS containing JCL to install the product. After you
have extracted the RIMLIB PDS, RIMLIB has the contents shown in the table above.
Note: The RIMLIB dataset also includes a $$README member with includes installation
instructions.
Note: Dell EMC strongly suggests that you use the DLMJCL utility, contained in the RIMLIB
dataset to perform this task. However, if you prefer to do it manually, refer to the $$README
member for manual editing instructions.
To customize the installation JCL using the DLMJCL utility with SETUP REXX:
Procedure
1. While in the EDIT or BROWSE member list, use the EX command on the SETUP member
and press <Enter>. A panel similar to the following is displayed:

+---------------------- EMC JCL Customization Utility ----------------------+

| COMMAND ==> _____________________________________________________________ |
| |
| Type EXEC on the command line and press ENTER to proceed, or PF3 to exit. |
| |
| CLIST library ==> 'EMC.DLM500.RIMLIB' |
| Edit macro name ==> DLM |
| Product dsname prefix ==> EMC.DLM500 |
| SMP/E dsname prefix ==> EMC.SMPE |
| SMP/E datasets volser ==> ______ |
| Install-to disk volser==> ______ Disk unit name ==> SYSDA |
| |
| Enter your job card below ('%MEMBER%' will be replaced by member name): |
| => //RGREEN7X JOB MSGCLASS=A,CLASS=A,MSGLEVEL=(1,1) |
+---------------------------------------------------------------------------+

136 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 SMP/E Installation

2. Customize the JCL:

a. The CLIST library field is set by default to the name of the RIMLIB library. This field
must contain the name of a library in which you want the edit macro created by this
dialog to be stored. The default value is fine for most users and need not be changed.
b. In the Edit macro name field, perform one of the following:
l Accept the default name displayed.
l If necessary, change the name of the edit macro.
Note: Normally, you should not have to change the name.

c. In the Product dsname prefix field, enter the Data Set name prefix you want to use for
the DLm target data sets. Dell EMC suggests EMC.fmid.
d. In the SMP/E dsname prefix field, enter the Data Set name prefix of the SMP/E data
sets into which you installed Mainframe Enablers (EMCSCF).
e. In the SMP/E data sets volser field, enter the six-character volume serial number of
the disk volume on which you want to allocate the SMP/E distribution libraries for DLm.
This volume may be the same as the volume you specify in the SMP/E dsname prefix
field, or you may elect to keep these data sets on a separate volume.

f. In the Install-to disk volser field, enter the six-character volume serial number of the
disk volume to which you want to install the DLm libraries.
g. In the Disk unit name field, you can specify an esoteric disk name that is appropriate to
your site. SYSDA is the default, but you can overtype it with another esoteric disk name.
h. Enter a site-appropriate job card.
The job card is initially set to a value that may be suitable to many users. The first seven
characters of the job name is set to your TSO user ID, plus X.
You can set the job name to %MEMBER%. This causes the edit macro to set each job
name equal to the JCL member name (that is, #01ALLOC, #02DDDEF, and so forth).

Note: Do not use any parameter that contains an ampersand (&), such as
NOTIFY=&SYSUID. An ampersand in the job card can cause edit-macro errors.

3. Enter the following information in the Dell EMC JCL Customization Utility panel to
customize your installation:

+---------------------- EMC JCL Customization Utility ----------------------+

| COMMAND ==> _____________________________________________________________ |
| |
| Type EXEC on the command line and press ENTER to proceed, or PF3 to exit. |
| |
| CLIST library ==> 'EMC.DLM500.RIMLIB' |
| Edit macro name ==> DLM |
| Product dsname prefix ==> EMC.DLM500 |
| SMP/E dsname prefix ==> EMC.SMPE |
| SMP/E datasets volser ==> DVOL01 |
| Install-to disk volser==> DVOL02 Disk unit name ==> SYSDA |
| |
| Enter your job card below ('%MEMBER%' will be replaced by member name): |
| => //RGREEN7X JOB MSGCLASS=A,CLASS=A,MSGLEVEL=(1,1) |
+---------------------------------------------------------------------------+

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 137
SMP/E Installation

4. Type EXEC on the Command line and press Enter. You will see an output similar to the
following:

BUILDING AN EDIT MACRO(DLM) IN 'EMC.DLMS500.RIMLIB'

Processing Member: #U1ALLOC
Processing Member: #U2DFZON
Processing Member: #U3REPRO
Processing Member: #U4DDDEF
Processing Member: #01ALLOC
Processing Member: #02DFZON
Processing Member: #03REPRO
Processing Member: #04DDDEF
Processing Member: #05RECEV
Processing Member: #06APPLY
Processing Member: #07ACCPT
Processing Member: #08CLEAN
Processing Member: #99MAINT
***

Running the installation jobs

About this task
Carefully examine each job before you submit it to make sure that it was customized the way you
intended. Submit the customized jobs in the following order, making sure that each job completes
successfully before submitting the next one:
Procedure
1. Installing into a new SMP/E CSI:
a. #01ALLOC
b. #02DFZON
c. #03REPRO
d. #04DDDEF
e. #05RECEV
f. #06APPLY
g. #07ACCPT
h. #08CLEAN
2. Installing into an old SMP/E CSI from a previous version of DLM or a version of Dell EMC
Mainframe Enablers V7.0.0 or higher:
a. #U1ALLOC
b. #U4DDDEF
c. #05RECEV
d. #06APPLY
e. #07ACCPT
You should expect completion codes of 00 for all jobs except for #04DDDEF and
#U4DDDEF, where 04 is acceptable if this is a new installation rather than an upgrade, and
#07ACCPT, where 04 is acceptable on the SMP/E accept JOB.

138 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 SMP/E Installation

Performing a cleanup
About this task
After you are satisfied that DLm is correctly installed and functioning properly, run the #08CLEAN
job to delete data sets and DDDEFS used during the installation process that are no longer needed.

Applying maintenance
About this task
You must install any available maintenance for DLm before you start running. (If there is no current
maintenance, keep these instructions for future maintenance downloads.) You can obtain the
latest maintenance updates and current release or service notes (identical to release notes) from
the Downloads section on the Support menu in the Dell EMC Online Support website. Refer to the
“Loading DLMSxyz.XMITLIB to disk” section using DLMSxyz for the search. Any and all
maintenance that must be applied to this release will be in an item called DLMSxyz_Fixes.zip.
Note: If this file does not exist, there is no current maintenance to be applied.

This zip file contains the following:

l ReadMe_DLMSxyz_Fixes.txt: lists the fixes included in the release.
l Service_Notes_DLMSxyz.txt: updates the release notes with information discovered after
initial product release.
l DLMSxyz_Fixes.zip: contains the two previous files, as well as a software patch file
(DLMSxyzFix.bin), and a sample job (smpjob.txt) with instructions about how to apply the
maintenance.
To download maintenance from Dell EMC online support:
Procedure
1. Click Downloads, type DLMSxyz in the Search for Product text box, and press Enter.
2. Click the zip file, DLMSxyz_fixes.zip. Download the zip file to your home system, unpack the
zip file, and follow the instructions it contains.
3. When you are finished reading or copying from Dell EMC online support, return to the
previous pages to view other products and services, or choose Logout from the menu bar at
the top of any page.

Authorizing DLm LINKLIB and Recycle DLMHOST

About this task
The installed Linklib must be APF-Authorized. Add it to your existing authorized dataset list and/or
enter a SETPROG z/OS Console command to mark it as authorized until the next IPL for your
LPAR.
SETPROG APF,ADD,DSNAME=EMC.DLMSxyz.LINKLIB,SMS

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 139
SMP/E Installation

Shutting down and restarting DLMHOST

About this task
After you install this release of DLm and performed the above authorization, you must recycle
DLMHOST, (if it is currently running). Ensure that your DLMHOST JCL points to the installed
LINKLIB.

140 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
APPENDIX C
AWSTAPE Information

This appendix provides information on AWSTAPE.

l AWSTAPE format................................................................................................................ 142

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 141
AWSTAPE Information

AWSTAPE format
DLm stores virtual tape volumes on disk in the AWSTAPE format. The AWS format allows DLm to
maintain an exact representation of a physical tape, including variable block sizes, tapemarks,
labels, and so on.
Each AWSTAPE disk file emulates one physical tape volume.
Each emulated physical record in the emulated tape volume is represented by one or more pairs of
block headers followed by data. An emulated tapemark is represented only by a block header.
The following figure illustrates an AWSTAPE disk file:
Figure 40 AWSTAPE single disk file

1 2 3 4 5 6 7 8

Physical Tape Volume data block tapemark

H H HH H H H HH H H
D 1 D 2 DD 3 D 4 D 5 D 6 DD 7 D 8 D
R R RR R R R RR R R
AWSTAPE-Single Disk File Representing One Physical Tape Volume GEN-001170

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.

142 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
APPENDIX D
Volume Handling

This appendix describes volume handling in DLm. Major topics are:

l Volume serial numbers......................................................................................................... 144

l Scratch volumes.................................................................................................................. 144
l Mount volumes ................................................................................................................... 146

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 143
Volume Handling

Volume serial numbers

DLm supports those VOLSERs that conform to the IBM standard VOLSER naming convention.
IBM standard VOLSERs contain one to six alphanumeric EBCDIC characters of uppercase A
through Z, 0 through 9, and hyphen. VOLSERs are left-justified and padded with spaces on the
right.
The disk filename of a virtual tape volume matches the VOLSER converted from EBCDIC to ASCII
and holds the virtual tape volume.
The virtual volume's disk filename is equivalent to a physical tape's external label. It is important
for a physical tape's external label to always match the VOLSER recorded on the tape's VOL1 label
to identify, store, and retrieve it, and it is vital that a virtual volume's disk filename matches the
recorded VOLSER for the same reason.
As long as the host does not write a different VOLSER to the virtual volume, the disk filename and
the VOLSER recorded in the volume remain the same.
Under some circumstances, the host writes a new VOL1 label containing a VOLSER different from
the original that is associated with the mounted volume. This occurs when the host uses a program
such as Ditto to perform a physical tape copy that copies the original volume's labels and also its
data to the new tape.
Whenever the host writes a VOL1 label, Virtuent checks whether the VOLSER being written differs
from the original VOLSER under which the volume was mounted. This maintains the association
between a virtual volume's disk filename and the actual VOLSER recorded in the volume.
If the new VOLSER is different, Virtuent tries to rename the volume's disk filename to match the
new VOLSER in the VOL1 label being written. If the new VOLSER does not already exist in the
virtual tape library, Virtuent allows the VOL1 write and renames the disk file to the new VOLSER.
If the new disk filename (that is, the new VOLSER) already exists, Virtuent does not rename the
mounted volume and does not allow writing of the new VOL1 label. This returns an error (Unit
Check status with Command Reject sense) to the host's write command.
If the host changes a labeled volume to an unlabeled volume by writing over the standard labels
with data or a tapemark, Virtuent accepts the change but does not change the volume's filename.

Scratch volumes
Virtual volumes in a tape library exist in one of the three states:
l Active
Any volume that is not currently a scratch tape. A scratch volume becomes active whenever it
is mounted in response to a request from the host (or by a manual mount), whether by explicit
VOLSER or to fulfill a scratch tape request. Once a volume is active it is no longer a scratch
tape, so you can mount it again only by explicitly requesting it by specific VOLSER, not by a
scratch tape request.
You can recognize an active volume by its filename, which is exactly the same as its VOLSER.
Once a volume is active, it remains active in the virtual tape library until it is explicitly scratched
by the host.
l Scratched
Volumes created by Virtuent INITIALIZE command and available to be mounted in response
to a scratch tape request.
You can recognize a scratch volume by the fact that its filename is preceded by a tilde (~), for
example, ~BT0040.

144 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Volume Handling

When the host requests a scratch volume, Virtuent selects the oldest scratch volume from the
tape library directory that has the most free space, but only after any erased scratch volumes
have been used. You can also mount a scratch volume by explicitly requesting it by VOLSER. In
either case, whenever a scratch volume is mounted, it is changed to active status by renaming
the file from ~VOLSER back to VOLSER (without the ~) and is no longer a scratch tape.
Virtuent never moves an active volume to scratch status on its own. You can move volumes
from active to scratched state by using the DLMSCR utility running on the host. The Dell EMC
Disk Library for mainframe Command Processors and Utilities for z/OS Guide provides more
information on the DLMSCR utility. DLMSCR processes a host-generated scratch report and
sends scratch volume requests over the channel to Virtuent. When Virtuent receives a request
to scratch an active volume, the disk file for that volume is renamed from VOLSER to
~VOLSER. For example, scratching B00004 would rename the file to ~B00004. All of the data
in the scratched volume is retained at this time, although it may be deleted ("erased") later if
DLm needs the disk space.
l Erased
A scratch volume that has had its data deleted to recover disk space. Scratched tapes retain
their data as long as possible until Virtuent needs to reclaim disk space to write new data.
When DLm starts running out of disk space, it selects the oldest scratched volume from the
tape library and deletes its data. Virtuent will also erase scratched tapes when their "Time-To-
Live" (TTL) value has been exceeded.
When a scratch tape is "erased," all of the data in the volume past the standard header labels
is deleted. Only the VOL1 and HDR labels are retained (these are retained as some host tape
management systems verify the labels and previous dataset name (DSN) on a tape before
allowing a previously scratched tape to be reused). The disk filename remains ~VOLSER.
Note: After a scratch volume has been erased, the data cannot be recovered.

Virtuent selects an erased scratch tape in response to a scratch tape request from the host,
before selecting an unerased scratch tape. As with any scratch tape, whenever an erased
scratch volume is mounted, it is moved back to active status by renaming the file from
~VOLSER to VOLSER (without the ~).

Delete (erase) scratch volume data

When a virtual volume is scratched, the data in the volume remains intact for some period of time.
This provides some time to unscratch a tape that was accidentally scratched.
Eventually, as the library fills up, space must be recovered from scratched tapes to write new data.
By default, when the usage in any tape library directory within a tape library reaches 85 percent,
Virtuent starts recovering the disk space from scratch volumes in that library. The oldest scratch
volumes are moved to erased status and the data is deleted. Virtuent continues to erase scratched
volumes until the disk usage drops below 85 percent (or the value specified by the SET RECOVER
option) by an amount equal to five percent of the available disk space (or the percentage specified
by the SET RECOVERAMT option).
If the recovery percentage is set to 100 percent, Virtuent never automatically erases data from
scratch volumes to recover disk space.
In addition to the automatic space recovery based on disk usage described above, Virtuent will also
erase tapes when they reach the optional, configurable "Time-to-Live" (TTL) time. The TTL time
interval starts from the time when a tape is scratched.
Virtuent never automatically moves an active tape to scratch status, nor does it ever erase data
from an active tape.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 145
Volume Handling

Mount volumes
This section describes how to:
l Mount a specific volume by VOLSER
l Mount a scratch volume

Mount a specific volume by VOLSER

This section describes how VTEs handle requests to mount a specific volume by VOLSER, when:
l The requested VOLSER exists
l The requested VOLSER does not exist
l The volumes are write-protected

Requested VOLSER exists

When the host requests a specific VOLSER, the VTE receiving the Load Display command first
searches for the requested VOLSER as an active volume in the tape library. If not found, the VTE
searches for it as a scratch volume. If the VTE finds the specified VOLSER, it opens the file and
positions the file at the beginning of the volume (load point). The virtual tape drive presents a Not-
Ready-to-Ready interrupt to the host and enters the Ready state, ready for I/O from the host.
If the volume is a scratch volume, it is changed to active status by renaming the file VOLSER
(without the ~) before it mounts it.
If the volume is a scratch volume and its data has been deleted (it is in the erased state), the
volume is still mounted as requested. If the host attempts to read past the standard labels into the
non-existent data, it receives an I/O error (Unit Check status, Tape Void sense).

Requested VOLSER does not exist

If the host requests a VOLSER that does not exist as either an active or scratched volume in the
tape library assigned to this device, the virtual tape drive remains in a "mount-pending" state; the
drive will continue to search for the specified tape either until it finds it, or until the host cancels
the mount request.

Write-protected volumes
If a tape volume's disk file can only be opened in Read-Only mode (for example, it resides on a
read-only medium, in a directory with read-only access, or the file itself is read-only), the Write
Protect bit is set on the virtual tape drive while this volume is mounted. You can only read the
volume but you cannot write to it, in this situation. Any attempt to write (Write, Write Tapemark,
or Erase) to the volume results in a Unit Check error being presented to the host.

Mount a scratch volume

This section describes how VTEs handle requests to mount a scratch volume. z/OS uses some
character strings to indicate a request for a scratch tape to be mounted for output. These strings
are called scratch synonyms. By default, Virtuent recognizes SCRTCH and PRIVAT as a request
for a scratch tape and mounts an available scratch tape on the requested device to be used for
output. Virtuent allows you to define your own scratch synonyms. Do not use the names
"SCRTCH" or "PRIVAT" for the scratch synonyms you create.

146 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Volume Handling

Unlabeled scratch request

If the host requests an unlabeled scratch volume (determined by an N in the eighth position of the
mount message), Virtuent displays an error message and ignores the mount request, and the
virtual tape drive remains in the Not Ready state. This is because an unlabeled scratch tape cannot
be subsequently tracked or retrieved as no permanent VOLSER is associated with the volume.

Labeled scratch request

If the host requests a scratch volume with standard labels (anything other than N in the eighth
position of the Load Display Mount message), Virtuent checks any scratch synonym definitions
that might exist to identify which file systems in the tape library are eligible to supply the tape
based on CLASS definition (if any). Virtuent checks those eligible file systems to determine which
has the most free space. After identifying the file system, Virtuent searches that file system for a
scratched, erased volume. If it finds a scratched, erased volume, it changes the volume status to
active by renaming the file from ~VOLSER to VOLSER (without the ~).
Virtuent allows scratch volume allocations to be restricted to a specific range of tape volumes
beginning with the prefixes defined in the VOL parameter. 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.
Note: In an erased volume, no data follows the standard labels. Any attempt by the host to
read past the labels results in an I/O error (Unit Check status with Data Check and Tape Void
sense).
If Virtuent does not find a scratched, erased volume, it searches the selected file system for the
oldest scratch volume. If it finds a scratch volume, it changes the volume status to active by
renaming the file from ~VOLSER to VOLSER (without the ~). The existing data in the scratch
volume is not erased before mounting the tape.
Virtuent allows you to select one of two methods for choosing a file system for a scratch tape
mount:
l Round Robin (RR): Virtuent cycles to the least-frequently used eligible file system to fulfill a
scratch tape mount request. RR is the recommended setting as it tends to allocate scratch
tapes evenly from all the file systems over time.
l Space: The SPACE setting instructs Virtuent to use the file system with the most available free
space.
If DLm does not find a scratch volume on the tape library file system with the maximum free
space, it searches the next eligible file system with the next most free space, and so on until it
finds a scratch tape or until it has searched all file systems.
If DLm does not find a scratch volume to fulfill the mount request, it displays a message on the VT
Console and enters a "mount-pending" state. The drive continues to search for the specified tape
either until it finds it, or until the host cancels the mount request.
After Virtuent allocates a volume for the mount request, it opens the file and places it at the
beginning of the volume (load point). The virtual tape drive presents a Not-Ready-to-Ready
interrupt to the host and enters the Ready state, ready for I/O from the host.

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 147
Volume Handling

148 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
APPENDIX E
Load Display Command — CCW Opcode x'9F'

This appendix describes the Load Display command (CCW Opdcode x’9F’). Major topics are:

l Load display messages.........................................................................................................150

l Load display data................................................................................................................. 150

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 149
Load Display Command — CCW Opcode x'9F'

Load display messages

IBM-compatible 3480/3490/3590E tape drives support a Load Display command (CCW
Opcode x’9F’) that is used to display messages on the tape drive's LED display. The mainframe
operating system or the tape management system typically sends these messages to request the
operator to mount a specific volume.
Virtuent depends on the Load Display messages to determine when virtual tape volumes should be
mounted on its virtual tape drives. When Virtuent 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 Virtuent 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. Virtuent 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. Virtuent requires a specific Load Display message format to
determine that the host is requesting a volume mount. Specifically, Virtuent has been designed to
recognize the Load Display Mount messages issued by z/OS.
The format of the mount messages that Virtuent recognizes follows. “Format Control Byte”
provides detailed information about the Load Display messages format.
Format Control Byte
Virtuent 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.
Virtuent recognizes a mount request by the Load Display message format.
If the Load Display message does not pass all the tests to determine a mount request, the message
is simply ignored.

Load display data

The following table provides information about load display.

Table 19 Load display data

Bytes Description

0 Format Control Byte

1–8 Message 0

9–16 Message 1

Format Control Byte

The following table describes the Format Control Byte (FCB).

150 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax
 Load Display Command — CCW Opcode x'9F'

Table 20 Format Control Byte

Bits Value Description

0–2 Function select

000 The message specified in bytes 1–8 and 9–16 is maintained until the tape drive next starts tape motion or the
message is updated.

001 The message specified in bytes 1–8 is maintained until the tape cartridge is physically removed from the tape
drive or the next unload or load cycle.

010 The message specified in bytes 1–8 is maintained until the drive is next loaded.

011 This value is used to physically access a drive without changing the message display. This option can be used
to test whether a control unit can physically communicate with a drive.

100 to Reserved.
110

111 The message specified in bytes 1–8 and 9–16 is displayed. The message in bytes 1–8 is displayed until a tape
cartridge is physically removed from the tape drive, or until the drive is next loaded. The message in bytes
9–16 is displayed until the drive is next loaded (not including the loading of the cleaning cartridge). If no
cartridge is present in the drive, the first message is ignored and only the second message is displayed until
the drive is next loaded (not including the loading of the cleaning cartridge).

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)

Sample Load Display messages

The following are some sample Load Display messages. The hex values are in EBCDIC:
l 48D4C2E3 F0F0F0F1 E2000000 00000000 00
Interpretation:
n 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.
n Virtuent would interpret this as a valid mount request for standard labeled volume BT0001.
l 28D9C2E3 F4F44040 40000000 00000000 00
Interpretation:

Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax 151
Load Display Command — CCW Opcode x'9F'

n 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.
n Virtuent would ignore this message because it is not a mount request.
l F0D9C2E3 F0F0F2F2 40D4C2E3 F2F7F2F7 E2
Interpretation:
n 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.
n Virtuent would interpret this as a valid mount request for standard labeled volume BT2727.

152 Dell EMC Disk Library for mainframe User Guide for DLm8500 with PowerMax