Professional Documents
Culture Documents
Version 3.0
User Guide
P/N 300-012-441
REV A01
EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
Copyright © 2011 EMC Corporation. All rights reserved.
EMC believes the information in this publication is accurate as of its publication date. The information is
subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO
REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS
PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable
software license.
For the most up-to-date regulatory document for your product line, go to the Technical Documentation and
Advisories section on EMC support website.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.
All other trademarks used herein are the property of their respective owners.
Preface
Power up DLm.................................................................................. 57
VNX power-up........................................................................... 57
DD890 power-up ....................................................................... 61
ACP power-up ........................................................................... 62
VTE power-up............................................................................ 63
Power down DLm ............................................................................ 67
Power down the VTE ................................................................ 68
Power down DD890 .................................................................. 69
Power down VNX7500 ............................................................. 70
Power down the ACP ............................................................... 73
Start and stop tape devices.............................................................. 74
Initialize scratch volumes ................................................................ 76
Support access to DLm .................................................................... 78
ESRS............................................................................................. 78
Modem support ......................................................................... 79
IMPORT..................................................................................... 186
INITIALIZE............................................................................... 187
LOAD......................................................................................... 188
QUERY....................................................................................... 189
QUIESCE ................................................................................... 196
READY ...................................................................................... 197
RESET CHANNEL ADAPTER .............................................. 197
REWIND.................................................................................... 198
SAVE TRACE............................................................................ 198
SET ............................................................................................. 198
SHOW........................................................................................ 202
SNMP......................................................................................... 202
STARTVT................................................................................... 202
STOPVT ..................................................................................... 203
STOP CHANNEL ADAPTER ................................................ 203
UNLOAD .................................................................................. 203
UNQUIESCE............................................................................. 204
UNREADY ................................................................................ 204
Index
Title Page
1 DLm6000 overview ........................................................................................ 20
2 Front view of the VTE.................................................................................... 21
3 Rear view of a VTE......................................................................................... 22
4 Front view of the ACP ................................................................................... 23
5 Rear view of the ACP .................................................................................... 23
6 24-port AT-9924TL switch............................................................................. 24
7 Fujitsu XG2000R switch................................................................................. 24
8 DD890 Controller—Rear view ..................................................................... 25
9 DLm Console login page............................................................................... 46
10 DLm Console .................................................................................................. 47
11 DLm date and time ........................................................................................ 48
12 User ID creation.............................................................................................. 50
13 LDAP user authentication............................................................................. 52
14 VT console ....................................................................................................... 54
15 Rear of the SPS ................................................................................................ 58
16 Storage processor LEDs................................................................................. 58
17 VNX7500 cabinet ............................................................................................ 60
18 DD890 controller - front view....................................................................... 61
19 ACP indicators and controls......................................................................... 62
20 VTE indicators and controls ......................................................................... 64
21 VT console with VT application................................................................... 75
22 EMC Secure Remote Support ....................................................................... 78
23 Global options................................................................................................. 86
24 Control units ................................................................................................... 89
25 Add devices section ....................................................................................... 91
26 Scratch Synonyms .......................................................................................... 97
27 Save configuration.......................................................................................... 99
28 System status................................................................................................. 105
29 VTE logs......................................................................................................... 106
30 Gathering ACP and VTE support data ..................................................... 106
Title Page
1 DD890 stream count limits............................................................................. 25
2 FICON adapter LED indicators..................................................................... 29
3 DLm6000 device details.................................................................................. 30
4 Details of FICON connections ....................................................................... 31
5 DLm system access details............................................................................. 44
6 DD890 controller LEDs................................................................................... 62
7 Example of LIBRARY-ID and LIBPORT-ID .............................................. 141
8 Parameters in DLMSCR ............................................................................... 154
9 Error code from DLMCMD ......................................................................... 159
10 Load display data.......................................................................................... 210
11 Format Control Byte ..................................................................................... 210
Purpose EMC Disk Library for mainframe (DLm) provides IBM tape drive
emulation to the z/OS mainframe using disk storage systems in place
of physical tapes. This guide provides information about the features,
performance, and capacities of DLm 3.0 and later. It also includes
installation and configuration information that is required for
ongoing operation.
Audience This guide is part of the EMC DLm documentation set, and is
intended for use by system operators to assist in day-to-day
operation. Installation, configuration, and maintenance tasks must be
accomplished by qualified EMC service personnel only.
Readers of this document are expected to be familiar with tape library
operations and the associated tasks in the mainframe environment.
Conventions used in EMC uses the following conventions for special notices:
this document
DANGER
DANGER indicates a hazardous situation which, if not avoided, will
result in death or serious injury.
WARNING
WARNING indicates a hazardous situation which, if not avoided,
could result in death or serious injury.
! CAUTION
CAUTION, used with the safety alert symbol, indicates a
hazardous situation which, if not avoided, could result in minor or
moderate injury.
! IMPORTANT
An important notice contains information essential to software or
hardware operation.
Typographical conventions
EMC uses the following type style conventions in this document.
Normal Used in running (nonprocedural) text for:
• Names of interface elements (such as names of windows,
dialog boxes, buttons, fields, and menus)
• Names of resources, attributes, pools, Boolean expressions,
buttons, DQL statements, keywords, clauses, environment
variables, functions, utilities
• URLs, pathnames, filenames, directory names, computer
names, filenames, links, groups, service keys, file systems,
notifications
Bold Used in running (nonprocedural) text for:
• Names of commands, daemons, options, programs,
processes, services, applications, utilities, kernels,
notifications, system calls, man pages
Used in procedures for:
• Names of interface elements (such as names of windows,
dialog boxes, buttons, fields, and menus)
• What user specifically selects, clicks, presses, or types
Italic Used in all text (including procedures) for:
• Full titles of publications referenced in text
• Emphasis (for example a new term)
• Variables
Courier Used for:
• System output, such as an error message or script
• URLs, complete paths, filenames, prompts, and syntax when
shown outside of running text
Courier bold Used for:
• Specific user input (such as commands)
Courier italic Used in procedures for:
• Variables on command line
• User input variables
<> Angle brackets enclose parameter or variable values supplied by
the user
[] Square brackets enclose optional values
| Vertical bar indicates alternate selections - the bar means “or”
{} Braces indicate content that you must specify (that is, x or y or z)
... Ellipses indicate nonessential information omitted from the
example
Where to get help EMC support, product, and licensing information can be obtained as
follows.
Product information — For documentation, release notes, software
updates, or for information about EMC products, licensing, and
service, go to the EMC Online Support website.
Your comments Your suggestions will help us continue to improve the accuracy,
organization, and overall quality of the user publications. Please send
your opinions of this document to:
techpubcomments@emc.com
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).
VTE Each DLm configuration can have 1—6 VTEs. The mainframe virtual
tape emulation software, Virtuent, executes on the VTEs. VTEs
emulate IBM tape drives and interface to the mainframe and direct
tape data to and from the backend storage arrays. This data is written
to the storage arrays and stored in NFS filesystems over a redundant
10G data network.
GEN-001774
FICON Channel 1
FICON Channel 0
op e n
op e n
GEN-001775
ACP The ACPs are the Management Controller for the DLm6000. For high
availability reasons, the DLm6000 comes with two ACPs in a
primary-secondary configuration. This highly available configuration
requires a highly available IP address that is always associated with
the primary ACP. This ensures management access even when one of
the ACPs fail. If the primary ACP fails, the secondary ACP becomes
the primary.
Since the ACPs are the management interface for the DLm6000, they
provide a user-friendly console (DLm Console) to execute various
setup and configuration tasks. The ACPs connect to the DLm
management LAN of the DLm6000. The ACPs act as the firewall
isolating the internal DLm networks from the external LAN.
1 2
GEN-001776
B MG MT
CS
GEN-001777
DLm management The DLm6000 has an internal Gigabit Ethernet network for
network management purposes. The ACPs, VTEs, VNX, and Data Domain
systems management ports are connected to a pair of ATI9924TL
switches to protect against a single switch failure.
2
AT-9924TL-EMC
GEN-001778
10G data network The data from the mainframe is transferred to the DLm storage
systems over 10 Giga bit Ethernet connections. The 10G Ethernet
network has a pair of Fujitsu XG2000R switches to protect against a
single switch failure.
FUJISU
1 3 5 7 9 11 13 15 17 19 XG2000 Status
Dump Alarm
Power
2 4 6 8 10 12 14 16 18 20
Mng-LAN Console RS-232C
GEN-001779
Backend storage DLm6000 uses either a VNX7500 or a Data Domain DD890 for storing
the data written to the virtual tapes.
The DD890 is to be used for data that deduplicates well and the
VNX7500 should be used for all other data. Both systems export NFS
filesystems and the VTEs then use these NFS filesystems to store the
data.
Deduplicating storage The Data Domain system provides DLm's deduplication feature.
DLm uses a highly optimized inline data deduplication technology
that reduces the footprint by storing only the unique data. This also
reduces power consumption and provides a significant total cost
saving. The data is streamed from the mainframe through the VTEs
to the backend Data Domain storage system. Due to the inline
implementation, only the deduplicated, unique data gets stored on
the drives.
VNX storage The DLm6000 can be configured with a maximum of two VNX7500
network file servers. Each VNX7500 file can have 2-8 storage
controllers called Data Movers. All VNX7500 storage systems are
configured with a standby storage controller.
Choose VNX file storage for a large volume of data that does not need
to be stored for long periods of time and is not extensively redundant
to warrant deduplication.
Connect DLm to a DLm can be connected directly to the mainframe FICON channel or it
FICON channel can be connected through a FICON switch. In either case, to properly
define a DLm V348x, or 3490, or 3480 device on a z/OS system, the
following parameters are required:
◆ TYPE must be FC.
◆ UNIT can be defined as one of the following:
• One of the virtual device types: V3480, V3481, V3482, or
V3483
• A real 3490
• A real 3480
◆ CHPID can be defined as any one of the following:
• SHARED
• DED
• REC
Note: When configuring DLm devices as device type 3490, the maximum
number of devices per control unit is 16.
IODEVICE ADDRESS=(EA80,32),CUNUMBR=(EA80), +
STADET=Y,UNIT=V3480
CNTLUNIT CUNUMBR=EA80,PATH=(0A), +
UNITADD=((00,32)),UNIT=V3480
IODEVICE ADDRESS=(EA80,32),CUNUMBR=(EA80), +
STADET=Y,UNIT=V3480
CNTLUNIT CUNUMBR=EA80,PATH=(0A), +
UNITADD=((00,32)),UNIT=V3480
IODEVICE ADDRESS=(EA80,32),CUNUMBR=(EA80), +
STADET=Y,UNIT=V3480
Note: With EMIF (shared) mode, specify LPAR=n in the DLm virtual device
configuration program, where n is the LPAR to which the DLm device is
connected.
CNTLUNIT CUNUMBR=EA80,PATH=(0A,0B), +
UNITADD=((00,32)),UNIT=V3480
IODEVICE ADDRESS=(EA80,32),CUNUMBR=(EA80), +
STADET=Y,UNIT=V3480
Note: With EMIF (shared) mode, specify LPAR=n in the DLm virtual devices
configuration program, where n is the LPAR to which the DLm device is
connected.
CNTLUNIT CUNUMBR=300,PATH=(22),LINK=(C2), +
UNITADD=((00,32)),UNIT=V3480
IODEVICE ADDRESS=(300,32),CUNUMBR=(300),UNIT=V3480
`Status indicators Each FICON interface has a four-character display visible at the back
of the system adjacent to the interface connector. The display scrolls
the status of the interface. Under normal operating conditions, the
version of the emulation firmware interface is displayed.
On On On Power on
Logical storage at 10:1 total compression (TiB) 2.856 PiB 476 TiB
Number of ports 1
Tape emulation
DLm VTEs emulate the IBM tape drives to the mainframe and direct
the tape data to and from the backend storage arrays. Each VTE, once
configured, operates independently of the other VTEs in the VTEC
and can be configured with up to 256 tape drives. A DLm configured
with two VTEs can emulate up to 512 virtual tape devices, while one
with six VTEs can emulate up to 1,536 virtual tape devices at one
time.
The virtual tape emulation software:
◆ Receives and interprets channel command words (CCWs) from
the host
◆ Sends and receives the tape data records and reads and writes
corresponding disk data in response to the CCWs
◆ Presents initial, intermediate, and final status to the host
commands and asynchronous status as needed
◆ Sends and receives control information (such as sense and load
display data) to and from the host in response to the CCWs
Virtual tape drive A virtual tape drive is in one of the two basic states at any given
states time—Not Ready or Ready:
◆ In the Not Ready state, the virtual tape drive appears to the host
to be online but in an unmounted state. As on a real tape drive,
most channel commands are not accepted in this state and receive
a Unit Check status with an Intervention Required sense. While
in the Not Ready state, no disk file is opened on the disk
subsystem.
The Not Ready state is the initial state of all virtual tape drives,
and is entered whenever an Unload command is received from
the mainframe.
◆ In the Ready state, the virtual tape drive accepts all data
movement, read, and write commands from the host exactly like
the emulated tape drive. As the host reads, writes, and otherwise
positions the virtual tape, the application maintains
synchronization of the associated disk file to exactly match the
content and positioning of the virtual tape volume.
A virtual tape drive enters the Ready state when it receives a load
request from the host. When the Mount message is received, the
disk file associated with the volume specified in the Mount
message is opened, and the virtual tape drive comes Ready to the
host. The virtual tape drive remains in the Ready state, with the
associated disk file open, until an Unload command is received
from the host. On receiving an Unload command, the disk file is
closed and the virtual tape drive enters the Not Ready state.
Data formats The default file format for tape data written to the DLm disks is a
modified AWSTAPE format. This format keeps track of record
lengths as the file is being written so that the variable length records
can be read exactly as they were originally written.
Optionally, data can also be written as a plain, sequential (flat) file. In
this format, the original data record lengths, labels, and tapemarks
are lost, but any open-system application can read the data as a
sequential dataset.
Tape emulation 33
Overview of EMC Disk Library for Mainframe
Data Domain Because the Data Domain operating system (DD OS) is designed for
data protection, the goal of its architecture is data invulnerability. Its
design includes:
◆ End-to-end verification
◆ Fault avoidance and containment
◆ Continuous fault detection and healing
◆ Filesystem recovery
End-to-end When the DD OS receives a write request from the backup software,
verification it computes a huge checksum over the data. After analyzing the data
for redundancy, it stores only the new data segments and all of the
checksums. After the backup is complete and all the data has been
synchronized to disk, the DD OS verifies that it can read the entire file
from the disk platter through the Data Domain filesystem, and that
the checksums of the data that is read back match the checksums
written. This ensures that the data on the disks is readable and
correct, can be recovered from every level of the system, and that the
filesystem metadata structures used to find the data are also readable
and correct.
Fault avoidance and The biggest risk to filesystem integrity is filesystem software errors
containment that occur when writing new data. New data can accidentally write
on existing data, and new updates to filesystem metadata can mangle
existing structures. Data Domain systems are equipped with a
specialized log-structured filesystem that has four important benefits:
◆ New data never overwrites good data
Unlike a traditional filesystem, which will often overwrite blocks
when data changes, Data Domain systems write only to new
blocks. This isolates any incorrect overwrite (for example, a
software defect issue) to only the newest backup data. Older
versions remain safe.
◆ Fewer complex data structures
The Data Domain filesystem was built to protect data in backup
applications, where the workload is primarily sequential writes of
new data. Because the application is simpler, fewer data
structures are required to support it. As long as the system can
keep track of the head of the log, new writes will not touch old
data. This design simplicity greatly reduces the chances of
software errors that could lead to data corruption.
◆ NVRAM for fast, safe restart
The system includes a non-volatile RAM write buffer into which
it puts all data not yet safely on disk. The filesystem leverages the
security of this write buffer to implement fast and safe restart
capability. The filesystem includes many internal logic and data
structure integrity checks. If any problem is found by one of these
checks, the filesystem restarts. The checks and restarts provide
early detection and recovery from the kinds of bugs that can
corrupt data.
As it restarts, the Data Domain filesystem verifies the integrity of
the data in the NVRAM buffer before applying it to the filesystem
and so ensures that no data is lost due to the restart. Data Domain
systems never update just one block in a stripe. Following the
no-overwrite policy, all new writes go to new RAID stripes and
those new RAID stripes are written in their entirety. The
verification after write ensures that the new stripe is consistent.
New writes do not put existing backups at risk.
Continuous fault As a basis of continuous fault detection and healing, the Data
detection and healing Domain system uses RAID 6 protection to protect against double disk
faults.
Filesystem recovey Data Domain systems include features for reconstructing lost or
corrupted filesystem metadata, as well as filesystem check tools that
can quickly bring an ailing system safely back online.
Note: If the VTE has tape libraries with VOLSER that reside on the Data
Domain DD890, the erase policy must be configured to one of the
Time-to-live options.
DLm Operations
DLm Operations 43
DLm Operations
Gather connection To connect to the DLm system, you will need some IP addresses and
data passwords.
You need three IP addresses for the ACPs: one for ACP1, one for
ACP2, and a third highly available IP address which is assigned to
the primary ACP. Use the highly available IP address to access the
DLm Console.
Table 5 on page 44 lists the details that you will need before you
access the DLm system.
DLm Console
HA IP address
Username dlmadmin
ACP1
IP address
Username dlmadmin
Password password
ACP2
IP address
Username dlmadmin
Password password
Access the DLm The DLm Console is a web-based console that is used to configure
Console and monitor the DLm system. It is the management interface to the
DLm system.
3. Type the username and password. For a first-time login, enter the
following user and password:
• User: dlmadmin
• Password: password
The DLm Console opens as shown in Figure 10 on page 47. At
first login, DLm prompts you to change the DLm Console
password.
Exit DLm Console To exit the DLm Console, click Logout on the DLm Console menu
bar.
Set date and time The DLm system time is displayed in the status line at the bottom of
the VT console. If you need to adjust the system date or time you may
do so from the Time tab on the DLm Console:
1. Access the DLm Console as described in “Connect to the DLm
Console” on page 45.
2. Click External.
3. Click the Time tab if it is not already displayed.
4. Use one of these two methods to set the date and time on a VTE:
• Configure the system to use a Network Time Protocol (NTP)
server.
Note: If you use a network name to identify an NTP server, you will
need to configure a Domain Name Server (DNS) as part of the
network configuration.
To manually set the date and time, adjust the date and time in
the Current date and time fields and click Set.
The date and time is set in all the VTEs in the system.
User administration By default, DLm ships with two default user IDs:
◆ dlmadmin
◆ dlmuser
The default password for these two usernames is password.
The dlmadmin user has full administrator rights and can create new
configurations or modify the existing configurations. This user can
monitor and control the operation of the VTE. The dlmadmin user
can create new users with the same rights as dlmuser; dlmadmin
cannot create another user with administrative rights.
The dlmuser user can view the configuration and check the status of
the VTEs but does not have the authority to modify configurations or
operate the VTEs.
From the Authentication tab of the DLm Console, the dlmadmin
user can add, delete, or modify usernames recognized by the system:
1. Access the DLm Console as described in “Connect to the DLm
Console” on page 45.
2. Click External.
3. Click the Authentication tab.
! CAUTION
Be careful not to delete all usernames with full administrator
privileges. If there are no administrator users you will not be
able to modify or operate the system.
! CAUTION
Do not attempt to change the authentication type from Native to
LDAP unless your DLm system is attached to your corporate
network and you already have the appropriate directory server
installed and running on the network. Failure to successfully
attach to an external directory server could result in not being able
to log in to DLm.
Access a VTE
You can access the VTE through the DLm Console.
1. Access the DLm Console as described in “Connect to the DLm
Console” on page 45.
The System status tab of the System menu opens by default.
The console displays icons for each configured VTE. From the
bottom up, the VTEs in your DLm cabinet are named VTE1,
VTE2, VTE3, and so on. Only the icons matching the VTEs
installed on DLm are displayed on the console.
2. In the Console column, double-click the icon corresponding
to the VTE you want to access.
Figure 14 VT console
The title bar displays the name of the VTE. The blue bar at the bottom
of the screen displays the status of the virtual tape application. The
informational, warning, and error messages from the VT application
scroll on the console window.
VT console A VT console does not need to be open for the VTE to be working.
You can open a specific VT console when you configure that VTE or
when you want to monitor the status of tape operations on that VTE.
You can have all VT consoles open simultaneously. All VTEs continue
to operate normally regardless of which console is open.
The VT console is divided into three sections:
◆ The larger, top section displays log messages as they are issued
from the VT application. On startup, the VT console displays the
messages in the log (up to the last 100,000 bytes) since the last
startup of the VT console.
The following navigation keys (or commands) can be used to
scroll through the messages:
• Home—Move to the top
• End—Move to the bottom
• PgUp—Move up one screen
• PgDn—Move down one screen
◆ The smaller, lower section of the VT console is blue and always
shows the current status of the VT application on this VTE. When
the VT application is not active, the VT status is Not running.
When the VT application is active, the VT status on the VT
console is Running. Use the START VT and STOP VT commands
to start and stop the VT applications, respectively. “Start and stop
tape devices” on page 74 provides information.
The DLm system time is displayed in the status line at the bottom
of the VT console.
◆ Below the VT Status line is a command line where you may enter
and edit VT commands.
The following navigation keys can be used on the command line:
• Up Arrow or Ctrl+P—Previous command in history
• Down Arrow or Ctrl+N—Next command in history
• Left Arrow—Move 1 character to the left in the command line
Access a VTE 55
DLm Operations
Note: Vary all the devices on the VTE offline to the mainframe before you
reboot the VTE.
Power up DLm
Note: You must coordinate planned powerdown and powerup events with
EMC Customer Support.
Note: The Ethernet switches are powered up as soon as the cabinets are
powered up. Wait at least 10 minutes for the storage to power up before
powering up the ACPs and the VTEs.
VNX power-up 1. Ensure that the switches for SPS A and SPS B are turned OFF.
2. Verify that the cabinet circuit breakers are in the OFF position.
[1 in Figure 17 on page 60]
3. Connect the power cables as follows:
a. The standby power supply (SPS) A to power distribution
panel (PDU A). [2 in Figure 17 on page 60]
b. The SPS A to storage processors A & B (Ensure that the
retention bails are in place.) [3 in Figure 17 on page 60]
c. The DAE 0 to SPS A & SPS B. [4 in Figure 17 on page 60]
4. Turn on the circuit breakers using the Master switches.
5. Turn the SPS switches ON.
This powers up the storage subsystem of the VNX7500. This takes
about 10-12 minutes.
Power up DLm 57
DLm Operations
CL4847
6. Check the following LEDS on the front and rear of the VNX7500:
• Amber warning LEDs flash during the power-on self-test
(POST) and then go off.
• The front fault LED and the SPS recharge LEDs commonly
stay on for several minutes while the SPSs are charging.
7. Ensure that the storage array is up and running.
The storage processors are immediately above the SPS. The
physical indication that the storage array is up and running:
• The Power LED on the storage processors is green.
• The Fault LED on the storage processor is not lit amber.
• DAE 0 status is green.
• The first four drives in the DAE are green.
PS A0 PS A1 PS B0 PS B1
CPU A CPU B
AC AC AC AC
A B
Power up DLm 59
DLm Operations
! CAUTION
The DLm bays and power systems are designed to support DLm
equipment only. EMC does not support any other components in
these bays, and recommends that you do not install any additional
equipment in the DLm bays.
DD890 power-up The ES30 shelves of the DD890 must be powered up before powering
up the DD890 controller. Make sure the SAS cabling to the ES30
drives are connected and plugged in before powering the systems
ON.
1. Ensure that the master switch on the DD890 rack is in the OFF
position.
2. Connect power cables to both the power receptacles of the ES30
shelves and make sure the retention clips at both ends are
engaged.
3. Power on the expansion shelves. The ES30 shelves take about 3-4
minutes to power ON. (Make sure you power on the ES30 shelves
before powering on the DD890 controller.)
4. Connect both power cables to the DD890 controller. Ensure that
the retention clips are engaged at the PDUs and the cable restraint
tie is connected at the controller.
If the DD890 controller does not automatically power on, push
the power button on the front of the controller.
! IMPORTANT
Wait for about 10-15 minutes for the DD890 System to power
up.
Power up DLm 61
DLm Operations
The system fault LED on the controller should stay green if there
are no faults detected. Table 6 on page 62 describes the status of
this LED.
Display Description
2. Press the power button located in the front of the ACP: button B
in Figure 19 on page 62.
You might hear the fans start and then slow down to adjust the
system temperature. Shortly thereafter, the system begins to boot
and the hard drive activity LED blinks.
A B C D E F G CNS-000979
A USB 2.0 port Allows you to attach a USB component to the front of the
ACP.
D Power LED • Continuous green light indicates the system has power
applied to it.
• No light indicates the power is off.
Note: You can power up the VTEs in any order as they operate
independently of each other.
Power up DLm 63
DLm Operations
You should hear the fans start and then slow down as they adjust for
system temperature. Shortly after that, the VTE's disk activity LED
begins blinking indicating startup of the VTE.
AB C D E F G
Disk 0 Disk 1
L K J
GEN-000718
G System The ID LEDs allow you to easily identify the VTE you are
identification (ID) working on in a rack:
LED • A blue light that lights when the ID Button has been
pressed.
• A second blue ID LED on the back of the unit also lights
up when the ID Button has been pressed.
H ID button Toggles the ID LEDs that enable you to identify the VTE you
are working on in a rack.
J USB Connector Allows you to attach a USB component to the front of the
ACP.
K NMI button Pressing this recessed button with a paper clip or pin issues
a non-maskable interrupt and puts the system into a halt
state for diagnostic purposes.
L Video Connector
Note: All LEDs are visible through the front bezel. However, you must
remove the bezel to press the NMI, Power, Reset, or ID buttons.
Normal startup of a VTE takes 5 - 10 minutes. After the VTE starts its
network services, you will be able to access the VTE through the DLm
Console.
Power up DLm 65
DLm Operations
Note: If the entire VTEC bay is in the powered down state, some of the LED
panel indicators may light when power is applied. This is only an indication
that the units have power available, it is not an indication that the ACP or
VTEs are started. You must press the Power button on the ACPs and each
VTE to actually start them when appropriate.
Note: The powerdown procedures are different for Data Domain DD890
and VNX7500.
3. The ACPs
a. The secondary ACP
b. The primary ACP
Note: The powerdown process takes up to 30 minutes after the tape drives
are varied offline.
Power down the VTE Always use the poweroff command to shut down a VTE in an
orderly manner. If you simply power off the VTE by pressing the
Power or Reset buttons, unpredictable errors occur on the host for
any active connections, possibly resulting in data loss. Before using
this command, you must stop all host programs using the VTE, and
vary off the tape devices from the host.
! CAUTION
Do not power off while the VTE is online to the host. Follow the
shutdown procedure before pressing the Power button.
Note: Vary the tape drives offline from every LPAR and wait for it to go
offline. If a job is accessing the drive at that point, the drive does not go
offline until the job releases the drive. Depending on the usage, this could
take more than an hour.
Note: The virtual tape application automatically restarts the next time
you start the system.
After you execute the poweroff command, the VTE powers down.
Pressing the Power button after a poweroff command will turn the
VTE on again.
Power down DD890 If you have both VNX7500 and DD890, power down DD890 before
you power down VNX7500.
You can power down the DD890 system from the ACP by executing a
CLI command.
To shut down the power to the Data Domain system:
1. Log in as an administrative user and type this command:
# ssh -l sysadmin 192.168.100.110 system poweroff
2. When the system prompts for confirmation, type yes and press
Enter.
The command automatically performs an orderly shutdown of
DD OS processes.
! CAUTION
Do not use the chassis power switch to power off the system.
Use the system poweroff command instead.
Power down If you have both VNX7500 and DD890, power down DD890 before
VNX7500 you power down VNX7500.
! CAUTION
A planned powerdown of the VNX server and integrated storage
array requires access to the VNX Control Station. Call EMC
Customer Support for assistance.
Note: This healthcheck ensures that there are no major errors in the
system that would prevent the system from being turned on during the
power up process.
Verify Control Station To verify that the server has been shut down:
powerdown
1. Reboot the Control Station by pressing the power button in the
front of the Control Station. To reach the power button on the
Control Station, you might have to remove the front bezel.
2. Wait for 5 minutes, and then verify that the system is powered off.
3. Verify that the Data Movers are shut down using this command:
# ssh -q 192.168.100.200 /nasmcd/sbin/getreason
After ensuring that the Data Movers are shut down, you can now
proceed to powering down the Control station.
4. From the prompt, issue the following command to power down
the Control Station:
ssh -q 192.168.100.200 poweroff
You can now proceed to powering down the storage controller and
the drives.
Power down the To shut down the storage controllers (SPE and boot DAE), use only
storage controllers the power switches on the SPS.
! CAUTION
Failure to follow this procedure can result in the loss of data and
extended periods of data unavailability while the array is returned
to normal functionality.
SPE chassis and OS-Boot chassis DAEs are plugged into the SPS
units. From the rear of the cabinet, the left power supply of each
chassis (SPE and OS-boot) is plugged into the left SPS and the right
power supplies are plugged into the right SPS. To power down the
storage array:
1. Vary off all tape drives, power down all VTEs, and halt the VNX
server to stop all I/O activity.
2. Wait approximately five minutes to allow the write cache to finish
writing to the storage system.
3. Use the SPS power switches to power off the array. Turn off (0
position) the power switch on the standby power supplies (SPS).
Figure 15 on page 58 shows the SPS power switches. Make sure
the SPS power indicators are off before continuing.
WARNING
Never turn off the power directly to the SPE chassis or the
OS-boot chassis by using any switches on the power supplies.
Never unplug any of the AC cables going to the SPE or OS-boot
chassis to disconnect power.
4. Wait for two minutes to allow the storage system to write its
cache to disk and to power off. Then, disconnect the power cables
that run from the SPSs to the DAE.
5. If there are multiple DAEs present, disconnect the power cable
from each DAE to the PDU. This powers down the DAEs.
6. Disconnect the power cables for each Data Mover and Control
Station from the PDUs.
7. Make sure that the LEDs on all the management switches are off.
Once they are off, the server is completely powered down.
Power down the You can power down and reboot the ACP without affecting the
ACP operation of the VTE.
To power down the ACP:
1. Access the ACP:
a. Start an SSH client, such as PuTTY.
b. Select the SSH connection type.
c. Type the IP address of the primary ACP in the hostname (or IP
address) field. The primary ACP is always assigned the
highly available IP (HA IP) address and can reside on either
ACP1 or ACP2.
d. Click Open.
e. Log in to the ACP as root. The password is Just4Eng&Use.
2. Verify if the ACP that you are logged into is the primary ACP. At
the prompt, enter:
ha_status
3. Power down the secondary ACP before you power down the
primary ACP.
a. To power down the secondary ACP:
ssh -q acp<n> poweroff
where <n> is 1 or 2.
b. After you have powered down the secondary ACP, power
down the primary ACP:
poweroff
Note: This may result in an incomplete output tape volume if the host
has not yet completed writing and properly closing the tape. For this
reason, the STOPVT! command should only be used in an emergency
situation where VTE must be brought down immediately. Any virtual
tape volumes currently being written should be considered invalid.
The blue bar at the bottom of the VTE console displays the changed
status of the VT application.
where:
◆ volser is the starting serial number to initialize.
◆ devname is the device name (address) of any tape drive pointing to
the tape library.
◆ count is the number of serial numbers to initialize.
◆ n is the class these volumes are to be added to.
◆ dirname is a specific directory the volumes should be placed in.
DIR is an optional parameter. DIR is not a requirement . If DIR is not
specified, INITIALIZE places the volumes into the first filesystem it
finds within the storage class. During processing, scratch tapes will
be automatically moved as needed from one directory (filesystem) to
another in the same storage class. However, if you wish to spread
scratch volumes across multiple filesystems within a class you may
use the DIR parameter to direct a range of tapes to a specific
filesystem. CLASS is a required parameter.
This would result with volumes ranging from 000000 to 000499 being
created in the first filesystem in class 0.
If your library has two storage classes defined, class 1 and class 2, the
following commands would initialize 1000 VOLSERs per class in the
library making both classes ready for use:
INITIALIZE VOL=000000 DEV=E980 COUNT=1000 CLASS=1
INITIALIZE VOL=001000 DEV=E980 COUNT=1000 CLASS=2
Note: If your tape devices are defined in a Manual Tape Library (MTL), you
must also define them in the mainframe's tape configuration database
(TCDB). You must run the DLMLIB utility to do this. Instructions for
running DLMLIB are provided in “Locate and upload the DLm utilities and
JCL for z/OS” on page 151.
ESRS ESRS for VNX file storage monitors the operation of DLm for error
events and automatically notifies your service provider of error
events. It also provides a path for your service provider to use to
securely connect to your monitored DLm systems.
Modem support DLm provides an external modem to allow remote access to the ACPs
for support and diagnostic purposes. The supplied modem is
normally attached to ACP1, the bottom ACP. A telephone line should
be connected to the ACP modem (which in turn should be cabled to
the COM1 port of the ACP). Figure 5 on page 23 shows the rear panel
of the ACP.
The ACP can be configured to send messages to EMC using the VNX
ConnectEMC function when problems are detected within the VNX
storage systems or the VTEC. The ConnectEMC options include
sending the messages via a modem through a customer-supplied
analog telephone line.
DLm Administration
DLm Administration 81
DLm Administration
Tape libraries
A virtual tape library is controlled by a top level directory stored on
the VTE’s system disks. Each filesystem to be used as part of the tape
library must be mounted as a subdirectory within that top level
directory. The VTE automatically uses all filesystems mounted under
the top level directory to store tape volumes. For example,
/tapelib/CEL1_P1_FS1, where /tapelib is the top level directory and
/CEL1_P1_FS1 is the subdirectory.
DLm stores any number of VOLSERs in the filesytems within the
library until space within the filesystems is depleted. Additional
filesystems can be added to the library at any time without
disrupting the operation of the library. When a new filesystem is
available, DLm automatically begins using it when creating new tape
volumes. Each tape volume (VOLSER) is stored as a single file on one
filesystem.
Like real tape volumes, virtual volumes are written, read, and
scratched. Once a VOLSER has been scratched within the library, it
can be re-used during a future tape allocation process.
Tape libraries allow for multiple storage classes to be defined. Each
filesystem defined to a virtual library is assigned to only one storage
class. The storage classes are identified by numbers; for example: 0, 1,
2, etc. If you do not define a class, the filesystem you define is
assigned to the default storage class 0.
EMC service personnel define tape libraries during initial setup. The
steps to successfully define a tape library:
1. Create the filesystem on backend storage subsystems like VNX
and/or DD using DLm tools.
2. Define the lock file systems and other file systems in VTE
configuration.
3. Define the libraries to be used by each VTE and configure devices.
4. Install the configuration on all VTEs.
5. Initialize scratch tapes (VOLSERs) into the library.
At least one filesystem must be defined for each virtual tape library
you intend to define. It is also mandatory to define one small (10
MByte) filesystem to use as a lock directory.
Lock filesystem In addition to defining filesystems to the virtual tape libraries, DLm
also requires a small filesystem to use as a lock directory. A lock file
system is an NFS filesystem that is required during the allocation of
scratch volumes to keep temporary lock files. A 10 MB filesystem is
generally sufficient. EMC service personnel create the lock file during
initial system configuration and setup.
Some important considerations:
◆ The lock filesystem must be separate from the filesystems making
up your virtual tape library (libraries).
◆ When multiple VTEs share a virtual library, the lock filesystem
must be resident on the shared (NFS or fibre channel) storage that
all VTEs can access. It must be mounted on all the VTEs.
◆ Only one lock filesystem is required regardless of how many
virtual tape libraries you may be defining to the VTEs.
◆ Only one lock filesystem is required even if you have multiple
storage subsystems, such as VNX and DD.
◆ The same lock directory MUST be defined to each VTE accessing
a virtual tape library. The same lock directory can be used for
more than one virtual tape library.
◆ The lock filesytem is only used during the process of allocating a
new scratch volume for output. This filesystem is not used to
store tape volumes. (Therefore, the size of the lock filesystem
(directory) can be as small as 10 MB).
The lock directory is identified with a global parameter called
VOLSERLOCKDIR. This parameter is defined as an additional
parameter under the Global options on the Devices panel.
Note: If you do not define a lock directory filesystem, DLm assumes that you
want to operate in compatibility mode using an existing virtual library that
was created with an earlier version of VTE software.
Tape libraries 83
DLm Administration
Planning ◆ For z/OS systems, plan for one virtual device that will always be
considerations offline and can be used by DLm utilities to communicate with the
VTE.
◆ Additionally, if you plan to run the DLm z/OS started task
(DLMHOST), plan for one virtual device per VTE to remain
offline and be used by DLMHOST to communicate with the VTE.
DLm configuration The DLm Console allows you to configure the VTE and save your
files configuration as a configuration file. The default configuration file is
config. If you simply begin modifying the configuration, you will be
working with this default configuration file. Optionally, you can
create and use your own configuration files. DLm allows you to store
as many configuration files as you want. However, only one
configuration file will be the active configuration at any point in time.
The Configuration page shown in Figure 27 on page 99 allows you to
select the configuration file for a VTE. “Manage configuration files”
on page 101 provides more information. You must save your
configuration to a configuration file and install the configuration for
it to take effect on the VTE. The current active configuration file is
displayed in the Last installation field under the Description field.
4. Enter values in the fields under Global options at the top of the
Devices panel:
Note: If the VTE has tape libraries with VOLSERs that reside on
DD890, the erase policy must be configured to TTL.
Note: This field is visible only if the Erase policy option, Space or
Both, is selected.
Note: This field is visible only if the Erase policy option Space or
Both is selected.
Note: This field is visible only if the Erase policy option TTL or Both
is selected.
! IMPORTANT
Stagger the Time-to-Live values across VTEs to ensure that
multiple VTEs do not start TTL cleanup at the same time.
Add devices Define the virtual tape devices (drives) to be emulated to the
mainframe by this VTE in the Control units section.
Note: All devices on the same Control Unit must be the same type.
• IDRC
This parameter turns on or off write compression of the data
that DLm writes to the library. The available values are Yes,
No, and Force. The default value is IDRC=Yes.
When IDRC is set to Yes (IDRC=Yes), the VTE compresses the
data it writes to a virtual tape disk file, but only if the
mainframe instructs it to do so. Compression is controlled
differently by various host operating systems, but is generally
configurable in the JCL.
Note: For devices attached to tape libraries that are configured for
deduplication, select No for IDRC during device configuration.
When writing to VOLSERs stored on deduplicated storage, the IDRC
setting is ignored. The VTEs do not compress the data before it is
written to the deduplicated storage. The deduplication device
deduplicates the data and compresses only the unique data before
writing to its drives.
• Additional parameters
The Additional parameters field allows you to code a number
of optional keyword parameters which will be assigned to the
devices being created:
– GROUP=nn
nn is any decimal number. GROUP should be coded
whenever DLm is to be used on multiple LPARs. When
DLMMOUNT requests a mount, only virtual drives in the
same group are considered for the mount. When not coded
all drives default to GROUP=0.
– LABELS=S/N/A
– TRACE=n
This parameter allows you to set the trace option for this
specific device:
0 — No tracing
1 — Trace errors only (default)
2 — Trace errors and status
3 — Trace errors, status, and headers
Note: If you configure the tape devices into a Manual Tape Library (MTL) on
the mainframe, be aware that MTLs only allow 16 devices per control unit. In
that case, instead of defining 32 devices on a single control unit, define two
control units with 16 devices each.
Scratch synonyms When the mainframe wants a tape volume (VOLSER) mounted on a
tape device, it sends a load display command (CCW) over the
channel to the device identifying the VOLSER to be mounted. For
example, in z/OS, if a user codes JCL for a tape volume that reads
"VOL=SER=000001", z/OS sends DLm a load display CCW
indicating that the tape volume with VOLSER '000001' needs to be
mounted on the drive. After sending the load display CCW, z/OS
waits for the device to become ready and then reads the VOL1 label
to verify the serial number.
z/OS uses the default character strings SCRTCH and PRIVAT to
indicate a request for a scratch tape to be mounted for output. By
default, DLm recognizes these two strings as a request for a new
scratch tape and mounts an available scratch tape on the requested
device to be used for output.
Most commercial tape management systems (TMS) support the
concept of tape pools, allowing you to define your own scratch pools
for use when mounting a new scratch tape. In support of TMS tape
pools, DLm allows you to define unique “scratch synonyms” to the
VTEs. During installation, you can configure your own sub-pools of
scratch tapes to request tape mounts using meaningful names.
DLm accepts up to 64 scratch synonyms. It also tolerates the presence
of (but does not allow editing of) more than 64 scratch synonyms.
The field in the Scratch Synonyms section under Global options let
you include whatever names your installation uses to request scratch
tape mounts. DLm recognizes these synonyms, along with SCRTCH
and PRIVAT, as a request for a new scratch volume when they are in
a load display CCW.
Note: Synonyms are not case sensitive and may be entered in either
upper or lower case.
Save configuration 1. Select the Configurations menu at the top of the screen.
2. On the Configurations panel, click Save Changes to save your
configuration to disk.
Delete a device 1. Select the Devices menu at the top of the page.
range
100 EMC Disk Library for mainframe Version 3.0 User Guide
DLm Administration
Activate or install a You must install a configuration for it to be used by a VTE. If you
configuration modify the currently installed configuration, the changes will not
become active until you re-install the configuration.
To install (and activate) your configuration:
1. Select the Configuration menu at the top of the DLm Console
screen.
2. Select the VTE on which it must be installed at the bottom of the
page and click Install on nodes.
3. Click Install on the Configuration operations panel.
! CAUTION
When you click Install, the virtual tape application (VTD) restarts.
If your VTE is currently online with the mainframe, DLm strongly
recommends that you idle all tape drives and vary them offline
before installing a new configuration.
If your DLm system has multiple VTEs, the VTD on every VTE
detecting a change to its current configuration will automatically
restart. However, if you are adding a new VTE to an existing system,
you can install the configuration while the existing VTEs are active as
long as you take care not to modify any of the existing VTE’s
configurations.
Create a new 1. Select the Configuration menu at the top of the DLm Console.
configuration 2. Enter a configuration name in the text box adjacent to the Create
configuration named: button.
3. Select the Devices menu at the top of the DLm Console and enter
the configuration values described in:
• “Configure global parameters” on page 85
• “Add devices” on page 89
• “Scratch synonyms” on page 96
Copy a 1. Select the Configuration menu at the top of the DLm Console.
configuration 2. At the top right corner of the page, select the configuration file
you wish to copy.
3. From the list box near the Copy to field select the config file to
which the configuration must be copied.
4. Click Copy to.
5. At the top right corner of the page, select the configuration file
you just copied changes to.
6. Click Save changes.
Modify or delete a 1. Select the Configuration menu at the top of the DLm Console.
configuration 2. Select the configuration file you wish to modify or delete.
3. Do one of the following:
• To modify the configuration file:
a. Select the Devices menu at the top of the DLm Console and
make the required changes.
b. Return to the Configuration menu and click Save changes.
• To delete the configuration file:
Click Delete.
102 EMC Disk Library for mainframe Version 3.0 User Guide
DLm Administration
Tape Erase
DLm supports a space recovery feature that automatically erases data
from scratch tapes on the filesystem based on an erase policy.
The available erase policies are:
◆ Space
◆ Time-To-Live (TTL)
◆ Both (default)
Note: If the VTE has tape libraries with VOLSERs that reside on the Data
Domain DD890, the erase policy must be configured for one of the
Time-to-Live options.
Space erase policy When a filesystem reaches a specified percentage of space usage,
DLm begins erasing data in that filesystem until the amount of space
specified in the recovery amount parameter has been recovered. The
threshold value, which triggers DLm to erase data from scratch tapes
is specified using the Start space recovery at field.
This automatic space recovery erases the oldest scratch tapes first
(based on the time it was scratched). This method is used so that the
most recently scratched tapes can be available for sometime before
being erased.
Time-to-Live erase The TTL erase policy gives you better control over the length of time
policy that the data on a scratch tape is retained when the tape is in the
scratch pool. The data on a particular tape is erased when the amount
of time since this tape was moved from the active pool to the scratch
pool exceeds the duration specified for TTL in the erase scratched
tapes after option. Once the period expires, the tapes will
automatically be erased regardless of current space utilization. The
default TTL value is 365 days.
Note: If the VTE has tape libraries with VOLSERs that reside on the Data
Domain DD890, the erase policy must be configured to one of the
Time-to-Live options.
! IMPORTANT
Stagger the Time-to-Live values across VTEs to ensure that
multiple VTEs do not start TTL cleanup at the same time.
Staggering the Time-to-Live values across VTEs ensures that only the
required number of VTEs are engaged in TTL cleanup. The VTE with
the minimum Time-to-Live value starts recovering space. If that VTE
cannot complete erasing the scratched tapes before the next higher
Time-to-Live value, the next VTE joins in and helps to complete the
space recovery.
For example, in a four-VTE system, if you set the Time-to-Live value
of VTE4 to 48 hours, set that of VTE3 to 36, that of VTE2 to 24 hours,
and that of VTE1 to 12 hours.
In the case of this example, VTE1 starts erasing tapes that were
scratched 12 hours ago. If it cannot complete the recovery, VTE2 starts
at the end of the twenty fourth hour. Both VTEs recover space until all
the tapes are cleaned up. If VTE1 and VTE2 cannot complete the
space recovery at the end of the thirty sixth hour, VTE3 joins VTE1
and VTE2 in recovering space.
104 EMC Disk Library for mainframe Version 3.0 User Guide
DLm Administration
VTE logs VTEs maintain a log of all messages issued by the virtual tape
application. Log files are automatically rotated each day at midnight.
Old log files are compressed to minimize the space they take and then
kept for a period of time.
To view the latest VTE logs:
1. Access the DLm Console using the web browser. “Connect to the
DLm Console” on page 45 provides instructions.
The System status tab of the Status menu opens by default.
Support data To gather ACP and VTE details for diagnostic purposes:
1. On the Status menu, click the Gather logs menu.
The ACPs and VTEs are listed in the Machine name column.
106 EMC Disk Library for mainframe Version 3.0 User Guide
DLm Administration
After the drive is physically attached to a VTE, you have two choices:
◆ Map a single mainframe tape drive (device address) to the
physical tape drive for writing real tape cartridges from the
mainframe. This capability is referred to as Direct Tape.
◆ Use the DLm VTE-based Export and Import utilities to copy
individual volumes (VOLSERs) from or to the tape.
Direct Tape
DLm is primarily a tape-on-disk controller, which emulates tape
drives to the mainframe and stores tape volumes on a back-end disk
subsystem. However, it also allows a tape-drive-to-tape-drive
mapping of an emulated 3590 tape drive to a physical IBM tape drive
attached to a DLm VTE.
108 EMC Disk Library for mainframe Version 3.0 User Guide
DLm Administration
At this point, the tape application should start and verify the
external tape drive.
If you receive an error and the tape daemon stops, verify that the
tape drive displays "online" and try again.
6. Vary the drives defined on this VTE online to the mainframe.
7. Close the VT.
Compression
DLm supports IDRC data compression. If a mainframe tape device
mapped to a physical fibre channel attached drive requests
compression VTE will instruct the drive to compress the data before
writing it to tape. The tape drive, rather than DLm, will perform the
data compression in order to ensure compatibility with other IBM
drives that may later attempt to read the data.
110 EMC Disk Library for mainframe Version 3.0 User Guide
DLm Administration
Export to and import As an alternative to Direct Tape, when a mainframe tape drive is
from tapes mapped directly to a physical IBM drive, DLm includes two utilities
for exporting and importing tape volumes between the DLm disk
library and a tape drive attached to a DLm VTE.
These commands are executed within the tape-on-disk application
running on the VTE, where the drive is attached. You can have either
pass-through or import/export functionality, not both.
The EXPORT and IMPORT utilities are disabled in the default DLm
VTE configuration because:
◆ These commands copy tape volumes based only on the VOLSER
irrespective of the data actually contained on the volume.
◆ A DLm VTE does not usually have a tape drive physically
attached to it.
To enable the EXPORT / IMPORT utilities:
1. Access the DLm Console using the web browser. “Access the
DLm Console” on page 45 provides instructions.
2. Click Devices to display the Tape device configuration panel.
This panel contains a tab for each configured VTE.
3. Click the tab pertaining to the VTE you want to configure. (The
screen shown in Figure 23 on page 86 opens.)
4. Select the Tape import/export enabled check box. “Configure
global parameters” on page 85 provides more information about
this field.
5. Save the configuration as described in “Save configuration” on
page 99 and install it on the VTE as described in “Activate or
install a configuration” on page 101.
The next time the VT application restarts, the EXPORT and
IMPORT utilities are available.
Note: DLm does not support import and export of scratch tapes.
112 EMC Disk Library for mainframe Version 3.0 User Guide
DLm Administration
SNMP
Each VTE contains an SNMP agent and MIB files for monitoring and
analysis. Once configured, the VTE can send SNMP alerts to a
designated SNMP manager.
The VTEs are preconfigured so that once the agent has been given the
IP address of the management console, SNMP traffic flows from the
VTE to the ACP. The ACP forwards SNMP traffic to an SNMP
manager on your corporate network. The SNMP alerts are forwarded
to the VT console.
To configure a VTE to send SNMP alerts:
1. Access the DLm Console as described in “Connect to the DLm
Console” on page 45.
2. Click External.
ConnectEMC
The DLm ConnectEMC function can automatically notify the EMC
service center or other service providers if the VTEC or VNX system
detects a serious problem. ConnectEMC sends messages using one of
the following:
◆ Email
◆ FTP
◆ Modem (through a customer-supplied analog telephone line)
The FTP and e-mail connections require the DLm to have access to
your company's LAN.
ConnectEMC is configured by EMC personnel during initial setup.
You can have them configure the VTEC to generate ConnectEMC
events for error-level SNMP traps. “VTEC errors that generate
ConnectEMC events” on page 374 provides a list of traps that
generate ConnectEMC events.
114 EMC Disk Library for mainframe Version 3.0 User Guide
DLm Administration
Autosupport e-mails The Data Domain DD890 generates daily e-mails to the EMC Data
(generated once a Domain support group. These e-mails contain information about all
day) outstanding alerts and the status summary of the general health of
the DD890. You an also configure Autosupport emails to be sent to
the email address of the system administrator.
116 EMC Disk Library for mainframe Version 3.0 User Guide
DLm Administration
118 EMC Disk Library for mainframe Version 3.0 User Guide
4
DLm Replication
Overview
DLm offers IP-based remote replication, which leverages your IP
network infrastructure, eliminating the need for channel extension
hardware. The replication is storage-based and therefore has no
impact on mainframe host operations or performance. DLm
replication is asynchronous and only the changes are replicated
between the remote sites.
DLm supports unidirectional and bidirectional replication, which
means that the source system can also be a target system and vice
versa. VNX replication supports up to four target sites per source
system, which means you can replicate data to four different sites.
The source and destination DLm systems do not have to be
configured with the same capacity.
DLm replication is a separately licensed feature. In the DLm6000,
VNX replication and deduplication storage replication are licensed
separately. There are some key differences in the way VNX
replication and Data Domain replication work.
120 EMC Disk Library for mainframe Version 3.0 User Guide
DLm Replication
Mainframe Mainframe
VTEC VTEC
Overview 121
DLm Replication
Replication terminology
The following is some of the terminology used when describing
DLm replication:
◆ Replication
The process of sharing information to ensure consistency between
redundant resources.
◆ Source object (SO) is also known as:
• The production object (PO)
• The production filesystem (PFS)
• The source filesystem (SFS)
This is the original source collection of data to be replicated.
◆ Destination object (DO) is also known as:
• The destination filesystem (DFS)
• The target filesystem (TFS)
• The secondary filesystem (SDS)
This is the replicated copy of the original data.
◆ Replication session
The relationship that enables replication between the SO and the
DO, including two internal checkpoints or snapshots for both SO
and DO.
◆ Time-out-of-sync
Defines how closely you want to keep the destination object
synchronized with the source object. This is specified in minutes.
◆ Full copy
The complete copy of the source object that is sent to the
destination when a replication session is first started, or when a
common base is not found.
◆ Differential copy
The changes made to the source object (since the previous
replication) that are sent to the destination during replication.
122 EMC Disk Library for mainframe Version 3.0 User Guide
DLm Replication
◆ Snapshot or checkpoint
A point-in-time copy of data. This view of data takes very little
space and are just pointers to where the actual files are stored.
Snapshots/checkpoints are used when transporting the full copy
after first synchronization. Using SnapSure on VNX provides
detailed information on snapshots. This document is available at
EMC Online Support website.
◆ Disaster recovery (DR)
The process, policies, and procedures for restoring operations
critical to the resumption of business, including regaining access
to data, communications, and other business processes after a
natural or human-induced disaster.
◆ Recovery point objective (RPO)
A description of the amount of data lost, measured in time. For
example, if the last available good copy of data was made 18
hours before an outage, then the RPO is 18 hours. You can define
different RPO values for different VOLSER ranges or tape
libraries based on information criticality.
◆ Recovery time objective (RTO)
A specified amount of time within which a business process must
be restored after a disaster to avoid unacceptable consequences
associated with a break in continuity. RPO and RTO form the
basis on which a disaster recovery strategy is developed.
◆ Storage controller interconnect is also known as:
• Data Mover interconnect (DMIC)
• DART interconnect (DIC)
The storage controller interconnect is a communication path
between two VNX storage controllers (Data Movers) that is used
for all replication sessions between those two storage controllers.
This connection defines all interfaces that can be used on each
storage controller, and also the bandwidth throttle schedule. This
interconnection must be created in both directions.
VNX replication
VNX replication is based on EMC VNX Replicator V2. Using VNX
Replicator (V2) provides more information on VNX V2 replication.
This document and the latest documentation for your specific version
of VNX operating environment (OE) code are available on the EMC
Online Support website.
Prerequisites for VNX replication are:
◆ The required replication licenses are installed in the source and
destination DLm systems.
◆ VNX7500 runs the VNX OE version 7.0.12.0 or later.
◆ You have the IP addresses that are assigned to the source and
destination storage controllers (Data Movers).
◆ The HTTPS connections between the source and destination
storage controllers (port 5085) and between the source and
destination Control Stations (port 443) are secure.
◆ Sufficient storage space is available for the source and destination
filesystems.
Supported configurations
DLm supports the following configurations for VNX replication:
◆ Local replication: Between two separate storage controllers
located within the same DLm.
◆ Remote replication: Between two separate DLm systems,
typically (but not necessarily) in different geographic locations.
This includes replicating from a single source to up to four
separate destinations.
◆ Bi-directional replication: DLm A replicates to DLm B, while
DLm B replicates a different filesystem to DLm A.
Currently, these configurations are not supported:
◆ Replication to more than four separate destinations
◆ Cascading (for example, DLm A replicates to DLm B which in
turn replicates to DLm C)
124 EMC Disk Library for mainframe Version 3.0 User Guide
DLm Replication
Data replication The replication of source data occurs in the following way:
1. An application running under z/OS writes data to one or more
virtual tapes (VOLSERs) within a filesystem (VOLSER range) set
up for replication on DLm.
2. Replication creates a checkpoint—a point-in-time, block-level
copy of the underlying filesystem.
3. Using intelligent scheduling algorithms, checkpoints are
transferred to the remote destination asynchronously.
4. Only changed blocks are copied.
126 EMC Disk Library for mainframe Version 3.0 User Guide
DLm Replication
6. After all the changes have been copied to the source, change the
configuration to the original configuration.
Replication reduces both RPO and RTO. Each filesystem (VOLSER
range) maintains a unique and independent value for:
◆ Time-out-of-sync — This controls how often the destination site is
refreshed. Depending upon your load and bandwidth, this can be
nearly synchronous. This value is equivalent to the RPO
described in “Replication terminology” on page 122.
◆ Quality of service (QoS) — This controls bandwidth throttling by
specifying limits on specific days and hours.
Quality of service Interconnect QoS defines up to six bandwidth schedules. These are
defined in terms of days, hours, and bandwidth.
Identifying lost tapes To identify tapes that have been lost due to the disaster event:
1. Use the awsprint utility to identify the list of scratch tapes in the
file systems that have been disrupted. Compare the output of the
utility with the list of scratch tapes for this VOLSER range
according to the Tape Management Catalog. Some will appear in
the awsprint output but not in the Tape Management Catalog as
they were no longer in scratch state when the disaster event
occurred. These tapes might not have completed replicating to the
target Celerra. “AWSPRINT library utility” on page 117 provides
information about the utility.
2. Identify the last snapshot that was transferred successfully to the
target using the command processor CP504. The output contains
the last successful sync time for a particular file system.
3. Execute GENSTATS with the following options:
a. STILLINUSE
b. PATHNAME=“name of tape library”
This list indicates the VOLSERs that has been lost due to the
disaster event and these jobs will need to be re-run.
EMC Disk Library for mainframe Command Processors User Guide
contains more information about GENSTATS and command
processor CP504.
128 EMC Disk Library for mainframe Version 3.0 User Guide
DLm Replication
Note: The two replication ports on the DD890 are configured in Failover
mode to protect against link failures. Failover is the only configuration that
DLm supports for the DD890 replication ports. No other configuration is
supported for these replication ports.
130 EMC Disk Library for mainframe Version 3.0 User Guide
DLm Replication
Supported configurations
The following configurations are supported:
◆ Unidirectional from a single source to a single destination
◆ Bidirectional between a single source and destination pair
Note: Data Domain replication is supported only when both the source and
target systems are DLm DD systems. Replication from a DD890 to a VNX is
not supported.
Replication session The requirements for the successful setup of a Data Domain directory
setup replication are:
◆ The destination system must be large enough to store all the data
replicated from the source.
◆ The network link bandwidth must be large enough to replicate
data to the destination.
◆ The fully qualified domain names FQDN for the source and the
destination DD890 systems must be registered in the DNS
servers.
If the hostname of the DD890 is DD-1, the FQDN, for example,
may be"DD-1.customer.com."
Throttling As a basic form of quality of service (QoS), times of day during which
data may or may not be sent, along with limits to the amount of
bandwidth that can be used.
Recovery point In a Data Domain system, deduplication is fast and inline, and
replication can be simultaneous with backup, so it can finish shortly
after backup. The restore image is available immediately from the
replica. The recovery point is from the current snapshot before the
delay represented by the backup window.
Recovery time The replica contains only deduplicated data. The recovery time is the
same as the restore rate from the deduplication pool in the replica.
This should be measured carefully with a large dataset to ensure
sustained performance characteristics.
The Data Domain Replicator uses the directory replication feature to
support replication at the tape library level.
132 EMC Disk Library for mainframe Version 3.0 User Guide
DLm Replication
Note: If you run GENSTATS with the PATHNAME option, the report
lists VOLSERs in the tape library that correspond to the specified
pathname, the updates of which have not been replicated.
134 EMC Disk Library for mainframe Version 3.0 User Guide
DLm Replication
136 EMC Disk Library for mainframe Version 3.0 User Guide
5
Mainframe Tasks
Configure devices
z/OS uses the Hardware Configuration Definition (HCD) utility to
define devices on the system. HCD provides an interactive interface
that allows you to define the system's hardware configuration to both
the channel subsystem and the operating system.
The three alternatives for configuring DLm devices on the mainframe
are:
◆ Configure the devices as real 3480, 3490, or 3590 tape drives.
◆ Configure the devices as MTL devices.
◆ Configure the devices with a unique device type using the EMC
UIM.
These alternatives are discussed in the following sections. The
preferred approach is to configure the devices as MTL devices.
If you are planning to use DLm with IBM's Object Access Method
(OAM), you must configure the devices as MTL devices. OAM needs
tape drives to be SMS-managed and treats them on the host as a
single tape library. The IBM document SC35-0427, DFSMS Object
Access Method Planning, Installation, and Storage Administration Guide
for Tape Libraries provides more information on using a library for
OAM object.
138 EMC Disk Library for mainframe Version 3.0 User Guide
Mainframe Tasks
Note: This does not require the use of the EMC UIM; use the standard
HCD 3490 or 3590 definitions.
140 EMC Disk Library for mainframe Version 3.0 User Guide
Mainframe Tasks
5. Make sure that each control unit's devices have the same
LIBRARY-ID, but a unique LIBPORT-ID per control unit.
Table 7 on page 141 contains an example of having the same
LIBRARY-ID with its unique LIBPORT-IDs.
After defining DLm using HCD, it must be defined to SMS using the
library management function. Then your ACS routines must be
updated to allow jobs to select the new library with appropriate user
defined ACS management, data, and storage classes and groups. For
example, if you define a new esoteric called VTAPE, your ACS
routines could allocate the dataset to the SMS storage group using the
DLm MTL whenever UNIT=VTAPE is specified in JCL.
The characteristics of DLm virtual tape cartridges match the SMS
Media Type: "MEDIA2" for 3490 or "MEDIA4" for 3590. Make sure
that you specify the appropriate media type (MEDIA2 or MEDIA4)
on the Library Definition screen. In addition, since SMS requests
scratch tapes using media type, you must add MEDIA2 or MEDIA4
to the list of DLm scratch name synonyms as explained in “Scratch
synonyms” on page 96. Z/OS might request for mounts by media
type based upon the DATACLAS definition. The customer's ACS
routines or tape display exits may also change the mount request to
use storage group names, LPAR names, pool names etc. All such
names must be entered into the synonym list.
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.
142 EMC Disk Library for mainframe Version 3.0 User Guide
Mainframe Tasks
where xxxx is the offline virtual tape device on the VTE you wish
to access.
For DLMCMD and DLMSCR steps, this parameter eliminates
the need to code a DLMCTRL DD statement.
144 EMC Disk Library for mainframe Version 3.0 User Guide
Mainframe Tasks
146 EMC Disk Library for mainframe Version 3.0 User Guide
Mainframe Tasks
You must define a V348x tape drive for each virtual tape device that
you have configured in DLm. All virtual tape drives assigned to the
default virtual tape library in the DLm filing structure (/tapelib) are
normally defined with the same generic name (for example, V3480).
If you plan to have a drive assigned to a different tape library path in
the DLm filing structure, you should define that drive with a separate
generic name (for example, V3481).
Once the DLm device definitions are active, you must either specify
UNIT=V348x or hard code the unit address allocated to a device. In
this way, regular jobs that call for real tape drives or use tapes
previously cataloged on real 3480s are not allocated to the DLm
devices. After a tape is cataloged as created on a V348x device, it is
allocated to that same device type when called again. Conversely, a
tape cataloged as created on a real tape drive is not allocated to a
device.
148 EMC Disk Library for mainframe Version 3.0 User Guide
Mainframe Tasks
DFSMShsm considerations
If you plan to use DLm with HSM, the various SETSYS tape
parameters do not accept V348x generic names as valid. In that case,
it is necessary to define esoteric names that are unique to the various
V348x devices.
To identify esoteric tape unit names to DFSMShsm, you must first
define these esoteric tape unit names to z/OS during system I/O
generation (HCD). Then, you must include the esoteric tape unit
names in a DFSMShsm SETSYS USERUNITTABLE command.
Only after they have been successfully specified with the SETSYS
USERUNITTABLE command are they recognized and used as valid
unit names with subsequent DFSMShsm commands.
Note: All data written to the deduplicating storage on the DD890 should be
written without IDRC.
150 EMC Disk Library for mainframe Version 3.0 User Guide
Mainframe Tasks
Locate and upload the DLm utilities and JCL for z/OS
EMC provides a set of utilities and a UIM for the z/OS environments.
The utilities are:
◆ GENSTATS — A utility that generates reports from VTE and
VOLSER range statistics
◆ DLMSCR — A scratch utility that sends VOLSER scratch
requests to DLm
◆ DLMCMD — A utility that allows the mainframe to send DLm
commands
◆ DLMLIB — A utility that is required to define scratch volumes on
an MTL
◆ DLMVER — A utility that reports the versions of all the DLm
mainframe utilities on the mainframe and the z/OS release.
◆ DLMHOST — A host utility that provides z/OS Console
Operation support. Chapter 7, “z/OS Console Support,” provides
details about this utility.
Locate and upload the DLm utilities and JCL for z/OS 151
Mainframe Tasks
receive indataset('uid.dlmzos.xmi')
152 EMC Disk Library for mainframe Version 3.0 User Guide
Mainframe Tasks
GENSTATS utility The GENSTATS utility generates reports on the tape mount and
unmount statistics logged at the VTE level and at the VOLSER range
level. It can selectively present:
◆ Daily and hourly throughput numbers
◆ Mount rates
◆ Concurrent tape drive usage details
◆ Compression ratio
◆ Average and slow mount response information
GENSTATS uses command processors, such as CP998 and CP999, to
summarize virtual tape activity. A GENSTATS job consists of two
steps:
1. Execute a command processor which accesses the appropriate
statistics file and writes the data to a non-labeled tape file.
2. Run GENSTATS to generate a report from the non-labeled tape
file data.
EMC Disk Library for mainframe Command Processors User Guide
contains more information about GENSTATS. It includes samples of
JCL for GENSTATS, which show how GENSTATS uses CP998 and
CP999 to generate reports. These sample jobs access VTE and
VOLSER range statistics and make the data available on the
mainframe.
Locate and upload the DLm utilities and JCL for z/OS 153
Mainframe Tasks
Parameters Specification
TYPE=x Where x is used to select the tape management system. Valid types include RMM, TLMS,
TMS, TSM, ZARA, CTLM, AFM, or CTLT. This is the only required parameter.
PREFIX=y Where y is a string of prefix characters that limits processing to volumes whose VOLSER
begins with the characters specified. Unless otherwise specified by the PREFIXLN
parameter, the default prefix length is 2.
PREFIX=AAABAC would cause DLMSCR to process only volumes whose serial numbers
begin with AA, AB, or AC. Coding this parameter prevents DLMSCR from trying to
unnecessarily scratch volumes that are not stored on DLm. If no PREFIX is specified,
DLMSCR processes the entire scratch list.
PREFIXLN=n Where n can be a single digit between 1 and 5. This value replaces the default prefix length
of 2 for the PREFIX= parameter.
PARM='PREFIX=ABCD,PREFIXLN=1' causes DLMSCR to process only volumes whose
serial numbers begin with A, B, C, or D.
NODSNCHK DLm normally validates dataset names (dsname) if found in the scratch report as part of the
scratch process. A scratch is not successfully completed if the dsname in the scratch report
does not match the dsname in the HDR1 label on the volume being scratched. NODSNCHK
prevents the data set name check from being performed and is not recommended for
normal use.
154 EMC Disk Library for mainframe Version 3.0 User Guide
Mainframe Tasks
Parameters Specification
FREESPACE By default, DLMSCR reclassifies volumes being scratched as eligible for scratch allocation
requests, without freeing the space occupied by that volume. The FREESPACE parameter
may be used to request that the space be freed.
Keep in mind that DLm automatically frees the space of scratched volumes when it needs
space. So, it is generally not necessary to run DLMSCR with the FREESPACE parameter.
FREEAFTER While the FREESPACE parameter requires that a volume already be in a scratched state,
SCR FREEAFTERSCR frees space from a volume immediately after DLMSCR has scratched it.
Note: Once FREEAFTERSCR frees the space associated with the execution ofDLMSCR,
the volume cannot be recovered if it was scratched by mistake.
NODATECHK DLm normally checks the creation date of a tape volume and does not allow any volume to
be created and scratched in the same 24-hour period. Setting this parameter allows
volumes to be created and scratched on the same day. This parameter ignores the default
date check in DLMSCR.
IGNLCSERR This parameter ignores any errors reported by Library Call Subsystem (LCS) used by OAM
with the MTL volumes. Normally, DLMSCR logs any error returned by LCS and stops
processing scratch tapes when these errors occur. If this parameter is set, DLMSCR scratch
processing continues even when the LCS errors are encountered.
ALLVOLS This parameter allows scratch of volumes with dsnames of all zeros.
IGNLCSRC4 This allows DLMSCR processing to continue after receiving a return code of 4 from LCS
processing, but terminates if the return code from LCS processing is greater than 4.
NOTCDB This prevents DLMSCR from attempting any TCDB updates. This should be used only if the
TMS already performs this function.
NOTIFSCR This prevents DLMSCR from attempting to change the TCDB use attribute to scratch if DLm
reports that the VOLSER was already scratched.
TEST This parameter allows for testing—no actual changes will be performed.
DEV=xxxx This allows the specification of an offline virtual tape device and the elimination of the
DLMCTRL DD statement as shown on page 143.
Locate and upload the DLm utilities and JCL for z/OS 155
Mainframe Tasks
156 EMC Disk Library for mainframe Version 3.0 User Guide
Mainframe Tasks
◆ After completing the DLMSCR utility, you can use or reuse tapes
that the utility successfully scratched.
RMM considerations
Observe the following rules when using DLm with RMM:
◆ Predefine the DLm scratch volumes to RMM. If you have not
predefined DLm VOLSERs as scratch in RMM, RMM rejects the
new volumes, which results in an unsatisfied mount request on
the mainframe. To resolve the unsatisfied mount, define the DLm
scratches in RMM, and execute a LOAD command at the
appropriate VT console to satisfy a stalled request.
◆ When defining a new DLm scratch tape to RMM, set the initialize
option to no. If you select yes and RMM detects that the volume
must be initialized (or EDGINERS is run), RMM sends a request
to mount a 'blank' VOLSER on a DLm device. DLm is not
automatically ready as it cannot recognize which volume to
mount. Consequently, you must use the LOAD command at the
VT console to manually mount each volume being initialized.
◆ DLMSCR processes two types of RMM scratch reports:
• The scratch report that EGDRPTD creates
• The scratch report that EDGJRPT creates using the
EDGRRPTE exec (EDGRPT01)
Use the DATEFORM(I) parameter when running EDGRPTD to
create scratch reports to ensure the expected date format is used.
When the REXX exec form is used, DLMSCR may not accept a
user-tailored version of EDGRRPTE.
TMS considerations
DLMSCR expects Report-05, Report-06, or Report-87 to be used.
TLMS considerations
DLMSCR expects either the TLMS003 or the TLMS043 report as
input.
TSM considerations
DLMSCR expects a Tivoli Storage Manager (TSM) Volume History
Report to be used as input to the DLMSCR DD.
Locate and upload the DLm utilities and JCL for z/OS 157
Mainframe Tasks
ZARA considerations
DLMSCR expects the LIST SCRATCH type of scratch report to be
used as input from ZARA.
Note: Any messages and other textual results of the command that
display on the DLm Console are not returned to the host.
158 EMC Disk Library for mainframe Version 3.0 User Guide
Mainframe Tasks
Note: This error code is generated when the HOSTCOMMAND option is set to
NO in the xmap file. To enable it, you must manually modify the xmap file.
0xFC (-4) An "E" level error other than general syntax error occurred.
(A console error message other than DLM891E was displayed.)
Locate and upload the DLm utilities and JCL for z/OS 159
Mainframe Tasks
For example:
//LOG EXEC PGM=DLMCMD,PARM='WTOR'
//DLMLOG DD DSN=DLM.LOGFILE,DISP=OLD
//DLMCTRL DD DSN=DLM.CTRL,UNIT=V3480,VOL=SER=BT9999,
DISP=(,KEEP)
◆ Sample 2:
//S1 EXEC PGM=DLMVER
//DLMLOG DD DSN=logfile,DISP=SHR
160 EMC Disk Library for mainframe Version 3.0 User Guide
Mainframe Tasks
Locate and upload the DLm utilities and JCL for z/OS 161
Mainframe Tasks
162 EMC Disk Library for mainframe Version 3.0 User Guide
Mainframe Tasks
164 EMC Disk Library for mainframe Version 3.0 User Guide
6
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.
Ring-Out Mount The Unisys Load Display mount request uses the 8th position of the
request mount message as a file protect indicator. If that position contains the
character 'F', the Unisys mainframe expects to have the tape mounted
"ring-out" (read-only). DLm honors the 'F' indicator and mounts the
requested volume in read-only mode.
166 EMC Disk Library for mainframe Version 3.0 User Guide
Using DLm with Unisys
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.
Device type When configuring devices for use by a Unisys mainframe the Device
Type should be set to '3490'.
Labels When the Unisys operating system sends a Load Display mount
message, it does not specify a label type. Unisys always expects an
ANSI label by default. To accommodate this, you must configure
each Unisys-attached device with the LABEL=A parameter. This will
change the DLm default for this device to ANSI labels instead of IBM
standard labels. Figure 34 shows a sample device definition screen
where sixteen tape drives are being defined including the LABEL=A
parameter.
Scratch tapes The Unisys operating system does not send the "MSCRTCH" message
to request a scratch tape as an IBM mainframe would. Instead it
sends an L-BLNK command. To accommodate the L-BLNK
command, you must specify a scratch synonym equal to L-BLNK.
Figure 34 shows a properly configured scratch synonym for Unisys
mainframes.
168 EMC Disk Library for mainframe Version 3.0 User Guide
Using DLm with Unisys
170 EMC Disk Library for mainframe Version 3.0 User Guide
Using DLm with Unisys
172 EMC Disk Library for mainframe Version 3.0 User Guide
7
174 EMC Disk Library for mainframe Version 3.0 User Guide
z/OS Console Support
DLMHOST
DLMHOST is a host utility that provides z/OS Console Operation
support. The DLMHOST utility runs as a started task, and accepts
commands from the operator. By default, DLMHOST uses
Write-to-Operator (WTOR) capabilities for sending DLm commands.
Optionally, you may configure DLMHOST to use the z/OS MODIFY
function in place of WTOR.
At startup, DLMHOST reads a configuration file that defines the
VTEs to be supported as well as the device addresses, per VTE, to be
used for communication and logging. Each DLm VTE will be
identified with a unique name so that commands can be targeted to
specific VTEs. A tape drive device address must be selected from
each VTE's range of addresses that will be used as the
command/communication path. A second device address is
required on each VTE if you want DLm to send log messages to the
z/OS console. These devices will not be eligible for allocation once
DLMHOST has been started.
Only log messages that have passed message filtering will be
received by the host.
It should be noted that, depending upon the filtering options set on
the VTEs, there may be many log messages sent to the consoles.
Optionally, DLMHOST supports a configuration option to send the
messages to a host file instead of the operator's console.
Installing DLMHOST
DLMHOST is only supported in a single Logical Partition (LPAR).
You cannot connect multiple DLMHOST tasks running in multiple
LPARs to the same DLm VTE.
DLMHOST is distributed in the 3.0 DLMZOS.XMI and the package is
available on the EMC support website. “Downloading and using the
DLm utilities and JCL for z/OS” on page 151 provides more details.
The DLMHOST utility must be linked as an authorized program into
an authorized library under the name DLMHOST. It is highly
recommended that RACF be used to restrict the use of DLMHOST to
authorized users only.
DLMHOST 175
z/OS Console Support
Running DLMHOST
The following JCL is used to execute DLMHOST:
//DLMSTEP EXEC PGM=DLMHOST,PARM='parameters'
//DLMCFG DD DSN=PARMLIB(nodecfg),DISP=SHR
//DLMLOG DD DSN=logfilename,DISP=SHR
//* THE FORMAT OF THE CONFIG FILE IS AS FOLLOWS:
//* Col 1 -10 Nodename
//* Col 12-15 Command path device address
//* Col 17-20 Log path device address
//* Col 22-29 Console name
176 EMC Disk Library for mainframe Version 3.0 User Guide
z/OS Console Support
Col. 1 - 10 : NODENAME
The name used by the mainframe operator to identify which VTE to
communicate with.
DLMHOST 177
z/OS Console Support
178 EMC Disk Library for mainframe Version 3.0 User Guide
z/OS Console Support
Where:
msg# is the reply message number returned from the d r,l command.
COMMAND is the DLMHOST command to be executed.
When DLMHOST is executed with the NOWTOR parameter, the
following message is returned:
DLM002I jobname USE MODIFY TO ENTER COMMAND, EOJ, OR ?
FOR HELP
where:
jobname is the job name of DLMHOST reported in the DLM002I
message.
command is the DLMHOST command to be executed.
DLMHOST commands
The following commands are recognized by DLMHOST:
◆ CMD
The CMD sends a DLm command to a specific VTE.
This command requires a nodename also be specified by using
the NODE= parameter (or N=).
A nodename of ALL can be specified to send the command to
every VTE.
All DLm Operator commands can be entered as parameters to
this command.
The following are examples of valid use of this command:
CMD=Q SPACE,NODE=NODE1
CMD=FIND VOLUME 000001,N=N1
◆ STOPLOG
The STOPLOG command requests that DLMHOST stop logging
VTE log messages for a specific VTE. This command requires that
a nodename be specified by using the NODE= parameter (or N=).
A nodename of ALL can be specified to stop host logging for all
defined VTEs.
For example:
STOPLOG,N=ALL
STOPLOG,N=VTLNODE1
◆ STARTLOG
The STARTLOG command requests that DLMHOST start host
logging of VTE log data for a specific VTE. This command
requires that a nodename be specified by using the NODE=
parameter (or N=). A nodename of ALL can be specified to start
logging for all defined VTEs.
180 EMC Disk Library for mainframe Version 3.0 User Guide
z/OS Console Support
For example:
STARTLOG,N=NODE2
STARTLOG,NODE=ALL
◆ STATUS
The STATUS command requests that DLMHOST display the
current configuration and status of the command and logging
functions.
DLMHOST will issue this message followed by the status of each
configured node:
DLM240I NODENAME CMDDEV LOGDEV CONSNAME
A y or n next to the device address indicates whether the
command/logging function is currently active or inactive for that
node name, respectively.
For example:
DLM2401 NODENAME CMDDEV LOGDEV CONSNAME
NODE1 038E Y 038F Y CON1
NODE2 048E N 048F Y
◆ EOJ
The EOJ Command will terminate the DLMHOST task.
◆ HELP or ?
The Help (?) command returns the DLM000I message with a list
of the valid DLMHOST commands.
The commands that DLM000I lists are:
STARTLOG,N=nodename/ALL
STOPLOG,N=nodename/ALL
C=Command,N=nodename/ALL
STATUS
where msg# is the message number returned from the d r,l (/d r,l
from SDSF).
The following are valid examples of the same DLMHOST commands
when DLMHOST has been executed with the NOWTOR parameter
using the job name DLMHOST:
F DLMHOST,STATUS
F DLMHOST,C=Q SPACE,N=N1
F DLMHOST,STOPLOG,N=ALL
182 EMC Disk Library for mainframe Version 3.0 User Guide
A
Virtual Tape Operator
Command Reference
Syntax
Virtual tape operator commands use the following syntax rules:
◆ UPPERCASE words are keywords and must be spelled as shown.
You can type the keywords in either uppercase or lowercase.
◆ Lowercase words in italics are values that you supply. Generally,
you can type these values in either uppercase or lowercase. The
exceptions are noted in the command description.
◆ Values in square brackets [] are optional.
◆ When multiple values are separated by a pipe symbol (|), enter
only one of the choices.
184 EMC Disk Library for mainframe Version 3.0 User Guide
Virtual Tape Operator Command Reference
Note: Make sure that the volume does not exceed the physical capacity of the
cartridge being written to. If you attempt to write to tape a volume that
cannot fit on the cartridge, the export fails and invalidates the data on the
tape by rewinding and writing a tapemark in the front of the tape.
The example returns the current status of the tape volume with the
serial number 000001.
Note: The Help information pertains to the virtual tape application (VT
Console) only.
186 EMC Disk Library for mainframe Version 3.0 User Guide
Virtual Tape Operator Command Reference
Note: In DLm command syntax, you can use DEVICE and DEV
interchangeably.
188 EMC Disk Library for mainframe Version 3.0 User Guide
Virtual Tape Operator Command Reference
Note: You can enter additional commands while the QUERY SPACE
command is being processed.
190 EMC Disk Library for mainframe Version 3.0 User Guide
Virtual Tape Operator Command Reference
• Q = Quiesced
• R = Ready
• NR = Not ready
• NA = Not accessible
• UA = Not currently allocated by a Host
• An = Allocated on n logical channel paths: A1 = allocated on
one logical channel path, A2 = allocated on two paths, A3 =
allocated to three paths, etc.
(For a non-autoswitched device, An means one Host has
varied online n paths and the device; for an autoswitched
device, or in a JES3 environment, An means the Host has
reserved the device for use on n logical channel paths.)
◆ Volume status:
• aws or flat is the virtual tape file format.
• scsi for a SCSI or Fibre-Channel-attached tape drive.
• rw is read-write.
• ro is read-only.
• lfp is logical file protect set by the Host.
• If a volume is mounted, the current block position or LP (for
loadpoint) is displayed, and whether the last operation was a
read or write.
Other notations might also be displayed when a volume is being
written:
• h-compr or s-compr signifies that the most recent write was
compressed by hardware or software, respectively. The total
volume size shown is after the compression notation, if any.
• crypt signifies that the most recent write was encrypted.
• AMDD signifies that the AMDD feature has modified one or
more blocks being written to this volume.
• GR signifies that the volume is being written to a replicating
filesystem and a replication-refresh will be performed when
the tape is closed.
If a mount previously failed, the most recently requested VOLSER
and the reason for the mount failure are displayed.
192 EMC Disk Library for mainframe Version 3.0 User Guide
Virtual Tape Operator Command Reference
194 EMC Disk Library for mainframe Version 3.0 User Guide
Virtual Tape Operator Command Reference
◆ Tape library space for drives: All devices sharing the same tape
library are grouped together.
◆ Path: The first (or only) entry is the tape library base directory. If
the base tape library contains subdirectories, they are listed
separately and a total is printed.
◆ Size: This is the size of the entire filesystem.
◆ Active: This is the amount of space being used by non-scratch
tape volumes.
◆ Scratch: This is the amount of space that scratch tape volumes
use. The system can reclaim scratch tape space at any time as
needed.
◆ Qty: This is the number of scratch tape volumes in this directory.
◆ Free: This is the amount of free space currently available on the
entire filesystem. Note that if the filesystem holds files in
directories other than the tape library directory, the space of all
other files will reduce the free space. For this reason (Size - Active
- Scratch) it may not add up (Unused), as seen in the first
example.
◆ Filesystem: The filesystem device name, typically a hard drive
partition name or an NFS or SMB mount point.
When a Data Domain DD890 is integrated with the DLm system, the
following differences appear:
◆ The Size column: The total may not reflect the actual total because
the Data Domain storage appliance uses one filesystem for all its
exports. In the above example, all the sizes will be equal and the
total will be the total of the exports.
◆ Active, Scratch, and Qty remain the same.
◆ Free: All exports reflect the same amount of free space due to the
single partition with many exports. The Totals column reflects
larger quantity than is really available because it is a total of the 3
individual free spaces.
196 EMC Disk Library for mainframe Version 3.0 User Guide
Virtual Tape Operator Command Reference
the Not Ready state. These ignored mount requests stay pending just
like other unsuccessful mounts, until the host cancels the mount
request. It is automatically retried when a drive is unquiesced.
Other than ignoring any new mount requests, quiesced drives
continue to function normally; any volume already loaded on the
drive continues to be normally accessible until it is unloaded.
Quiescing a drive does not send any signal to the host.
ALL and * are synonymous and mean quiesce all drives at once.
Note: If the host is still processing the volume and has not yet closed the tape,
manual repositioning may make the host read from or write to an incorrect
location of the virtual tape volume. For this reason, use the REWIND
command only in an emergency situation when a tape volume is known and
is not in use by a host application, but needs to be rewound to loadpoint
immediately.
198 EMC Disk Library for mainframe Version 3.0 User Guide
Virtual Tape Operator Command Reference
Use the SET command to set various options for the virtual tape
devices. Any option set by the SET command is a temporary change,
and the setting reverts to the configuration file or default value the
next time the virtual tape application is started. To make permanent
changes, make the changes in the VTE configuration file. Following is
the description of options within the command:
◆ HWCOMP=ON/OFF indicates whether the VTE must perform
hardware data compression on a given drive. By default, the VTE
uses hardware data compression (HWCOMP=ON) if the
compression hardware is present and the mainframe has
requested IDRC. If you set HWCOMP=OFF, the VTE does not
use the compression hardware to do data compression. It
performs software compression when IDRC is requested by the
mainframe.
◆ HWDECOMP=ON/OFF indicates whether the VTE must
perform hardware decompression on a given drive. By default,
the VTE uses hardware decompression (HWDECOMP=ON)
whenever the compression hardware is present and
decompression is required. If HWDECOMP is set to OFF, the
VTE uses software decompression when decompression is
needed.
◆ IDRC=ON/OFF turns on or off write compression on a given
drive. IDRC=FORCE causes the VTE to compress all data even if
the host does not specify compression on the write. When IDRC is
set to OFF, the VTE still reports to the host that it supports
compression, although it does not actually perform any
compression when it writes data to disk. This is because some
host operating systems or tape managers do not use drives that
support compression. IDRC=OFF affects writing of data. If IDRC
is set to OFF, the VTE can read virtual tape volumes that it
previously wrote with compression ON.
When writing to VOLSERs stored on deduplicating storage, the
IDRC setting Yes is ignored and the VTEs do not compress the
data before it is written to the deduplicating storage. However,
using Force with a deduplicating file system can severely limit
the ability of the storage system to de-duplicate and will,
therefore, use more real disk storage.
◆ PATH=pathname sets the path for the virtual tape library for a
specific device. This option requires a specific DEVICE
specification. If a tape volume is not currently loaded on the
drive, the new pathname specification takes effect immediately.
200 EMC Disk Library for mainframe Version 3.0 User Guide
Virtual Tape Operator Command Reference
Note: If the recovery percentage is set to 100, the DLm VTE never deletes
scratch volume data to recover disk space.
Note: The SIZE= option is not allowed for SCSI tape devices.
STARTVT STARTVT
This command starts the virtual tape application on the VTE.
This command is only valid when the console window indicates that
the VT status is Not Running.
Once the VT application has initiated the VT Status indicates
Running. At this point, tape devices on this VTE may be varied
online on the mainframe.
202 EMC Disk Library for mainframe Version 3.0 User Guide
Virtual Tape Operator Command Reference
STOPVT STOPVT[!]
This command stops the VT application running on the VTE.
This command is only valid when the console window indicates that
the VT status is Running.
This command causes all tape emulation to stop. To prevent input /
output errors from occurring on the mainframe, all tape devices on
this VTE should be varied offline before issuing the STOPVT
command.
STOPVT does not cause emulation to stop if any tape device on the
VTE is active. However, STOPVT! forces termination of the all tape
emulation regardless of the status of the tape devices. Stopping tape
emulation results in I/O errors and job termination on the mainframe
when tapes are actively being used when STOPVT! is issued.
Note: An I/O error (Intervention Required) occurs if the host tries to read
from or write to the drive when it is not ready. For this reason, use the
UNREADY command only in an emergency situation when a tape volume is
known and no host application is using it.
204 EMC Disk Library for mainframe Version 3.0 User Guide
B
AWSTAPE Information
AWSTAPE format
DLm stores virtual tape volumes on disk in the AWSTAPE format.
The AWS format allows DLm to maintain an exact representation of a
physical tape, including variable block sizes, tapemarks, labels, and
so on.
Each AWSTAPE disk file emulates one physical tape volume.
Each emulated physical record in the emulated tape volume is
represented by one or more pairs of block headers followed by data.
An emulated tapemark is represented only by a block header.
Figure 35 on page 206 illustrates an AWSTAPE disk file.
1 2 3 4 5 6 7 8
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
206 EMC Disk Library for mainframe Version 3.0 User Guide
C
Load Display
Command—CCW
Opcode x'9F'
Format Control Byte DLm recognizes Function Select (bits 0–2) values of 000, 010, and 111
as potential mount messages.
Messages 0 and 1 If the Format Control Byte (FCB) Alternating Message bit (bit 3) is on,
0 is checked for a first mount message, then message 1.
If the FCB Alternating Message bit (bit 3) is off, the FCB Display
Low/High Message bit (bit 5) is checked to determine which message
(0 or 1) is to be checked for a mount message. If bit 5 is on, only
message 0 is checked for a mount message. If bit 5 is off, only
message 1 is checked for a mount message.
208 EMC Disk Library for mainframe Version 3.0 User Guide
Load Display Command—CCW Opcode x'9F'
Bits Description
1–8 Message 0
9–16 Message 1
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).
210 EMC Disk Library for mainframe Version 3.0 User Guide
Load Display Command—CCW Opcode x'9F'
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
1 The message specified by setting bit 5 blinks repeatedly. When bit 3 is set to 1,
bit 4 is ignored.
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
The following are some sample Load Display messages. The hex
values are in EBCDIC:
48D4C2E3 F0F0F0F1 E2000000 00000000 00
Interpretation:
– Display message 0 (bytes 1–8) MBT0001S, blink, and retain
until loaded. In other words, mount volume BT0001.
Volume BT0001 is expected to be a standard labeled
volume.
– DLm would interpret this as a valid mount request for
standard labeled volume BT0001.
Interpretation:
– Display message 0 (bytes 1–8) "RBT44," blink it, and retain
until the tape is removed from the drive. In other words,
Remove volume BT44.
– DLm would ignore this message because it is not a mount
request.
F0D9C2E3 F0F0F2F2 40D4C2E3 F2F7F2F7 E2
Interpretation:
– Display in an alternating fashion message 0 (bytes 1–8)
RBT0022 and message 1 (bytes 9–16) MBT2727S. Stop
displaying (or never display) message 0 when the tape is
removed from the drive. Stop displaying (or never display)
message 1 when the tape drive is next loaded. In other
words, remove volume BT0022, then mount volume
BT2727.
– DLm would interpret this as a valid mount request for
standard labeled volume BT2727.
212 EMC Disk Library for mainframe Version 3.0 User Guide
D
Extraction utility
DLm is distributed with a Linux utility program that will extract the
statistics to a comma-delimited output format. The format of the
statfmt command line is:
statfmt [--help] [--hourly [--minutes]] [--mount] [--unmount] infile
Hourly statistics
To extract the hourly statistics, specify the - -hourly parameter. In this
case, the infile parameter must be a DLm hourly statistics file, that is,
/var/bti/stats/hourly.
If the optional - -minutes parameter is omitted, the following
comma-delimited fields are output to stdout:
Date — In the format MM/DD/YYYY.
Hour — In the format HH, where HH is 00-23.
Mounts — The number of successful mounts performed in this hour.
Drives — The maximum number of drives in use at any one time
within this hour.
214 EMC Disk Library for mainframe Version 3.0 User Guide
Extract DLm statistics
Volume statistics
To extract the volume statistics, specify the - -mount or - -unmount
parameter. In either of these cases, the infile parameter must be a
DLm volume statistics file, that is, /var/bti/stats/vstats.
Mount statistics
If the - -mount parameter is specified, the following
comma-delimited fields are output for each virtual tape mount
recorded in the statistics file:
Date — In the format MM/DD/YYYY.
Time — In the format HH:MM:SS in 24-hour time.
Volser — Volume serial number; for scratch tapes, this is the actual
volume that was mounted.
Device — DLm device name.
Error — For a successful mount, this will be zero; for an unsuccessful
mount, that will be non-zero.
Scratch — For a scratch mount, this will be 1; for non-scratch
mounts, this will be zero.
Created — If the volume was created in response to the mount
request, this will be 1; otherwise, zero.
Protected — If the volume was mounted read-only ("ring out"), this
will be 1; otherwise, zero.
Howlong — How long it took to perform the mount, in milliseconds.
Filesize — The size of the virtual tape volume, in bytes, at the time it
was mounted.
Unmount statistics
If the - -unmount parameter is specified, the following
comma-delimited fields are output for each virtual tape unmount
recorded in the statistics file:
Date — In the format MM/DD/YYYY.
Time — In the format HH:MM:SS in 24-hour time.
Volser — Volume serial number; for scratch tapes, this is the actual
volume that was mounted.
BlocksRead — The number of tape blocks read by the host from this
virtual tape during this mounting. This number does not include
tapemarks read.
216 EMC Disk Library for mainframe Version 3.0 User Guide
Extract DLm statistics
BytesRead — The number of bytes read by the host from this virtual
tape during this mounting. This number reflects the uncompressed
data delivered to the host.
BlocksWritten — The number of tape blocks written by the host to
this virtual tape during this mounting. This number does not include
tapemarks written.
BytesWritten — The number of bytes written by the host to this
virtual tape during this mounting. This number reflects the
uncompressed data delivered from the host.
LowWrite — The lowest byte offset where a host write, write
tapemark, or erase was performed to this virtual tape during this
mounting. If no data was written to the tape, -1 will be output to
distinguish it from a write at loadpoint.
Filesize — The size of the virtual tape volume, in bytes, at the time it
was unmounted. If no writes were performed during this mounting,
-1 is output to distinguish that the file is unchanged.
GoodLocates — The number of locates performed to valid block IDs
during this mounting.
BadLocates — The number of locates performed to invalid block IDs
during this mounting.
volumesMounted — The number of concurrent tape mounts there
at the time of that volume allocation (whether its read or write).
pendingMounts — The number of outstanding mounts that have
not been serviced at the volume allocation time. Usually these
mounts only last a few seconds.
Example 1
# statfmt --hourly /var/bti/stats/hourly
statfmt - DLm statistics extractor, version 5.00-24.
Copyright (c) 2007
input file is '/var/bti/stats/hourly'
Date,Hour,Mounts,Drives,BlocksRead,Blockswritten,-
BytesRead,BytesWritten
09/21/2007,14,4,1,-1,-1,968,0
09/21/2007,16,7,2,-1,-1,6198537240,1102968477
09/21/2007,17,4,2,-1,-1,7585128104,1100001400
09/22/2007,15,1,1,-1,-1,0,0
09/23/2007,21,3,3,-1,-1,1000480,1000400
09/23/2007,22,4,4,69,68,1000480,1000400
Example 2
# statfmt --hourly --minutes /var/bti/stats/hourly
statfmt - DLm statistics extractor, version 5.00-24.
Copyright (c) 2007
input file is '/var/bti/stats/hourly'
Date,Hour,Mounts,Drives,BlocksRead,Blockswritten,-
BytesRead[00],BytesWritten[00],BytesRead[01],BytesWritten[01],-
BytesRead[02],BytesWritten[02],BytesRead[03],BytesWritten[03],-
BytesRead[04],BytesWritten[04],BytesRead[05],BytesWritten[05],-
BytesRead[06],BytesWritten[06],BytesRead[07],BytesWritten[07],-
BytesRead[08],BytesWritten[08],BytesRead[09],BytesWritten[09],-
BytesRead[10],BytesWritten[10],BytesRead[11],BytesWritten[11],-
BytesRead[12],BytesWritten[12],BytesRead[13],BytesWritten[13],-
BytesRead[14],BytesWritten[14],BytesRead[15],BytesWritten[15],-
BytesRead[16],BytesWritten[16],BytesRead[17],BytesWritten[17],-
BytesRead[18],BytesWritten[18],BytesRead[19],BytesWritten[19],-
BytesRead[20],BytesWritten[20],BytesRead[21],BytesWritten[21],-
BytesRead[22],BytesWritten[22],BytesRead[23],BytesWritten[23],-
BytesRead[24],BytesWritten[24],BytesRead[25],BytesWritten[25],-
BytesRead[26],BytesWritten[26],BytesRead[27],BytesWritten[27],-
BytesRead[28],BytesWritten[28],BytesRead[29],BytesWritten[29],-
BytesRead[30],BytesWritten[30],BytesRead[31],BytesWritten[31],-
BytesRead[32],BytesWritten[32],BytesRead[33],BytesWritten[33],-
BytesRead[34],BytesWritten[34],BytesRead[35],BytesWritten[35],-
BytesRead[36],BytesWritten[36],BytesRead[37],BytesWritten[37],-
BytesRead[38],BytesWritten[38],BytesRead[39],BytesWritten[39],-
BytesRead[40],BytesWritten[40],BytesRead[41],BytesWritten[41],-
BytesRead[42],BytesWritten[42],BytesRead[43],BytesWritten[43],-
BytesRead[44],BytesWritten[44],BytesRead[45],BytesWritten[45],-
BytesRead[46],BytesWritten[46],BytesRead[47],BytesWritten[47],-
BytesRead[48],BytesWritten[48],BytesRead[49],BytesWritten[49],-
BytesRead[50],BytesWritten[50],BytesRead[51],BytesWritten[51],-
BytesRead[52],BytesWritten[52],BytesRead[53],BytesWritten[53],-
BytesRead[54],BytesWritten[54],BytesRead[55],BytesWritten[55],-
BytesRead[56],BytesWritten[56],BytesRead[57],BytesWritten[57],-
BytesRead[58],BytesWritten[58],BytesRead[59],BytesWritten[59]
09/21/2007,14,4,1,-1,-1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
240,0,0,0,0,0,240,0,240,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,248,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0
09/21/2007,16,7,2,-1,-1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,160,533,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,160,-
370400240,0,531456000,176928720,198145160,287040160,82320,-
305952000,0,292832800,1016128,305952000,0,291872800,1868096,-
306752000,0,305700640,0,308448000,0,306336000,0,308448000,0,-
307168000,0,306880000,0,305056000,0,307776480,0,299392000,0,-
296288160,0,293440080,0,293056000,0,296480000,0,296737080,0
218 EMC Disk Library for mainframe Version 3.0 User Guide
Extract DLm statistics
09/21/2007,17,4,2,-1,-1,0,0,0,0,0,0,0,0,0,0,160,216416240,248,-
516192000,63008720,367393160,305056248,0,293248240,0,-
271232000,0,301632008,0,306016000,0,308000000,0,305184000,0,-
306884640,0,306656000,0,299744000,0,291392000,0,293248000,0,-
293664000,0,291360000,0,293344640,0,290784080,0,288704080,0,-
295904080,0,296832160,0,298144080,0,295968080,0,289984240,0,-
291168240,0,295360000,0,297920080,0,114688080,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0
09/22/2007,15,1,1,-1,-1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0
09/23/2007,21,3,3,-1,-1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
1000480,1000400,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
09/23/2007,22,4,4,69,68,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,-
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1000480,-
1000400,0,0,0,0,0,0,0,0,0,0,0,0
Example 3
# statfmt --mount /var/bti/stats/vstats
statfmt - DLm statistics extractor, version 5.00-24.
Copyright (c) 2007
input file is '/var/bti/stats/vstats'
Date,Time,Volser,Device,Error,Scratch,Created,Protected,-
Howlong,Filesize
09/21/2007,14:16:28,2500,N47061,0,0,0,0,47,5571614
09/21/2007,14:19:04,2500,N47061,0,0,0,0,37,5571614
09/21/2007,14:20:49,2500,N47061,0,0,0,0,8,5571614
09/21/2007,14:40:06,2500,N47061,0,0,0,0,119,5571614
09/21/2007,14:43:42,2500,N47061,0,0,0,0,38,5571614
09/21/2007,14:44:30,2500,N47061,0,0,0,0,6,5571614
09/21/2007,14:52:02,2500,N47061,0,0,0,1,73,106478280
09/21/2007,16:27:00,2500,N47062,0,1,0,0,274,184
09/21/2007,16:28:48,2500,D3L063,1,0,0,0,-1,-1
09/21/2007,16:37:18,2404,N47063,0,1,0,0,281,184
09/21/2007,16:40:03,2502,N47064,0,1,0,0,240,184
09/21/2007,16:42:33,250A,N47064,0,0,0,0,2,7880
09/21/2007,16:42:38,2501,N47064,0,0,0,0,1,15329
09/21/2007,16:44:23,2500,N47064,0,0,0,0,3,38466
09/21/2007,16:44:27,2500,N47064,0,0,0,0,2,61593
09/21/2007,17:05:37,2404,N47065,0,1,0,0,239,184
09/21/2007,17:06:21,2500,N47061,0,0,0,1,4,106478280
09/21/2007,17:08:13,2500,N47061,0,0,0,1,29,106478280
09/21/2007,17:09:34,2500,N47061,0,0,0,1,11,106478280
09/22/2007,15:32:50,2500,N47061,0,0,0,1,37,106478280
09/23/2007,21:08:08,2400,N47066,0,1,0,0,300,184
09/23/2007,21:08:10,2401,N47067,0,1,0,0,219,184
09/23/2007,21:09:43,2402,N47068,0,1,0,0,222,184
09/23/2007,22:53:03,2500,N47069,0,1,0,0,243,184
09/23/2007,22:53:08,2502,N47070,0,1,0,0,225,184
09/23/2007,22:53:11,2506,N47071,0,1,0,0,223,184
09/23/2007,22:53:36,2402,N47072,0,1,0,0,434,184
Example 4
# statfmt --unmount /var/bti/stats/vstats
statfmt - DLm statistics extractor, version 5.00-24.
Copyright (c) 2007 .
input file is '/var/bti/stats/vstats'
Date,Time,Volser,BlocksRead,BytesRead,Blockswritten,-
BytesWritten,LowWrite,Filesize,GoodLocates,BadLocates
09/21/2007,14:16:30,N47061,3,240,0,0,-1,-1,0,0
09/21/2007,14:19:05,N47061,4,248,0,0,-1,-1,0,0
09/21/2007,14:20:51,N47061,5,256,0,0,-1,-1,0,0
09/21/2007,14:40:07,N47061,3,240,0,0,-1,-1,0,0
09/21/2007,14:43:43,N47061,3,240,0,0,-1,-1,0,0
09/21/2007,14:44:31,N47061,3,240,0,0,-1,-1,0,0
09/21/2007,14:52:11,N47061,4,248,0,0,-1,-1,0,0
09/21/2007,16:27:01,N47062,2,160,6,533,0,593,0,0
09/21/2007,16:40:10,N47064,2,160,10,82320,0,7880,0,0
09/21/2007,16:42:36,N47064,5,400,7,82080,7690,15329,0,0
09/21/2007,16:42:41,N47064,5,400,59,934048,15139,38466,0,0
09/21/2007,16:44:26,N47064,5,400,59,934048,38276,61593,0,0
09/21/2007,16:44:30,N47064,5,400,59,934048,61403,84786,0,0
09/21/2007,17:04:03,N47063,231018,7391304720,34381,-
1100001400,0,1100207710,0,0
09/21/2007,17:06:31,N47061,4,248,0,0,-1,-1,0,0
09/21/2007,17:08:24,N47061,4,248,0,0,-1,-1,0,0
09/21/2007,17:11:17,N47061,4,248,0,0,-1,-1,0,0
09/21/2007,17:33:22,N47065,237081,7585127360,34381,-
1100001400,0,1100207710,0,0
09/22/2007,15:33:30,N47061,0,0,0,0,-1,-1,0,0
09/23/2007,21:09:43,N47068,69,1000480,68,1000400,0,85185,0,0
09/23/2007,22:28:23,N47066,0,0,0,0,-1,-1,0,0
09/23/2007,22:28:24,N47067,0,0,0,0,-1,-1,0,0
09/23/2007,22:53:37,N47072,69,1000480,68,1000400,0,85185,0,0
09/24/2007,12:08:18,N47071,0,0,0,0,-1,-1,0,0
09/24/2007,12:08:18,N47069,0,0,0,0,-1,-1,0,0
09/24/2007,12:08:18,N47070,0,0,0,0,-1,-1,0,0
220 EMC Disk Library for mainframe Version 3.0 User Guide
E
System Messages
This appendix lists the DLm system, EMCvts, and z/OS system
messages. The major topics are:
◆ Message format ................................................................................ 222
◆ DLm system messages .................................................................... 223
◆ Call home messages......................................................................... 366
◆ EMCvts messages ............................................................................ 367
◆ z/OS system messages.................................................................... 369
◆ VTEC errors that generate ConnectEMC events ......................... 374
Message format
The EMC DLm system message format is:
DLmxxxy
where:
xxx = message number
y = message class:
I (Informational)
W (Warning)
E (Error)
222 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
224 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: The DLm was unable to validate the license for the
specified feature.
System action: The specified feature is not available.
User action: Contact EMC Customer Support for assistance.
226 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: The specified DLm directory did not exist, and the DLm
application was not able to create the directory. This error can only
occur during application startup.
System action: Application startup terminates.
User action: Contact EMC Customer Support for assistance.
Description: The specified file was not successfully closed. The 'error
message' text explains the reason for the failure.
System action: None
User action: If you are unable to correct the problem, contact EMC
Customer Support for assistance.
228 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: The specified DLm directory did not exist, so the DLm
is now creating the directory.
System action: The specified directory is created.
User action: None.
230 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
232 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: The DLm application was not able to open the pipe over
which it receives Alert (error and warning) information from the
channel adapter drivers.
System action: The DLm continues to function, but channel adapter
alerts are not noted by the DLm.
User action: Contact EMC Customer Support for assistance.
Description: The EMC channel driver has closed the pipe over which
it sends alert messages, which are warning and error messages about
channel adapter problems, to the DLm application.
System action: The DLm continues to function, but channel adapter
alerts are not noted by the DLm.
User action: Contact EMC Customer Support for assistance.
234 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
236 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: The DLm has detected that the specified virtual device
is attached to a Unisys Host. This message is displayed once for each
virtual device attached to a Unisys.
System action: The DLm automatically makes accommodations for
the differences between an IBM and a Unisys Host.
User action: None (unless the Host is not actually a Unisys Host, in
which case EMC Customer Support should be contacted for
assistance).
238 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: This message displays the current erase policies for this
controller. Space needed indicates that the erase policy is to erase
scratch tapes when the tape library disk usage reached the RECOVER
setting. TTL indicates that the erase policy is to erase scratch tapes as
soon as they reach the age specified in hours or days.
System action: None.
User action: None.
240 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
242 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
244 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
246 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
248 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
250 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
252 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
254 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: Describes some event that has occurred within the IPMI
subsystem. The IPMI subsystem is responsible for monitoring and
reporting system events other than those occurring within the DLm
application, the channel interface adapter, or the adapter device
drivers.
System action: None.
User action: None.
Description: An error has occurred that has resulted in the loss of the
IPMI subsystem service. The IPMI subsystem is responsible for
monitoring and reporting system events other than those occurring
within the DLm application, the channel interface adapter, or the
adapter device drivers.
System action: The error is logged and the IPMI subsystem is shut
down.
User action: If the cause of the problem cannot be determined and
corrected, contact EMC Customer Support for assistance.
256 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: During startup, and any other time a tape library path
change is requested, the DLm validates the tape library for various
integrity issues.
System action: If any errors are found, subsequent messages report
the problems.
User action: If any errors are reported, correct the problems, then
SET PATH= to the desired path.
Description: While validating the tape library, the specified path was
found to be not browsable, which means the contents could not be
listed.
System action: During system startup, this is a warning message. If
this error occurs when processing a SET PATH command, the SET
PATH command fails.
User action: Make sure that the tape library is mounted correctly, and
that it is owned by user 'vtape' and has the 'x' permission set.
258 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: During startup, and any other time a tape library path
change is requested, DLm validates the tape library path.
System action: If any errors are found, subsequent messages will
report the problems.
User action: If any errors are reported, correct the problem(s), then
SET PATH= to the desired path.
Description: During startup, and at any other time a VTL volume list
update is requested, DLm will display the VTL volume list state.
System action: None.
User action: None.
Description: The VTL has defined more slots than the application can
support.
System action: None.
User action: Define the number of slots on the back-end VTL to
within our maximum of 20,000 slots.
Description: The SCSI tape drives are being scanned and cataloged.
System action: None.
User action: None.
260 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: During startup, and any other time a tape library path
change is requested, the DLm validates the tape library and each of
its subdirectories for various integrity issues.
System action: If any errors are found, subsequent messages report
the problems.
User action: If any errors are reported, correct the problems, then SET
PATH= to the desired path.
Description: During validation of the tape library, the DLm found the
specified subdirectory, but the subdirectory name does not conform
to a valid volser prefix. Every subdirectory in a tape library must
have a two-character name that consists of valid volser characters
(A–Z, 0–9).
System action: During system startup, this is a warning message. If
this error occurs when processing a SET PATH command, the SET
PATH command fails.
User action: Either remove the invalid subdirectory from the tape
library base directory, or rename the subdirectory to a valid volser
prefix.
Description: The specified file does not belong in the specified tape
library subdirectory because it does not begin with the same first two
characters (\volser prefix\) as the subdirectory name.
System action: During system startup, this is a warning message. If
this error occurs when processing a SET PATH command, the SET
PATH command fails. If this message occurs during a tape volume
mount, the mount fails.
User action: Correct the error, then retry the SET PATH command to
set the tape library path to the desired path or retry the tape volume
mount.
262 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: The specified file does not belong in the base tape
library directory because it begins with the same first two characters
(\volser prefix\) as an existing subdirectory name. The file should
reside in that subdirectory.
System action: During system startup, this is a warning message. If
this error occurs when processing a SET PATH command, the SET
PATH command fails. If this message occurs during a tape volume
mount, the mount fails.
User action: Correct the error, then retry the SET PATH command to
set the tape library path to the desired path or retry the tape volume
mount.
264 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
266 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
268 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
270 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: The specified number of blocks read from this tape were
found to have been AMDD-modified blocks. This informational
message is displayed at unload time whenever any AMDD-modified
blocks had been read.
System action: None.
User action: None.
Description: The Host has requested that the data it is writing should
be compressed, but the data will be written uncompressed because
the type of tape library filesystem it is being written to performs
better with uncompressed data. <type> may be "EMC DLm Data
Domain".
System action:The data being written is not compressed. If desired,
compression can be forced, regardless of filesystem, by setting the
IDRC=FORCE option on a device-by-device basis. This message will
display only once per volume as a reminder.
User action: None.
Description: The file specified in the command does not exist. The
command stopped with no action.
System action: None.
User action: Execute the command with the correct file.
272 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Note: This message applies to Fibre Channel drives as well. The message
mentions "SCSI" because DLm uses SCSI tape drivers.
274 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Note: This message also applies to Fibre Channel drives. The message
mentions "SCSI" because DLm uses SCSI tape drivers.
276 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
278 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
280 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: Data was received from the channel adapter from a path
on which the DLm was not currently handling a CCW.
System action: The unexpected data is ignored. The application
continues to run, but the device may not continue to function
properly.
User action: Contact EMC Customer Support for assistance.
Description: Data was received from the channel adapter while the
DLm was not currently handling a CCW that should return data.
System action: The unexpected data is ignored. The application
continues to run, but the device may not continue to function
properly.
User action: Contact EMC Customer Support for assistance.
Description: The virtual tape drive has become Ready, but there is no
online path to send the Ready Status message to the Host. Most likely
the drive, path, or channel was never configured/varied online on
the Host, or has been varied offline.
System action: The drive is mounted and ready from the DLm point
of view, but since a Ready Status was not presented, the Host most
likely reports that the drive is still not ready.
User action: Check that the specified device is varied online on the
Host. You can cause the DLm to present another 'Ready' signal to the
Host by typing an \Unready\ command, followed by a \Ready\
command. If this problem recurs, contact EMC Customer Support for
assistance.
282 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: After several retries, the DLm was unable to present the
asynchronous status ('Ready' signal) to the Host.
System action: The application continues without presenting the
status to the Host. The virtual volume remains mounted on the drive,
but the Host most likely reports that the drive is still not ready.
User action: You can cause the DLm to present another 'Ready' signal
to the Host by typing an \Unready\ command, followed by a
\Ready\ command. If this problem recurs, contact EMC Customer
Support for assistance.
Description: The Host has removed the specified channel path to the
DLm.
System action: This path is no longer available for channel I/O.
User action: None.
284 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: The DLm has turned tracing off for channel interface #n.
System action: Firmware tracing in channel interface #n remains off
until turned back on.
User action: None.
Description: The DLm has restored the trace options for channel
interface #n.
System action: Firmware tracing resumes in channel interface #n.
User action: None.
286 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
288 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
290 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: The Host sent a CCW that can only be executed while in
supervisor state but a prior Mode Set CCW had disabled this state.
System action: The CCW is not executed, and a unit check status
with command reject sense is sent to the Host.
User action: Investigate why the Host application is attempting to
illegally execute a supervisor state CCW.
292 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: The DLm received a write operation from the Host, but
the tape is full.
System action: The write operation fails (Unit Check status,
Intervention Required sense), and the virtual drive is put into the
'Not Ready' (Intervention Required) state. The DLm leaves the drive
in the Not Ready state until the DLm operator changes the drive to
Ready. Most Host systems reports the 'Intervention Required' to the
Host operator, pause the current job, and wait for the drive to come
ready.
User action: Insert another tape in this drive to resume.
294 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: The Host has read or spaced backwards from the virtual
tape volume's loadpoint.
System action: The DLm returns an error status (Read Backwards at
Loadpoint) to the Host I/O request.
User action: This is most likely a Host application error. Correct the
application causing the error.
Description: The Host read or positioned past the end of data on the
tape volume or physical end of tape on the physical tape volume.
System action: The DLm returns an error status (Data Check, Tape
Void) to the Host I/O request.
User action: This is most likely a Host application error. Correct the
application causing the error.
296 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: The Host attempted to write data with options set (such
as the 'store CRC' option) which requires expanded headers, but the
tape consists of blocks with regular headers. Tape header types
cannot be intermixed on the same tape.
System action: An error status (equipment check) is returned to the
host I/O request.
User action: Clear the options that require expanded headers.
Contact EMC Customer Support for assistance.
298 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: The disk usage for the specified tape library has
exceeded the current WARNING value.
System action: The DLm continues to warn at every percentage
change as long as the usage exceeds the WARNING value.
User action: Consider scratching and erasing unneeded virtual tape
volumes to free some disk space.
Description: The disk usage for the specified tape library directory
has exceeded the current RECOVER value.
System action: The DLm erases the data from previously scratched
virtual tape volumes until the disk usage falls to (RECOVER minus
RECOVERAMT) percent.
User action: Consider scratching and erasing unneeded virtual tape
volumes to free some disk space.
300 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: The DLm has created the new volume 'volser', but is not
able to initialize it because it is read-only. This is only possible when a
manual LOAD command with the PROTECTED option is typed for
a new (non-existing) volume.
System action: The volume is created and mounted, but it appears to
the Host as an empty, un-initialized (and read-only) tape.
User action: Do not do this.
302 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
304 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
306 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
User action: The Host most likely complains about the invalid labels;
take the appropriate action required by the Host. If the Host refuses
to use the corrupted volume as is, perform a reinitialization of the
virtual tape volume using the standard Host initialization
procedures. Try to determine the reason the Host previously wrote
invalid labels to this tape volume. This condition is most often caused
by an error on the Host during volume initialization or at some other
time when the Host is writing the volume labels. In particular, this
problem has been seen when a Host job is cancelled while it is
opening an output tape.
308 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
310 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
312 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
314 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: The DLm has detected that the tape library for the
specified virtual tape drive is on a CIFS/SMB filesystem and the
current maximum volume setting for this drive was greater than 2
GB.
System action: The maximum volume size for this drive is adjusted
to 2 GB. If the tape library path is ever changed back to a non-SMB
filesystem, the maximum volume size automatically changes back to
the previous value.
User action: None.
Description: The DLm has detected that the tape library for the
specified virtual tape drive is no longer on a CIFS/SMB filesystem,
and the maximum volume setting for this drive was previously
adjusted to 2 GB.
System action: The maximum volume size for this device is adjusted
back to the previous value.
User action: None.
Description: The DLm received a write operation from the Host, but
the tape library disk is full. 'nnnnnnn' is the number of bytes written
so far.
System action: The write operation fails (Unit Check status,
Intervention Required sense), and the virtual drive is put into the
'Not Ready' (Intervention Required) state. The DLm leaves the drive
in the Not Ready state until the DLm operator changes the drive to
Ready. Most Host systems reports the 'Intervention Required' to the
Host operator, pause the current job, and wait for the drive to come
ready.
User action: When space is available on the tape library disk, execute
the READY command to this drive to resume.
316 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: The DLm received a write operation from the Host, but
the tape library disk is full. The DLm cannot recover and continues
because the tape library is on an NFS filesystem. 'nnnnnnn' is the
number of bytes written so far.
System action: The write operation fails (Unit Check status,
Equipment Check sense). The contents of the volume being written is
unpredictable.
User action: Rerun the job after more space is made available on the
target tape library filesystem.
318 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
320 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
322 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
324 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
326 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: The specified DLm console command was sent from the
Host through the specified virtual tape device.
System action: The command is executed. Depending on the results
of the command, a return code returns to the Host program.
User action: If the command is successful, none. Otherwise,
determine the reason for the DLm console command failure and
correct the problem.
Description: A DLm console command was sent from the Host, but
the DLm is not configured to allow Host-initiated commands.
System action: The command not be executed. A failure code be
returned to the Host program.
User action: If you want the Host to be able to initiate DLm console
commands, correct the DLm configuration to allow for this feature.
Description: A DLm RUN console command was sent from the Host,
but the DLm is not able to locate the specified script.
System action: The command is not executed. A failure code returns
to the Host.
User action: Check that the correct script name was specified in the
RUN command, and that the script file has the proper permissions to
be executed by the DLm user 'vtape.'
Description: A DLm RUN console command was sent from the Host,
but the DLm is not able to execute the specified script.
System action: The command is not executed. A failure code returns
to the Host.
User action: Check that the correct script name was specified in the
RUN command, and that the script file has the proper permissions to
be executed by the DLm user 'vtape.'
Description: A DLm RUN console command was sent from the Host,
but the DLm is not configured to allow the RUN command.
System action: The command is not executed. A failure code returns
to the Host.
User action: If you want the Host to be able to initiate DLm RUN
commands, correct the DLm configuration to allow for this feature.
328 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: A DLm RUN console command was sent from the Host
and executed by the DLm, but the specified script did not complete
within the specified time limit.
System action: The DLm cancels the process identified by process ID
#nnnnn. A failure code returns to the Host.
User action: If the specified script normally takes longer than the
time specified, specify a longer time on the RUN command.
330 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
332 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
334 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: The DLm received too many labels to store (more than
legally allowed for standard label processing) while processing the
trailer labels for a standard labeled flat file.
System action: The Host write is canceled with a unit check.
User action: Correct the condition that is causing too many labels to
be written.
Description: The Host wrote a HDR1 label to a flat file volume, and
the DLm attempted to change the volume's filename from
VOLSER.FLAT to VOLSER.DATASETNAME.FLAT (where
DATASETNAME is the data set name from the HDR1 label), but the
file VOLSER.DATASETNAME.FLAT already exists in the tape
library.
System action: The Host write request is canceled with a unit check.
User action: Either delete or rename the existing file in the tape
library before writing a flat file with the same name, or use a different
data set name in the JCL for the new output file.
336 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: The Host wrote a HDR1 label to a flat file volume, and
the DLm attempted to change the volume's filename from
VOLSER.FLAT to VOLSER.DATASETNAME.FLAT (where
DATASETNAME is the data set name from the HDR1 label), but an
error occurred while renaming.
System action: The Host write request is canceled with a unit check.
User action: See the 'error message' portion of this message to
determine the reason for the error.
Description: The data block read from the tape is larger than the
maximum supported by DLm.
System action: The DLm returns an error status (equipment check) to
the Host.
User action: The tape is not compatible with the DLm because of the
large blocks it contains.
338 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: The DLm has received a tape block with size ('xxxxxx')
that is larger than the maximum tape blocksize ('yyyyyy') that can be
presented to the SCSI Tape Device.
System action: An I/O error is returned to the Host.
User action: Correct the Host application to send a blocksize that can
be handled by the tape drive.
Note: This message also applies to Fibre Channel drives. The message
mentions "SCSI" because DLm uses SCSI tape drivers.
DLm789I Device <device name> does not support the SCSI <cmd>
command
Description: The physical tape drive does not support the specified
command.
System action: DLm will continue, but the specified command
cannot be performed.
User action: Determine that the attached device is a supported device
type.
Note: This message also applies to Fibre Channel drives. The message
mentions "SCSI" because DLm uses SCSI tape drivers.
Note: This message also applies to Fibre Channel drives. The message
mentions "SCSI" because DLm uses SCSI tape drivers.
Note: This message also applies to Fibre Channel drives. The message
mentions "SCSI" because DLm uses SCSI tape drivers.
Note: This message also applies to Fibre Channel drives. The message
mentions "SCSI" because DLm uses SCSI tape drivers.
340 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
342 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
344 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Note: This message also applies to Fibre Channel drives. The message
mentions "SCSI" because DLm uses SCSI tape drivers.
Description: The OSADDR value for this device has been changed.
The OSADDR value is used with the VSE BTIMOUNT program to
identify the name by which VSE knows a DLm application virtual
device.
System action: The new OSADDR value will be used to find a virtual
device when BTIMOUNT requests a mount on a specific drive by
name, and DLm will report the OSADDR value to BTIMOUNT when
it completes a mount on ANY drive.
User action: None.
346 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Description: The GROUP value for this device has been changed.
The GROUP value is used with the VSE BTIMOUNT program to
identify drives that belong to the same VSE group as the control
drive.
System action: The new GROUP value will be used to find a virtual
device when BTIMOUNT requests a mount on ANY drive.
User action: None.
Description: With the value set to off, the stored CRC value in the
aws header will not be confirmed.
System action: None.
User action: None.
Description: With the value set to off, the CRC value will not be
stored in the aws header.
System action: None.
User action: None.
348 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Note: This message also applies to Fibre Channel drives. The message
mentions "SCSI" because DLm uses SCSI tape drivers.
350 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Note: This message also applies to Fibre Channel drives. The message
mentions "SCSI" because DLm uses SCSI tape drivers.
DLm864E You can only create <nnn> volumes starting from <volser>
Description: The tape library type assigned to this device does not
support tape initialization. Volumes can be initializedonly in tape
libraries on direct-access filesystems.
System action: The INITIALIZE command is ignored.
User action: Specify a DEVICE=device that has a tape library defined
on a valid direct-access filesystem.
352 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
354 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
356 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
358 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
360 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
362 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
System action: The DLm attempts to shut down all virtual devices.
All devices are taken offline to the Host, and the DLm application
terminates.
User action: Contact EMC Customer Support for assistance.
364 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Mgmt001E ACP1 is not directly accessible from the base VNX primary
Control Station.
Mgmt002E ACP2 is not directly accessible from the base VNX primary
Control Station.
366 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
EMCvts messages
EMCvts is the script that starts the DLm application. The following
messages may be displayed by EMCvts while starting the DLm
application.
The script has determined that the firmware on the channel adapter
card (xxxx) is actually newer than the firmware file found on the
system disk (yyyy). The adapter firmware not be changed.
The script has determined that the firmware on the channel adapter
card (xxxx) should be updated to a newer version found on the
system disk (yyyy), and is doing so.
EMCvts: The "file EMCDR" or "EMCDIR environment variable" contains an invalid directory!
This message is always preceded by the message stating that the
directory containing the EMC DLm executable files cannot be
located. Contact EMC Customer Support if you need additional
assistance in determining the cause of this problem.
368 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
Note: The Help command does not support z/OS system messages.
DLMCMD messages
The following messages can be returned by the DLMCMD program
running on the mainframe.
An I/O error occurred on the DLMCMD control tape. See the CSW
and SENSE information and any additional messages on the z/OS
and controller consoles to resolve the problem.
DLMCMD was unable to open the DLMCTRL control tape. Check the
JCL and any additional messages on the joblog to resolve the
problem.
DLMCMD was unable to open the DLMLOG log file. Check the JCL
and any additional messages on the joblog to resolve the problem.
DLMCMD was unable to open the input DLMCMD file. Check the
JCL and any additional messages on the joblog to resolve the
problem.
DLMLIB message
The following message can be returned by the DLMLIB program
running on the mainframe.
An invalid volser was specified in the input file. Correct the input
and rerun.
DLMSCR messages
The following messages can be returned by the DLMSCR program
running on the mainframe.
The control tape that sends scratch requests to the controller had an
I/O error. Check to make sure the controller is still running. If this is
the case use the CSW and SENSE provided to correct the problem.
370 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
The DLMSCR control tape failed to open. Make sure the controller is
up and running and the unit address used for the DLMSCR control
tape is a valid controller device and has been varied online to the
mainframe.
DLMSCR maintains a log file with all the error and informational
messages from any DLMSCR runs. Check the mainframe job log to
determine why it did not open properly.
The default for the PREFIXLN is 2. In most cases the customer using 2
for their prefix length. If the tape library resides on Centera a prefix
length of 1 is common. In that case PREFIXLN=1 should be coded.
Check your input parameters.
The device specified on the DEV= parameter was not found in the
active configuration. Correct the parameter and retry.
372 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
DLMVER messages
DLV010I UTILITY VERSIONS (<z/os release level>):
374 EMC Disk Library for mainframe Version 3.0 User Guide
System Messages
376 EMC Disk Library for mainframe Version 3.0 User Guide
Index
EMC Disk Library for mainframe Version 3.0 User Guide 377
Index
G T
GENSTAT utility 153 Tape
direct 108
export command 184
I
export/import utilities 111
indicators
import command 186
FICON 28
Tape Library unaccessible
DLm156W 249
L DLm400E 290
Library utility, awsprint 117
U
M utility
message DLm scratch 156
class 222 DLMCMD 158
DLm system 223 DLMSCR 153
DLMCMD 369 DLMVER 151
378 EMC Disk Library for mainframe Version 3.0 User Guide
Index
GENSTAT 153 Z
z/OS
V compaction of the virtual tape data 150
VNX configuring the devices 138
halting 70 Load display message 208
power down 72 Missing Interrupt Handler 148
VTE operator command 148
configuring virtual device 85 utilities 151
power down 68
EMC Disk Library for mainframe Version 3.0 User Guide 379
Index
380 EMC Disk Library for mainframe Version 3.0 User Guide