emc disk library for mainframe dlm1000 - dell emc brazil · pdf fileemc® disk library for...

EMC® Disk Library for mainframe DLm1000

System Messages P/N 300-013-755 Rev 03

EMC® DLm1000 System Messages

2 2

Copyright © 2012 EMC Corporation. All rights reserved.

Published August, 2012

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

EMC2, EMC, Data Domain, RSA, EMC Centera, EMC ControlCenter, EMC LifeLine, EMC OnCourse, EMC Proven, EMC Snap, EMC Source-One, EMC Storage Administrator, Acartus, Access Logix, AdvantEdge, AlphaStor, ApplicationXtender, ArchiveXtender, Atmos, Authentica, Authentic Problems, Automated Resource Manager, AutoStart, AutoSwap, AVALONidm, Avamar, Captiva, C-Clip, Celerra, Celerra Replicator, Centera, CenterStage, CentraStar, ClaimPack, CLARiiON, ClientPak, Codebook Correlation Technology, Common Information Model, Configuration Intelligence, Configuresoft, Connectrix, CopyCross, CopyPoint, CX, Dantz, DatabaseXtender, Data Domain, Direct Matrix Architecture, DiskXtender, DiskXtender 2000, Document Sciences, Documentum, elnput, E-Lab, EmailXaminer, EmailXtender, Enginuity, eRoom, Event Explorer, FarPoint, FirstPass, FLARE, FormWare, Geosynchrony, Global File Virtualization, Graphic Visualization, Greenplum, HighRoad, HomeBase, InfoMover, Infoscape, Infra, InputAccel, InputAccel Express, Invista, Ionix, ISIS, Max Retriever, MediaStor, MirrorView, Navisphere, NetWorker, nLayers, OnAlert, OpenScale, PixTools, PowerPath, PowerSnap, QuickScan, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, SafeLine, SAN Advisor, SAN Copy, SAN Manager, Smarts, SnapImage, SnapSure, SnapView, SRDF, StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix, Symmetrix DMX, Symmetrix VMAX, TimeFinder, UltraFlex, UltraPoint, UltraScale, Unisphere, Vblock, VMAX, VPLEX, Viewlets, Virtual Matrix, Virtual Matrix Architecture, Virtual Provisioning, VisualSAN, VisualSRM, Voyence, WebXtender, xPression, xPresso, YottaYotta, the EMC logo, the RSA logo, and where information lives are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to the technical documentation and advisories section on EMC Online Support.

EMC® DLm1000

System Messages

Part Number 300-013-755-03


3

Contents

Preface ........................................................................................................ 5

vt (DLM) Messages ...................................................................................... 7

vtd Messages .......................................................................................... 159

z/OS System Messages ........................................................................... 161

DLMCMD ............................................................................................... 161

DLMLIB Messages ................................................................................. 162

DLMSCR Messages ................................................................................ 162

DLMHOST Messages .............................................................................. 165

GENSTATS Messages ............................................................................. 168

VSE System Messages ............................................................................. 171

DLMSS(D E) REXX Script Messages ....................................................... 171

DLMSCR Messages ................................................................................ 173

DLMDTSCR Output Log Error Messages .................................................. 174

DLMEPSCR Messages ............................................................................ 176

DLMEPSCR Output Log Error Messages .................................................. 177

DLMMOUNT Messages .......................................................................... 179


5

Preface

This publication contains all messages issued by EMC DLm1000.

DLm1000 is a virtual tape controller for IBM and Unisys mainframe. DLm1000 uses EMC’s virtual tape emulation engine known as Virtuent. The name Virtuent is used throughout this manual to refer to the virtual tape engine. Virtuent system administrators researching the meaning of any message can refer to this manual by message number.

Virtuent tape-on-disk technology is a hardware / software solution that provides a mainframe attached tape controller emulation tape drives to IBM, compatible, and Unisys mainframes.

Virtuent is used exclusively in EMC’s family of virtual tape products known as the Disk Library for mainframe (DLm). Different models of DLm provide either a single controller or multiple, independently operating controllers. A single virtual tape controller running Virtuent tape emulation is known as a Virtual Tape Engine and is commonly referred to as a VTE. For the purpose of this error messages manual, the words controller and VTE are equivalent. You may substitute the term “VTE” wherever the word “controller” is used.


7

vt (DLM) Messages

vt messages are messages that are issued by the Virtuent tape-on-disk application (vt) running on a DLm VTE. These messages will be written to the Virtuent log file and will be displayed on the VTE’s console when the vt console application is active.

DLM000I: <debugging message>

Description: Various debugging messages are displayed if the DLm application's debugging level is set to 1 or higher.

System action: None.

User action: You really should not be seeing any DLm000I messages unless you have invoked a debugging mode. For best performance, debugging should be left off unless directed otherwise by EMC Customer Support. Type the command SET DEBUG=0 to turn debugging off.

DLM010I: Compression hardware [not] available

Description: This message reports on the availability of a hardware compression card in the controller.

System Action: If a hardware compression card is present (and is not disabled through configuration or operator command), the card will be used for compressing and decompressing virtual tape data.

User Action: None.

DLM011I: Compression driver version: x.x.x

Description: This message displays the version number of the hardware compression card driver.

System Action: None.

User Action: None.

vt (DLM) Messages


8

DLM012I: Compression card #n:id=xx version=nnn state=xxxxxxxx

Description: This message displays information about the hardware compression card installed in the controller.


User Action: None.

DLM013I: Hardware compression/decompression set ON/OFF

Description: This message reports on the status of the hardware compression and decompression features.


User Action: None.

DLM014E: Unknown hardware compression card, id=0xXXXX

Description: The identity of the hardware compression adapter cannot be determined.

System Action: Hardware compression and decompression will not be available until the problem is resolved and the controller is restarted.

User Action: Contact EMC Support for assistance.

DLM015E: Hardware compression driver error

Description: An error has occurred while initializing the hardware compression adapter.


User Action: Contact EMC support for assistance.

DLM016E: Device <devicename> Error opening hardware compression driver: <error message>

Description: An error has occurred while opening the hardware compression adapter.



vt (DLM) Messages


9

DLM017I: Removing all VOLSER locks owned by this system...

Description: During startup and shutdown, all file locks held by this application, if any, are removed.

System Action: All VOLSER locks owned by this system are removed.

User Action: None.

DLM018E: Error creating <processname> Thread: <error message>

Description: This internal error can only occur during application startup.

System Action: Application startup terminates.


DLM019E: Error allocating memory for <name>: <error message>

Description: An internal memory allocation error has occurred in the Virtuent application.

System Action: Depending on the error, the controller may abend or may need to be restarted to regain some functionality.


DLM020E: Cannot verify <feature> license: <error message>

Description: The controller was unable to validate the license for the specified feature.

System Action: The specified feature will not be available.


DLM021E: <parameter=value> incompatible with <license> license

Description: The specified parameter is not compatible with the specified licensed feature.

System Action: If the error is in the configuaration file, the application startup terminates. If the error is in a SET command the command is rejected.

User Action: Contact EMC Support for additional assistance.

DLM022E: Unable to find userid 'vtape'

Description: The Virtuent application must run under the user ID 'vtape', but this user ID does not exist on the controller.



vt (DLM) Messages


10

DLM023E: Unable to switch to user and group 'vtape'

Description: The Virtuent application must run under the user ID 'vtape', but the application was unable to switch to this ID.



DLM024E: Program not started with effective userid 'root'

Description: The Virtuent application must be started under the userid 'root'.



DLM025E: Invalid license combination, <license1>+<license2>.

Description: The combination of license files on the system is not valid.



DLM026E: Pid file <filename> must be full path name. Use -? for Help

Description: The command line that starts the virtual tape application contains an invalid argument.



DLM027E: Failed to fork daemon: <error message>

Description: The application failed to daemonize itself.



DLM028E: Internal Error calling setsid: <error message>




DLM029E: Internal Error changing working directory to '/': <error message>



vt (DLM) Messages


11


DLM030I: Traces are [un]buffered

Description: The Virtuent application trace files are buffered (saved in memory and written to disk periodically) by default for better performance. If the environment variable BTITRACEUNBUFFERED has been set to any value when the application starts, trace files are written in an unbuffered manner (every event is written to disk immediately).


User Action: The buffered default should be sufficient for most tracing needs, unless directed otherwise by EMC support. When traces are buffered be sure to enter the Virtuent command 'Save Trace' to write all trace buffers to disk before examining or copying the trace files.

DLM031E: Cannot Create PID file <filename>: error message

Description: The application failed to to create the process ID file.



DLM032E: Trace task error reading pipe, errno=0x<xx> (<nnn>)

Description: An I/O error has occurred during device tracing.

System Action: Virtuent attempts to continue tracing. One or more events may be lost from the device trace.


DLM033E: Error writing to <file type> file <filename>:<error message>

Description: An I/O error occurred while writing to the specified file.

System Action: Virtuent continues running without writing additional messages to the specified file.

User Action: Refer to any earlier message(s) and the 'error message' portion of this message to determine the cause of the failure. If the problem cannot be corrected, contact EMC support for assistance.

DLM034I: <STDOUT/STDERR message>

Description: A message was received from Standard OUT or Standard ERROR.


vt (DLM) Messages


12

User Action: None

DLM035E: Error creating directory 'directory': <error message>

Description: The specified directory did not exist, and Virtuent was not able to create the directory. This error can only occur during startup.

System Action: Virtuent startup terminates.


DLM036E: Error closing <file type> file <filename>: <error message>

Description: The specified file was not successfully closed. The 'error message' text explains the reason for the failure.

System Action: None

User Action: If you are unable to correct the problem, contact EMC support for assistance.

DLM037E: Error creating/opening <feature> message pipe: <error message>

Description: An error occurred while initializing the specified feature. This error can only occur during Virtuent startup.

System Action: Startup terminates or continues without the specified feature. The 'error message' text explains the reason for the failure.

User Action: If you are unable to correct the problem, contact contact EMC support for assistance.

DLM038I: Creating directory 'directory'

Description: The specified directory did not exist, so Virtuent is now creating the directory.

System Action: The specified directory is created.

User Action: None.

DLM039E: Error opening output <file type> file <filename>: <error message>

Description: The specified output file was not successfully opened. This error can only occur during Virtuent startup.

System Action: Startup terminates. The 'error message' text explains the reason for the failure.

User Action: If you are unable to correct the problem, contact EMC support for assistance.

DLM041E: Device <devicename> error <nnn> going online

vt (DLM) Messages


13

Description: The specified device was not able to go online to the channel. This error can only occur during Virtuent startup.

System Action: Startup terminates.

User Action: Verify in the Virtuent configuration file that the configuration data for the specified device is correct. If the problem recurs, contact EMC support for assistance.

DLM042E: Error <nnn> going live to channel. Interface=n, slot=nnnnnn

Description: The channel interface number 'n' was not able to go online to the channel.

System Action: This channel interface will be out of service until the problem is corrected and the adapter is reset.

User Action: The RESET CHANNEL ADAPTER command might be able to bring this adapter online. Contact EMC support for more assistance.

DLM044W: WARNING: /var filesystem usage at nn%

Description: The specified critical system filesystem is starting to run low in free disk space. If this filesystem were to fill, it might have a detrimental effect on the system operation.

System Action: Warning messages will continue to be displayed at every percentage of change in usage as long as the usage exceeds the designated warning level.

User Action: Contact EMC support for assistance in freeing space on the designated filesystem.

vt (DLM) Messages


14

DLM045E: Error getting status of <filesystem> filesystem: <error message>

Description: An unexpected error occurred while trying to get information about the specified filesystem.

System Action: The system will continue to run, but some features (such as warnings about the capacity limits of certain filesystems) may not be functional.

User Action: If this problem recurs, contact EMC support for assistance.

DLM046W: /var has <nnn> remaining bytes, debugging messages turned off

Description: A debugging mode that writes messages to the console log is active, and the /var filesystem, where the messages are stored, is starting to fill.

System Action: The debugging mode is turned off to suppress further debugging messages.

User Action: Contact EMC support for assistance in freeing space on the designated filesystem.

DLM047E: Internal Error <function>: <error message>

Description: An internal error has occurred.

System Action: The function listed cannot be completed.


DLM048E: Internal Error <process>: <error message>

Description: An internal error has occurred.

System Action: Virtuent terminates.


DLM049E: Internal Error <function>: <error message>

Description: An internal error has occurred due to external conditions.

System Action: The function listed cannot be completed.


vt (DLM) Messages


15

DLM050E: Invalid command line parameter: <value>. use -? for help

Description: The command line that starts Virtuent contains an invalid argument.


User Action: Correct the command line argument(s) and restart Virtuent.

DLM052E: Invalid command line Configuration File Name parameter: <value>. Use -? for Help

Description: The command line that starts Virtuent contains an invalid argument.


User Action: Correct the command line argument(s) and restart Virtuent.

DLM055E: Error getting channel adapter driver version number

Description: Virtuent was unable to determine the version of the channel adapter driver.



DLM056I: Channel adapter driver version is x.x.x

Description: This message displays the version number of the channel adapter driver.


User Action: None.

DLM057E: This application requires minimum channel adapter driver version x.x.x!

Description: The channel adapter driver is below the minimum release level required by this version of Virtuent. Message DLM056I that precedes this message identifies the channel adapter driver currently loaded.



vt (DLM) Messages


16

DLM058I: Device <devicename> MIHn set to nnn seconds

Description: The MIH (Missing Interupt Handler) timeout value that the Virtuent application reports to the Host has been set to the specified value. MIHn will be MIH1 or MIH2. MIH1 is the primary or fast MIH value that most Host operating systems use for most CCWs, such as reads and writes. MIH2 is the secondary or slow MIH value that some Hosts use for certain long-running CCWs such as Locate, FSF, and Data Security Erase commands. By default, the Virtuent application sets these values to 3000 and 18000 seconds, respectively.

System Action: The specified value is reported to the Host on the next Read Configuration Data command.

User Action: None.

DLM060E: There is already an instance of <program> running

Description: Another copy of Virtuent is currently running.

System Action: The second copy of Virtuent terminates.

User Action: Make sure that Virtuent is not already running before starting a second copy.

DLM061E: Cannot register <function> handler: <error message>

Description: This internal error can only occur during Virtuent startup.



DLM062E: Error opening Alert FIFO <filename>: <error message>

Description: Virtuent was not able to open the pipe over which it receives alert (error and warning) information from the channel adapter driver.

System Action: Virtuent continues to function, but channel adapter alerts will not be noted by Virtuent.


DLM064E: Alert FIFO has been closed

Description: The channel adapter driver has closed the pipe over which it sends alert messages, which are warning and error messages about channel adapter problems, to Virtuent.

System Action: Virtuent continues to function, but channel adapter alerts will not be noted by Virtuent.


vt (DLM) Messages


17

DLM065E: Invalid data (nn bytes) read from Alert FIFO

Description: The channel adapter driver has sent an unrecognized alert message to Virtuent.

System Action: Virtuent continues to function, but channel adapter alerts will no longer be noted by Virtuent.


DLM066E: Error creating/opening Read named pipe <filename>: <error message>

Description: This internal error can only occur during Virtuent startup.



DLM0067I: BusyType set to Busy/Immediate/Deferred

Description: Virtuent can be configured to send various status codes to hold off the host under busy conditions. The default is to send a true busy signal.

System Action: Virtuent sends a busy status if BusyType is set to “Busy”, an immediate command retry for “immediate”, and a deferred command retry for “deferred”.

User Action: None. Do not change this setting unless directed to do so by EMC support. This setting could cause channel errors.

DLM068I: Double testing of compressed data set ON/OFF

D escription: By default, the DLm application performs an extra CRC check of data that has been compressed before writing it to the tape library.

S ystem A ction: If this option is ON (the default), the data is checked just before it is written to the library. If a discrepancy is found, an error is returned to the Host's write command. If this option is turned OFF, no extra integrity check is performed.

U ser A ction: It is recommended that this option always be left ON.

vt (DLM) Messages


18

DLM069I: Resetting Events will [not] be sent to firmware

Description: A resetting event is any event that resets a Virtuent device's pathgroup ID or assignment, such as a system or selective reset or restarting of the Virtuent application. Normally after a resetting event has occurred the next command sent by the Host receives a resetting event unit check to notify the Host that the resetting event occurred. The Host should respond appropriately by restoring the device's pathgroup ID and assignment information, and re-issue the unit-checked command. In addition, some channels expect a low-level indication that a resetting event has occurred. By default, Virtuent sends this special indication to the channel along with the unit check. For exceptional conditions, Virtuent can be configured to NOT send the low-level resetting event indication to the channel when it sends a resetting event unit check to the Host. This message is displayed at Virtuent application startup and whenever the low-level channel resetting event notification option is switched on or off.

System Action: Low-level channel resetting event status will not be sent to the channel when this option is set OFF.

User Action: None. Under normal conditions, the low-level channel resetting event indication should NOT be configured OFF. Under rare conditions, a channel may not correctly handle the low-level channel resetting event indicator, and channel errors may occur. In this case, consult EMC support before configuring this option off. Also see message DLM082I.

DLM070I: <emulation type> emulation version set to n

D escription: The DLm is configured to invoke the specified channel adapter emulation version.

S ystem A ction: None.

User Action: None.

DLM071E: No channel interface cards present!

Description: No channel interface adapters were detected in the system. This error can only occur during Virtuent startup.



DLM072E: Virtuent requires minimum firmware version nnnn!

Description: The firmware in a channel adapter is below the minimum release level required by this version of Virtuent. Message

vt (DLM) Messages


19

DLM075I that precedes this message identifies the channel adapter in question.



DLM073E: Interface #<n> (slot <nnnnnn>) returned bad status = <nnn>

Description: The specified channel interface adapter returned an error status to Virtuent. This error can only occur during startup.



DLM074E: Interface #<n> (slot <nnnnnn>) error getting <adapter info>

Description: The specified channel interface adapter returned an error status to Virtuent. This error can only occur during startup.



DLM075I: Interface #n: n (0xxxxxx) bus:n slot:n type:n (adaptertype) media:n (mediatype)

Description: This message displays information about the channel interface adapter(s) in the controller. This message is displayed at startup and in response to the QUERY ALL or QUERY CHANNEL ADAPTER command.


User Action: None.

DLM076I: Interface #n: [hardware s/n | s/n override] xxxxxxxxxxxx



User Action: None.

DLM077I: Interface #n: Firmware emulation type: XXXX, version: nnnn yyyy/mm/dd


vt (DLM) Messages


20


User Action: None.

DLM078I: Disk usage WARNING level set to nn%

Description: Virtuent is configured to warn about tape library disk utilization when usage reaches nn% full.


User Action: None.

DLM079I: Disk space RECOVER level [set to nn%]/[is N/A]

Description: The virtual tape application is configured to start erasing scratch tape volumes to recover disk space when disk utilization reaches nn% full. If "is N/A" is displayed, the Erase Policy is set to a "time-to-live" policy rather than a space-usage policy, so the RECOVER setting is irrelevant.


User Action: None.

DLM080I: Device <devicename> UNISYS detected

Description: Virtuent has detected that the specified virtual device is attached to a Unisys Host. This message will be displayed once for each virtual device attached to a Unisys.

System Action: Virtuent will automatically make accommodations for the differences between an IBM and a Unisys Host.

User Action: None (unless the Host is not actually a Unisys Host, in which case EMC support should be contacted for assistance).

vt (DLM) Messages


21

DLM081I: Interface #n: Current state <state>; Desired state <state>

Description: This message displays information about the channel interface adapter(s) in the controller. This message is displayed at application startup and in response to the QUERY ALL or QUERY CHANNEL ADAPTER command.


User Action: None.

DLM082I: Resetting Events will [not] be ignored

Description: A resetting event is any channel event that resets a channel-attached device's pathgroup ID or assignment, such as a system or restarting of the controller. Normally, after a resetting event has occurred the next command sent by the Host receives a resetting event unit check to notify the Host that the resetting event occurred. The Host should respond appropriately by restoring the device's pathgroup ID and assignment information, and re-issue the unit-checked command. Occasionally, especially with older standalone IPL programs, a Host may not handle a resetting event unit check correctly. In this case, the controller can be configured to NOT send resetting event unit checks. This message is displayed when resetting event notification is turned on or off.

System Action: Resetting event unit checks will not be sent to the Host when this option is set.

User Action: None. Under normal conditions, the controller should NOT be configured to ignore resetting events. Doing so can cause problems when varying on devices to a Host that does properly handle, and actually expects, resetting event unit checks. Contact EMC support for more information.

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

Description: This message displays the compression level set by default, in the configuration file, or by the SET COMPRESSION command. The compression level ranges from 0 (no compression at all) to 9 (maximum compression with maximum overhead). The default compression level is 1 (minimum compression with minimum overhead).


User Action: None.

DLM084I: Disk space RECOVERAMT set to nn%

vt (DLM) Messages


22

Description: Virtuent is configured to stop erasing scratch tape volumes to recover disk space when disk space usage falls to (RECOVER minus RECOVERAMT) percent.


User Action: None.

DLM085I: <feature> support enabled

Description: This message displays if support for an optional feature has been enabled in the configuration file.

System Action: The optional feature is enabled.

User Action: None.

DLM086I: <WORM-filesystem-type> default retention: nn Days/Months/Years

D escription: This message displays if there is a WORM filesystem default retention period set in the configuration file.


U ser A ction: None.

DLM087I: Checking of CRCs from channel set ON|OFF

DLM088I: Sending

DLM089I: UNISYS set ON/OFF for device <devicename> / ALL devices

Description: The SET UNISYS command has been accepted for a device or all devices.

System Action: Virtuent will adjust for the differences between an IBM and a Unisys Host for the specified device(s).

User Action: None (unless the Host is not actually a Unisys Host, in which case you shouldn't have done this).

DLM090I: AMDD feature turned ON/OFF [for device devicename]/[for all devices]

D escription: The AMDD feature has been set ON or OFF.



DLM091I: AMDD pad boundary set to <nnn>

D escription: The AMDD pad boundary has been set to the designated value.


vt (DLM) Messages


23


DLM092E: SET AMDD cannot specify a specific device

Description: For EMC DLm and MDL-1000DD/2000DD models only, AMDD is a global setting and cannot be SET by individual device.

System Action: The SET command is ignored.

User Action: None.

DLM093I: AMDD support for <application-type> is ON/OFF

D escription: This node is configured to perform AMDD processing on the specified data type. This option affects writing of data only; regardless of this setting, reading of all data types previously written by AMDD is always supported.



DLM094I: AMDD DD marker insertion algorithm: <method>

D escription: This node is configured to insert "extra" DD markers into AMDD records using the specified algorithm. This option applies only to FDR Upstream data being written to a Data Domain filesystem. The possible options are:

STANDARD - No "extra" markers are inserted (default)

MARKEVERYD - A marker is inserted on every data record

MARKFILES - A marker is inserted on the first data record of every file

MARKEVERY8KD - A marker is inserted on every 8K data record

MARK8K - A marker is inserted at every 8K interval in the file




U ser A ction: None.te m Me ssa

DLM095I: AMDD DD <configuration information>

Description: These messages describe configuration parameters that apply specifically to FDR Upstream data being written to a Data Domain filesystem. The values which may be displayed include:

vt (DLM) Messages


24

<minimum markable block size is nnnn> This node is configured to insert AMDD DD markers only on segments of data larger than <nnnn> bytes.

<maximum marker length is nnnn> This node is configured to write AMDD DD markers no larger than <nnnn> bytes.


User Action: None.

DLM096I: Erase Policy: [TTL for <nn> hours/days] [Space needed]

D escription: 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.



DLM097I: Maximum TTL Erase Time set to <nn> seconds

D escription: This message displays the current maximum amount of continuous time that the application will spend erasing scratch tapes that have exceeded the TTL erase policy period. If the TTL erase time is exceeded, the application stops erasing for a short period before resuming erasing. The default time is 30 seconds.



vt (DLM) Messages


25

DLM098I: Encryption initialized, <#keys> keys ready

Description: Encryption capability was initialized successfully, with <#keys> keys available for encryption and decryption.


User Action: None.

DLM099I: New mount on already-mounted drive will be allowed

Description: Virtuent has been explicitly configured to honor a mount request for a drive that already has a virtual tape volume mounted.

System Action: If Virtuent receives a mount request on a drive that already has a tape mounted, and the drive had received an Unassign command from the Host while that tape was mounted, Virtuent will unload the tape and honor the new mount request.

User Action: None. This option is not recommended except in specific circumstances. Contact EMC support for more assistance.

DLM100I: Configuration file opened: <filename>

Description: The specified input configuration file was successfully opened.


User Action: None.

DLM101W: Missing or invalid file /etc/bti/ximl, using config file /etc/bti/xmap0

Description: The file /etc/bti/ximl should contain the name of the configuration file that the DLm loads at startup. If /etc/bti/ximl does not exist, the DLm loads the default configuration file /etc/bti/xmap0.

System action: The default configuration file, /etc/bti/xmap0, is used.

User action: The /etc/bti/ximl file should normally point to the desired DLm configuration file. Reconfigure the DLm and Select Configuration for Next Startup to identify which of the four DLm configuration files you want to use. Contact EMC Customer Support if this problem recurs.

vt (DLM) Messages


26

DLM102I: Configuration file is <filename> [(changed!)]

Description: Displays the name of the configuration file currently in use. (changed!) means that the configuration file has changed since the last startup.


User Action: None.

DLM104W: Device <devicename> Warning. no tapelib found for path:dir: <directory>

Description: During logging of volume statistics, the specified directory was not found.

System Action: The volume statistics record will not be recorded.


DLM105E: <command> command is no longer supported

Description: The Virtuent application no longer supports this command.

System Action: None, the command is ignored.

User Action: None.

DLM106I: Guaranteed Replication enabled on <nn> devices, checking for any replicating filesystems...

Description: <nn> virtual tape drives are configured to support the Guaranteed Replication feature.

System Action: Each of the tape library directories will be checked to see if it is a replicating filesystem. A subsequent DLM161I message will be displayed for each tape library found to be on a replicating filesystem.

User Action: None.

DLM107I: Guaranteed Replication delay set to <nn> seconds

D escription: The system is configured to wait for <nn> seconds between tape close and starting a replication-refresh, to make sure that the file is completely written to disk before replication begins.



DLM108I: Guaranteed Replication Timeout set to n seconds

D escription: Indicates that the system is configured to wait n seconds for a GR replication refresh to complete. If replication does not

vt (DLM) Messages


27

complete within this time, an error indication is returned to the host's unload command.



DLM109I: Scratch mounts will [not] ignore full filesystems (UseFullFS=TRUE/FALSE)

Description: By default, filesystems with less than a full tape's worth (based on the current SIZE= value) will be skipped when searching for a scratch tape. This option can be overridden with the UseFullFS TRUE configuration option or SET UseFullFS=TRUE command.

System Action: Unless overridden, full filesystems will be bypassed when a scratch tape mount is requested.

User Action: None.

DLM110I: Channel adapter firmware tracing by DEVICE/PATH

Description: Virtuent has been configured to trace channel adapter activity on a Device or Path basis. When tracing by Device, all of the activity for a given device on all of that device's channel paths are traced in a common trace buffer per device; the advantage is an overall larger trace buffer per device; the disadvantage is that a lot of activity on other channel paths can cause loss of trace entries for events that occurred on another path. When tracing by Path, each channel path per device has an independent trace buffer. The advantage is that activity on one channel path cannot cause loss of trace events on another channel path, but the overall size of the trace buffer (per path per device) is smaller than with a full device trace.


User Action: None.

vt (DLM) Messages


28

DLM111I: Maximum tape block size set to nnn

Description: Virtuent has been configured to support a maximum tape block size different from the default of 256K.

System Action: Virtuent will support host reads and writes up to the specified block size.

User Action: None. Do not change this setting unless directed to do so by EMC support.

DLM112I: Using NEW/FAST scratch search method

Description: The Virtuent application has been explicitly configured to support either the standard documented scratch tape allocation technique (NEW), or an alternative faster method that ignores scratch tapes' last-used dates.

System Action: The Virtuent application will use the technique described. The default method is NEW.

User Action: None.

DLM113E: ScratchSearchMethod=OLD is no longer a supported option

D escription: The value "OLD" was specified for the ScratchSearchMethod parameter. This value is no longer supported.

S ystem A ction: The DLm uses the "NEW" (default) technique.

U ser A ction: Contact EMC Customer Support for more information.

DLM114I: Using DEFAULT/RR method of filesystem allocation

Description: If "RR", the virtual tape application has been explicitly configured to select filesystems in a round robin fashion when allocating a scratch tape, as opposed to the default method which is to pick the filesystem with the most free space.

System Action: The application will use the technique described.

User Action: None.

DLM115E: Error returned from fsync. fd n. <description> file <filename>: error <error message>

D escription: Error returned from fsync.

S ystem A ction: The specified file was not successfully fsynced.

U ser A ction: If you are unable to correct the problem, contact EMC Support for assistance.

DLM116I: Query Space timeout set to <nnn> minutes

vt (DLM) Messages


29

D escription: The system is configured to wait <nnn> minutes for a query space to complete. If query space does not complete within this time, an error indication is displayed on the console.



DLM117I: Query Space <status>

D escription: If the Query Space is invoked while it is running an <already in progress> message will be displayed. If the Query Space exceeds the QSPACETIMOUT a <has exceeded the timeout value> message will be displayed.



DLM118I: Celerra report interval set to <nn> seconds

D escription: The application is configured to check every <nn> seconds for a Celerra status report written by the Celerra control station. The default is 15 seconds.



DLM119E: Error reading configuration file <filename> line nnn: <error message>

Description: An IO error occurred while reading the specified configuration file.


User Action: Use the Virtuent configuration program to reconfigure and save the specified configuration file. If the problem persists, contact EMC support for assistance.

vt (DLM) Messages


30

DLM120I: Disk RECOVERYUPDATE set to <hours>

Description: The Disk Recovery Update time is set to a number of hours in the range of 1 hour to 8760 (365 days)in hours. This is a forced space recovery update based only on time and not space.


User Action: None.

DLM121E: Cannot open configuration file <filename>: <error message>

Description: The specified configuration file was not successfully opened.


User Action: Use the Virtuent configuration program to reconfigure and save the specified configuration file. If the problem persists, contact EMC support for assistance.

DLM122E: No devices defined in configuration file

Description: There were no virtual tape drives configured in the Virtuent configuration file.


User Action: Use the Virtuent configuration program to reconfigure and save the configuration file. If the problem persists, contact EMC support for assistance.

DLM123E: Error in config file, line nn: Unrecognized keyword '<keyword>'

Description: The Virtuent configuration file contained an error.


User Action: Use the Virtuent configuration program to reconfigure and save the configuration file.

DLM124E: Error in config file, line nn: Incorrect number of <keyword> parameters




vt (DLM) Messages


31

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




DLM126E: Maximum number of devices (nnn) exceeded, terminating

Description: Too many devices have been defined in the configuration file.


User Action: Use the configuration program to reconfigure with a valid number of devices.

DLM127I: ERASEPOLICYTTL set to (nnn)(H/D) (config/default)

Description: Displays the erase Policy TTL Time value in hours or days and the config/default status.

System Action: None

User Action: None

DLM129E: Error in config file, line nn: <value> is not a valid parameter




DLM130E: Error in config file, index xx: <value> is not a valid parameter




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




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

vt (DLM) Messages


32




DLM133E: Error in config file, line nnn: Too many <keyword> parameters

Description: The virtual tape configuration file contained an error.


User Action: Use the configuration program to reconfigure and save the configuration file. If the problem persists, contact EMC Customer Support for assistance.

DLM134E: Duplicate INDEX=0xXX in configuration file, line nnn




DLM135E: Error attaching device index xx




DLM136E: Error in config file, line nnn: Duplicate "CELERRA DM=" parameter

Description: The Celerra Data Mover address (DM= parameter) on this CELERRA configuration statement has already been defined on another Celerra definition.


User Action: Correct the configuration file. For more assistance, contact EMC Customer Support.

DLM137W: Invalid TRACE= value 'value'


System Action: Startup continues with the default value of 1.

vt (DLM) Messages


33


DLM138E: Volser Lock Directory <DIR> is not mounted correctly.

Description: An NFS Volser Lock Directory should use the soft instead of the hard mount option.

System Action: Scratch tapes will not be moved from their initial directory and.space may no longer even out.

User Action: Use the configuration program to reconfigure and save the configuration file.

DLM140E: Error in config file, line nnn: <feature> not supported

Description: The virtual tape configuration file contains parameters for a feature that is not licensed for use by this DLM.


User Action: Contact EMC Support for more information on enabling the licensed feature.

DLM144E: Duplicate NAME=value in configuration file, line nn




DLM155I: Device <devicename> data path='<pathname>' [by default][, volser prefix=<volid>]

Description: The specified pathname will be the base tape library directory for this device; virtual tape volumes for this device will be reside in this directory and its immediate subdirectories. '[by default]' signifies that PATH= was not specified for the device and it was set to the standard default value; otherwise, PATH=pathname was explicitly set in the device configuration. If a volser prefix is shown, it signifies that virtual tape volumes that begin with the prefix <volid> will be automatically created as needed by the Virtuent application, if they haven't been pre-initialized.


User Action: None.

DLM156W: Device <devicename> Data path <pathname> is not accessible!

Description: The specified virtual tape library directory cannot be accessed.

vt (DLM) Messages


34

System Action: During system startup, this is a warning message and startup continues. However, no virtual tape volumes that reside in this directory can be mounted on this drive until the specified directory is made accessible. If this error occurs when processing a SET PATH command, the SET PATH command will fail and the current tape library path is unchanged.

User Action: If the configured directory name is correct, make sure that it is mounted and accessible to the user 'vtape'. If the directory name was misconfigured, correct the PATH= parameter in the Virtuent configuration file and restart Virtuent.

DLM157W: Device <devicename> tapelib subdirectory 'xxx' is not accessible!

Description: The specified virtual tape library subdirectory cannot be accessed.

System Action: During system startup, this is a warning message and startup continues. However, no virtual tape volumes that reside in this subdirectory can be mounted on this drive until the specified subdirectory is made accessible. If this error occurs when processing a SET PATH command, the SET PATH command will fail and the current tape library path is unchanged.

User Action: Make sure that the proper filesystem is mounted on the specified subdirectory and it is accessible to the user 'vtape'.

vt (DLM) Messages


35

DLM160I: Device <devicename> enabled for Guaranteed Replication

Description: Indicates that the device has been enabled for Guaranteed Replication.


User Action: None.

DLM161I: Tape library pathname enabled for Replication

Description: Indicates that the tape library directory resides on a filesystem that is enabled for replication.


User Action: None.

DLM162I: nn of maximum mm SSH sessions in use

Description: SSH sessions are used to communicate certain special requests to a VNX filesystem. This system is configured to support a maximum of mm concurrent SSH sessions, of which nn are currently being used.


User Action: None.

DLM163I: nn tasks are waiting to obtain an SSH session

Description: SSH sessions are used to communicate certain special requests to a VNX filesystem. nn tasks are waiting for an available SSH session.


User Action: None.

DLM164I: Device <devicename> enabled for FLR

Description: This device is configured to support File Level Retention.


User Action: None.

DLM165I: Tape library <pathname> enabled for FLR

Description: This tape library directory resides on a filesystem that is enabled for File Level Retention.


User Action: None.

vt (DLM) Messages


36

DLM166E: Unable to read VNX #n report file '/pathname/filename': <reason>

Description: An unexpected error occurred while trying to determine the current state of the specified VNX by reading the specified report file.

System Action: VNX-related features such as Guaranteed Replication and FLR may not function correctly.

User Action: If the error message describes a correctable problem, correct the problem and restart the application. Contact EMC Support if more assistance is needed.

DLM167I: <option> forced to <value> for DLm-1000/2000

Description: The specified configuration option has been forced to a specific value for this controller model.

System Action: The normal default value or configured value is ignored, and the specified value is used.

User Action: None.

DLM168W: Invalid DEBUG= value 'value'

Description: The configuration file or operator SET DEBUG command contained an error.

System Action: If a configuration, startup terminates. If a SET DEBUG command error, the SET command is ignored.

User Action: If a configuration error, reconfigure Virtuent to correct the configuration file. If a SET DEBUG command error, use the HELP command to obtain correct syntax.

DLM169I: Celerra #n report file 'filename' successfully read

Description: The specified report file written by Celerra #n was successfully read. The report is read and the new report data is used whenever the report content has changed from the last time it was read and stored.

System Action: Celerra-related features such as Guaranteed Replication and FLR will be enabled as appropriate for this Celerra.

User Action: None.

DLM170W: Celerra #n report file is over 30 minutes old; check Celerra control station

Description: The specified status report file written by Celerra #n was written more than 30 minutes ago. This signifies that the report-writing script on the Celerra control station is probably not functioning correctly.

vt (DLM) Messages


37

System Action: Celerra-related features such as Guaranteed Replication and/or FLR may not function correctly.


DLM171E: File <filename> line nnn is too long

Description: The configuration file contained an error.


User Action: Reconfigure the specified Virtuent configuration file. If the problem persists, contact EMC support for assistance.

DLM180E: Error [opening|configuring] <name> communication device <details>

Description: An internal error has occurred within either the SNMP or the IPMI subsystem. The IPMI subsystem is responsible for monitoring and reporting system events other than those occurring within the Virtuent application, the channel interface adapter, or the adapter device driver. The SNMP subsystem is responsible for broadcasting all Virtuent event messages that were selected during configuration to the SNMP management station.

System Action: The controller continues to function in a degraded state. Data transfer and storage continue to operate normally, but the SNMP and/or the IPMI subsystem facility is no longer available.

User Action: It may be possible to identify the resource that caused the failure and correct the problem. If the problem persists, contact EMC support for assistance.

DLM181I: SNMP data dump file <NAME> has been created

Description: This message displays the name of the file that was created to save SNMP diagnostic information.


User Action: None.

DLM182W: Unable to save SNMP data dump

Description: The system is unable to create the file to be used to save SNMP diagnostic information.

System Action: The error is logged and operation continues. If the failure persists, the SNMP subsystem will be disabled.

User Action: The user may retry the attempt to save the data by entering the command 'SNMP ACKNOWLEDGE FAILURE'. If the problem persists, contact EMC Support for assistance.

vt (DLM) Messages


38

DLM183W: [SNMP|IPMI] [read|write] failure, <additional information>

Description: A management subsystem operation has failed and event messages may have been lost. This message may be accompanied by additional information associated with the failure. The IPMI subsystem is responsible for monitoring and reporting system events other than those occurring within the Virtuent application, the channel interface adapter, or the adapter device driver. The SNMP subsystem is responsible for broadcasting all controller event messages that were selected during configuration to the SNMP management station.

System Action: The error is logged and operation continues. If the failure persists the subsystem will be disabled.

User Action: If the SNMP subsystem is disabled as a result of this failure, it can be re-enabled from the Virtuent console. If the problem persists, or it cannot be corrected, contact EMC support for assistance.

DLM184E: Error <number> building SNMP OID. Disabling SNMP

Description: SNMP has detected an internal error and SNMP event messages may have been lost.

System Action: SNMP is disabled.

User Action: It may be possible to restart SNMP from the Virtuent console. Contact EMC support for assistance.

DLM185E: Error - SNMP <entity> initialization failed (<details>)

Description: entity is 'thread', 'library', or 'IPMI'. A failure has occurred during initialization of the entity. The IPMI subsystem is responsible for monitoring and reporting system events other than those occurring within the Virtuent application, the channel interface adapter, or the adapter device driver. The SNMP subsystem is responsible for broadcasting all controller event messages that were selected during configuration to the SNMP management station.

System Action: If the failure occurred within the SNMP subsystem, initialization is aborted and the SNMP services will not be available. If the failure occurred within the IPMI subsystem, SNMP will continue to function but no system platform events will be reported.


DLM187E: SNMP message(s) have been lost - <details>

Description: Due to resource limitation an attempt to send one or more SNMP messages failed. Failing messages have been lost.

vt (DLM) Messages


39

System Action: The failure is logged, and the application continues.

User Action: Examine the controller’s log to view the lost messages. Contact EMC support for assistance.

DLM188I: SNMP is [ Not] Operational

Description: This message is used to display the current SNMP operating status.


User Action: None.

DLM189W: SNMP subagent service is unavailable

Description: SNMP is not initialized or it has terminated.


User Action: None.

DLM190I: SNMP terminated

Description: The SNMP subsystem has shut down normally.


User Action: None

vt (DLM) Messages


40

DLM192I: SNMP communication device has closed (flags = 0x<value>). SNMP terminating

Description: The SNMP internal communication mechanism has shut down normally.

System Action: SNMP subsystem terminates.

User Action: None.

DLM193I: IPMI <informational message>

Description: This message describes some event that has occurred within the IPMI subsystem. The IPMI subsystem is responsible for monitoring and reporting system events other than those occurring within the Virtuent application, the channel interface adapter, or the adapter device driver.


User Action: None.

DLM194W: IPMI <warning message>

Description: An internal failure has occurred. The system has recovered, but event messages may have been lost. The IPMI subsystem is responsible for monitoring and reporting system events other than those occurring within the Virtuent application, the channel interface adapter, or the adapter device driver.

System Action: The condition is logged and operation continues. If the condition persists, the IPMI subsystem will be shut down.

User Action: If the problem persists, contact EMC support for assistance.

DLM195E: IPMI <error message>

Description: An error has occurred that has resulted in the loss of the IPMI subsystem service. The IPMI subsystem is responsible for monitoring and reporting system events other than those occurring within the Virtuent application, the channel interface adapter, or the adapter device driver.

System Action: The error is logged and the IPMI subsystem is shut down.

User Action: If the cause of the problem cannot be determined and corrected, contact EMC support for assistance.

DLM196I: (System Event) <informational message>

Description: This is an informational message describing a system platform event that was detected by the IPMI subsystem. The IPMI subsystem is responsible for monitoring and reporting system events other than those occurring within the Virtuent

vt (DLM) Messages


41

application, the channel interface adapter, or the adapter device driver.

System Action: The message is saved to both the system event log as well as the Virtuent event log.

User Action: None.

DLM197W: (System Event) <warning or error message>

Description: This message warns of a system platform event that was detected by the IPMI subsystem. The event should be evaluated to determine if corrective action is needed. The IPMI subsystem is responsible for monitoring and reporting system events other than those occurring within the Virtuent application, the channel interface adapter, or the adapter device driver.

System Action: The message is saved to both the system event log as well as the Virtuent event log.

User Action: The user action will vary with the event. In some cases, such as a chassis intrusion warning following the replacement of a system component, the warning may be ignored. In other cases, the message may indicate a failure or loss of redundancy in a power supply, fan, memory device, or other component and the component should be replaced. Contact EMC support if assistance is needed.

DLM198E: (System Event) <error message>

Description: This message indicates that a system platform event that was detected by the IPMI subsystem that may result in significant functional or security problems. The event should be evaluated to determine if corrective action is needed. The IPMI subsystem is responsible for monitoring and reporting system events other than those occurring within the Virtuent application, the channel interface adapter, or the adapter device drivers.

System Action: The message is saved to both the system event log as well as the Virtuent application event log

User Action: The user action will vary with the event. In some cases, such as a chassis intrusion warning following the replacement of a system component, the warning may be ignored. In other cases, the message may indicate a failure or loss of redundancy in a power supply, fan, memory device, or other component and the component should be replaced. Contact EMC support if assistance is needed.

DLM201I: Validating tape library '<pathname>'...

vt (DLM) Messages


42

Description: During startup, and any other time a tape library path change is requested, Virtuent validates the tape library for various integrity issues.

System Action: If any errors are found, subsequent messages will report the problem(s).

User Action: If any errors are reported, correct the problem(s), then SET PATH= to the desired path.

DLM202I: Device <devicename> <nn> subdirectories under tape library 'pathname'

Description: While validating the specified tape library, Virtuent displays the number of subdirectories found in that tape library.

System Action: If any subdirectories exist, they will also be validated.

User Action: None.

DLM203I: There is no <volser> directory, using <pathname>

Description: When attempting to mount, scratch, unscratch, erase, or delete a volume, Virtuent found that there was no tape library subdirectory matching the first two characters (volser prefix) of the specified volume.

System Action: The system will search only in the base tape library directory for the desired volume.

User Action: None.

vt (DLM) Messages


43

DLM204E: Device <devicename> tapelib directory '<pathname>' is not browsable!

Description: While validating the tape library, the specified path was found to be not browsable, which means the contents could not be listed.

System Action: During system startup, this is a warning message. If this error occurs when processing a SET PATH command, the SET PATH command fails.

User Action: Be sure the tape library is mounted correctly, and that it is owned by user 'vtape' and has the 'x' permission set.

DLM205E: Device <devicename> error while checking tape library '<pathname>' subdirectories: error message

Description: An I/O error occurred while searching the specified tape library for subdirectories.


User Action: The 'error message' portion of this message will describe the error that occurred. Correct the error and retry the SET PATH command to set the tape library path to the desired path.

DLM206W: Device <devicename> bypassing full filesystem <pathname>

Description: A filesystem with less than a full tape's worth of free space (based on the current SIZE= value) will be skipped while searching for a scratch tape. This option can be overridden with the UseFullFS TRUE configuration option or SET UseFullFS=TRUE command.

System Action: The specified filesystem is bypassed during this scratch tape search.

User Action: None.

DLM207W: Device <devicename> bypassing stalled filesystem <pathname> (nnn seconds)

Description: The specified filesystem will be skipped while performing a virtual tape search because it has not responded to I/O requests for the past nnn seconds.

System Action: The specified filesystem is bypassed during this tape search.

User Action: A filesystem should not be this unresponsive. Check your backend filesystem and network connections for problems. For more assistance, contact EMC Support.

DLM210I: Validating tape library '<pathname>'...

vt (DLM) Messages


44

Description: During startup, and any other time a tape library path change is requested, the Virtuent application validates the



DLM211I: Tape Library <VTL-ID> <status>

Description: During startup the Virtuent application determines whether the discovered tape library is supported or not.

System Action: During system startup this is an informational message.

User Action: If a library is not supported the operator could change the VTL back end to disable this library and enable a supported library instead.

DLM212I: VTL <VTL-ID> Volume List <status>

Description: During startup, and at any other time a VTL volume list update is requested, the Virtuent application will display the VTL volume list state.


User Action: None.

DLM213I: SCSI Media Changer Driver version: x.x.x

Description: This message displays the version number of the scsi media changer driver.


User Action: None.

DLM214E: Error creating/mapping/opening ATL Volume List file:<filename>: <error message>

Description: An error occurred while initializing the specified feature. This error can only occur during startup.

System Action: startup terminates or continues without the specified feature. The 'error message' text explains the reason for the failure.

User Action: If you are unable to correct the problem, contact contact EMC support for assistance.

DLM216I: VTL-SN Environment Changed, Please Update Volume List. Update of Volume List could take some time.

vt (DLM) Messages


45

Description: The application volume list no longer matches the VTL environment.


User Action: Invoke the <Update Volume List> command to resynchronize the VTL and application.

DLM217W: VTL-SN volumes in slots x to y exceed maximum and will not be used.

Description: The VTL has defined more slots than the application can support.


User Action: Define the number of slots on the back-end VTL to within our maximum of 20,000 slots.

DLM218I: Scanning tape drive devices...

Description: The SCSI tape drives are being scanned and cataloged.


User Action: None.

DLM219I: No VTL drives available.

Description: The VTL has no drives available. All configured drives are allocated.


User Action: Configure more VTL drives or fewer channel attached drives.

DLM220I: Validating tapelib subdirectory '<name>'...

Description: During startup, and any other time a tape library path change is requested, Virtuent validates the tape library and each of its subdirectories for various integrity issues.



DLM221E: Device <devicename> subdirectory name '<name>' is not a valid volser prefix

Description: During validation of the tape library, the virtual tape application found the specified subdirectory, but the subdirectory name does not conform to a valid volser prefix. Every subdirectory in a tape library must have a two-character name that consists of valid volser characters (A-Z, 0-9). This

vt (DLM) Messages


46

message will only occur if enhanced filesystem support is NOT enabled on this VTE.

System Action: During system startup, this is a warning message. If this error occurs when processing a SET PATH command, the SET PATH command will fail. User Action: Either remove the invalid subdirectory from the tape library base directory, or rename the subdirectory to a valid volser prefix.

DLM222E: Device <devicename> subdirectory name '<name>' is not a valid tape library subdirectory name

Description: During validation of the tape library, the virtual tape application found the specified subdirectory, but the subdirectory name is not a valid enhanced filesystem subdirectory name. Every subdirectory in an enhanced filesystem tape library must have an alpha-numeric name containing only upper-case letters and/or numbers. This message will only occur if enhanced filesystem support is enabled on this VTE.

System Action: During system startup, this is a warning message. If this error occurs when processing a SET PATH command, the SET PATH command will fail.

User Action: Either remove the invalid subdirectory from the tape library base directory, or rename the subdirectory to a valid enhanced filesystem subdirectory name.

vt (DLM) Messages


47

DLM224E: Device <devicename> tapelib subdirectory '<name>' is not browsable!

Description: While validating this tape library subdirectory, the specified path was found to be not browsable, which means the contents could not be listed.


User Action: Be sure the tape library is mounted correctly, and that each subdirectory is owned by user 'vtape' and has the 'x' permission set.

DLM225E: Device <devicename> Error while checking tapelib subdirectory '<name>': error message

Description: An I/O error occurred while searching the contents of the specified tape library subdirectory.


User Action: The 'error message' portion of this message will describe the error that occurred. Correct the error and retry the SET PATH command to set the tape library path to the desired path.

DLM226E: Device <devicename> file '<filename>' does not belong in subdirectory '<name>'

Description: The specified file does not belong in the specified tape library subdirectory because it does not begin with the same first two characters (volser prefix) as the subdirectory name.

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.

vt (DLM) Messages


48

DLM227E: Device <devicename> file '<filename>' in base library belongs in subdirectory '<name>'

Description: The specified file does not belong in the base tape library directory because it begins with the same first two characters (volser prefix) as an existing subdirectory name. The file should reside in that subdirectory.

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.

DLM230W: WARNING:Device <devicename> path <dirname> is on root filesystem!

Description: The directory assigned to hold the virtual tape volumes for this device is mounted on the root filesystem. This usually means that the real tape library filesystem was not mounted, since tapes aren't expected to be stored on the internal system disk(s), but on a high capacity external disk.

System Action: The specified directory continues to be used as the tape library for this drive. This message will display every time a virtual tape volume is successfully mounted and the tape library is still mounted on the root filesystem.

User Action: Make sure that the proper disk filesystem is mounted on the tape library path specified for this drive.

DLM231W: Unable to determine <pathname> device name: <error message>

Description: Virtuent was unable to determine on which disk filesystem the specified directory is mounted.

System Action: Processing continues normally. This message should not normally occur, but it will display every time a virtual volume is successfully mounted while the 'pathname' filesystem device cannot be determined.


vt (DLM) Messages


49

DLM232W: Device <devicename> Unable to determine <pathname> filesystem type: <error message>

Description: An unexpected error occurred while trying to determine what type of filesystem holds the specified tape library.

System Action: Virtuent will continue to run, but some features (such as warnings about the capacity limits of certain filesystems) may not be functional.


DLM233E: Device <devicename> data path <pathname> is not accessible

Description: During mounting of a tape volume, Virtuent was not able to access the specified tape library subdirectory.

System Action: This subdirectory is ignored. If there are other tape library subdirectories, they will be considered in order to attempt to fulfill the mount request.

User Action: If the configured tape library is correct, make sure that all of its subdirectories are mounted and accessible to the user 'vtape'. If the tape library is misconfigured, correct the PATH= parameter in the configuration file and restart the Virtuent application, or use the SET PATH command to temporarily change the tapelib path.

DLM234W: Device <devicename> data path <pathname> is not accessible: not readable

Description: During mounting of a scratch volume, the virtual tape application was not able to access the specified tape library subdirectory.

System Action: This subdirectory is ignored. If there are other tape library subdirectories, they will be considered in order to attempt to fulfill the mount request.

User Action: If the configured tape library is correct, make sure that all of its subdirectories are mounted and accessible to the user 'vtape'. If the tape library is misconfigured, correct the PATH= parameter in the configuration file and restart the virtual tape application, or use the SET PATH command to temporarily change the tapelib path.

DLM235E: Device <devicename> failed deferred tapelib path change to <path>

Description: A tape library change was previously deferred while a volume was mounted on this drive. Now that there is no longer a volume mounted, an attempt to change the tape library to the new path has failed.

vt (DLM) Messages


50

System Action: The tape library path is not changed.

User Action: This message should have been preceded by one or more messages that explained the problem. Refer to these messages, correct the problem(s), and then SET PATH= to the desired path.

DLM236W: Error reading filesystem info for <pathname>: error message

Description: An unexpected error occurred while trying to determine what filesystem holds the specified tape library directory.

System Action: The application will continue to run, but some features that need to know information about the filesystem, such as Guaranteed Replication, will not be functional.

User Action: If the error messages describe a correctable problem, correct the problem and restart the application. Contact EMC Support if more assistance is needed.

DLM237W: Device <devicename> Volume <volser> Error reading Celerra Report: error message

Description: An unexpected error occurred while trying to determine the current state of replication on a Celerra filesystem.

System Action: Guaranteed Replication may not function correctly. If replication reports cannot be properly read in order to guarantee replication before the Guaranteed Replication timeout period expires, an I/O error will be returned to the Host.


DLM238I: Guaranteed Replication method is by <method>

Description: The Guaranteed Replication feature is configured to use the specified method to determine when a given file's replication is complete.

System Action: The specified method will be used to determine when a given file's replication is complete.

User Action: None.

DLM239E: Error opening Celerra report file <pathname>: error message

Description: An unexpected error occurred while trying to determine the current state of replication on a Celerra filesystem.

vt (DLM) Messages


51

System Action: The application will continue to run, but some features that need to know information about the filesystem, such as Guaranteed Replication, will not be functional.


DLM240E: Unable to open tape library path <pathname>

Description: A tape library path couldn’t be opened.

System Action: The search for a particular volser was not completed.

User Action: Check to be sure the path exists.

DLM241E: Unable to read contents of volser lock file <volser>: <error>

Description: While unlocking a volume, the contents (owner) of a volser lock file could not be read.

System Action: The owner of the volser lock could not be determined. The lock remains in place.

User Action: Verify that the volser lock directory is mounted and accessible.

DLM242E: Error deleting lock file <filename>: <error>

Description: While unlocking a volume, an error occurred while trying to remove the lock file for this volser.

System Action: The status of the volser lock is unknown.

User Action: Verify that the volser lock directory is mounted and accessible.

DLM243E: Unable to open lock file <file>: <error>

Description: An error occurred while opening a lock file for reading.

System Action: The file could not be opened.

User Action: Verify that the file exists.

DLM244E: Error reading file <file>: <error>

Description: An error occurred while reading a file.

System Action: The file could not be read.

User Action: Verify the file exists.

DLM245E: Unable to open volser lock directory <directory>

Description: The system was unable to open the volser lock directory.

System Action: The existing locks could not be read.

vt (DLM) Messages


52

User Action: Verify the lock directory is mounted and accessible.

DLM246E: Device <device> error returned from stat command to file <file>: <error>

Description: A stat command to a file failed.

System Action: Information on the file could not be obtained.

User Action: Verify that the path to the file is mounted and accessible.

DLM247E: Device <device> error returned from statfs command to directory <dir>: <error>

Description: An error occurred while getting information about a directory.

System Action: Directory information was not obtained.

User Action: Verify the directory path is online, mounted, and accessible.

DLM248E: Device <device> error getting offset to file <file>: <error>

Description: A seek command to a file returned an error.

System Action: The current file offset to a file could not be obtained.

User Action: Verify that the file path is mounted and accessible.

DLM249E: Device <device> error opening file <file>: <error>

Description: A new file could not be created.

System Action: A new file could not be created. The volume will not be moved.

User Action: Verify that the file path is mounted and accessible.

DLM250E: Device <device> Incomplete read from file <file>: <error>

Description: A read of the file returned 0 bytes when data was available.

System Action: This volser will not be moved.

User Action: None. If the problem persists, contact EMC support.

DLM251E: Problem accessing directory <dirname>: <error>

Description: A problem occurred while accessing the destination directory for the new volume(s).

System Action: No volumes will not be created in this directory.

User Action: None. If the problem persists, contact EMC support.

DLM252E: Wrong storage class. REQ <requested class>, WAS <actual class> for <dirname>

vt (DLM) Messages


53

Description: The INITIALIZE command specified both CLASS= and DIR= parameters, but the specified directory has a class different from the specified CLASS.

System Action: No volumes created.

User Action: Retry the command with a different storage class or directory.

DLM253E: No subdirectory found at <base directory> with storage class <requested storage class>

Description: No tape volume libraries of the requested class were found at the tape library location.

System Action: No volumes created.

User Action: Retry the command with a different storage class.

DLM254I: Invalid storage class file: <directory/filename>

Description: The class file (.CLASSx) found in this directory is invalid.

System Action: Storage class could not be determined.

User Action: Rename or remove the offending file.

vt (DLM) Messages


54

DLM255I: Max display count <count> exceeded for key: <key>

Description: The number of matches for the find volume exceeded the limit.

System Action: No more volumes will be displayed for this command, command processing ended.

User Action: Retry the find command with a key that will have fewer matches.

DLM256I: Volser Lock Directory set to: <directory>

Description: A volser lock directory has been specified for Enhanced Filesystem Architecture operations.


User Action: None.

DLM257I: The Maximum Find Volume Display Count is: <count>

Description: This is the maximum number of volumes displayed by the ‘find volume’ command.

System Action: Not more than <count> volumes will be displayed for the find volume command.

User Action: None.

DLM258E: Invalid storage class parameter: <class>

Description: The IMPORT command CLASS= parameter is invalid.

System Action: The command will not be executed.

User Action: Retry the command with valid parameters.

DLM259E: No storage class <class> directory found.

Description: The IMPORT command CLASS= parameter specified a storage class that cannot be found.

System Action: The command will not be executed.

User Action: Retry the command with valid parameters.

DLM260E: Could not determine the storage class of directory <directory>: <reason>

Description: While processing an IMPORT command, the storage class of the directory could not be determined.

System Action: The operation will not be executed.

User Action: Retry to a different directory.

DLM261E: Device <devicename> Unable to lock volser <volser>: <reason>

vt (DLM) Messages


55

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


User Action: Verify the VOLSERLOCKDIR setting the configuration file.

DLM262E: Device <devicename> Unable to unlock volser <volser>: <reason>

Description: A lock could not be removed from a volser.


User Action: Verify the VOLSERLOCKDIR setting in the configuration file.

DLM263I: Device <devicename> moved <volser path> to <volser path>, <size> bytes

Description: A device moved a newly acquired scratch volume from one filesystem to another filesystem of the same class.

System Action: None

User Action: None

DLM269I: Device <devicename> forcing CRC storing/large headers for Data Domain filesystem

Description: The device is writing to a filesystem that resides on a Data Domain. This type of file system requires large headers to be used.

System Action: None

User Action: None

DLM270I: Device <devicename> Volume <volser> writing AMDD optimized volume

Description: During a write operation, the data on this tape volume has been modified by the AMDD feature to achieve better back-end data duplication. This message will be displayed only once per volume.

System Action: None. When the data is read back, the AMDD modifications will be transparent to the host.

User Action: None.

DLM271I: Device <devicename> Volume <volser> reading AMDD optimized volume

Description: During a read operation, the data on this tape volume was found to have been modified by the AMDD feature to achieve better back-end data duplication. This message will be displayed only once per volume.

System Action: None. When the data is read back, the AMDD modifications will be transparent to the host.

vt (DLM) Messages


56

User Action: None.

DLM272E: Device <devicename> Volume <volser> block #nnnn contains unknown AMDD version id

Description: During a read operation, the data on the specified tape block was flagged as having been modified by the AMDD feature, but data in the AMDD block header isn't recognized as valid.

System Action: An equipment check error status is returned to the Host I/O request.


DLM273W: Device <devicename> Volume <volser> AMDD skipping incompatible <type> block #nnnnn, offset <nnnn>: <reason>

Description: While considering this block for AMDD processing during a write, it was found that although the block was initially thought to be of a <type> recognized by AMDD (DSS, FDR, etc), some inconsistencies in the data prevented AMDD from being able to process the block.

System Action: The block is written without any AMDD modification.

User Action: Rarely, data that normally isn't handled by AMDD can initially be mistaken as a recognized data type. In this case, this message can be ignored. If this message is displayed while the specified <type> of data (i.e. DSS, FDR, etc) is being written, it signifies an incompatibily that should be reported to EMC Support for evaluation.

DLM274I: Device <devicename> Volume <volser> AMDD modified <nnnnn> of <nnnnn> blocks written

Description: AMDD has modified the specified number of blocks in order to improve back-end data-deduplication performance. This message is displayed when an AMDD-modified tape is unloaded.


User Action: None.

DLM275I: Device <devicename> Volume <volser> <AMDD informational message>

Description: This message is used for displaying any number of AMDD informational/statistical messages. These messages are only displayed when AMDD debugging is enabled.


User Action: None.

vt (DLM) Messages


57

DLM276I: Device <devicename> Volume <volser> AMDD read <nnnnn> AMDD-modified blocks

Description: The specified number of blocks read from this tape were found to have been AMDD-modified blocks. This informational message is displayed at unload time whenever any AMDD-modified blocks had been read.


User Action: None.

DLM277E: Device <devicename> Volume <volser> Invalid AMDD identifier, block #nnn

Description: The specified block is flagged as an AMDD-modified data block, but does not contain valid AMDD data.

System Action: An equipment check error status is returned to the Host I/O request.


DLM278I: Device <devicename> Volume <volser> Suppressing IDRC for <type> library

Description: The Host has requested that the data it is writing should be compressed, but the data will be written uncompressed because the type of tape library filesystem it is being written to performs better with uncompressed data. <type> may be either "EMC DLm Data Domain", "DLm-1000", or "DLm-2000".

System Action: The data being written is not compressed. If desired, compression can be forced, regardless of filesystem, by setting the IDRC=FORCE option on a device-by-device basis. This message will display only once per volume as a reminder.

User Action: None.

DLM279W: Device <devicename> Volume <volser> Suppressing AMDD due to encryption

Description: The specified device is configured to use AMDD data optimization, but the device is also configured to encrypt the data.

System Action: The data being written is encrypted but not optimized by AMDD. This message will display only once per volume as a reminder.

User Action: None.

DLM281E: EXPORT/IMPORT FROM file not found. EXPORT/IMPORT command aborted.

vt (DLM) Messages


58

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


User Action: Issue the command with the correct file.

DLM282E: EXPORT TO device already in use. EXPORT command aborted.

Description: The SCSI TO device specified in the EXPORT command is already in use. The EXPORT command stopped with no action.


User Action: Issue the EXPORT command when the device becomes free.

DLM283E: EXPORT/IMPORT FROM/TO file already in use. EXPORT/IMPORT command aborted.

Description: The file specified in the command is currently in use by another device. The command stopped with no action.


User Action: Issue the command again once the current operation that is using the file has completed.

DLM284E: EXPORT/IMPORT FROM/TO device block could not be created. EXPORT/IMPORT command aborted.

Description: An internal error occurred while trying to set up to execute the command. The command stopped with no action.


User Action: Check for previous error message that may indicate cause of problem. Verify that the SCSI device is properly attached to the system. If this problem recurs, contact EMC support for assistance.

DLM285E: EXPORT/IMPORT FROM/TO device is not a valid device type for this command. EXPORT/IMPORT command aborted.

Description: One of the parameters specified is not a valid type for this command. The command stopped with no action.


User Action: Issue the command again with valid parameters.

DLM287E: IMPORT SCSI device is already in use. IMPORT command aborted.

Description: The SCSI device specified in the command is currently in use. The command stopped with no action.

vt (DLM) Messages


59


User Action: Issue the IMPORT command when the device becomes free.

DLM288E: IMPORT TO file already exists. Import will not overwrite an existing file. IMPORT command aborted.

Description: The file specified in the command to write to already exists. Overwriting an existing file is not allowed. The command stopped with no action.


User Action: Issue the command again with a file that does not already exist.

vt (DLM) Messages


60

6

DLM289E: EXPORT/IMPORT FROM/TO file is invalid. Scratch file not permitted. EXPORT/IMPORT command aborted.

Description: Scratch file specified in EXPORT or IMPORT command. Scratch file use is not permitted in these operations.


User Action: None.

DLM290I: <IMPORT/EXPORT> operation starting: FROM=file (dev=EXFRxxxx) TO=device (dev=EXTOxxxx)

Description: Message indicating the IMPORT or EXPORT operation is starting.


User Action: None.

DLM291I: IMPORT/EXPORT operation finished (successfully/with error): FROM=file (dev=EXFRxxxx) TO=device (dev=EXTOxxxx)

Description: Message indicating the operation has completed. If with error, check previous messages for cause of error.


User Action: None.

DLM294I: EXPORT/IMPORT operation performing rewind or rewind/unload: FROM=name (dev=EX/IMFROMxxxx) TO=name (dev=IMTOxxxx)

Description: Message indicating the operation has completed and is now rewinding and / or unloading the tape device per the NORUN flag.


User Action: None.

DLM295E: EXPORT operation reached PEOT. Tape invalid: FROM=name (dev=EXFROMxxxx) TO=name (dev=EXTOxxxx)

Description: The EXPORT command reached the physical end of tape before completing the export operation.

System Action: The incomplete output tape is overwritten by tape marks to invalidate the incomplete transfer.

User Action: Repeat the EXPORT operation with a larger tape.

DLM296E: Error rewinding tape after PEOT: FROM=name (dev=EXFROMxxxx) TO=name (dev=EXTOxxxx)

vt (DLM) Messages


61

Description: The EXPORT command got an error rewinding the tape after it reached the physical end of tape. The tape contains incomplete contents.


User Action: None.

DLM297E: Error writing tapemark after PEOT: FROM=name (dev=EXFROMxxxx) TO=name (dev=EXTOxxxx)

Description: The EXPORT command got an error writing tape marks after a rewind of the tape after it reached the physical end of tape. The tape contains incomplete contents.


User Action: None.

DLM298E: SCSI device not ready, operation aborted: FROM=name (dev=EX/IMFROMxxxx) TO=name (dev=EX/IMTOxxxx)

Description: The SCSI device specified in the command was not in the ready state, and the operation was aborted.


User Action: Ready the SCSI device and issue the command again.

DLM300W: Device <devicename>, connection n, received pkt 0xXXXX (packettype )

Description: The channel interface adapter sent an unexpected message type to the Virtuent application.

System Action: The message from the channel adapter is ignored.


DLM301W: Channel event 'eventtype' (0xXXXX) on device <devicename> <pathinfo> [XXXX XXXX]

Description: The specified exceptional channel event 'eventtype' has been detected. Some common eventtypes which may occur include:

Halt I/O: Host has issued a Halt I/O command, usually as a result of a Host job being cancelled.

System Reset: Host has issued a System Reset, usually as a result of the Host being reset.

Link Error: An error has occurred at the channel link level. This is usually the result of the channel 'dropping light', most often because the channel cable was unplugged or is faulty. This can also be the result of a channel protocol error caused by a

vt (DLM) Messages


62

6

faulty channel, director, or channel adapter hardware or firmware problem.

Selective Reset: The Host has issued a Selective Reset to this device, usually because the device is being varied online or offline, or because a serious I/O error has occurred on this device.

System Action: Processing continues normally; it is presumed that the Host will perform the proper error recovery procedure, to which Virtuent will respond like a real tape drive.

User Action: Unless this is an expected occurrence (such as the Host job is being canceled, the Host is being reset, or a channel or device is being varied off or on), check the Host console logs to determine the cause of the problem. Contact EMC support for assistance if the problem persists.

DLM302I: Device <devicename> <pathinfo> Offline to channel

Description: The specified device has been taken offline on the specified channel interface. This is usually the result of the channel being varied offline or unplugged.

System Action: This device will be unavailable to the Host until it is brought back online.

User Action: None, unless this is an unexpected occurrence, in which case you should investigate the cause at the Host.

DLM303I: Device <devicename> <pathinfo> Online to channel

Description: The specified device has been brought online on the specified channel interface.

System Action: This device is available to the Host on this channel interface.

User Action: None.

DLM304E: Interface #n exceeded automatic restart limit of <count>, NOT restarting

Description: The specified channel interface was reset because of an error, or because of an operator action from outside the Virtuent application. Virtuent will automatically recover from this situation <count> number of times, but this count has been exceeded.

System Action: This channel interface remains offline to the Virtuent devices.

User Action: The situation causing the channel interface adapter to reset should be investigated; contact EMC support for more assistance if necessary. The channel interface can be brought back online for the Virtuent devices by entering, the Virtuent RESET CHANNEL ADAPTER n command.

vt (DLM) Messages


63

DLM305E: Active path(s) on Interface #n, cannot stop adapter

Description: There was an attempt to reset or stop channel interface #n while there were active device(s) online.

System Action: The channel interface remains online without having been stopped or reset.

User Action: Before stopping or resetting a channel interface, all channel paths using that channel adapter must be varied offline from the Host.

DLM306W: Active path on Interface #n, device <devicename>

Description: Channel interface #n is being forcefully stopped or reset while there are active device(s) online. This may cause I/O errors on the Host channel.

System Action: Stopping or resetting of the channel interface continues.

User Action: None.

DLM308I: Rebooting Interface #n, slot=nnnnnn

Description: Channel interface #n is being reset.


User Action: None.

vt (DLM) Messages


64

6

DLM309I: Device <devicename> NOT sending a resetting event unit check

Description: A resetting event is any channel event that resets a channel-attached device's pathgroup ID or assignment, such as a system or restarting of the controller. Normally, after a resetting event has occurred the next command sent by the Host receives a resetting event unit check to notify the Host that the resetting event occurred. The Host should respond appropriately by restoring the device's pathgroup ID and assignment information, and re-issue the unit-checked command. Occasionally, especially with older standalone IPL programs, a Host may not handle a resetting event unit check correctly. In this case, Virtuent can be configured to NOT send resetting event unit checks. This message is displayed when the controller is so configured and would have normally sent a resetting event unit check to a Host command.

System Action: Processing of Host commands continues without the occurrence of a resetting event unit check.

User Action: None. Under normal conditions, the controller should NOT be configured to ignore resetting events. Doing so can cause problems when varying on devices to a Host that does properly handle, and actually expects, resetting event unit checks. Contact EMC support for more information.

DLM310E: <process> received unexpected packet type 0xXXXX (packettype)

Description: An error was sent from the channel adapter. This error can only occur during startup.



DLM311W: Device <devicename> received <info> on path <n> but in chain on path <n>

Description: An unexpected message was sent from the channel adapter.

System Action: The application continues to run, but this device may not continue to function properly.


DLM312E: Device <devicename> Error reading from Interface #n: error message

Description: An error was returned from the channel adapter.



DLM313E: Device <devicename> error sending <info>, error = nn (0xXX)

vt (DLM) Messages


65

Description: An error was returned from the channel adapter.



DLM314E: Device <devicename> <path> unexpected <type> XX CCW while inccw for XX

Description: An unexpected packet sequencing error occurred. This is an internal error.

System Action: A Unit Check is returned to the host.


DLM315W: Device <devicename> selection (ccw XX) on path <n> not assigned

Description: The virtual tape device has been Assigned (reserved) by a specific Host LPAR, but it received an I/O command over a channel path on which it isn't currently assigned.

System Action: The I/O command is ignored.

User Action: Check that the virtual tape devices configuration matches the Host’s configuration.

DLM316E: Device <devicename> received <info> on unexpected connection nn, path=nn

Description: A message was received from the channel adapter from a path that Virtuent does not recognize as a valid path.

System Action: The unexpected message is ignored. The application continues to run, but this device may not continue to function properly.


DLM317E: Device <devicename> received data on unexpected connection nn, path=nn

Description: Data was received from the channel adapter from a path on which Virtuent wasn't currently handling a CCW.

System Action: The unexpected data is ignored. The application continues to run, but this device may not continue to function properly.


DLM318E: Device <devicename> received unexpected data on connection nn, path=nn

Description: Data was received from the channel adapter while Virtuent was not currently handling a CCW that should return data.

vt (DLM) Messages


66

6

System Action: The unexpected data is ignored. The application continues to run, but this device may not continue to function properly.


DLM319E: Device <devicename> <path> invalid data chaining flags (XXX) for XX CCW

Description: An invalid message was received from the channel adapter. This is an internal error.

System Action: The CCW is rejected with a Unit Check.


DLM320I: Firmware trace enabled/disabled interface #n, slot nnnnnn

Description: Firmware tracing was enabled or disabled on the specified channel adapter.

System Action: Channel adapter tracing will remain in this state until Virtuent is restarted.

User Action: None. You can use the Virtuent ENABLE FIRMWARE TRACE or DISABLE FIRMWARE TRACE command to turn tracing on or off.

vt (DLM) Messages


67

DLM326E: Channel Adapter #n NOT reset/stopped/started

Description: A RESET/STOP/START CHANNEL ADAPTER command was entered, but the specified action could not be performed.


User Action: Examine any preceding related messages, if any, for additional error messages that explain why the action could not be performed, correct the problem, and try the command again.

DLM327I: Channel Adapter #n reset/stopped/started

Description: The specified action was taken in response to the Virtuent RESET/STOP/START CHANNEL ADAPTER command.


User Action: None.

DLM331E: Device <devicename> <type of> paths to send Ready Status

Description: The virtual tape drive has become Ready, but there is no online path to send the Ready status message to the Host. Most likely the drive, path, or channel was never configured/varied online on the Host, or has been varied offline.

System Action: The drive is mounted and ready from Virtuent’s point of view, but since a Ready status was not presented the Host will most likely report that the drive is still not ready.

User Action: Check that the specified device is varied online on the Host. You can cause Virtuent to present another 'Ready' signal to the Host by entering an Unready command, followed by a Ready command. If this problem recurs, contact EMC support for assistance.

DLM332E: Device <devicename> [pathNumber] Error sending Async Ready Status, err=nnn

Description: An error has occurred while attempting to send an unsolicited status ('Ready' signal) to the Host.

System Action: Virtuent will attempt to present the status several more times. If the Host never takes the status, the virtual tape volume will remain mounted on the drive, but the Host will most likely report that the drive is still not ready.

User Action: You can cause Virtuent to present another 'Ready' signal to the Host by entering an Unready command, followed by a Ready command. If this problem recurs, contact EMC support for assistance.

DLM333E: Device <devicename> failed to send Ready interrupt to Host

vt (DLM) Messages


68

6

Description: After several retries, Virtuent was unable to present the asynchronous status ('Ready' signal) to the Host.

System Action: The application continues without the status having been presented to the Host. The virtual tape volume will remain mounted on the drive, but the Host will most likely report that the drive is still not ready.

User Action: You can cause Virtuent to present another 'Ready' signal to the Host by entering an Unready command, followed by a Ready command. If this problem recurs, contact EMC support for assistance.

DLM335I: Device <devicename> unassigned while volume <volser> mounted

Description: The host has sent an Unassign command to this device while a tape was mounted on the device.

System Action: The Unassign command is processed normally. The tape remains ready and at its current position.

User Action: This is a valid but unusual condition. Check that the Host is not having some kind of problem with this virtual device. Contact EMC support if you need additional assistance.

DLM338I: New path established: board=n, path=n, link=xx, lpar=xx, cu=xx

Description: The Host has established a new channel path to the Virtuent application.

System Action: This path is available now for channel I/O.

User Action: None.

DLM339I: Path removed: board=n, path=n, link=xx, lpar=xx, cu=xx

Description: The Host has removed the specified channel path to the Virtuent application.

System Action: This path is no longer available for channel I/O.

User Action: None.

DLM340E: Device devicename Incorrect CRC in data received from channel

Description: Virtuent has detected a corruption of data written by the host.

System Action: Virtuent will instruct the Host to retransmit the data up to ten times (displaying “retrying” each of these times). If the error occurs on eleven consecutive writes, Virtuent will return a unit check to the Host, with a sense of Bus Out error (displaying “failed” this time).

vt (DLM) Messages


69

User Action: A data CRC error may indicate failing hardware, cabling, or a weak data link between the Host and Virtuent. Contact your hardware support personnel for assistance.

DLM341E: Device <devicename> Volume <volser> CRC mismatch in data block #nnnnnn at yyyyyyyy, file 'full path file'.

Description: The Virtuent application has detected a corruption of data when comparing the CRC value stored in the awsheader from a file with a newly calculated CRC value after reading the data.

System Action: The Virtuent application will return a unit check to the Host, with sense of Bus Out Error.

User Action: A data CRC error may indicate failing hardware. Contact EMC support for assistance.

DLM342E: Device <devicename> volser <volser> block nnnnn disk read CRC error

Description: After reading data from the tape library storage, the virtual tape application detected that the CRC stored with the data does not match the data just read.

System Action: The virtual tape application will return a unit check to the Host, with sense of Equipment Check.

User Action: A CRC error indicates that corruption data has occurred. Contact EMC Support for assistance.

DLM350E: Unable to get trace flags for interface #n

Description: Virtuent is attempting to obtain the current trace options from channel interface number #n, but has failed to do so.

System Action: The current trace settings will not be available to Virtuent. As a result, some subsequent function may not complete.


DLM351E: Unable to set trace flags for interface #n

Description: Virtuent is attempting to set the trace options in channel interface number 'n', but has failed to do so.

System Action: The current trace settings are not changed.


DLM352I: Firmware tracing stopped on interface #n

Description: Virtuent has turned tracing off for channel interface #n.

System Action: Firmware tracing in channel interface #n remains off until turned back on.

vt (DLM) Messages


70

User Action: None.

DLM353I: Firmware tracing restored on interface #n

Description: Virtuent has restored the trace options for channel interface #n.

System Action: Firmware tracing resumes in channel interface #n.

User Action: None.

DLM354E: Error saving firmware trace

Description: An error has occurred while attempting to save the firmware trace from channel interface #n.

System Action: The trace was not saved.


DLM355W: Device <devicename> Attempting to save firmware trace on interface #n

Description: An error or other unusual event has occurred on channel interface #n, and Virtuent will attempt to save a firmware trace from that interface.

System Action: Virtuent will attempt to stop the firmware trace and save it to disk. After the trace is saved, firmware tracing will resume.


DLM356E: Interface #n exceeded automatic save trace limit of nn, NOT saving trace

Description: An error or other unusual event has occurred on channel interface #n. Virtuent will automatically save a firmware trace 'nn' number of times, but this count has been exceeded for this interface.

System Action: Virtuent continues running without automatically saving the firmware trace.


DLM357E: Interface #n NOT saving trace for unexpected packet

Description: An error or other unusual event has occurred on channel interface #n. Normally, saving of a firmware trace would be triggered by this event, but Virtuent has been configured to not save a trace for this kind of event.

System Action: Virtuent continues running without automatically saving the firmware trace.


DLM358I: Tracing of unexpected packets set ON/OFF

vt (DLM) Messages


71

Description: The automatic saving of a firmware trace when an unexpected packet is received on a channel interface has been turned ON or OFF.

System Action: If ON (the default) a firmware trace is saved when this type of unexpected event occurs. If set OFF, no firmware trace will be automatically saved.

User Action: Contact EMC support for assistance with this option.

DLM366E: Device <devicename> <function> error, Interface #n, error=0xXX (nnn)

Description: An error involving channel interface adapter #n has occurred.

System Action: This channel interface may not be available to this Virtuent device until the adapter is reset.


vt (DLM) Messages


72

DLM370E: Unable to open connection to slot 0xXXXXXX: err=nn (0xXX)

Description: An error has occurred while opening a channel adapter driver during Virtuent application startup.



DLM379E: <function>: <error message>

Description: An internal error has occurred in the Virtuent application during shutdown.

System Action: Shutdown continues.


DLM380W: Severity n Alert Interface #n (XXX:YYY) <type:subtype (additional parms)>

Description: Virtuent has received an alert message from the channel adapter driver, for channel adapter 'n'. XXX:YYY are the alert type and subtype, which are also translated in <type:subtype>.

System Action: Depending on the alert severity and type, Virtuent may continue to function normally, or it may require service or other attention.


DLM381I: Channel Interface #n <message>

Description: Virtuent has received an informational message from channel adapter 'n'.


User Action: None.

DLM390E: Invalid encryption key file (rc=n)

Description: The encryption key file has been corrupted.

System Action: Encryption or decryption will not be available on this controller until the encryption key file is restored or reconfigured.

User Action: Restore the encryption key file from a backup copy, or reconfigure the key(s) via the encryption key configuration program. Contact EMC support for more assistance.

DLM391I: ENCRYPTKEY set to [KEYn|NONE] for device <devicename>

Description: Key #n will be used for encryption on device <devicename>, or if 'NONE' is specified, no encryption will be performed on device <devicename>

vt (DLM) Messages


73

System Action: The specified encryption key (or none, for 'NONE') will be used for all data written to the specified device.

User Action: None.

DLM392E: Encryption is not available

Description: Encryption is not set up, or the encryption initialization failed.

System Action: Encryption and decryption will not be available for any devices for which encryption was requested.

User Action: Verify that the encryption key file is installed, or reconfigure the key(s) via the encryption key configuration program.

DLM393E: No encryption key available for reading encrypted block on <devicename>

Description: Encryption was not set up at all, or the encryption initialization failed, and then an encrypted block was requested to be read.

System Action: The requested block will not be read. A unit check is returned to the host.

User Action: The user should check the encryption configuration.

DLM395E: Device <devicename>, no matching decryption key, block <block#>

Description: No key currently installed on Virtuent was able to decrypt this encrypted block.

System Action: If this error occurs during an I/O initiated by the host, an I/O error (equipment check) will be returned to the host. During an Import or Export operation this is a warning rather than an error; the data will be copied it is original encrypted format to a new location.

User Action: Check that Virtuent is configured with the proper encryption key(s).

DLM397E: Device <devicename> is not a supported tape type for encryption

Description: Encryption is not supported on this device type.

System Action: The encryption option is not changed for this device.

User Action: The user should choose another device, or reconfigure the given device.

DLM398E: Device <devicename> must be unloaded before changing encryption

Description: Encryption cannot be changed when a device has a tape volume mounted.

System Action: The encryption option is not changed for this device.

vt (DLM) Messages


74

User Action: Wait until the tape is unloaded before setting the encryption key for a device.

DLM399E: Syntax error. Format is 'DRIVE-', not 'DRIVE='.

Description: The correct format for specifying this device is 'DRIVE-'.

System Action: The command was invalid and not performed.

User Action: Specify the command again with valid syntax.

DLM400E: Device <devicename> Data path <pathname> is not accessible

Description: The specified virtual tape library directory cannot be accessed at the time of a tape mount.

System Action: The mount is ignored and the drive remains Not Ready without mounting the virtual tape volume. Virtual tape volumes cannot be mounted on this device until the specified directory is made accessible to the application.

User Action: If the configured directory name is correct, make sure that it is mounted and accessible. If the directory name was misconfigured, correct the Virtuent configuration file PATH= parameter and restart the Virtuent application. (The path can be temporarily corrected with the SET PATH= command.)

vt (DLM) Messages


75

DLM401E: Device <devicename> error opening <filename>, error=nnn; <error message>

Description: The virtual tape file could not be opened.

System Action: The mount is ignored and the drive remains not ready without mounting the virtual tape volume.

User Action: Examine any preceding related messages and the 'error message' portion of this message for a description of the problem and correct the problem. If the problem recurs, contact EMC support for assistance.

DLM402E: Device <devicename> cannot LOAD PROTECTED, volume <volser> does not exist

Description: The specified virtual tape volume specified in the operator command 'LOAD ... PROTECTED' does not currently exist. Only existing volumes can be mounted as protected (read-only) volumes.

System Action: The mount is ignored and the drive remains not ready without mounting the virtual tape volume.

User Action: Specify an existing volume in the 'LOAD ... PROTECTED' command.

DLM403E: Device <devicename> volume <volser> (filename) invalid AWS block header at nnnnn (n) xxxxxxxx xxxx, curblkl=xxxx, prvblkl=xxxx , flags1=xx, flags2=xx

Description: An invalid AWS block header was encountered at offset 'nnnnn' in the specified volume. (n) is one of the following error codes: (1) error reading block header; (2) prvblkl not zero in first block header; (3) unknown bit in flags1; (4) unknown bit in flags2; (5) tapemark record with data length; (6) non-tapemark record with zero data length; (7) prvblkl contains zero past first block header; (8) curblkl or prvblkl contains an invalid length value; (10-12) unsupported segmented aws block The second line of the message shows the block header contents.

System Action: The operation reading the volume will fail.

User Action: Delete and re-create the volume that has the invalid format. If this problem recurs, contact EMC support for assistance.

vt (DLM) Messages


76

DLM404E: Device <devicename> Error deleting unused scratch volume <volser>: error message

Description: The specified volume was created in response to a scratch tape mount request. Because it was unloaded without ever having been written to, Virtuent tried to delete it. An I/O error occurred during the attempt to delete.

System Action: The volume may or may not have been deleted from the tape library.

User Action: The 'error message' portion of this message describes the error that occurred. Correct the error.

DLM405I: Device <devicename> Display: 'message1' 'message2' [(blink)]

Description: The Host has sent these message(s) to be displayed on the virtual tape drive's operator display unit.

System Action: If the message is a Mount message, and the virtual tape drive is currently unloaded, and the volume serial number falls within the range managed by Virtuent, then the specified volume will be mounted.

User Action: None.

DLM406I: Device <devicename> CCW:XX @block id nnnnn; rejected due to supervisor inhibit

Description: The Host sent a CCW that can only be executed while in supervisor state but a prior Mode Set CCW had disabled this state.

System Action: The CCW is not executed, and a unit check status with command reject sense is sent to the Host.

User Action: Investigate why the Host application is attempting to illegally execute a supervisor state CCW.

DLM407E: Device <devicename> Rejecting ACLON request - invalid synonym

Description: The mainframe request for ACLON is rejected because the synonym that was passed is not in the synonym list.

System Action: The command is rejected.

User Action: None.

vt (DLM) Messages


77

DLM408I: Device <devicename> ACL turned <ON/OFF> <synonym> <reason>

Description: ACL turned <state>

System Action: The ACLON or ACLOFF request was granted. If the request was ON and a synonym was passed from the mainframe it will become the default synonym If the request was OFF and there is a reason, it will be displayed.

User Action: None.

DLM409I: Command received: 'command'

Description: The specified operator console command was received.

System Action: The specified command is processed.

User Action: None.

DLM410E: Device <devicename> error nnn initializing Volume <volser>: <error message>

Description: An error occurred while creating the specified virtual tape volume.

System Action: The volume is not mounted.

User Action: Examine any preceding related messages and the 'error message' portion of this message for a description of the problem and correct the problem. If the problem recurs, contact EMC support for assistance.

DLM411E: Device <devicename> AWS block #nnn too large (xxxxxx) to handle (max=yyyyyy)

Description: Virtuent has encountered a tape block in the virtual tape volume that is larger than the maximum tape blocksize ('yyyyyy') it is capable of presenting to the Host. This block in the virtual tape file is 'xxxxxx' bytes and is not compressed in the file.

System Action: An I/O error is returned to the Host.


vt (DLM) Messages


78

DLM412E: Device <devicename> AWS block #nnn too large to handle (max=yyyyyy)

Description: Virtuent has encountered a tape block in the virtual tape volume that is larger than the maximum tape blocksize ('yyyyyy') it is capable of presenting to the Host. This block in the virtual tape file is compressed and the exact un-compressed block length, while larger than 'yyyyyy', is unknown.



DLM413E: Device <devicename> Unexpected EOF in block header at nnnnn, file <filename>

Description: An error occurred while accessing the specified virtual tape volume. 'nnnnn' is the file offset where the error occurred.

System Action: Virtuent returns an error status to the current Host I/O request.

User Action: Examine any preceding related messages, if any, for additional error information, and correct the problem. If the problem recurs, contact EMC support for assistance.

DLM414W: Device <devicename> tape full writing <data/TM> at PEOT, file <filename>

Description: While writing to a physical tape drive Virtuent received a response that the physical tape cartridge is full.

System Action: The write operation fails with a unit check.

User Action: Investigate why the host application wrote past the logical end of the tape (LEOT).

DLM415E: Device <devicename> Unexpected EOF in data block at nnnnn, file <filename>

Description: An error occurred while accessing the specified virtual tape volume. 'nnnnn' is the file offset where the error occurred.



DLM416E: Device devicename not responding.

Description: The physical tape device is no longer responding to Virtuent.

System Action: Virtuent will set the tape device to NA (Not Accessible).

User Action: Virtuent must be restarted after repairing the problem with the specified tape drive.

vt (DLM) Messages


79

DLM417E: Device <devicename> I/O error: <function description>; error=nnn; <error message>

Description: An error occurred while reading a virtual tape file.



DLM418W: Device <devicename> Hardware decompression not available, using software only

Description: A hardware-compressed block has been read from the virtual tape volume, but a hardware compression card is not available on this controller to decompress the data.

System Action: The data is decompressed with software. This message will display only once per volume as a reminder.

User Action: For best performance, data compressed with a hardware compression adapter should be decompressed with a compression adapter as well.

DLM419E: Device <devicename> data read [backwards] returned error

Description: An error occurred while reading a virtual tape file.

System Action: The read command is unsuccessful and an error indication (unit check) is returned to the Host. This message is preceded by one or more messages that explain the I/O error.


DLM420W: Device <devicename> write attempt to protected volume

Description: The volume on the specified device is mounted in read-only mode, but the Host has attempted to perform a write operation to the volume.

System Action: The Host's write command is rejected (with unit check status, command reject sense).

User Action: Correct the condition that caused the Host to attempt to write to a read-only volume.

DLM421I: Device <devicename> signaled end of volume to Host on <command>

Description: While writing to a virtual tape volume, logical end of volume (CSW status Control Unit End plus Unit Exception) was signaled to the Host because the capacity of the virtual volume is being

vt (DLM) Messages


80

approached. 'command' could be Write, Write Tapemark, or Erase Gap.

System Action: The write command was successful. The logical end of volume condition remains true and will be signaled for all subsequent writes as long as the virtual tape volume remains positioned past the logical end of volume point.

User Action: The Host is expected to close the virtual tape volume and open a new volume.

DLM422W: Device <devicename> <command> at loadpoint

Description: The Host has read or spaced backwards from the virtual tape volume's loadpoint.

System Action: Virtuent returns an error status (Read Backwards at Loadpoint) to the Host I/O request.

User Action: This is most likely a Host application error. Correct the application causing the error.

DLM423W: Device <devicename> <command> past <place>

Description: The Host read or positioned past the end of data on a virtual tape volume or a physical tape volume. This message will also be displayed at the end of an Import or Export command, because these commands will read and copy all data until they reach the end of the input tape volume. This is normal operation of the Import and Export commands and does not signify an error.

System Action: If this occurs as a result of a Host I/O request, an error status (Data Check, Tape Void) is returned to the Host I/O request. For an Import or Export operation, this message is normal and does not signify an error.

User Action: If caused by a Host operation, correct the application causing the error. For an Import or Export operation, this message is normal and does not signify an error.

DLM424I: Device <devicename> Volume <volser> rewound

Description: The operator REWIND command completed successfully.

System Action: The virtual tape volume is now at loadpoint.

User Action: None.

DLM425E: Device <devicename> Data block exceeds maximum of yyyyyy bytes

Description: The Host wrote a block larger than the maximum blocksize supported by Virtuent.

vt (DLM) Messages


81

System Action: The block is not written to the virtual tape file, and an I/O MBE error is returned to the Host's write command.

User Action: Change the Host application and/or JCL to write data blocks within Virtuent’s capability ('yyyyyy' bytes or less).

DLM426E: Device <devicename> write attempt required expanded headers

Description: The Host attempted to write data with options set (such as the ‘store CRC’ option) which requires expanded headers, but the tape consists of blocks with regular headers. Tape header types cannot be intermixed on the same tape.

System Action: An error status (equipment check) is returned to the host I/O request.

User Action: Clear the option(s) that require expanded headers. Contact EMC support for assistance.

vt (DLM) Messages


82

DLM427W: Device <devicename> write [TM] attempt past end of tape

Description: The Host attempted to write data or a tapemark past the absolute end of tape capacity.

System Action: Virtuent returns an error status (Equipment Check, Physical End of Tape) to the Host I/O request.

User Action: This is most likely a Host application error, since logical end of tape signal would have been returned for many writes preceding the failing one. Correct the application causing the error.

DLM428I: Device <devicename> possibly lengthy operation <command> begun

Description: Virtuent is executing the specified I/O command from the Host. Virtuent has determined that this command may take a considerable period of time (more than a few seconds) and issues this message for informational purposes.

System Action: The command continues normally. If the command takes a very long time, it is possible that the Host may cancel the operation because it thinks a missing interrupt situation has occurred.

User Action: If the Host cancels a job because it thinks a missing interrupt has occurred while a long positioning command is taking place, consider increasing the Host's missing interrupt timer for Virtuent devices.

DLM429E: Device <devicename> <function description> while device not ready

Description: The requested operation requires a tape to be loaded in the physical tape drive.

System Action: The Virtuent application returns an error status to the current Host I/O request.

User Action: Load the tape drive.

DLM430I: Device <devicename> volume <volser> accommodated old-style AWS header at offset nnnnnn

Description: Earlier Virtuent releases could write incorrect metadata in a virtual tape block under certain specific rare conditions. Subsequent backwards traversal over such a block would result in an I/O error (Invalid block header). Later Virtuent releases, including this one, automatically recover from this metadata error without returning an I/O error to the host. This message is displayed strictly for informational purposes.

System Action: The virtual tape operation completes successfully. There is no data loss or error indication returned to the host. The invalid metadata in this virtual tape volume is NOT corrected by this

vt (DLM) Messages


83

action, so this message may be seen in the future as long as this data exists on this volume.

User Action: None.

DLM431I: Device <devicename> fast operation <command> resumed

Description: The virtual tape application is executing a Host I/O command that it had previously determined might take a considerable period of time (more than a few seconds) to complete (see message DLM428I). During the possibly lengthy operation, a suitable index entry has been encountered to complete the operation quickly.

System Action: The command continues normally.

User Action: None.

DLM432I: Device <devicename> possibly lengthy operation (<command> from <blockid>) complete (at <blockid>)

Description: The virtual tape application has completed executing a Host I/O command that it had previously determined might take a considerable period of time.

System Action: The command completed normally, although possibly slowly.

User Action: None.

DLM433I: Device <devicename> is not writing expanded headers.

Description: The device is set to write expanded headers, but is currently not honoring the value.


User Action: None.

vt (DLM) Messages


84

DLM434W: WARNING:Path <pathname> disk usage at nn%

Description: The disk usage for the specified tape library has exceeded the current WARNING value.

System Action: Virtuent will continue to warn at every percentage change as long as the usage exceeds the WARNING value.

User Action: Consider scratching and erasing unneeded virtual tape volumes to free some disk space.

DLM436I: Attempting to recover space from scratch volumes in <pathname>

Description: The disk usage for the specified tape library directory has exceeded the current RECOVER value.

System Action: Virtuent will erase data from previously scratched virtual tape volumes until the disk usage falls by RECOVERAMT percent.

User Action: Consider scratching and erasing unneeded virtual tape volumes to free some disk space.

DLM437I: Finished space recovery, nn bytes recovered from scratch volumes in <pathname>

Description: Virtuent has finished attempting to recover space for the specified tape library directory, because either (1) the disk space has been reduced by RECOVERAMT, or (2) it has found no more previously scratched volumes to erase. ‘nn’ bytes is the number of bytes erased from scratch volumes and made available for reuse.


User Action: None.

DLM438I: Finished space recovery, nn bytes recovered from nn scratch volumes in <pathname>

Description: The DLm application has recovered the specified amount of space from scratch tapes that have surpassed the erase policy retention time.


User Action: None.

vt (DLM) Messages


85

DLM439I: Device <devicename> Volume <volser> unloaded without I/O

Description: The specified virtual tape volume was unloaded. During the time that the volume was mounted, the Host did not perform any reads from or writes to this volume.

System Action: The specified drive enters the Not Ready state and is available for another job. If the tape was a scratch tape when it was mounted, it will be returned to the scratch state.

User Action: None.

DLM440I: Device <devicename> Volume <volser> mounted

Description: The specified virtual tape volume has been mounted; the device will now present a ready interrupt to the Host.


User Action: None.

DLM441I: Device <devicename> initializing new [flat] volume <volser> [(labeled)|(unlabeled)]

Description: A mount of a non-existent volume has been requested.

System Action: The new virtual tape volume is created and initialized.

User Action: None.

DLM442E: Device <devicename> unable to allocate an SL/AL/NL scratch volume: <error message>

Description: Loading of a scratch volume was requested, but a scratch volume with the requested label type could not be found. The 'error message' portion of this message explains the reason.

System Action: The requested volume is not loaded and the drive remains Not Ready.

User Action: Correct the problem preventing the scratch volume allocation and try to re-load a scratch tape. If no scratch volumes are available, consider scratching some old, unneeded volumes or INITIALIZE some more scratch volumes.

vt (DLM) Messages


86

DLM443E: Device <devicename> unable to create new scratch volume <volser>

Description: Loading of a new scratch volume was requested, but the new virtual tape volume could not be created.

System Action: The requested volume is not loaded and the drive remains Not Ready.

User Action: One or more previous message(s) should explain the reason for the problem. Correct the problem preventing the scratch volume allocation, and try to re-load a scratch tape. For instance, enter the 'Query Space' command to determine if any free space exists on the tape library disk; if no space is available, delete some unneeded volumes to free some disk space. Make sure that a valid, writable directory is specified in the configuration file for this device, and that the directory is currently mounted and accessible. If all possible scratch tapes are already in use, scratch some existing volumes for re-use.

DLM444I: Device <devicename> new scratch volume <volser> created

Description: Loading of a scratch volume was requested, and a new virtual tape volume was created to accommodate the request.

System Action: The specified volume was created, initialized, and loaded on the specified drive.

User Action: None.

DLM445I: Device <devicename> cannot initialize protected new volume <volser>

Description: Virtuent has created the new volume 'volser', but is not able to initialize it because it is read-only. This is only possible when a manual LOAD command with the PROTECTED option is entered for a new (non-existing) volume.

System Action: The volume is created and mounted, but it will appear to the Host as an empty, un-initialized (and read-only) tape.

User Action: Don't do this.

vt (DLM) Messages


87

DLM446E: Device <devicename> cannot create volume <volser>, path <pathname> is read-only

Description: The specified volume does not exist and cannot be opened for writing because the virtual tape library directory 'pathname' is write protected.

System Action: The volume is not created, the mount request is ignored, and the device remains not ready.

User Action: In order to write new volumes, make sure that the virtual tape library is correctly mounted and is write-enabled for user 'vtape'.

DLM447W: Device <devicename> invalid volid 'volser', mount request ignored

Description: The Host requested the mounting of a volume serial number that is not a valid IBM volume serial number.

System Action: The mount request is ignored and the device remains not ready.

User Action: Correct the Host JCL to request a valid IBM volume serial number. An IBM standard volume serial number consists of the upper-case letters A-Z, numbers 0-9, and the hyphen.

DLM448W: Device <devicename> volume <volser> already mounted, new mount request ignored

Description: The Host requested the mounting of a volume, but the specified drive already has a virtual tape volume mounted. The currently mounted tape is NOT at loadpoint.

System Action: The mount request is ignored. The volume already mounted on the drive remains mounted.

User Action: Correct the Host JCL that caused a mount request to be sent to a drive that already has a volume mounted. If the Host is finished with the volume that is current mounted on the drive, you can manually unload that volume and then manually mount the new volume.

DLM449I: Device <devicename> Label request changed from ' ' to default 'X'

Description: The current mount request did not specify a desired label type, so it was set to the default type configured on Virtuent for this virtual tape device. The only value which you'll see for 'X' is 'A' for ANSI labels, because this message does not display if the default label type is 'S' for IBM standard labels.

System Action: The mount process continues, using the default label type configured for this device.

vt (DLM) Messages


88

User Action: None, unless the default label type is incorrect, in which case the Virtuent configuration default should be changed or an explicit label type should be requested in the JCL.

DLM450W: Volume <volser> file is busy on device devicename1, mount on devicename2 is ignored

Description: The mounting of a virtual tape volume has been requested, but that volume is currently mounted on another virtual tape drive. A volume can be mounted on only one drive at a time.

System Action: The mount request is ignored.

User Action: Correct the Host operational issue that resulted in the duplicate request for the same volume. Restart the second job when the virtual tape volume becomes available.

DLM451E: Volume <volser> file is open elsewhere, mount on <devicename> ignored

Description: Mounting of the specified virtual tape volume has been requested, but the volume is currently open by another program or system.

System Action: The mount will be retried several times over several seconds. If the volume does not become free during this time, the mount request is ignored.

User Action: Correct the Host operational issue that resulted in the duplicate request for the same volume by two programs at the same time. Restart the second job when the virtual tape volume becomes available.

DLM452W: Device <devicename> is quiesced, mount ignored

Description: Mounting of the specified virtual tape volume has been requested, but the specified drive is in the 'quiesced' state, meaning it will not accept any tape mounts until it is 'unquiesced' (or until Virtuent is restarted).


User Action: UNQUIESCE the drive, or use a different drive.

DLM453W: Device <devicename> volume <volser> already mounted, new mount request honored

Description: The Host requested the mounting of a volume, and the specified drive already has a virtual tape volume mounted. The currently mounted tape is at loadpoint.

System Action: The mount request is honored. The volume already mounted on the drive is unloaded and the new mount request is processed.

vt (DLM) Messages


89

User Action: Correct the Host JCL that caused a mount request to be sent to a drive that already has a volume mounted.

DLM454E: Device <devicename> volume <volser> not found

Description: Virtuent was requested to load a virtual tape volume that does not exist in the library.

System Action: The drive remains unloaded and Not Ready.

User Action: Verify that the correct volume is being requested. Also check that the tape library directory(s) are properly mounted and are accessible to Virtuent. If the requested volser is for a scratch tape, make sure that there are scratch volumes, initialized with the correct label type, available.

DLM455E: Error locking volume <volser> (filename); <error message>

Description: An error occurred while trying to mount the specified virtual tape volume.


User Action: Consult any preceding related messages and the 'error message' portion of this message for a description of the problem and correct the problem. If the problem recurs, contact EMC support for assistance.

DLM456W: Device devicename volume volser already mounted, new mount request honored

Description: The Host requested the mounting of a volume, and the specified drive already has a virtual tape volume mounted. The currently mounted tape is not at loadpoint, but 1) Virtuent is explicitly configured to honor a new mount request while a tape is already mounted; and 2) the drive had received an Unassign command from the Host while the currently mounted tape was mounted.

System Action: The mount request is honored. The volume already mounted on the drive is unloaded and the new mount request is processed.

User Action: Consider correcting the Host JCL or Host operating system that allows a mount request to be sent to a drive that already has a volume mounted. Contact EMC support for additional assistance.

DLM457E: Device devicename volume volser already mounted, new mount request ignored

Description: The Host requested the mounting of a volume, but the specified drive already has a virtual tape volume mounted, and the currently mounted tape is NOT at loadpoint. Although

vt (DLM) Messages


90

Virtuent is explicitly configured to honor a new mount request while a tape is already mounted, the drive had not received an Unassign command from the Host while the currently mounted tape was mounted.

System Action: The mount request is ignored. The volume already mounted on the drive remains mounted.

User Action: Consider correcting the Host JCL or Host operating system that allows a mount request to be sent to a drive that already has a volume mounted. Contact EMC support for additional assistance.

DLM458W: Device <devicename> volume <volser> already mounted, new mount request deferred

Description: The Fujitsu Host requested the mounting of a volume, and the specified drive already has a virtual tape volume mounted.

System Action: The mount request will be honored after the Host unloads the volume currently mounted on the drive.

User Action: If possible, correct the Host JCL that caused a mount request to be sent to a drive that already has a volume mounted.

vt (DLM) Messages


91

DLM459W: Device <devicename> volume <volser> has a corrupted IBM/ANSI label set

Description: During opening of an existing virtual tape volume, Virtuent has determined that the volume contains a valid VOL1 label but the rest of the header label set is missing, incomplete, invalid, or corrupted in some way.

System Action: This is a warning message only. The mount completes successfully and is available for normal use by the Host.

User Action: The Host will most likely complain about the invalid labels; take the appropriate action required by the Host. If the Host refuses to use the corrupted volume as is, perform a re-initialization of the virtual tape volume using the standard Host initialization procedures. Try to determine the reason the Host previously wrote invalid labels to this tape volume. This condition is most often caused by an error on the Host during volume initialization or at some other time when the Host is writing the volume labels. In particular, this problem has been seen when a Host job is cancelled while it is opening an output tape.

DLM460I: Device <devicename> volume <volser> file renamed to <filename>

Description: The Host has written a HDR1 label in a flat file.

System Action: The virtual volume's disk file was successfully renamed to the new filename as shown.

User Action: None.

DLM461I: Device <devicename> performing deferred mount request

Description: The Fujitsu Host requested the mounting of a volume while the specified drive already had a virtual tape volume mounted. The drive is now unloaded and the mount request will be re-evaluated.

System Action: The mount request will be attempted at this time.

User Action: If possible, correct the Host JCL that caused a mount request to be sent to a drive that already had a volume mounted.

vt (DLM) Messages


92

DLM462W: Mount error renaming volume <volser> <pathname> to <pathname>: <error message>; retrying…

Description: The host has asked for a previously scratched volume by specific volser. Virtuent was unable to rename the scratch volume (~VOLSER) to an active volume (VOLSER),

System Action: The rename will be retried several time over several seconds. If the rename does not succeed during this time the mount request will be ignored.

User Action: Refer to any earlier messages and the ‘error message’ portion of this message to determine the cause of the failure.

DLM463W: Volume <volser> file is open elsewhere, retrying...

Description: Mounting of the specified virtual tape volume has been requested, but the volume is currently open by another program or system.

System Action: The mount will be retried several times over several seconds. If the volume does not become free during this time, the mount request will be ignored.

User Action: Correct the Host operational issue that resulted in the duplicate request for the same volume by two programs at the same time. Restart the second job when the virtual tape volume becomes available.

DLM464E: Device <devicename> volser volser prefix differs from existing volser volser

Description: The Host is attempting to write a VOL1 label with a different volume serial number onto the virtual tape volume, but the new VOLSER does not start with the same 2-character VOLSER prefix as the existing volume serial number.

System Action: Virtuent rejects the Host's write, returning a Unit Check status and Command Reject sense.

User Action: You can only write over an existing VOLSER with a new volume serial number of the same 2-character prefix. Correct the JCL or operator procedure that attempted to rename the volume.

vt (DLM) Messages


93

DLM465E: Device <devicename> invalid volser 'volser' in VOL1 label

Description: The Host is attempting to write a new VOL1 label to the virtual tape volume, but the volume serial number in the VOL1 label is invalid.


User Action: Correct the Host job that is attempting to write the invalid volume serial number to Virtuent.

DLM466E: Device <devicename> volser 'volser' from VOL1 already exists [as scratch]

Description: The Host is attempting to write a VOL1 label with a different volume serial number onto the virtual tape volume, but the new VOLSER is the same as a volume that already exists in the tape library.


User Action: Correct the Host job that is attempting to write the duplicate volume serial number to Virtuent, or delete the existing volume before rerunning the job.

DLM467E: Device <devicename> error renaming volume <volser1> (filename) to <volser2> (filename); <error message>

Description: The Host is attempting to write a VOL1 label with a different volume serial number onto the virtual tape volume, but Virtuent is failing in its attempt to rename the mounted volume to the new volume name.


User Action: Refer to any earlier messages and the 'error message' portion of this message to determine the cause of the failure. If the problem cannot be corrected, contact EMC support for assistance.

DLM468I: Device <devicename> overwrote VOL1 with [data|tapemark] on volume <volser>

Description: The volume mounted on this device was previously a labeled volume, but the Host has written either data or a tapemark at loadpoint, erasing the VOL1 label. The virtual tape is now an unlabeled volume.


User Action: None.

vt (DLM) Messages


94

DLM469I: Device <devicename> volume <volser1> renamed to <volser2> (filename)

Description: The Host has written a VOL1 label with a different volume serial number onto the virtual tape volume.

System Action: The virtual volume file was successfully renamed to the new volume serial number.

User Action: None.

DLM470E: MOUNT volume 'volser' failed

Description: Mounting of the specified virtual tape volume was unsuccessful.

System Action: The mount request is ignored and the drive remains Not Ready.

User Action: This message will be preceded by one or more messages that explain the reason for the mount failure. Correct the error indicated in the preceding message(s).

DLM471E: Device address xxxx on GROUP n doesn't exist

Description: Mounting of a virtual tape volume on OSADDR 'xxxx' was requested by the EMC VSE mount program, but the specified device does not exist in the specified GROUP.

System Action: The mount request is ignored and the drive remains Not Ready. A return code of 0x82 is returned to the Host program.

User Action: Reconfigure the EMC VSE mount program and/or Virtuent to use the proper device address(es).

DLM472I: Volume <volser1> is currently on <devicename>, cannot mount <volser2>

Description: Mounting of volume 'volser2' on the specified drive was requested by the EMC VSE mount program, but the specified device already has the virtual tape volume 'volser1' mounted.


User Action: Correct the operational issues that resulted in the attempt to mount on a busy drive.

DLM473E: Invalid mount request x'xx' 'aaaaaaaa' 'bbbbbbbb'

Description: Mounting of a virtual tape volume was requested by the VSE mount program, but the second word of the request ('bbbbbbbb') did not contain a proper drive designation.



vt (DLM) Messages


95

DLM474E: No free device in default GROUP n to mount 'volser'

Description: Mounting of a virtual tape volume on ANY available drive address was requested by the VSE mount program, but there is no free drive in this GROUP.

System Action: The mount request is ignored and the drive remains Not Ready. A return code of 0x80 is returned to the Host program

User Action: Retry the Host mount when a virtual drive becomes available.

DLM475E: No free device in GROUP n to mount 'volser'

Description: Mounting of a virtual tape volume on ANY available drive address was requested by the VSE mount program, but but there is no free drive on this LPAR and GROUP.


User Action: Retry the Host mount when a virtual drive becomes available.

DLM476W: WARNING: Device <devicename> OSADDR is 000

Description: Mounting of a virtual tape volume was requested by the VSE mount program, but the device upon which the volume is being mounted has an OSADDR of 000.

System Action: The mount proceeds, but the mount device address of 000 is reported back to the Host program. If the mount request was for a specific device address, this probably won't be of any consequence, but if the request was for 'Any' drive, the Host program won't be able to determine on which drive the volume was mounted.

User Action: Reconfigure Virtuent and add the correct OSADDR parameter for each device that will be attached to a VSE system.

DLM477E: Mount requested on <devicename1> by <devicename2> failed

Description: Mounting of a virtual tape volume on ANY available drive address was requested by the VSE mount program, but the volume could not be mounted on <devicename2>. This message will be preceded by one or more messages that explain the reason for the mount failure.


User Action: Refer to any preceding messages for the reason for the mount failure and correct the problem(s).

DLM478I: Device <devicename> Requesting mount 'volser' on 'device'

vt (DLM) Messages


96

Description: Mounting of a virtual tape volume was requested by the VSE mount program or a tape manager on the host.

System Action: Virtuent attempts to mount the requested volume on the requested drive.

User Action: None.

DLM479W: Device <devicename> volume <volser> is completely empty!

Description: The specified tape volume was successfully mounted, but contains no data or tape marks.

System Action: The specified volume is mounted as requested, but any attempts to read from the volume will result in an I/O error (Unit Check status, Tape Void sense) being presented to the Host.

User Action: Be certain that the correct volume is being requested. If necessary, delete and re-initialize the virtual tape volume.

vt (DLM) Messages


97

DLM480E: Both active and scratch volser volumes exist in <pathname>, mount ignored

Description: While mounting a volume, Virtuent found both active (VOLSER) and scratch (~VOLSER) copies of the volume in the same tape library.

System Action: The mount request is ignored, and the drive remains not ready.

User Action: Determine which, if any, of the volumes is valid and should be kept, and delete the invalid volume.

DLM481E: <function> error renaming volume <volser> (filename); <error message>

Description: The Host has asked for a previously scratched volume by specific volser. Virtuent was unable to rename the scratch volume (~VOLSER) to an active volume (VOLSER).

System Action: The mount request is ignored, and the drive remains Not Ready.

User Action: Refer to any earlier messages and the 'error message' portion of this message to determine the cause of the failure.

DLM482I: Scratch tape <volser> made active

Description: The Host has asked for a previously scratched volume by specific volser.

System Action: Virtuent returns the requested volume to active status by renaming it from ~VOLSER to VOLSER, then mounts the volume.

User Action: None.

DLM483E: Error scratching/unscratching/erasing volume <volser> (filename); <error message>

Description: An error has occurred while scratching, unscratching, or erasing a scratch tape.

System Action: The scratch, unscratch, or erase function fails.

User Action: Refer to any earlier messages and the 'error message' portion of this message to determine the cause of the failure.

DLM484W: Mount loop on device <devicename>, volume <volser> mount ignored

Description: The Host repeatedly requested the mounting of the specified volume, but immediately unloaded the volume each time without reading past labels or writing to it. This usually signifies that the Host is not satisfied with the contents of the virtual tape volume, so it unloads it and requests it again.

vt (DLM) Messages


98

System Action: The last mount request is ignored, and the drive remains Not Ready.

User Action: Examine the Host console to determine the problem with the volume. Correct the Host JCL to use the correct volume or a different volume.

DLM485W: Device <devicename> Mount of unlabeled [SCRTCH/PRIVAT] volume ignored

Description: The Host requested the mounting of an unlabeled scratch tape. Virtuent does not support the mounting of unlabeled scratch tapes because there is no way to track the volume by volser once the Host writes unlabeled data.

System Action: The mount request is ignored and the device remains Not Ready.

User Action: Specify a specific volume serial number for unlabeled usage, or specify a labeled tape for scratch usage.

DLM486E: Device <devicename> Unable to allocate a [SCRTCH/PRIVAT] volume

Description: The mount request for a scratch tape failed.

System Action: The mount request is ignored and the device remains Not Ready. This message is preceded with one or more messages that explain the reason for the mount failure.

User Action: Correct the error and rerun the job.

DLM487I: Device <devicename> volume <volser> mount will be retried

Description: The preceding virtual tape mount request could not be satisfied at this time.

System Action: The specified mount request will be automatically retried until successful or until the Host cancels the mount request with a new Load Display command.

User Action: None

DLM488I: Device <devicename> Unused scratch volume <volser> deleted

Description: The specified volume was created in response to a scratch tape mount request, but it was unloaded without ever being written to.

System Action: The volume is deleted from the virtual tape library.

User Action: None.

DLM489E: Device <devicename> Error loading volume 'filename'

Description: The specified virtual tape file could not be opened.

vt (DLM) Messages


99

System Action: The load request is ignored and the device remains Not Ready. This message is preceded with one or more messages that explain the reason for the error.

User Action: Correct the error and rerun the job.

DLM490I: Device <devicename> Volume <volser> unloaded

Description: The specified virtual tape volume was unloaded.

System Action: The specified drive enters the Not Ready state and is available for another job.

User Action: None.

DLM491I: Device <devicename> on SMB filesystem, max volume size changed to 2G

Description: Virtuent has detected that the tape library for the specified virtual tape drive is on a CIFS/SMB filesystem and the current maximum volume setting for this drive was greater than 2 GB.

System Action: The maximum volume size for this drive is adjusted to 2 GB. If the tape library path is ever changed back to a non-SMB filesystem, the maximum volume size will be automatically changed back to the previous value.

User Action: None.

DLM492I: Device <devicename> not on SMB filesystem, max volume size changed back to size

Description: Virtuent has detected that the tape library for the specified virtual tape drive is no longer on a CIFS/SMB filesystem, and the maximum volume setting for this drive was previously adjusted down to 2 GB.

System Action: The maximum volume size for this device is adjusted back to the previous value.

User Action: None.

DLM493W: Device <devicename> write [TM] attempt to protected volume

Description: The Host attempted to write data or a tapemark to this read-only tape volume.

System Action: Virtuent returns an error (Command Reject, File Protected) to the Host application.

User Action: Correct the JCL, program or operational procedure that caused the Host to try to write to a protected volume, or mount the volume in read-write mode.

DLM494W: Device <devicename> disk full writing data/TM at nnnnnnn, file <filename>

vt (DLM) Messages


100

Description: Virtuent received a write operation from the Host, but the tape library disk is full. 'nnnnnnn' is the number of bytes written to the tape so far.

System Action: The write operation fails (Unit Check status, Intervention Required sense), and the virtual drive is put into the 'Not Ready' (Intervention Required) state. Virtuent will leave the drive in the Not Ready state until the operator changes the drive to Ready. Most Host systems will report the 'Intervention Required' to the Host operator, pause the current job, and wait for the drive to come ready.

User Action: When space is available on the tape library disk, issue the READY command to this drive to resume.

DLM495E: Device <devicename> disk full writing data/TM at nnnnnnn, file <filename>

Description: Virtuent received a write operation from the Host, but the tape library disk is full. Virtuent cannot recover and continue because the tape library is on an NFS filesystem. 'nnnnnnn' is the number of bytes written to the tape so far.

System Action: The write operation fails (Unit Check status, Equipment Check sense). The contents of the volume being written is unpredictable.

User Action: Rerun the job after more space is made available on the target tape library filesystem.

DLM496W: Device <devicename> write compression suppressed by IDRC=NO / forced by IDRC=FORCE>

Description: Either the Host requested compression of the output data but the virtual tape drive is currently set to IDRC=NO, or the Host did not request compression but the drive is currently set to IDRC=FORCE. This message will only be displayed once per volume.

System Action: If IDRC=NO is set, the data is written uncompressed to the virtual tape library. If IDRC=FORCE is set, the data is compressed.

User Action: None, unless you truly wanted the data to be compressed or not compressed in a different way. In that case, reconfigure the virtual tape drive with the correct IDRC parameter, or enter the Virtuent console command 'SET IDRC=ON/OFF/FORCE [DEV=devicename]' to temporarily override the configuration.

DLM497W: Device <devicename> Hardware [de]compression configured off, using software only

Description: The controller has hardware compression/decompression capability but is currently configured to not use the hardware

vt (DLM) Messages


101

facility for compression/decompression. This message will display once per volume whenever this condition is true.

System Action: The data is compressed or decompressed with software rather than with the compression hardware.

User Action: None, unless you truly wanted the data to be compressed and/or decompressed with the compression hardware (which is much faster than software compression/decompression). In that case, enter the Virtuent command 'SET HWCOMPRESSION=ON' and/or 'SET HWDECOMPRESSION=ON to reactivate the hardware compression/decompression feature.

DLM499W: Device <devicename> Volume <volser> error compressing data: nnn

Description: An error occurred while writing compressed data to the virtual tape file.

System Action: The data is written uncompressed to the tape library, unless hardware compression was in use, in which case software compression is tried.


DLM500I: Scratching/Unscratching/Erasing of volume <volser> requested by host via device <devicename> [dsn='datasetname']

Description: Scratching, unscratching, or erasing of the specified virtual tape volume was requested by the Host. If the request is further qualified by a dataset name, it is shown in the message.

System Action: Virtuent will attempt to scratch, unscratch, or erase (delete the data of a scratch volume) the specified volume on the tape library disk. If a dataset name is specified the volume will first be checked to confirm that it contains the specified data set.

User Action: None.

DLM501I: Volume <volser> (filename) scratched/unscratched/erased/deleted

Description: Scratching, unscratching, erasing, or deletion of the specified virtual tape volume as requested by the Host was successful.

System Action: The specified virtual tape volume was scratched, unscratched, erased (data deleted), or deleted (file deleted) from the tape library disk as requested. A return code of 0 (success) was returned to the Host application.

User Action: None.

DLM502W: Volume <volser> is currently on <devicename>, cannot scratch/unscratch/erase

vt (DLM) Messages


102

Description: Scratching, unscratching, or erasing of the specified virtual tape volume was requested by the Host, but the specified volume is in use.

System Action: The virtual tape volume status is not changed. A return code of 0x06 is returned to the Host application.

User Action: Change the tape status later when it is not in use.

vt (DLM) Messages


103

DLM503E: Error scratching/unscratching/erasing volume <volser> (filename); <error message>

Description: An error occurred during the scratching, unscratching, or erasing of the specified virtual tape volume requested by the Host.

System Action: The volume is in an undefined state. It may have been scratched or it may still be active, depending on the error that occurred. A return code of 0x07 (volume does not exist) or 0x08 (any other error) is returned to the Host application.

User Action: Consult any preceding related messages and the 'error message' portion of this message for a description of the problem and correct the problem. If the problem recurs, contact EMC support for assistance.

DLM504E: Scratching/unscratching/erasing of invalid volume 'volser' requested by host via device <devicename>

Description: Scratching, unscratching, or erasing of the specified virtual tape volume was requested by the Host, but the requested volser is an invalid volume serial number.

System Action: The scratch, unscratch, or erase request is ignored. A return code of 0x05 is returned to the Host application.

User Action: Correct the volume serial number being sent by the Host program.

DLM505E: Device <devicename> received invalid scratch/unscratch/erase/execute request, length=nnn

Description: Scratching, unscratching, or erasing of the specified virtual tape volume, or execution of a Virtuent console command, was requested by the Host, but the data sent by the Host was of an incorrect length.

System Action: The Host initiated request is ignored. A return code of 0x01 is returned to the Host application.

User Action: Correct the data being sent by the Host program.

DLM506E: Both active and scratch <volser> volumes exist in <pathname>!

Description: Scratching or unscratching of the specified virtual tape volume was requested by the Host, but Virtuent found that the files VOLSER (not scratch) and ~VOLSER (scratch) both exist in the same tape library.

System Action: The scratch or unscratch request is ignored. A return code of 0x03 is returned to the Host application.


vt (DLM) Messages


104

DLM507E: Scratch/Unscratch Error renaming volume <volser> (filename); <error message>

Description: Scratching or unscratching of the specified virtual tape volume was requested by the Host, but Virtuent encountered a problem while renaming the volume to the specified filename.

System Action: The scratch or unscratch request is ignored. A return code of 0x08 is returned to the Host program.

User Action: Refer to the error message portion of this message to determine the reason for the error.

DLM508I: Volume <volser> (filename) erased

Description: The specified virtual tape volume was erased because the length of time since it was scratched has exceeded the Erase Policy retention time.

System Action: The specified virtual tape volume was erased (its data deleted) and its storage space returned to free space for reuse.

User Action: None.

DLM510W: Device <devicename> data path <pathname> is not accessible

Description: Scratching, unscratching, or erasing of a virtual tape volume was requested by the Host, but the specified tape library directory is not currently accessible.

System Action: The scratch, unscratch, or erase request is ignored. A return code of 0x0A is returned to the Host program.

User Action: Make sure that the device via which scratch/unscratch/ erase requests are sent by the Host application is assigned to the correct tape library directory, and that the directory is read-write accessible by the user 'vtape'.

DLM511W: Device <devicename> data path <pathname> is not writable

Description: Scratching, unscratching, or erasing of a virtual tape volume was requested by the Host, but the specified tape library directory is not currently writable.

System Action: The scratch, unscratch, or erase request is ignored. A return code of 0x0B is returned to the Host program.

User Action: Make sure that the device via which scratch/unscratch/ erase requests are sent by the Host application is assigned to the correct tape library directory, and that the directory is read-write accessible by the user 'vtape'.

DLM512E: Device <devicename> Scratching/Erasing/Unscratching/Deleting not allowed on <drive>

vt (DLM) Messages


105

Description: Scratching, unscratching, or erasing of a virtual tape volume was requested by the Host, but the virtual device is currently assigned to a physical tape drive.

System Action: The scratch, unscratch, erase, or delete request is ignored. A return code of 0x0A is returned to the Host program.

User Action: Make sure that the device via which scratch/unscratch/ erase/delete requests are sent by the Host application is assigned to a virtual tape library directory, not a physical tape drive.

DLM513E: Device <devicename> Volume <volser> error uncompressing data block #nnnnn: nn (error message), falling back to s/w decompression

Description: An error occurred while reading compressed data from the tape file.

System Action: The virtual tape application will fall back to s/w decompression.

User Action: None

DLM514E: Device <devicename> Volume <volser> error uncompressing data block #nnnnn: nn (error message)

Description: An error occurred while reading compressed data from the tape file.

System Action: The virtual tape application returns an error (Data Check) to the Host

User Action: If possible, recreate the corrupted volume. If this problem recurs, contact EMC Support for assistance.

vt (DLM) Messages


106

DLM515W: Volume <volser> file is open elsewhere, cannot scratch/unscratch/erase

Description: While considering the specified virtual tape volume for scratching, unscratching, erasing, it was found that the specified volume was currently being accessed on another program.

System Action: The scratch/unscratch/erase request is ignored. If the action was requested by the Host, a return code of 0x09 is returned to the Host application.

User Action: Scratch/unscratch/erase the volume later when it is not in use.

DLM516E: Error locking volume <volser> (filename); <error message>

Description: While considering the specified virtual tape volume for scratching, unscratching, erasing, an I/O error occurred while trying to lock the file for exclusive access.

System Action: The scratch/unscratch/erase request is ignored. If the action was requested by the Host, a return code of 0x08 is returned to the Host program.

User Action: Make sure that the specified volume exists, is owned by the user 'vtape', is writable, and is not in use by any other program. Scratch/unscratch/erase the volume later when it is not in use. If the problem recurs, contact EMC support for assistance.

DLM517E: Invalid VOL1 label in volume <volser> (filename)

Description: While considering the specified virtual tape volume for scratching, unscratching, erasing, it was found that the specified volume does not contain a valid VOL1 label.

System Action: The scratch/unscratch/erase request is ignored. If the action was requested by the Host, a return code of 0x0C is returned to the Host program.

User Action: Specify a valid standard labeled tape in the request. If the volume has somehow been overwritten with incorrect contents, delete and reinitialize the volume.

DLM518E: Mismatched volser <volser1> found in <volser2> (<filename>)

Description: While considering the specified virtual tape volume for scratching, unscratching, erasing, it was found that the volume serial number (volser1) found in the VOL1 label on the volume does not match the one expected (volser2).

System Action: The scratch/unscratch/erase request is ignored. If the action was requested by the Host, a return code of 0x0D is returned to the Host program.

vt (DLM) Messages


107

User Action: If the volume has somehow been overwritten with incorrect contents, delete the volume manually and reinitialize the volume.

DLM520E: Invalid HDR1 label in volume <volser> (<filename>)

Description: While considering the specified virtual tape volume for scratching, unscratching, erasing, it was found that the volume does not contain a valid HDR1 label.

System Action: The scratch/unscratch/erase request is ignored. If the action was requested by the Host, a return code of 0x0E is returned to the Host program.

User Action: If the volume has somehow been overwritten with incorrect contents, delete and reinitialize the virtual tape volume.

DLM521E: Volume <volser> (filename) has data set 'dataset1', not 'dataset2'

Description: While considering the specified virtual tape volume for scratching, unscratching, erasing, it was found that the volume contains the dataset 'dataset1', not the data set specified by the Host request ('dataset2').

System Action: The scratch/unscratch/erase request is ignored. A return code of 0x0F is returned to the Host program.

User Action: Correct the data being sent by the Host application.

DLM522E: Invalid date in scratch request 'xxxxxxxxxxxx'

Description: Scratching, unscratching, or erasing of a volume was requested by the Host, but the data sent by the Host program contains an invalid date. The date shown (xxxxxxxxxxxxx) is in hexadecimal as received from the Host program.

System Action: The scratch/unscratch/erase request is ignored. A return code of 0x10 is returned to the Host program.


DLM523E: Volume <volser> (filename) created too recently (nnnnnn) to scratch today (nnnnnn)

Description: Scratching of a virtual tape volume was requested by the Host, but the date found in the virtual tape volume's HDR1 label shows that the file was created on the same date that (or later than) the scratch request is being made. A volume can only be scratched one or more days later than the day on which it was created.

System Action: The scratch request is ignored. A return code of 0x11 is returned to the Host program.

vt (DLM) Messages


108

User Action: Resubmit the scratch request to Virtuent at least one day after the file on the volume was created.

DLM524E: Volume <volser> (filename) already scratched/unscratched/erased

Description: Scratching, unscratching, or erasing of a virtual tape volume was requested by the Host, but the specified virtual tape volume is already in the state designated in the message.

System Action: The scratch/unscratch/erase request is ignored. A return code of 0x02 is returned to the Host program.

User Action: Be careful not to submit duplicate scratch/unscratch/erase requests to Virtuent.

DLM525E: Volume <volser> (filename) not a scratched/erased tape

Description: Erasing or deleting of a scratch volume was requested by the Host, but the specified virtual tape volume is not in the scratched (for erase) or erased (for delete) state.

System Action: The erase or delete request is ignored. A return code of 0x04 is returned to the Host program.

User Action: Be careful to submit erase requests for previously scratched volumes only, or delete requests for previously erased volumes only.

DLM526E: Volume <volser> (filename) cannot un-scratch, already erased

Description: Un-scratching of the specified virtual tape volume was requested by the Host, but virtual tape volume has already been erased and cannot be un-scratched. Its former data cannot be recovered.

System Action: The unscratch request is ignored. A return code of 0x02 is returned to the Host program.

User Action: Once a virtual tape volume has been erased, it cannot be un-scratched.

DLM539E: Device <devicename> volser <volser> write verification error: error message

Description: An error occurred while verifying the data just written to disk.

System Action: An I/O error status is returned to the current host operation. This message should be preceded by one or more messages that explain the problem(s) encountered.

User Action If the error messages describe a correctable problem, correct the problem and retry the failing job. Contact EMC Support if more assistance is needed.

vt (DLM) Messages


109

DLM540W: Unexpected response received from <servername>: message

Description: While attempting to get filesystem information from the specified server, an unexpected response was received.

System Action: Any feature such as Guaranteed Replication or FLR that depends on knowing information about the back-end filesystem may not function properly on this filesystem.

User Action: If the message describes a correctable problem, correct the problem and restart the application. Contact EMC Support if more assistance is needed.

DLM541I: Device <devicename> Volser <volser> first write on Guaranteed Replication filesystem

Description: Indicates that the device is configured to use Guaranteed Replication and the volume is written on a Guaranteed Replication-enabled filesystem.

System Action: When the volume is unloaded, a replication refresh will be performed on the filesystem.

User Action: None.

DLM542I: Device <devicename> Volser <volser> preparing Guaranteed Replication

Description: Indicates that the device is configured to use Guaranteed Replication, and the volume is written on a Guaranteed Replication-enabled filesystem.

System Action: Prepares a GR replication refresh.

User Action: None.

DLM543I: Device <devicename> Volser <volser> starting Guaranteed Replication

Description: Indicates that the device is configured to use Guaranteed Replication, and the volume is being written on a Guaranteed Replication-enabled filesystem.

System Action: Performs GR replication refresh. If the replication does not complete in n seconds, an error status is returned to the host’s unload command.

User Action: None.

DLM544I: Device <devicename> Volser <volser> Guaranteed Replication complete

Description: Indicates that the GR replication refresh has completed successfully.

System Action: The tape volume will be unloaded, with normal unload status returned to the host's unload command.

vt (DLM) Messages


110

User Action: None.ste m Me ssa ge s

DLM545W: Device <devicename> Volser <volser> GR device writing to non-replicating filesystem

Description: The specified device is configured to use Guaranteed Replication, and the volume being written is NOT on a replication-enabled filesystem.

System Action: When the volume is unloaded, no replication-refresh will be performed.

User Action: None.

DLM546I: Device <devicename> Volser <volser> retrying replication through 'csname'

Description: Indicates that the refresh is being retried on the specified Control Station after GR replication refresh failed once due to a communication error.

System Action: Retries GR replication refresh.

User Action: Check the VNX configuration to make sure that the VNX Control Station is properly configured.

DLM547W: Device <devicename> Volser <volser> ssh error with control station 'csname'\n"

Description: Indicates that GR replication refresh has failed due to communication error.

System Action: Retries the GR replication refresh on each Control Station defined on this VNX.

User Action: Check the VNX configuration to make sure that the VNX Control Station is properly configured.

DLM548E: Device <devicename> Volser <volser> Guaranteed Replication error: error message

Description: A GR replication refresh has encountered an error.

System Action: Unloads the tape volume, with an error status returned to the host's unload command. The file is intact, but replication is not guaranteed.

User Action: Check the error message for a description of the problem, correct the problem, check the replication status, or force a manual replication of the filesystem. If necessary, contact EMC Support for more assistance.

DLM549E: Device <devicename> Guaranteed Replication cannot locate info for 'pathname'

vt (DLM) Messages


111

Description: Attempts to refresh GR replication, but cannot obtain detailed replication information about the filesystem.

System Action: The GR replication refresh is not performed. An error status is returned to the host's unload command. The file is intact, but replication is not guaranteed.

User Action: Force a manual replication of the filesystem to guarantee that the tape has been replicated. Contact EMC Support for assistance.

DLM550I: Command received from Host: device <devicename>: cmd = 'command'

Description: The specified Virtuent console command was sent from the Host via the specified virtual tape device.

System Action: The command will be executed. Depending on the results of the command, a return code will be returned to the Host program.

User Action: If the command is successful, none. Otherwise, determine the reason for the console command failure and correct the problem.

DLM551E: Host-initiated commands not allowed

Description: A Virtuent console command was sent from the Host, but Virtuent is not configured to allow Host-initiated commands.

System Action: The command will not be executed. A failure code will be returned to the Host program.

User Action: If you want the Host to be able to initiate Virtuent console commands, correct the Virtuent configuration to allow for this feature.

DLM552E: Unable to locate script <scriptname>: <error msg>

Description: A Virtuent RUN console command was sent from the Host, but Virtuent is not able to locate the specified script.

System Action: The command will not be executed. A failure code will be returned 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 Virtuent user 'vtape'.

DLM553E: Unable to execute script <scriptname>

Description: A Virtuent RUN console command was sent from the Host, but Virtuent is not able to execute the specified script.

vt (DLM) Messages


112


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 Virtuent user 'vtape'.

DLM555E: RUN command not allowed

Description: A Virtuent RUN console command was sent from the Host, but Virtuent is not configured to allow the RUN command.


User Action: If you want the Host to be able to initiate Virtuent RUN commands, correct the Virtuent configuration to allow for this feature.

DLM556W: RUN process #nnnnn has not finished in nn seconds

Description: A Virtuent RUN console command was sent from the Host and executed by Virtuent, but the specified script did not complete within the specified time limit.

System Action: Virtuent will cancel the process identified by process ID #nnnnn. A failure code will be returned to the Host.

User Action: If the specified script normally takes longer than the time specified, specify a longer time on the RUN command.

DLM560E: Device <devicename> Error gathering file segment data for volume <volser>

Description: An error has occurred while opening a previously extended virtual tape volume on a WORM filesystem. This message should be preceded by one or more messages that explain the problem(s) encountered.

System Action: The volume is not mounted, and the drive remains Not Ready.

User Action: If the preceding error message(s) describe a correctable problem, correct the problem and retry mounting the tape volume. Contact EMC Support if more assistance is needed.

DLM561E: Device <devicename> Missing or invalid AWSMAP in <filename>

Description: An error has occurred while opening a previously extended virtual tape volume on a WORM filesystem. The format of the specified file is invalid.



vt (DLM) Messages


113

vt (DLM) Messages


114

DLM562E: Device <devicename> Error extending volume <volser>:<error message>

Description: An attempt was made to write to (modify) a previously locked virtual tape volume on a WORM filesystem, but an error occurred while trying to create a new file to extend the volume. The <error message> portion of this message explains the problem that occurred.

System Action: The Host write command is rejected with a Unit Check.


DLM563E: Device <devicename> Info in file <filename> doesn't match previous segment

Description: An error has occurred while opening a previously extended virtual tape volume on a WORM filesystem. The previous file segment information stored in file segment 'filename' does not match the actual contents of the immediately preceding file segment.



DLM564E: Device <devicename> Invalid segment number in segment <n>

Description: An error has occurred while opening a previously extended virtual tape volume on a WORM filesystem. The file segment number stored in the file VOLSER_nnnnn, where nnnnn is the segment number <n> shown in the message, is not <n>.



DLM565E: Device <devicename> Illegal volume mod attempt, volume <volser>, offset <nnnnnn>, block <nnn>

Description: An attempt was made to write to (modify) a previously locked virtual tape volume on a WORM filesystem, at a location other than at the end of the existing data. Once a virtual tape volume is locked on a WORM filesystem, you can append to the dataset but you cannot modify it in any other way.


User Action: Correct the Host job or application so that it does not try to write anywhere but at the end of the existing data.

DLM566E: Device <devicename> Volume <volser> maximum number of modifications exceeded

vt (DLM) Messages


115

Description: An attempt was made to write to (modify) a previously extended virtual tape volume on a WORM filesystem, but the volume has already been modified the maximum of 9999 times.


User Action: Keep the number of modifications to a virtual tape volume on a WORM filesystem to a minimum, for performance reasons as well as to avoid reaching the maximum allowable modifications.

DLM567I: Device <devicename> Volume <volser> WORM file has <nn> modifications

Description: The specified volume resides on a WORM filesystem. If the volume had been previously modified since it was first placed into WORM mode, This informational message displays the number of times it has been modified.


User Action: None.

DLM568I: Device <devicename> Volume <volser> writing modification #nn

Description: The specified volume resides on a WORM filesystem, and is in WORM mode. The system is configured to allow appending to WORM files (FLRMOD=YES) and the host has performed a write to append to this tape.

System Action: The append to the WORM file is allowed. This message will be displayed once per mounting of any given tape.

User Action: None.

DLM569E: Device <devicename> error extending volume <volser>

Description: An error occurred during an attempt to write to (modify) a previously locked virtual tape volume on a WORM filesystem. This message should be preceded by one or more messages that explain the problem(s) encountered.


User Action: If the preceding error message(s) describe a correctable problem, correct the problem and retry the failing job. Contact EMC Support if more assistance is needed.

DLM570W: HDR1 has invalid expiration date `xxxxxx'

Description: During opening of an existing virtual tape volume, or when the Host wrote a new HDR1 label, the Virtuent application determined that the expiration date in the HDR1 label (xxxxxx) was invalid.

vt (DLM) Messages


116

System Action: Processing continues. The Virtuent application treats the volume as if no expiration date was specified in the HDR1. The only time a volume's expiration date is of any consequence to the Virtuent application is if the file is being written to a WORM filesystem. In this case, if the Virtuent application is configured with a default retention value, that retention period will be used. Otherwise, the retention period is treated as zero (no retention) and the file will be written in a non-WORM mode.

User Action: Correct the host JCL to write a valid expiration date.

DLM571W: Device <devicename> Retention date <yyyy/ddd> out of range, using YYYY/DDD

Description: During opening of an existing virtual tape volume, or when the Host wrote a new HDR1 label, Virtuent determined that the expiration date in the HDR1 label (yyyy/ddd) was outside of the range that can be converted to a retention period by the Virtuent application. The Virtuent application can process HDR1 expiration dates in the range Jan. 1, 2003, through Jan. 18, 2038.

System Action: Processing continues. If the HDR1 date was prior to Jan. 1, 2003, the Virtuent application regards the volume's expiration date to be Jan. 1, 2003. If the HDR1 date was after Jan. 18, 2038, the Virtuent application regards the volume's expiration date to be Jan 18, 2038. The only time a volume's expiration date is of any consequence to the Virtuent application is if the file is being written to a WORM filesystem. In this case, the file will be written in WORM mode with the modified retention date.


DLM572E: Unable to calculate retention time for xxxxxx (out of range?)

Description: During opening of an existing virtual tape volume, or when the Host wrote a new HDR1 label, the Virtuent application was unable to convert the HDR1 expiration date (xxxxxx) to a retention period, for an unknown reason.

System Action: Processing continues. The Virtuent application treats the volume as if no expiration date was specified in the HDR1. The only time a volume's expiration date is of any consequence to the Virtuent application is if the file is being written to a WORM filesystem. If the Virtuent application is configured with a default retention value, the default retention period will be used. Otherwise, the retention is treated as zero (no retention) and the file will be written in non-WORM mode.


DLM573E: Error while validating directory <directory>: <error message>

vt (DLM) Messages


117

Description: During the directory validation process a problem was discovered.

System Action: The specified directory cannot be used for the intended purpose.

User Action: Verify the existence and properties of the directory. Contact EMC support for assistance.

DLM580E: Error getting <volser> file status <error message>

Description: During closing of a virtual tape file, an error occurred reading the file's current status information.

System Action: Processing continues. There may be problems in accessing this file later.

User Action: The error message portion of this message identifies the reason for the error. Correct the reason if possible. If the problem recurs, contact EMC support for assistance.

vt (DLM) Messages


118

DLM581E: Device <devicename> Error setting volser file status to <status> <error message>

Description: During closing of a virtual tape file, an error occurred while setting the file's final status information.

System Action: Processing continues. There may be problems in accessing this file later.

User Action: The error message portion of this message identifies the reason for the error. Correct the reason if possible. If the problem recurs, contact EMC support for assistance.

DLM582I: Device <devicename> volume <volser> made/left read-only

Description: This message is displayed when an output virtual tape volume written to a WORM filesystem is unloaded and the volume has been made a read-only volume.

System Action: The virtual tape volume is now permanently read-only.

User Action: None.

DLM590E: Device <devicename> Volume <volser> Unable to calculate retention time for D/M/Y (out of range?)

Description: While closing a volume that has no valid HDR1 expiration date, written to a WORM filesystem, Virtuent was unable to calculate a valid retention period based on the configured default retention period.

System Action: Processing continues. Virtuent regards the volume's expiration date to be zero (no retention). In this case, the file will be written in non-WORM mode because of this error.

User Action: If the volume was to have been written in WORM mode, either correct the HDR1 expiration date, or specify a valid default retention period value. If this problem persists, contact EMC support for assistance.

DLM591E: Device <devicename> Volume <volser> Unable to set access time: <error message>

Description: While closing a volume written to a WORM filesystem, the Virtuent application was unable to set the retention period in the file's last access time.

System Action: Processing continues. Virtuent will attempt to write the file in WORM mode anyway. If successful, the file will be locked with a permanent retention period.

User Action: Refer to the `error message' portion of this message to determine the cause of the problem. If this problem persists, contact EMC support for assistance.

vt (DLM) Messages


119

DLM594W: Device <devicename> Volume <volser> configured FLR but no .FLR file found in <pathname>

Description: The specified virtual tape drive is configured for EMC FLR support, but the target directory does not contain a file named .FLR.

System Action: Processing continues. The virtual tape volume just written is not set to a WORM state.

User Action: Be sure that the correct tape library is configuredand the correct external filesystem is mounted for this device. If you wish tapes to be locked with FLR, you must create a file named .FLR in each FLR tape library directory.

DLM595W: Device <devicename> configured FLR and .FLR found but <pathname> is not a FLR directory

Description: The specified virtual tape drive and tape library directory are configured for FLR support, but the virtual tape application has determined that the target directory is not a FLR volume, because the virtual tape file just closed did not stay Read-Only.

System Action: Processing continues. The virtual tape volume just written is not protected from further modification.

User Action: Be sure that the correct tape library is configured and the correct external filesystem is mounted for this device.

DLM596W: Device <devicename> configured FLR but no .FLR file found in <pathname>

Description: The specified virtual tape drive is configured for File Lock Retention support, but the target directory does not contain a file called .FLR.

System Action: Processing continues. The virtual tape volume just written is not Locked.

User Action: Be sure that the correct tape library is configured and the correct external filesystem is mounted for this device. If you wish tapes to be locked, you must create a file called .FLR in each FLR directory.

DLM597W: Device <devicename> Volume <volser> configured FLR and .FLR found but <pathname> is not an FLR directory

Description: The specified virtual tape drive and tape library directory are configured for FLR support, but the application has determined that the target directory is not an FLR filesystem, because the virtual tape file just closed did not stay Read-Only.

System Action: Processing continues. The virtual tape volume just written is not protected from further modification.

vt (DLM) Messages


120

User Action: Be sure that the correct tape library is configured and the correct external filesystem is mounted for this device.

DLM607E: Device <devicename>, Volume <volser>: error while setting scratch state

Description: An error occurred while trying to scratch or unscratch a virtual tape file.



DLM612E: Device <devicename>, Volume <volser>: <message>

Description: Virtuent experienced an internal error, and will output a detailed error message.



DLM612W: <error message>

Description: A number of error / warning messages may be issued using this message number.

System Action: Variable depending on message.

User Action: Call EMC support for assistance.

DLM614E: Device <devicename>, Volume <volser>: could not get hint for block: nnnn

Description: Virtuent was unexpectedly unable to find an entry in an index of block IDs while performing a LOCATE.

System Action: Virtuent returns an error status to the Host's LOCATE request.


DLM631E: Device <devicename>, Volume <volser>: could not find block nnnn

Description: Virtuent was unable to locate a block specified in a LOCATE request.

System Action: Virtuent returns an error status to the Host's LOCATE request.

vt (DLM) Messages


121


DLM636I: Database timeout set to N seconds

Description: Normal response to an operator 'SET DBTIMEOUT=N' command.

System Action: The specified database timeout was changed.

User Action: None.

DLM637W: FIND command not supported for PATH-TYPE paths; skipping.

Description: The FIND command does not currently support this PATH-TYPE.

System Action: The FIND command does not query paths of the specified type.

User Action: None.

DLM660I: Device <devicename>, Volume <volser>: For Unisys only, trying again as SCRTCH

Description: The Host requested that Virtuent mount volume <volser>, but the volume does not exist. For Unisys devices only, Virtuent will now perform a SCRTCH mount request.

System Action: Virtuent attempts to mount a scratch volume.

User Action: None.

DLM671E: Device <devicename>, Volume <volser>: error while closing tape

Description: An error occurred while unmounting a virtual tape.



DLM674E: Device <devicename>, Volume <volser>: Bad path specified: full path(pathname)

Description: An internal error occurred while Virtuent was attempting to construct a path name.



DLM676E: Device <devicename>, Volume <volser>: internal I/O error

vt (DLM) Messages


122

Description: Virtuent experienced an internal I/O error.



vt (DLM) Messages


123

DLM677E: Device <devicename>, Volume <volser>: error while renaming tape to 'volser'

Description: An error occurred while changing a tape's volser.



DLM678E: Device <devicename>, Volume <volser>: Encryption/decryption failed

Description: An error occurred while encrypting or decrypting data.



DLM679E: Cannot set FIPS mode for encryption

Description: The initialization of FIPS-mode-certified encryption failed.

System Action: Virtuent initialization terminates.


DLM680E: Device <devicename>, Volume <volser>: internal I/O error while (un)reserving volser 'volser'

Description: An error occurred while performing a distributed lock or unlock on a virtual tape.



DLM681E: Device <devicename> <path-type> path 'path' specified, but no valid <path-type> license file exists.

Description: A Centera or HCAP path was encountered, but the Virtuent application is not licensed for that feature.

System Action: Virtuent will not accept mount requests on this path.

User Action: If Virtuent should be licensed for this feature, contact EMC support for assistance.

DLM682E: Device <devicename> unable to initialize VirtualFile path 'path'

vt (DLM) Messages


124

Description: An error occurred while determining the Centera or HCAP path.

System Action: Virtuent will not accept mount requests using the indicated path.

User Action: Ensure that the indicated path is correctly configured. If the problem persists, contact EMC support for assistance.

DLM683W: Nothing to recover for tape <volser>; cleaning up.

Description: A previous I/O failure caused recovery of a partially-written tape to be attempted, but no recovery was possible.

System Action: Virtuent cleans up the remnants of the unrecoverable tape.

User Action: None.

DLM684E: Device <devicename>, Volume <volser>: could not validate SL tape

Description: There was a problem in the format of the tape headers in a standard labeled tape.



DLM685E: unable to initialize path 'pathname': error message

Description: An error occurred while setting the specified path.

System Action: The path is not changed.


DLM686I: Device <devicename> Distributed Lock Mgr informational message <message>

Description: An error occurred while setting the specified path.


User Action: Examine message, contact EMC Support for assistance.

DLM687I: Enhanced FS move volume method is: <method>

Description: The enhanced FS will use the displayed method when moving a volume.


User Action: None.

vt (DLM) Messages


125

DLm688I: Enhanced FS move for volumes in <FLR/GR> tape libraries: <enabled/disabled>

Description: The enhanced FS move feature will be disabled for the file system type if selected as disabled or will use the efsmove method chosen for all file systems when selected as enabled


User Action: None.

DLM701E: Device <devicename> Data Exchange Feature not licensed, mount 'volser' ignored

Description: Mounting of a flat file (data exchange) volser was requested, but this controller is not licensed for flat file support.


User Action: Only flat files can start with the volser prefix BFL. If you want to use the Virtuent flat file / data exchange feature, you must obtain a license for this feature. Contact EMC support for assistance.

vt (DLM) Messages


126

DLM704E: Device <devicename> Error deleting unused flat volume <volser>: error message

Description: The specified volume was created in response to a flat tape mount request. Because it was unloaded without ever having been written to, Virtuent tried to delete it. An I/O error occurred during the attempt to delete.

System Action: The volume may or may not have been deleted from the tape library.

User Action: The 'error message' portion of this message describes the error that occurred. Correct the error.

DLM711I: Device <devicename> Unused flat volume <volser> deleted

Description: The specified volume was created in response to a flat tape mount request, but it was unloaded without ever being written to.

System Action: The volume is deleted from the tape library.

User Action: None.

DLM714E: Device <devicename> too many trailer labels!

Description: Virtuent received too many labels to store (more than legally allowed for standard label processing) while processing the trailer labels for a standard labeled flat file.

System Action: The Host write is canceled with a unit check.

User Action: Correct the condition that is causing too many labels to be written.

DLM715E: Device <devicename> data in trailer labels!

Description: Virtuent received a non-label data record while processing the trailer labels for a standard labeled flat file.


User Action: Correct the condition that is causing the invalid label or data to be written within the trailer labels.

DLM720E: Device <devicename> command in flat file

Description: Virtuent received a tape positioning command from the Host while positioned within the data area of a flat file.

System Action: The Host command is canceled with a unit check.

User Action: Spacing commands are not allowed within flat files; correct the condition that is causing the spacing within the file.

vt (DLM) Messages


127

DLM724E: Device <devicename> read backwards/previous in flat file

Description: The Virtuent application received a Read Backwards or Read Previous command from the Host while within the data area of a flat file.

System Action: The Host command is canceled with a unit check.

User Action: Reading backwards is not allowed in a flat file; correct the condition that is causing the backwards reading.

DLM766E: Device <devicename> file 'filename' already exists [as scratch]

Description: The Host wrote a HDR1 label to a flat file volume, and Virtuent attempted to change the volume's filename from VOLSER.FLAT to VOLSER.DATASETNAME.FLAT (where DATASETNAME is the dataset name from the HDR1 label), but the file VOLSER.DATASETNAME.FLAT already exists in the tape library.


User Action: Either delete or rename the existing file in the tape library before writing a flat file with the same name, or use a different dataset name in the JCL for the new output file.

DLM767E: Device <devicename> error renaming volume <volser> (oldfilename) to newfilename; <error message>

Description: The Host wrote a HDR1 label to a flat file volume, and Virtuent attempted to change the volume's filename from VOLSER.FLAT to VOLSER.DATASETNAME.FLAT (where DATASETNAME is the dataset name from the HDR1 label), but an error occurred during the renaming.


User Action: Refer to the 'error message' portion of this message to determine the reason for the error.

vt (DLM) Messages


128

DLM770E: Cannon set RSA mode for encryption

Description: The initialization of RSA mode encryption failed.


User Action: Examine any preceding related messages, if any, for additional error information and correct the problem. If the problem reoccurs contact EMC support for assistance.

DLM771E: Cannot get RSA key from decryption

Description: The request for an RSA decryption key failed.

System Action: The Host read is canceled with a unit check.

User Action: Confirm that the proper keys are installed in the RSA Key Manager, that the Key Manager is accessible from the controller, and that the access certificates are valid.

DLM772E: Cannot get RSA key for encryption

Description: The request for an RSA encryption key failed.

System Action : The Host write is canceled with a unit check.

User Action: Confirm that the proper keys are installed in the RSA Key Manager, that the Key Manager is accessible from the controller, and that the access certificates are valid.

DLM773E: Cannot user KEY= with RSA encryption

Description: Cannot use non-RSA along with RSA encryption.

System Action: The KEY= directive is rejected.

User Action: Note that only RSA keys can be configured when the RSA Key Manager is in use.

DLM774I: KEYCLASS set to [class|NONE] for device <devicename>

Description: Key class ‘class’ will be used for encryption on device <devicename>, or if ‘NONE’ is specified, no encryption will be done on device <devicename>.

System Action: The specified encryption key class (or none, for ‘NONE’) will be used for any blocks written to the specified device.

User Action: None.

DLM775E: Cannot encrypt a tape with more than one key on device <devicename>

Description: Two different keys were attempted to be used for encryption on device <devicename>.

vt (DLM) Messages


129


User Action: Use the key that was previously used to encrypt data for this tape.

DLM776E: Cannot stop RSA key module

Description: The attempt to stop the RSA key module failed.



DLM777E: RSA encryption is not available.

Description: RSA encryption is either not licensed, not configured, or had an error during initialization.

System Action: Check the logs for encryption initialization errors.

User Action: Depending on the cause of the error, either obtain a license for RSA encryption, configure RSA encryption properly, or fit her is an initialization error, contact EMC support for assistance.

DLM778I: Reusing encryption key for device <devicename>

Description: The tape includes a previously encrypted data set, and another data set is being added, so the previous key will be used for this new data set.

System Action: The previous key is used for the new data set.

User Action: None

DLM779I: Not encrypting on device <devicename>

Description: The tape has prior unencrypted data set(s), so this new appended data.

System Action: The new data set is written unencrypted.

User Action: None

vt (DLM) Messages


130

DLM780E: Restarting RSA peer process

Description: The RSA peer process has exited or become inactive, and needs to be restarted.

System Action: The RSA peer process is restarted.

User Action: None

DLM781W: Device <devicename> is open as a read only tape

Description: The volume on the physical tape drive is mounted in read-only mode.

System Action: The tape is mounted in read-only mode.

User Action: In order to write new volumes, make sure the tape is correctly mounted and is write-enabled.

DLM782E: Command <command> not supported on Physical Tape Device <devicename>

Description: The requested (rewind, unload, unready, ready) command is not supported on real physical tape devices.

System Action: The command is ignored.

User Action: Operator intervention is required to issue this command at the physical tape device.

DLM783W: Device <device name> tape door is open

Description: The physical tape drive door is open.

System Action: The system cannot mount the tape.

User Action: Physically close the tape door.

DLM785E: Device <device name> Read Buffer too small

Description: The data block read from the physical tape is larger than the maximum supported by Virtuent.

System Action: An error status (equipment check) is returned to the Host.

User Action: The tape is not compatible with Virtuent because of the large block(s) it contains.

vt (DLM) Messages


131

DLM786E: Device <device name> Failed to Open <device path>

Description: The physical tape drive is not accessible.

System Action: Virtuent will not communicate with this tape device.

User Action: The tape most likely requires manual intervention.

DLM787E: Device <device name> Unable to set Compression <errno>

Description: The physical tape drive did not accept the compression command.

System Action: Data written to this tape device will not be compressed.


DLM788E: Device <device name> SCSI block #nnn too large (xxxxxx) to handle <operation> (max=yyyyyy)

Description: Virtuent has received a tape block from the host with a size ('xxxxxx') that is larger than the maximum tape blocksize ('yyyyyy') that can be presented to the physical tape drive.


User Action: Correct the Host application to send a blocksize that can be handled by the tape drive.

DLM789I: Device <device name> does not support the SCSI <cmd> command

Description: The physical tape drive does not support the specified command.

System Action: Virtuent will continue, but the specified command cannot be performed.

User Action: Determine that the attached device is a supported device type.

DLM790I: ST driver version info: <description>

Description: This message displays the version number of the st (SCSI tape) driver.


User Action: None.

vt (DLM) Messages


132

DLM791I: BTISMC driver version info: <description>

Description: This message displays the version number of the btismc (EMC SCSI Media Changer) driver.


User Action: None.

DLM795I: Device devicename ready

Description: This message displays when a physical tape drive assigned to a virtual tape device transitions from not ready to ready.

System Action: A "Ready" interrupt is sent to the host.

User Action: None.

DLM796I: Device <devicename> offline and not ready

Description: This message displays when a physical tape drive assigned to a virtual tape device transitions from ready to not ready.

System Action: None. The drive will appear not ready to the host.

User Action: None.

DLM797E: Device devicename cannot unload during tape activity

Description: This message displays when an operator requests a tape unload while physical tape drive activity is in progress.


User Action: Retry the command when tape activity has completed.

DLM801I: Trace buffers saved to disk

Description: Normal response to the 'Save Trace' command.

System Action: All trace buffers currently held in memory have been written to disk.

User Action: None.

vt (DLM) Messages


133

DLM804I: Writing corefile to 'filename.gz' ...

Description: Normal response to the ‘ SAVE COREFILE’ command.

System Action: A diagnostic corefile of the virtual tape application will be saved to the specified file.

User Action: None.

DLM805I: corefile 'filename.gz' saved to disk

Description: Normal response to the ‘SAVE COREFILE’ command.

System Action: A diagnostic corefile of the Virtuent application has been to the specified file.

User Action: None.

DLM810E: Command failed: command: <error message>

Description: Virtuent received an error while trying to execute the specified command in an external shell.

System Action: The system continues running without executing the specified external command.


DLM812E: <command> feature is not licensed

Description: The specified command requires a feature that is not licensed for use on this controller.


User Action: Contact EMC for more information on enabling the licensed feature.

DLM813E: Command <command> is not permitted

Description: The specified command is not permitted by the Virtuent configuration.


User Action: Refer to Virtuent configuration documentation for instructions about how to activate this command.

DLM814E: Parameter #n 'keyword=value' is not a valid VOL= or DEV= parameter

Description: Syntax error on an operator command.


User Action: Use the 'Help' command to see the proper command syntax.

vt (DLM) Messages


134

DLM815E: Parameter n 'value' is not a valid VOLSER or synonym




DLM816E: No free device available to mount volume <volser>

Description: The operator 'Load' command specified any drive ('*'), but there was no free drive.


User Action: Wait for a drive to be free, then reenter the command.

DLM817E: Parameter n 'keyword=value' is not a valid parameter




DLM818E: Invalid device name 'value' specified (too long)

Description: The <devicename> specified in an operator command is invalid.



DLM819E: Unknown device name 'value' specified

Description: The <devicename> specified in an operator command is invalid.



vt (DLM) Messages


135

DLM820E: No devicenames match 'devicenames'




DLM821I: MediumSense23 set to ON/OFF for device <devicename>

Description: By default, a value of 0x24 (enhanced cartridge) is returned to a host media sense CCW. In very rare situations a host application might have a problem with this value. (SPXTAPE is one known program with this issue.) In this case, a configuration option can be used to return a 0x23 value (non-enhanced cartridge) in the media sense data.


User Action: The SET MEDIUMSENSE23=YES/NO command can be used to change this value if required. Contact EMC Support for more assistance with this option.

DLM822I: Guaranteed Replication refresh on Sync set ON/OFF

Description: Guaranteed Replication can be configured to perform a replication refresh at every tape sync point as well as at close time. This message displays the current setting of that option.

System Action: If ON, Guaranteed Replication (if enabled and writing to a GR-enabled filesystem) will perform a refresh every time the virtual tape file is sync'ed to disk.

User Action: None.

DLM825E: Volume <volser> is currently mounted on <devicename>, LOAD Command ignored

Description: The operator 'Load' command specified a drive that currently has a virtual volume loaded.


User Action: Wait for the specified drive to be free, or choose a different drive.

vt (DLM) Messages


136

DLM826W: Device <devicename> is already Ready/NotReady, READY/UNREADY command ignored

Description: The operator 'Ready' or 'Unready' command specified a drive that is currently in that state.


User Action: Specify the correct device and desired state in the command.

DLM828E: Nothing is currently mounted on <devicename>, command command ignored

Description: The operator Unload, Rewind, Ready, or Unready command specified a drive that does not currently have a tape loaded.


User Action: Specify the correct drive in the Unload, Rewind, Ready, or Unready command.

DLM829E: Device <devicename> is Ready, UNLOAD/REWIND/SET PATH command ignored

Description: The operator Unload or Rewind or Set Path command specified a drive that is in the Ready state.


User Action: If you want to manually unload or rewind or change the path of a device you must make in UNREADY first.

DLM830I: Device <devicename> made Ready/Unready

Description: The operator Ready or Unready command completed successfully.

System Action: The specified drive is now in the designated state.

User Action: None.

DLM831E: Invalid <parameter> value specified




vt (DLM) Messages


137

DLM832E: Invalid <parameter> value specified

Description: Syntax error on an operator command. Cannot set the same SCSI path to all devices



DLM834I: Device <devicename> tracelevel changed from n to n

Description: Normal response to an operator 'Set Trace ... DEV=' command.

System Action: The specified trace level was changed.

User Action: None.

DLM836I: ALL tracelevels set to n

Description: Normal response to an operator 'Set Trace ... ALL' command.

System Action: The specified trace level was changed.

User Action: None.

DLM839E: Unable to assess space for <path> (nnn)

Description: Virtuent was unable to obtain status information about the specified tape library subdirectory, in response to the. Query Space command.

System Action: This tape library subdirectory is skipped in the Query Space output.

User Action: Make sure that a valid tape library directory is specified in the configuration file for this device, that the directory is currently mounted and accessible, and that all subdirectories within the tape library are mounted and accessible. If the problem persists, contact EMC support for assistance.

DLM840I: Read-back write verification set to ON/DATA/OFF

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

System Action: When the Write Verify feature is set to ON or DATA, after every synchronization of data to the virtual tape during a write, the data will be read back to verify its integrity. If an error is found during the verification, a unit check is returned to the current Host write CCW that triggered the synchronization. ON checks just the headers of every block, DATA checks the integrity of all the data as well.

User Action: None.

DLM841I: System tracelevel is currently set to n

vt (DLM) Messages


138

Description: The tracelevel is displayed in response to the Query All command.


User Action: None.

DLM842I: System debuglevel is currently set to n

Description: The debuglevel is displayed in response to the Query All command.


User Action: None.

DLM843I: Filesystem stall detection threshold set to nnn minutes

Description: By default, a filesystem that has had uncompleted I/O pending for more than 5 minutes is considered "stalled". The time period for which a filesystem is considered stalled is configurable with the "SET StalledFilesystemThreshold=nnn command, or in the configuration file with the "StalledFilesystemThreshold nnn" option.

System Action: A stalled filesystems will be skipped when searching for a virtual tape during a mount request. When the stalled I/O completes, the filesystem will once again be used during mounts.

User Action: The default value of 5 minutes should be more than enough time to detect a stalled filesystem. Contact EMC Support before changing this value.

DLM844I: Device <devicename> OSADDR set to 'XXXX'

Description: The OSADDR value for this device has been changed. The OSADDR value is used with the VSE BTIMOUNT program to identify the name by which VSE knows a Virtuent 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 the Virtuent application will report the OSADDR value to BTIMOUNT when it completes a mount on ANY drive.

User Action: None.

DLM845I: Device <devicename> GROUP set to 'n'

Description: The GROUP value for this device has been changed. The GROUP value is used with the VSE BTIMOUNT program to identify drives that belong to the same VSE group as the control drive.

vt (DLM) Messages


139

System Action: The new GROUP value will be used to find a virtual device when BTIMOUNT requests a mount on ANY drive.

User Action: None.

DLM846I: AWS maps usage default value set to OFF

Description: An AWS map will not be written to an AWS file.


User Action: None.

DLM847I: Confirm stored CRC value in awshdr default value set to OFF

Description: With the value set to off, the stored CRC value in the aws header will not be confirmed.


User Action: None.

DLM848I: Device <devicename> maximum volume size changed from <oldsize> to <newsize>

Description: The operator SET SIZE= command was accepted for the specified device.

System Action: The maximum volume size was changed for the specified device. The SIZE change takes effect immediately.

User Action: None.

vt (DLM) Messages


140

DLM849I: Storing CRC value in awshdr default value set to OFF

Description: With the value set to off, the CRC value will not be stored in the aws header.


User Action: None.

DLM850I: Device <devicename> Label default changed from 'x' to 'x'

Description: The operator SET LABEL= command was accepted.

System Action: The default label value was changed for the specified device.

User Action: None.

DLM851I: ProtectVOL1 set ON/OFF

Description: By default, the virtual tape application prevents overwriting of VOL1 labels with data (ProtectVOL1=ON). The ProtectVOL1 feature can be disabled by entering the command "SET ProtectVOL1=OFF"; when off, it can be re-enabled with "SET ProtectVOL1=ON". The current ProtectVOL1 setting can be determined by entering the "QUERY ALL" command.

System Action: When the ProtectVOL1 feature is enabled, any attempt by the host to a VOL1 label with data is rejected with a unit check, with command reject sense.

User Action: None. It is recommended that the ProtectVOL1 feature be left enabled to protect against accidental corruption of tape volumes by errant mainframe software.

DLM852I: Full-erase set ON

Description: Virtuent has been configured to perform a more extensive erasure of data when a erasing of a virtual tape volume is requested. Most tape managers expect to find the complete original header label set on every scratched tape, but under some circumstances (for example, on a Unisys system), the full label set is not desirable.

System Action: By default, when erasing a virtual tape volume the VOL1 label, all HDRn labels, and one tapemark are retained. When the full erase option is set, only the VOL1 and two tapemarks are retained.

User Action: None.

DLM853I: Pending Mount Fairness (PMFAIR) set to <nnn>

Description: The PMFAIR option allows Virtuent to be configured to delay read and write I/Os while a tape mount operation is in

vt (DLM) Messages


141

progress. This can speed up tape mounts on a heavily loaded system, at a slight expense to overall throughput during tape mount operations. This option is off by default.

System Action: Every read and write I/O will be delayed by <nnn> milliseconds while a tape mount is in progress.

User Action: None.

DLM854W: Requested path already assigned to device <devicename>

Description: The device path requested is already assigned to this device.

System Action: The path is unchanged from the previous value.

User Action: None.

DLM855E: SCSI Tape Device <device path> does not exist

Description: The device path requested does not exist.



DLM856I: nn scratch synonyms: volser,volser,...

Description: This message displays any scratch synonyms that are defined in the configuration file.


User Action: None.

DLM857E: Error Invalid Path

Description: The Operator selected a path that requires a feature that is not licensed for use on this controller.


User Action: Contact EMC for more information on enabling the licensed feature.

DLM858I: Device <devicename> Data path deferred change from 'oldpath' to 'newpath'

Description: The operator SET PATH= command was accepted, but the specified device currently has a volume mounted.

System Action: The new data path will take effect immediately after the current volume is unmounted.

vt (DLM) Messages


142

User Action: None.

DLM859I: Device <devicename> Data path changed from 'oldpath' to 'newpath'

Description: The operator SET PATH= command was accepted.

System Action: The new data path will take effect immediately on the specified virtual tape drive.

User Action: None.

DLM860E: PATH= is no longer supported; use DEV= to specify the tape library

Description: The operator INITIALIZE command specified the obsolete PATH= parameter. Older versions of Virtuent supported a choice between using PATH= or DEV= to designate the tape library where the volumes would be initialized. The PATH= parameter is no longer supported, and DEV= is required.

System Action: The INITIALIZE command is ignored.

User Action: Do not specify PATH=, but use the required DEV= parameter on the INITIALIZE command. See HELP INITIALIZE for more information.

DLM861E: Tape library path not changed

Description: The SET PATH command has failed.



vt (DLM) Messages


143

DLM862E: Invalid volser <volser> for volume initialization

Description: The INITIALIZE command specified a volume serial number of 'SCRTCH' or 'PRIVAT', or beginning with 'BFL'. BFLxxx volsers are reserved for Data Exchange (flat) volumes, which cannot be pre-initialized on the library. Scratch volumes should be initialized with the actual volser desired, not by by using the word 'SCRTCH' or 'PRIVAT'.


User Action: Specify a valid volser that does not start with the prefix 'BFL' or ‘SCRTCH’ or ‘PRIVAT’.

DLM863E: SCSI Tape path already in use

Description: The SET PATH command has failed.


User Action: Set PATH= to a valid SCSI tape path that is not already in use

DLM864E: You can only create <nnn> volumes starting from <volser>

Description: The INITIALIZE command COUNT= parameter was too big for the specified starting volser.

System Action: The INITIALIZE command is rejected.

User Action: Use the HELP INIT command for more information about using the INITIALIZE command. Be sure that the specified COUNT value would not cause the numeric portion of the volser to overflow or the first two characters of the volser to change.

DLM865E: File '<filename>' [non-]scratch volume already exists

Description: While processing the INITIALIZE command, Virtuent found that the volume it is attempting to create already exists in the tape library, as either a scratch or non-scratch volume.

System Action: The new scratch volume is not created, and the original volume is unchanged.

User Action: Be careful to not create new scratch volumes in the range of existing volumes.

vt (DLM) Messages


144

DLM866E: File/Directory '<filename>' open failed, err=<nnn>: <error message>

Description: An I/O error occurred while attempting to create a new scratch volume.

System Action: The specified new scratch volume has not been created.

User Action: Refer to the `error message' portion of this message for an explanation of the error. Correct the error and try initializing the volume(s) again.

DLM867E: Error writing to <filename>: <error message>

Description: An I/O error occurred while attempting to create a new scratch volume.

System Action: The specified new scratch volume has not been created.

User Action: Refer to the `error message' portion of this message for an explanation of the error. Correct the error and try initializing the volume(s) again.

DLM868I: Too many errors have occurred, terminating

Description: Multiple errors have occurred during processing of the operator INITIALIZE command.

System Action: One or more new scratch volumes may have been created before the maximum number of errors occurred.

User Action: Review the messages prior to this one to determine the nature of the errors, and correct the errors and/or re-enter the correct INITIALIZE command.

DLM869I: nn Standard/ANSI-labeled volumes initialized

Description: Virtuent has completed an INITIALIZE command.

System Action: The specified number of new scratch volumes have been created.

User Action: None.

DLM870E: Device <devicename> Initializations not allowed in <tapelib>

Description: The tape library type assigned to this device does not support tape initialization. Volumes can only be initialized in tape libraries on direct-access filesystems.


User Action: Specify a DEV=device that has a tape library defined in a valid direct-access filesystem.

DLM871I: AttentionCount set to <value>

vt (DLM) Messages


145

Description: The configurable ATTENTIONCOUNT parameter has been set as shown.

System Action: The ATTENTIONCOUNT parameter defines how many times Virtuent should retry sending an asynchronous Ready interrupt should it be rejected by the channel or Host. The default number of retries is 45.

User Action: None.

DLM872E: Invalid SNn= value <value> (incorrect length)

Description: The operator SET command contained an incorrect serial number. The new serial number must be exactly twelve characters long.

System Action: The SET command is ignored.

User Action: Specify a valid value in the SET command. Use the 'Help' command to see the proper command syntax.

DLM873I: Attention set to <value>

Description: The configurable ATTENTION parameter has been set as shown.

System Action: The ATTENTION parameter defines which channel path(s) Virtuent should send a Ready interrupt to when a virtual tape drive comes ready. The possible values are: ALL - the interrupt is sent to every channel path established for this device; NONE - no interrupt is sent to any Host when a drive comes ready; ASSIGNED - the interrupt is sent to every channel path which has an Assignment in effect. An Assignment is typically made when a Host VARYs a drive online. This is the default action. PATHGROUP - the interrupt is sent to every channel path which currently has a Path Group ID (PGID) set. A PGID is typically set when a Host VARYs a path online. REQUESTER - the interrupt is sent only to the path from which the Load Display mount request was received.

User Action: None.

vt (DLM) Messages


146

DLM874E: Setting <parameter> requires a DEVICE= parameter too

Description: The operator SET command was entered without specifying a specific device to be set.

System Action: The <parameter> specified is ignored

User Action: This particular SET command <parameter> requires that a DEVICE= parameter be specified; re-enter the SET with a specific DEVICE specified. Use the 'Help' command to see the proper command syntax.DLM875I: Device <devicename> VOL= prefix changed from 'xx' to 'yy'

Description: The operator SET VOL= command was accepted.

System Action: The new volume serial prefix value takes effect immediately on the specified virtual tape drive.

User Action: None.

DLM876I: Unknown volumes will be treated as Scratch requests

Description: Normally, a request for a non-existent volume results in message DLM454E and the drive remains Not Ready. However, this controller has been configured to treat mount requests for non-existent volumes as if the request were for a scratch volume. This option only applies for devices connected to a Unisys mainframe.

System Action: Virtuent will proceed as if a SCRTCH volume was requested when a non-existent volume is requested, but only if the device is connected to a Unisys mainframe at the time.

User Action: None.

DLM877I: Support for VSE Host Utilities disallowed/allowed

Description: This virtual tape system was configured or SET to support the supplied VSE Host Utilities. This option should only be set if the supplied VSE utilities will be used; the default mode is to disable this support.

System Action: If the message says 'allowed', the supplied VSE Utilities will be supported by this virtual tape system. If the message says 'disallowed', the supplied VSE Utility programs will fail with command-reject I/O errors.

User Action: If you want to use the supplied VSE Utilities, enable this option; otherwise, leave this feature off by default.

DLM878I: <feature> enabled

Description: A special Virtuent debugging feature was enabled through configuration or with the SET command.

vt (DLM) Messages


147

System Action: The effect depends on the feature.

User Action: Special debugging features should only be enabled under direction of EMC support.DLM879I: [Device <devicename> / ALL devices] quiesced/unquiesced

Description: The QUIESCE or UNQUIESCE command was entered.

System Action: A quiesced device is in a state where it will not accept any new tape mounts until it is explicitly unquiesced (or until Virtuent is restarted). If a drive has a volume mounted at the time it is quiesced, it will continue to function completely normally; it will not accept another mount once the current volume is unloaded.

User Action: None.

DLM880I: GroupAccess set to 'R'

Description: By default, virtual tape files created by Virtuent are only accessible by the 'vtape' user. This message signifies that Virtuent is currently configured to allow other members of the 'vtape' user group to have Read access to the virtual tape files created by Virtuent.

System Action: All tapes created while this option is set will have group accessibility.

User Action: Reconfigure Virtuent if you do not wish other members of the 'vtape' group to have access to virtual tape files. Files that were created while this option was set will continue to be accessible by all members of the 'vtape' group unless the file permissions are manually changed by the administrator.

DLM881I: OtherAccess set to 'R'

Description: By default, virtual tape files created by Virtuent are only accessible by the 'vtape' user. This message signifies that Virtuent is currently configured to allow any user to have Read access to the virtual tape files created by the Virtuent.

System Action: All tapes created while this option is set will have global accessibility.

User Action: Reconfigure Virtuent if you do not wish everyone to have access to virtual tape files. Files that were created while this option was set will continue to be accessible by anyone unless the file permissions are manually changed by the administrator.

DLM882I: Disk usage warning percent changed from nn% to nn%

Description: The operator SET WARNING= command was accepted.

System Action: The new disk usage warning value takes effect immediately.

vt (DLM) Messages


148

User Action: None.

DLM883I: /var usage warning percent changed from nn% to nn%

Description: The operator SET VARWARNING= command was accepted. The VarWarning value is the percentage of usage of the /var filesystem at which point the system will begin warning that /var space utilization is high.

System Action: The new disk usage warning value takes effect immediately.

User Action: None.

DLM884I: Disk space RECOVERAMT changed from nn% to nn%

Description: The operator SET RECOVERAMT= command was accepted.

System Action: The new disk space recovery amount takes effect immediately.

User Action: None.

DLM885E: EXIT[!] and RESTART[!] are no longer supported.

Description: These commands are no longer supported.


User Action: To start/stop the VT service, use the command 'vtd' at an operating system prompt.

DLM886I: Disk space RECOVER percent changed to nn%

Description: The operator SET RECOVER= command was accepted.

System Action: The new disk space recovery threshold takes effect immediately.

User Action: None.

DLM887I: Channel adapter <n> serial number override set to <xxxxxxxxxxxx>

Description: The operator SET SNn= command was accepted.

System Action: The hardware serial number reported by Virtuent to the Host for channel adapter <n> has been set to the specified override value. If <xxxxxxxxxxxx> is blank, the override has been removed and Virtuent will report the actual hardware serial number once again.

User Action: None. Use the SET SNn= command to remove the override.

DLM888W: Warning: New serial number contains lower case letters!

vt (DLM) Messages


149

Description: The operator SET SNn= command was accepted, but the serial number specified contained one or more lower case alphabetic characters.

System Action: The specified serial number is accepted, and will be reported to the Host EXACTLY as you specified.

User Action: None, unless you really meant to type uppercase letters in the serial number. In that case, enter the command again with the proper value.

DLM889E: Encryption key n is not available

Description: The specified encryption key is not installed.

System Action: The ENCRYPTKEY value is not changed from the previous setting.

User Action: Specify a valid, installed key in the SET ENCRYPTKEY command.

DLM890E: Help has no additional information for 'something'

Description: The Virtuent command 'HELP something' was entered, but 'something' is not a valid Virtuent command or message number.


User Action: Use the 'Help' command alone to see a summary of the Virtuent commands available.

vt (DLM) Messages


150

DLM891E: Invalid command syntax

Description: The preceding operator command was invalid.



DLM892I: Write Sync set to nMB

Description: Virtuent has been configured to sync (flush) data written by the host to disk storage every <n> MB. This message is displayed whenever the option is changed, and is also displayed periodically if not set to 0.

System Action: Virtuent will flush the data to disk storage every <n> MB, or not at all if the <n> is set to 0.

User Action: For best performance, this option should be set to 0 (the default).

DLM893E: <feature> feature not yet supported

Description: The preceding operator command used a Virtuent feature that is not supported.



DLM894I: PenaltyUp/PenaltyDown value changed from <nn> to <nn>

Description: The operator SET PENALTYUP= or PENALTYDOWN= command was accepted. The PenaltyUp value is used to decrease the chance that a filesystem will be selected for the next scratch mount; it is applied every time a filesystem is selected for a scratch mount. PenaltyDown is used to reduce the penalty every time a filesystem is NOT selected for a scratch mount.

System Action: The new penalty value takes effect immediately.

User Action: None.

DLM896I: /var usage debugging limit changed from <nn> to <nn>

Description: The operator SET VARDEBUGLIMIT= command was accepted. The VarDebugLimit is the number of bytes remaining on the /var filesystem at which point the system will automatically turn off any debugging mode that generates console messages which go to /var.

System Action: The new threshold takes effect immediately.

User Action: None.

vt (DLM) Messages


151

DLM897E: Unexpected keyword parameter n 'keyword=value'

Description: Syntax error on an operator 'Load' command.



DLM898E: Unknown parameter n 'something'




DLM899I: <Thread> has been in state: <thread state> for <time> seconds

Description: The specified task has been in the specified state an unexpectedly long time. This most likely means that the task is "stuck" on some operation.

System Action: When the task is no longer in this state, message MAS900I will be displayed.

User Action: If these messages occur frequently, or the task does not transition back to normal, contact EMC Support for assistance.

DLM900I: <Thread> transitioned state

Description: The specified task was previously reported to be in a single state for an unusually long time (see DLM899I). This message is displayed when the task is no longer in that state.


User Action: None.

vt (DLM) Messages


152

DLM901E: Error reading Keyboard Data: <error message>

Description: An I/O error has occurred while reading a command from the keyboard.

System Action: The Virtuent application terminates.


DLM902E: Zero Bytes read from Keyboard

Description: An I/O error has occurred while reading a command from the keyboard.

System Action: The Virtuent application terminates.


DLM908E: Error formatting message for SNMP trap: error message

Description: An error has occurred while formatting a message before evaluation by the SNMP agent.

System Action: The message will be sent to the SNMP agent as is, but might not be perfectly formatted.


DLM910W: Device <devicename> <deliberate error message>

Description: This message immediately precedes a deliberate error performed by the Virtuent application, caused by setting a debugging mode for testing purposes.

System Action: A deliberate error of some kind will follow this message.

User Action: None. Don't be surprised by the error that follows. If you get this message unexpectedly, contact EMC support for assistance.


Description: This message immediately precedes a deliberate error caused by the Virtuent application, caused by setting a debugging mode for testing purposes.



vt (DLM) Messages


153


Description: This message immediately precedes a deliberate error caused by the Virtuent application, caused by setting a debugging mode for testing purposes.



DLM920E: Device <devicename> volume <volser> overwriting of VOL1 label blocked

Description: The virtual tape application prevented overwriting of this tape's VOL1label with data, because the ProtectVOL1 feature is currently enabled.

System Action: The host write command is rejected with a unit check, with command reject sense.

User Action: The ProtectVOL1 feature can be disabled by entering the command "SET ProtectVOL1=OFF"; when off, it can be re-enabled with "SET ProtectVOL1=ON".

DLM921I: Set ProtectVol1=OFF to enable VOL1 overwrites

Description: This message follows MAS920E as a reminder that the ProtectVOL1 feature can be turned off if overwriting a VOL1 label with data is desired.


User Action: The ProtectVOL1 feature can be disabled by entering the command "SET ProtectVOL1=OFF"; when off, it can be re-enabled with "SET ProtectVOL1=ON".

DLM930I: Device <devicename> contingent allegiance to <pathinfo> for <time> seconds

Description: A "contingent allegiance" is established between a device and the host from the time any unit check is presented to the host until the host performs a sense or other I/O operation to this device, or a selective reset or a system reset to this device, on the same channel path. Until the allegiance is cleared, this device will remain busy and will be unavailable for I/O on all other channel paths. This informational message will be displayed if a device remains in this type of contingent busy condition for an inordinate amount of time.

System Action: Until the host clears the contingent allegiance on the specified path, no I/O can be performed on this device.

vt (DLM) Messages


154

User Action: If these messages occur frequently, or the drive does not transition back to normal, contact EMC Support for assistance.

DLM940I: Device <devicename> Volume <volser> accommodated old-style AMDD DSS block #nnnnnn (file 'filename').

Description: Earlier virtual tape application releases could write incorrect metadata in a virtual tape block under certain specific rare conditions. Subsequent reading of such a block would result in a 341E CRC error message and return an error to the host. Later releases, including this one, automatically recover from this metadata error without returning an I/O error to the host. This message is displayed strictly for informational purposes.


User Action: None.

DLM950I: Message from Host

Description: A Host program has sent this message to be displayed on the Virtuent console.


User Action: None.

DLM951I: Message from another program

Description: An external program has sent this message to be displayed on the Virtuent console.


User Action: None.

DLM952E: Unable to get hostname

Description: The application was unable to get the hostname of the system

System Action: Unable to continue.

User Action: Verify that the hostname of the system is set correctly.

vt (DLM) Messages


155

DLM953I: DD Lock Parameter Set

Description: The application has been configured for Volser Locking.

System Action: Use external lock files when locking a volser (files: .lkVOLSER)

User Action: None.

DLM957I: Locking with NLM lock manager turned ON/OFF

Description: By default, virtual tape files on Celerra NFS filesystems are locked against concurrent usage by other nodes by using the Network Lock Manager (NLM) protocol (and .lk lock files for all other filesystems). The application can be configured to not use NLM and to instead use .lk lock files for virtual tapes on all types of filesystems.

System Action: If NLM locking is turned OFF, all locking of virtual tape files is performed with .lk lock files. If NLM locking is turned ON, files on Celerra NFS filesystems are locked with NLM, and with .lk files on all other types of filesystems.

User Action: Contact EMC Support for more information before changing file locking.

DLM970I: FTIDC Parameter Set ON/OFF

Description: The controller has been configured for FTIDC.

System Action: When set ON, the system will not check if a different VOL1 label volume serial number is being written on writes.

User Action: None.

DLM971E: Error closing input/output fifo: <filename>

Description: Virtuent received an error while closing the specified file. This error can only happen during program termination.



vt (DLM) Messages


156

DLM972E: Error deleting input/output fifo: <filename>

Description: Virtuent received an error while closing the specified file. This error can only happen during program termination.



DLM975I: Diagnostic data written to file '<file>' (<num> bytes)

Description: The diagnostic data was written to <file>


User Action: None.

DLM976E: Error writing diagnostic data dump file '<file>': open error <error detail>

Description: The diagnostic data could not be written to <file>.


User Action: If this problem recurs, contact EMC Support for assistance.

DLM979E: Error writing diagnostic data dump file '<file>': open error <error detail>

Description: The diagnostic data could not be written to <file>.


User Action: If this problem recurs, contact EMC Support for assistance.

DLM980E: Program Check error in thread nnnn (processname), state=XXXXXXXX

Description: An internal program error has occurred.

System Action: Virtuent attempts to shut down all virtual devices. All devices are taken offline to the Host, and Virtuent terminates.


vt (DLM) Messages


157

DLM981E: Program Check type 'error type'

Description: An internal program error has occurred.

System Action: Virtuent will terminate.


DLM990I: Shutting down this application...

Description: Virtuent is terminating.

System Action: Virtuent terminates.

User Action: None.

DLM991E: Error shutting down device <devicename>

Description: An error occurred while attempting to shut down a virtual device.

System Action: Shutdown continues..


DLM992W: <n> volumes mounted; use vtd to force shutdown

Description: The operator 'EXIT' or 'RESTART' command was entered while one or more virtual tape drives had a volume mounted.


User Action: Before shutting down, wait for all Host applications to finish and unload their tapes. If for some reason the Host cannot unload all of the Virtuent devices, manually unload all virtual tape volumes with the Virtuent 'UNLOAD' command. If, for some other reason, the Virtuent 'UNLOAD' command cannot unload all the Virtuent devices, the vtd force command will force a shutdown even while tapes are mounted.

DLM994E: Required service <service name> failed, unrecoverable <error detail>

Description: A required system service has failed and is unrecoverable.


User Action: Determine why the service has failed and correct it. For more assistance, contact EMC Support.

DLM999E: Terminating app

Description: The application is terminating because of some kind of fatal startup error.

System Action: The application terminates.

vt (DLM) Messages


158

User Action: Review any preceding message(s) to determine the cause of the problem. For more assistance, contact EMC Support.


159

vtd Messages

vtd is the script which starts the Virtuent application (vt). It is invoked by clicking on the "Start Virtuent Devices" icon on the Virtuent desktop. The following messages may be displayed by vtd while starting the Virtuent application:

vtd: Interface #n fw version xxxx newer than filename version yyyy vtd: Not loading older firmware

The script has determined that the firmware on the channel adapter card (xxxx) is actually newer than the firmware file found on the system disk (yyyy). The adapter firmware will not be changed.

vtd: Interface #n fw version xxxx older than filename version yyyy vtd: Loading newer firmware

The script has determined that the firmware on the channel adapter card (xxxx) should be updated to a newer version found on the system disk (yyyy), and is doing so.

vtd: Interface #n fw version xxxx same as filename version yyyy vtd: No need to reload firmware

The script has determined that there is no need to update the firmware on the channel adapter card.

vtd: Error loading firmware into slot nnnnnn (Interface n)!

An error occurred while attempting to load new firmware into the channel adapter card. Contact EMC support if you need additional assistance in determining the cause of this problem.

vtd: Error rebooting slot nnnnnn (Interface n) firmware!

An error occurred while rebooting the firmware on the channel adapter card. Contact EMC support if you need additional assistance in determining the cause of this problem.

vtd: n channel adapters found

Information message to display the number of channel interfaces found in the system.

vtd: No channel adapters installed, or driver not presently loaded

vtd Messages


160

No channel adapters could be located. Contact EMC support if you need additional assistance in determining the cause of this problem.

vtd: unable to determine filename firmware version!

An error occurred while trying to determine whether the channel adapter firmware should be updated. Contact EMC support if you need additional assistance in determining the cause of this problem.


161

z/OS System Messages

DLMCMD The following messages may be issued by the DLMCMD program running on the mainframe.

DLC010I I/O ERROR ON CTRL DEVICE: CSW=XXXX SENSE=XX

An I/O error occurred on the DLMCMD control tape. Refer to the CSW and SENSE information and any additional messages on the z/OS and controller consoles to resolve the problem.

DLC040I CONTROL PATH FAILED TO OPEN

DLMCMD was unable to open the DLMCTRL control tape. Check the JCL and any additional messages on the z/OS console or job log to resolve the problem.

DLC050I LOG FILE FAILED TO OPEN

DLMCMD was unable to open the DLMLOG log file. Check the JCL and any additional messages on the z/OS console or job log to resolve the problem.

DLC060I COMMAND FILE FAILED TO OPEN

DLMCMD was unable to open the input DLMCMD file. Check the JCL and any additional messages on the z/OS console or job log to resolve the problem.

DLC070I ENTER COMMAND

The PARM=WTOR parameter told DLMCMD to read input from the console. Enter a command to send to the controller, or END to terminate DLMCMD.

DLC182I WARNING: DRIVE xxxxx IS ONLINE. SHOULD BE OFFLINE WHEN USING DEV=

The control drive being used should be an offline device. Results are unpredictable in an online device is used.



162

DLMLIB Messages

The following messages may be issued by the DLMLIB program running on the mainframe.

DLL100I INVALID VOLSER xxxxxx SPECIFIED

An invalid volser was specified in the input file. Correct the input and re-run.

DLMSCR Messages

The following messages may be issued by the DLMSCR program running on the mainframe.

DLS010I I/O ERROR ON CTRL DEVICE: CSW=XXXX SENSE=XX

The control tape that sends scratch requests to the controller had an I/O error. Check to make sure the controller is still running. If this is the case use the CSW and SENSE provided to correct the problem.

DLS012I UNEXPECTED HEADER IN SCRATCH REPORT

While processing the scratch report DLMSCR found a header it not expecting. First make sure that the TYPE parameter is correct for the scratch report you are running. If so make sure the scratch report is of the correct format.

DLS020I NO VALID SCRATCH REQUESTS PROCESSED

DLMSCR processed the entire scratch report and found no valid scratch requests. First check the PREFIX and PREFIXLN parameters to make sure they correctly match the tape prefixes used on the Virtuent controller. If they are correct make sure that the scratch report contains tapes with those prefixes.

When this message is issued vtscr will end with a return code of 02.

DLS030I INPUT SCRATCH REPORT FAILED TO OPEN

The DLMSCR input scratch report failed to open. Check the DD statement for the DLMSCR input file and make sure it refers to a valid scratch report file.

DLS031I INPUT SCRATCH REPORT NOT RECFM=F OR FB

The scratch report, which is created by the customer’s TMS, must have a LRECL of 133 and a RECFM of F or FB.



163

DLS040I BTI040I CONTROL PATH FAILED TO OPEN

The DLMSCR control tape failed to open. Make sure the controller is up and running and the unit address used for the DLMSCR control tape is a valid controller device and has been varied online to the mainframe.

DLS050I BTI050I LOG FILE FAILED TO OPEN

DLMSCR maintains a log file with all the error and informational messages from any DLMSCR runs. Check the mainframe job log to determine why it did not open properly.

DLS060I SORTIN FILE FALED TO OPEN

DLMSCR requires a sortin file when processing a Tivoli Storage Manager (TSM) report.

DLS070I INPUT FILE IS NOT A NEW SCRATCH REPORT

DLMSCR requires the date on the Scratch Report that is created by the customer’s TMS to be today’s date. This is to prevent the inadvertent use of an old scratch report. Run a new scratch report.

DLS080I This is a request to free space from scrach tapes. Reply YES to continue

DLMSCR requests operator intervention before it frees space from scratched tapes. This is because after space is freed the data on scratched tape cannot be retrieved.

DLS081I FREExxxxx NOT ALLOWED WITH TYPE RMMDV

RMMDV has its own format, please see the documentation on RMMDV

DLS100I NO INPUT PARAMETERS FOUND

DLMSCR requires at least the TYPE= parameter be configured, please check the format of your input parameters.

DLS110I NO type FOUND IN INPUT PARAMETERS

DLMSCR requires the TYPE= parameter, please check your input parameters.

DLS111I UNKNOWN type FOUND IN INPUT PARMS

DLMSCR has found an incorrect TYPE= parameter, please check your input parameters.

DLS120I Freespace not confirmed - terminating

DLS080I did not receive a response of yes, scratched tapes will not be erased.

DLS130I PREFIX LENGTH INVALID

The default for the PREFIXLN is 2. In most cases the customer will be using 2 for their prefix length. If the tape library resides on Centera a prefix length of 1 is



164

common. In that case PREFIXLN=1 should be coded. Check your input parameters.

DLS140I SORT FAILED

The internal sort performed on a Tivoli Storage Manager (TSM) report failed. Refer to preceding console messages for the reason.

DLS150I INVALID DEV SPECIFIED

The parameter specified in the DEV= field is <3 or >4 characters, or contains non-hexadecimal characters. Correct the parameter and retry the job.

DLS160I DEVICE NOTE DURING UCBLOOK

The device specified on the DEV= parameter was not found in the active configuration. Correct the parameter and retry.

DLS170I ERROR DURING UCB CAPTURE / UNCAPTURE

A failure occurred attempting to capture / uncapture a 24-bit UCB address from a 31-bith one. Contact product support.

DLS180I DRIVE IS ALREADY ALLOCATED OR BOXED

The device specified on the DEV= parameter is either already in use or is boxed and cannot be used. Select a different drive and retry the job.

DLS181I DRIVE HAS NO ONLINE PATHS

The device specified on the DEV= parameter has no online paths available. Select a different drive and retry the job.

DLS182I WARNING: DRIVE xxxxx IS ONLINE. SHOULD BE OFFLINE WHEN USING DEV=


DLS190I DEBCHK FAILED

An internal DEBCHK macro returned a non-zero return code. Contact product support.



165

DLMHOST Messages

The following messages may be issued by the z/OS started task DLMHOST:

DLH000I COMMANDS ARE: STARTLOG,N=VTEname/ALL STOPLOG,N=VTEname/ALL STARTCMD,N=VTEname/ALL STOPCMD,N=VTEname/ALL N=VTEname/ALL,C=command HELP STATUS

Issued in response to a help or ? command. Followed by a list of eligible commands.

STARTLOG initiates/restarts logging from a single VTE or all VTEs. Logging device paths must already exist.

STOPLOG terminates logging from a single VTE or all VTEs.

STARTCMD initiates/restarts the command path from a single VTE or all VTEs.

STOPCMD terminates the command path from a single VTE or all VTEs.

N=VTEname C=command will pass the specified command to the designated VTE. The response will go to the operator or to the file designated by DLMLOG if parameter LOGFILE is used.

HELP or ? will produce the DLM000I messages.

STATUS will show the current status as indicated in DLH240I.

DLH001I jobname ENTER COMMAND, EOJ, OR ? FOR HELP

If the WTOR option is used, this is issued as the outstanding WTOR that the operator can reply to.

DLH002I jobname USE MODIFY TO ENTER COMMAND, EOJ OR ? FOR HELP

If the NOWTOR option is specified, this message indicates to the operator that the MODIFY command is available to issue requests.

DLH010I I/O ERROR ON DEVICE XXXX: CSW=XXXX SENSE=XX

An error occurred on one of the control paths. Appropriate CSW and sense data are provided.

The control path will be marked as inactive.

DLH030I CONFIG FILE FAILED TO OPEN



166

The file pointed to by the DLMCFG DD failed to open.

DLH040I CONFIG FILE INVALID RECFM

The recfm of the DLMCFG file is not F or FB.

DLH050I LOG FILE FAILED TO OPEN

The file pointed to by the DLMLOG DD card failed to open

DLH055I INPUT COMMAND FILE FAILED TO OPEN - IGNORING DOCMDS PARM

If the DOCMDS parameter is used, the DLMCMD DD card is missing or file failed to open.

DLH060I CANNOT START - PROGRAM ALREADY ACTIVE

Only one copy of DLMHOST is allowed to run at a time. This can be overridden by specifying parameter NOENQ

DLH150I INVALID DEV SPECIFIED

One of the devices specified is not a tape device.

DLH160I DEVICE NOT FOUND DURING UCBLOOK

The DEV= parameter is specified, but the device does not exist in the current configuration.

DLH170I ERROR DURING UCB CAPTURE/UNCAPTURE

An error occurred while capturing/uncapturing a 24-bit UCB address from a 31-bit one.

DLH180I DRIVE xxxx IS ALREADY ALLOCATED or BOXED

The designated device is already in use or is boxed

DLH181I DRIVE xxxx HAS NO OPERATIONAL PATHS

The designated device is marked as having no operational paths

DLH182I WARNING: DRIVE xxxxx IS ONLINE. SHOULD BE OFFLINE WHEN USING DEV=




167

DLH200I NODENAME NOT FOUND IN CONFIG TABLE

The VTEname specified in a command/modify request does not exist in the config table.

Use the STATUS command to list the available VTEnames.

DLH210I INVALID DEVICE xxxx IN CONFIG TABLE

The specified device contains invalid hexadecimal digits

DLH220I NODENAME NOT SPECIFIED IN COMMAND

A command was entered, and did not contain a VTEname as the target of the command

DLH230I NO COMMAND FOUND IN RESPONSE

There was no C= or CMD= in the operator request.

DLH240I NODENAME CMDDEV LOGDEV CONSNAME

This will be followed by one line showing the status for each VTE, path and console assignment.

NODENAME is the name assigned in the config table

CMDDEV shows the device (if any) assigned as the command path. A y/n indicates if it is currently active.

LOGDEV shows the device (if any) assigned as the log path. A y/n indicates if it is currently active.

CONSNAME shows the console name (if any) assigned to receive log messages from this VTE.

DLH250I NODE VTEname PATH xxxx INACTIVE

A command was requested to be issued to a command path that is marked inactive.

DLH260I PROCESSING COMMAND: command line

The DOCMDS parameter was used. This lists each command processed from the DLMCMD file as it is being processed.



168

GENSTATS Messages

GEN010I I/O ERROR ON CTRL DEVICE: CSW=XXXX SENSE=XX

An I/O error has occurred on the GENSTATS control tape device named with the DEV= parm. Processing stops. Try rerunning the job. Contact EMC support if the problem reoccurs.

GEN030I INPUT STATISTICS FILE FAILED TO OPEN

GENSTATS was unable to open the input file. Check your JCL and rerun. Contact EMC support if the problem reoccurs.

GEN040I VOL= PARM REQUIRED WHEN DEV= IS USED

When DEV= is used, GENSTATS must be told which VOLSER it is to process. Add the VOL= parameter and rerun the job.

GEN050I MOUNT FOR VOLSER XXXXXX FAILED TO COMPLETE

GENSTATS was trying to mount a virtual tape volume and the mount failed to complete. Check your JCL and retry.

GEN031I OUTPUT REPORT FILE FAILED TO OPEN

GENSTATS failed to open the SYSPRINT file. Check your JCL and retry.

GEN032I SORTIN FILE FAILED TO OPEN - REQUIRED FOR STILLINUSE PARM

GENSTATS requires the following JCL when the STILLINUSE report is request:

//SORTIN DD (temporary work file) //SORTOUT DD (temporary work file) //SYSOUT DD SYSOUT=*

Make sure these DD statements are in your JCL and rerun the job.

GEN140I SORT FAILED - CHECK LISTING

GENSTATS requires the following JCL when the STILLINUSE report is request:

//SORTIN DD (temporary work file) //SORTOUT DD (temporary work file) //SYSOUT DD SYSOUT=*

Make sure these DD statements are in your JCL and rerun the job. If the job still fails check the sort SYSOUT messages to identify the reason for the sort failure.



169

GEN150I INVALID DEV SPECIFIED

The parameter specified in the DEV= field must be 3 or 4 characters and must be a hexadecimal number.

GEN160I DEVICE NOT FOUND DURING UCBLOOK

The device specified on the DEV= parameter was not found in the active configuration. Correct the parameter and rerun the job.

GEN170I ERROR DURING UCB CAPTURE/UNCAPTURE

A failure occurred attempting to capture or uncapture a 24-bit UCB address from a 31-bit address. Contact EMC support.

GEN180I DRIVE IS ALREADY ALLOCATED or BOXED

A device specified on the DEV= parameter is either already in use or is boxed and cannot be used. Select a different drive and retry the job.

GEN181I DRIVE HAS NO ONLINE PATHS

The device specified on the DEV= parameter has no online paths available. Select a different drive and retry the job.

GEN182I WARNING: DRIVE xxxxx IS ONLINE. SHOULD BE OFFLINE WHEN USING DEV=


GEN190I DEBCHK FAILED

An internal DEBCHK macro returned a non-zero return code. Contact EMC support.

GEN200I DEVICE TABLE OVERFLOW

More than 2000 active devices were found in the input GENIN file. Add the DEVCNT=xxxx parameter to increase the tape size appropriately and rerun the job.

GEN300I DATE TABLE OVERFLOW - LIMIT RANGE

The internal date tape default of 128 days was exceeded. Either limit the range with DATESTART / DATEEND, or increase the default date table size with DAYCNT=xxxx.

GEN310I SYNCTIME REQUIRES THAT DATEEND BE SPECIFIED

The SYNCTIME parameter can only be used with the DATEEND parameter. Add an appropriate DATEEND parameter and retry the job.

GEN320I SYNCTIME FORMAT INVALID (HH:MM:SS)



170

The SYNCTIME parameter must be specified in the format HH:MM:SS. Correct the parameter and retry the job.

GEN400I PATHNAME TABLE OVERFLOW

The internal pathname table default of 512 pathnames was exceeded. Add the PATHCNT=xxxx parameter and rerun the job.

GEN450I VOLSER TABLE OVERFLOW

The internal volser table default of 2200 currently mounted volumes was exceeded. Add the VOLCNT=xxxx parameter and rerun the job.

GEN500I INPUT FILE WAS EMPTY - PROBABLE SCRIPT ERROR

The GENIN input file is empty. This is likely caused by a script error in the first step of the GENSTATS job. Check the script being run by DLMCMD and then retry the job.


171

VSE System Messages

VSE system messages are output by EMC supplied software running on an IBM VSE system.

DLMSS(D E) REXX Script Messages

DLM001I: MOUNTED NNNNNN VOLUME ON DEVICE CCUU

Description: Successfully mounted the requested volume.

System Action: Normal processing.

User Action: None.

DLM002I: INVALID PARAMETER – CONTACT SUPPORT

Description: The REXX script DLMSS has passed incorrect parameters to the assembler subroutine DLMLDSPL.

System Action: The mount request is not processed

User Action: If the problem persists, end the REXX DLMSS job by issuing the console command MSG nn,DATA=HI (where nn is PARTID where DLMSS is running). Save the SYSLST output containing a PDUMP and restart the DLMSS job.

DLM003I: CHECK CONTROLLER IS OPERATIONAL AND ONLINE

Description: The controller is not accessible from VSE.

System Action: The mount requests are not processed until the controller is made operational. The REXX DLMSS job will continue processing.

User Action: Make sure the controller is powered up, configured properly, and online.

DLM004I: NO UNMOUNTED VIRTUAL ADDRESS AVAILABLE

Description: Sense byte 23 = x’80’. A request to mount a volume on any available virtual tape address could not be completed because there are no unmounted addresses available.

System Action: The REXX DLMSS job will continue to issue mount requests until an address becomes available.

VSE System Messages


172

User Action: This can occur if tapes are left mounted after processing. Issue the VSE command VOLUME TAPE on the console and check that all of the mounted volumes are in use. Any volume not in use can be unloaded by pausing a partition and issuing the VSE command MTC RUN,cuu (where cuu is the address of the virtual tape).

DLM005I: NO UNMOUNTED VIRTUAL ADDRESS AVAILABLE FOR THIS VSE

Description: Sense byte 23 = x’81’. In a VM/VSE environment, a request to mount a volume on any available virtual tape address configured on the controller for this VSE could not be completed because there are no unmounted addresses available.

System Action: The REXX DLMSS job will continue to issue mount requests until an address becomes available.


DLM006I: NO SUCH ADDRESS CCUU ON CONTROLLER

Description: Sense byte 23 = x’82’. A mount was issued for specific virtual tape address that has not been defined on the controller.

System Action: The mount will not be processed. The REXX DLMSS job will continue to issue mount requests.

User Action: Refer this problem to your administrator. There may be a configuration problem between VM and/or VSE and the controller.

DLM007I: SPECIFIED ADDRESS CCUU IS IN USE

Description: Sense byte 23 = x’85’. A mount was issued for specific virtual tape address that is currently in use.

System Action: The REXX DLMSS job will continue to issue mount requests until the address becomes available.

User Action: None.

DLM008I: INVALID REQUEST – CONTACT SUPPORT

Description: Sense byte 23 = x’90’. The controller has detected an invalid parameter in a LOAD DISPLAY CCW from the assembler subroutine DLMLDSPL.

VSE System Messages


173

System Action: The mount request is not processed. The REXX DLMSS job will continue to issue mount requests.

User Action: If the problem persists, end the REXX DLMSS job by issuing the console command MSG nn,DATA=HI (where nn is PARTID where DLMSS is running). Save the SYSLST output containing a PDUMP and restart the DLMSS job.

DLM009I: UNKNOWN ERROR-CONTACT SUPPORT

Description: Sense byte 23 is unrecognized. The controller has passed an unknown sense byte 23 back to the assembler subroutine DLMLDSPL.

System Action: The mount request is probably not processed. The REXX DLMSS job should continue to issue mount requests.

User Action: If the problem persists, end the REXX DLMSS job by issuing the console command MSG nn,DATA=HI (where nn is PARTID where DLMSS is running).Save the SYSLST output containing a PDUMP and restart the DLMSS job.

DLM010I: VOLUME CURRENTLY IN USE OR NOT ACCESSIBLE

Description: Sense byte 23 = x’88’. The controller experienced an internal I/O error on the tape library file system.

System Action: The mount will not be processed. The REXX DLMSS job will continue to issue mount requests.

User Action: None. If this problem persists, report it to your administrator. Check the controller’s log file.

DLMSCR Messages

DLM100I: CHECK VIRTUAL TAPE DEVICE AND RERUN


System Action: The job is cancelled.


DLM101I: NO VALID DELETE REQUESTS FOUND

Description: There were no volumes owned by the controller to be scratched.


User Action: None.

VSE System Messages


174

DLM102I: DYNACC CALL ERROR XX

Description: The CA-Dynam DYNACC interface module returned an error.

System Action: Refer to the CA-Dynam documentation for DYNACC return codes.

User Action: A dump is produced. Refer this problem to your systems programmer.

DLMDTSCR Output Log Error Messages

INVALID DATA LENGTH

Description: Sense byte 23 = x’01’. The load display command sent to the controller was invalid.

System Action: The volume is not scratched on the controller.

User Action: Contact Support.

VOLUME PREVIOUSLY SCRATCHED

Description: Sense byte 23 = x’02’. The volume to be scratched has already been scratched.

System Action: None. The volume was probably scratched in a previous run.

User Action: None.

DUPLICATE COPIES EXIST

Description: Sense byte 23 = x’03’. Should not occur. There are both a scratched and a non-scratched version of the dataset on the controller.


User Action: Manually delete one of the versions on the controller. Report this problem to Support.

INVALID VOLUME SERIAL NUMBER

Description: Sense byte 23 = x’05’. The volume serial number is invalid.

System Action: none.

User Action: None.

VOLUME IN USE ON CONTROLLER

Description: Sense byte 23 = x’06’. The volume to be scratched is currently mounted on the controller.

VSE System Messages


175


User Action: None.

VOLUME NOT FOUND

Description: Sense byte 23 = x’07’. The volume to be scratched is not on the controller.


User Action: None.

I/O ERROR WHILE DELETING




FILE IS LOCKED

Description: Sense byte 23 = x’09’. The controller’s file for this volume is not accessible because it is locked by another application.

System Action: The volume is not scratched on the controller’s.

User Action: Report this problem to your administrator.

CANNOT ACCESS TAPE LIBRARY

Description: Sense byte 23 = x’0A’. The Directory for the tape library is not available. Possibly it has not been mounted to a mount point.



TAPE LIBRARY NOT WRITEABLE

Description: Sense byte 23 = x’0B’. The Directory for the VTAPE library is not Writeable. Possibly it is configured with incorrect parameters.



FILE NOT WRITEABLE

Description: Sense byte 23 = x’12’. The controller’s file for this volume is not Writable. Possibly it has been manually configured incorrectly.

VSE System Messages


176



UNKNOWN SENSE CODE RETURNED

Description: Sense byte 23 contained an invalid value.


User Action: A PDUMP is written to SYSLST. Report this problem to Support.

DLMEPSCR Messages

DLM200I: CHECK CONTROLLER VTAPE DEVICE AND RERUN




DLM201I: NO VALID BTXXXX DELETE REQUESTS FOUND

Description: There were no volumes owned by the controller to be scratched.


User Action: None.

VSE System Messages


177

DLM202I: TSIDAC2 CALL ERROR X

Description: The BIM-EPIC TSIDAC2 interface module returned an error.

System Action: Refer to the BIM-EPIC documentation for TSIDAC2 return codes.

User Action: A dump is produced. Refer this problem to your systems programmer.

DLM203I NO POOL ID PARM ON EXEC STMT.

Description: You must supply a parm for the pool ID.


User Action: Supply a parm and rerun the job.

DLMEPSCR Output Log Error Messages

INVALID DATA LENGTH

Description: Sense byte 23 = x’01’. The load display command to the controller was invalid.


User Action: Contact Support.

VOLUME PREVIOUSLY SCRATCHED

Description: Sense byte 23 = x’02’. The volume to be scratched has already been scratched.

System Action: None. The volume was probably scratched in a previous run.

User Action: None.

DUPLICATE COPIES EXIST

Description: Sense byte 23 = x’03’. Should not occur. There is both a scratched and a non-scratched version of the dataset on the controller.


User Action: Manually delete one of the versions on the controller. Report this problem to Support.

VSE System Messages


178

RESERVED

Description: Sense byte 23 = x’04’.


User Action: None.

INVALID VOLUME SERIAL NUMBER

Description: Sense byte 23 = x’05’. The volume serial number is invalid.


User Action: None.

VOLUME IN USE ON CONTROLLER

Description: Sense byte 23 = x’06’. The volume to be scratched is currently mounted on the controller.


User Action: None

VOLUME NOT FOUND

Description: Sense byte 23 = x’07’. The volume to be scratched is not on the controller.


User Action: None

I/O ERROR WHILE SCRATCHING




FILE IS LOCKED

Description: Sense byte 23 = x’09’. The controller file for this volume is not accessible because it is locked by another application.



CANNOT ACCESS TAPE LIBRARY

VSE System Messages


179

Description: Sense byte 23 = x’0A’. The directory for the VTAPE library is not available. Possibly it has not been mounted to a mount point.



TAPE LIBRARY NOT WRITEABLE

Description: Sense byte 23 = x’0B’. The directory for the VTAPE library is not writeable. Possibly it is configured with incorrect parameters.



INVALID OR MISSING VOL1 LABEL

Description: Sense byte 23 = x’0C’. The Volume Label is corrupted.



VOLUME SERIAL NUMBER MISMATCH

Description: Sense byte 23 = x’0D’. The Volume Label does not match the linux filename



FILE NOT WRITEABLE

Description: Sense byte 23 = x’12’. The controller file for this volume is not writable. Possibly it has been manually configured incorrectly.


User Action: Report this problem to your administrator

UNKNOWN SENSE CODE RETURNED

Description: Sense byte 23 contained an invalid value.


User Action: A PDUMP is written to SYSLST. Report this problem to your administrator.

DLMMOUNT Messages

DLM301I: DLM001I MOUNTED NNNNNN VOLUME ON SYS004

VSE System Messages


180

Description: Successfully mounted the requested volume.

System Action: Normal processing.

User Action: None.

DLM302I: INVALID PARAMETER PASSED

Description: An invalid parameter is on the EXEC statement.

System Action: The mount request is not processed.

User Action: Check the EXEC DLMMOUNT statement for a proper PARM. Refer to the manual.

DLM303I: CHECK CONTROLLER IS OPERATIONAL AND ONLINE

Description: The unit is not accessible from VSE.

System Action: The mount request is not processed.

User Action: Make sure the unit is powered up, configured properly, and online.

DLM304I: NO UNMOUNTED DLMTUAL ADDERSS AVAILABLE

Description: Sense byte 23 = x’80’. A request to mount a volume on any available virtual tape address could not be completed because there are no unmounted addresses available.

System Action: The mount is not processed. The job step ends with a return code of 999.


VSE System Messages


181

DLM305I: NO UNMOUNTED DLMTUAL ADDRESS AVAILABLE FOR THIS VSE

Description: Sense byte 23 = x’81’. In a VM/VSE environment, a request to mount a volume on any available virtual tape address configured on the controller for this VSE could not be completed because there are no unmounted addresses available.



DLM306I: NO SUCH ADDRESS

Description: Sense byte 23 = x’82’. A mount was issued for specific virtual tape address that has not been defined on the controller.

System Action: The mount is not processed. The job step produces a PDUMP and ends with a return code of 999.

User Action: Check the PARM on the EXEC DLMMOUNT statement. Make sure the tape address on the PARM is a valid controller address.

DLM307I: SPECIFIED ADDRESS IS IN USE

Description: Sense byte 23 = x’85’. A mount was issued for a specific virtual tape address that is currently in use.


User Action: Make sure the device address on the PARM is available and rerun the job.

DLM308I: INVALID REQUEST – CONTACT SUPPORT

Description: Sense byte 23 = x’90’. The controller has detected an invalid parameter in a LOAD DISPLAY CCW from DLMMOUNT.


User Action: Save the SYSLST output containing a PDUMP and notify your systems programmer. If necessary, manually mount the volume on the controller console.

DLM309I: UNKNOWN ERROR - CONTACT SUPPORT

VSE System Messages


182

Description: Sense byte 23 unrecognized. The controller has passed an unknown sense byte 23 back to DLMMOUNT.


User Action: Save the SYSLST output containing a PDUMP and notify your systems programmer. If necessary, manually mount the volume on the controller console.

DLM310I: CONTROLLER VOLUME CURRENTLY IN USE OR NOT ACCESSIBLE



User Action: Rerun the job. If this problem persists, report it to your administrator. Check the controller’s log file.


183

emc disk library for mainframe dlm1000 - dell emc brazil · pdf fileemc® disk library for...

Documents