BackBox®E4.07...

BackBox® E4.07Messages Manual and Troubleshooting

Published: February 2019Edition: H06.06, J06.06 or L06.06 RVUs, or subsequent H-series, J-series or L-series RVUs

Legal Notice

© Copyright 2019 ETI-NET Inc. All rights reserved.

Confidential computer software. Valid license from ETI-NET Inc. required for possession, use or copying.

The information contained herein is subject to change without notice. The only warranties for ETI-NETproducts and services are set forth in the express warranty statements accompanying such products and services. Noth-ing herein should be construed as constituting an additional warranty. ETI-NET shall not be liable for technical or editorial errors or omissions contained herein.

BackBox, BackPak, BackHome, BCOM, HCOM, EZX-Gateway, and BackLib are registered trademarks of ETI-NET Inc.

StoreOnce is a registered trademark of Hewlett Packard Development, L.P.

Microsoft, Windows, and Windows NT are U.S. registered trademarks of Microsoft Corporation.

Tivoli Storage Manager (TSM) is a registered trademark of IBM Corporation.

QTOS is a registered trademark of Quality Software Associates Inc.

All other brand or product names, trademarks or registered trademarks are acknowledged as the property of their respective owners.

This document, as well as the software described in it, is furnished under a License Agreement or Non-Dis-closure Agreement. The software may be used or copied only in accordance with the terms of said Agreement. Use of this manual constitutes acceptance of the terms of the Agreement. No part of this manual may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, and translation to another programming language, for any purpose without the written permission of ETI-NET Inc.

Messages Manual and Troubleshooting | 3

Table of Contents

Introduction 4Logs and Traces 4

NonStop Log 4Traces in NonStop 4Logs and Traces in VTC Server 5VTC Log Files 5TSM API Log and Traces 8Logs in the Workstation 8

Messages 12Messages 13

Appendix 120Common and Special Cases 120

Tape Subsystem Reset Procedure 120TCP/IP Connection Errors from the NonStop 122Error 190 on a NonStop Virtual Tape Drive 122$BBEXT EMS Extractor Abend at Start-up 124DSM/TC Tape Volume Jammed INUSE or SELECTED State 124$ZSVR or MEDIACOM Hang 125Windows Disk File Being Used by Another Process 125ABORT TASK Reported by the VTC Emulator 126Error Triggering a NonStop Utility 126Devices Connected Through SCSI Bridge Don’t Reconnect After Server Maintenance 127WARNING from SQL [6008]: Statistics … 128Shares and Files Access 128

Disk Shares 128Sub-Directories 128Local Disks 129File Access Security 129

Troubleshooting Copy Pool Sync 129


INTRODUCTIONThis manual applies to all BackPak family products. The numbered messages issued by the any of the BackPakproducts are described in the section Messages.

Logs and TracesIn addition to the immediate symptoms present on the output of a tape application or on a UI page, an error inthe may issue messages in the NonStop EMS log.The various sources of information for troubleshooting are detailed below.

NonStop Log

The EMS log is the main console for the . For all abnormal events occurring during regular operations or duringinstallations and updates, the EMS log must be first consulted.EMS will display:

l The messages from the NonStop tape system.l The messages from the NonStop components.l A copy of the most important messages logged by on the Windows platform.

The distribution set contains an EMS filter and an OBEY file (OEMS) to extract and transfer all tape related mes-sages to an Enscribe file. Before executing OEMS, it should be edited to specify a time interval.The OEMS2 OBEY file (executed by the command “RUN OEMS2”) extracts and transfers the current tape mes-sages to the TACL home-terminal. It is very useful to have the OEMS2 running when troubleshooting.The EMS log provides details about different symptoms shown in the UI.For an issue related to the operation of a tape device, check the EMS at the time the mount request has beenissued by $ZSVR. If the tape device is not attached to the node running the Domain Manager, but is attached toa different peripheral node, obtain the EMS from both nodes.

Traces in NonStop

It is possible to trace the domain internal activity on the NonStop. The trace is activated in the UI domain con-figuration page:

l Set the Trace Level to 1.l Enter a Trace sub-volume that will receive the trace files. This sub-volume must be dedicated to receiv-

ing traces. As the trace will produce many files, the Trace Level should be reset to "0" as soon as pos-sible.

When sending the traces to ETI-NET support, it is recommended to PAK everything in both the trace sub-volume and in the file BBSVCFG.

5 | Messages Manual and Troubleshooting

Logs and Traces in VTC Server

Windows Event Logs

software records to the following Windows event logs:

Log Name / Event Logs Source

Virtual Tape Controller All VTC services, except for the Script Controller

VTC Script Controller Only the Script Controller

BackPakUILog Only for the UI running locally

The provided message event number corresponds to the message numbers documented in Messages section.Normal operations, such as tape load and tape unload are reported systematically. Important messages, suchas errors and device starting/de-activation messages are logged in Windows and forwarded to the NonStopcomponent for logging in the EMS.This Event log is managed by Windows; therefore, the old entries are deleted.

VTC Log Files

All logs are saved in C:\ProgramData\ETINET\VTC\Log . This directory can be reached using the BackPakDefault Folder from the Windows START button (2008-R2 and 2008/ 2012):In Windows 2012, go to the UI start panel and type “BackPak” in the search field. All related program(s) andfolder(s) starting with “BackPak” will be listed.


Several logs are internal and only used by technical support.users may consult, if needed, the script logs located in the sub-directories \Log\Script\<data-store-id>\.

AdmLog.log is written by the VTC Admin service. This service is controlled by the VTC Management Console. Formore information refer to E4.07 User Manual.AdmTCP/IPSession_<n>.logThis file logs the TCP/IP connection to the VTC Admin service.These logs are automatically purged: up to 5 or 10 occurrences of these files of limited size are produced in around-robin fashion.EndOperationLog_<n>.log


This file forwards tape unload messages to the Domain Manager on the NonStop.These logs are automatically purged: up to 5 or 10 occurrences of these files of limited size are produced in around-robin fashion.EVMessageLog_<n>.logThis file forwards local messages to the NonStop EMS.These logs are automatically purged: up to 5 or 10 occurrences of these files of limited size are produced in around-robin fashion.FCLog.log is written by the VTC Emulator (FC) serviceAll Emulator service start-ups and every severe errors, although logged in this log, are not purged auto-matically. Detailed tracing (more than level 1) must not be kept enabled for long periods of time.Additional entries are written if VTC tracing is enabled through the UI, by modifying the Advanced Propertiesof the configuration.To enable the traces:

1. Set the Trace Level to 16 > Update > Save the configuration.

2. Run the tape application on NonStop.

3. Set the Trace Level to "0" > Update > Save the configuration.

This trace control works correctly only when a receives activity (load requests) from a singledomain. This may require stopping EMS Extractors of domains sharing the same VTC, but whichhave a different trace setting for the VTC.

It is also possible to control the trace level using the VTC Management Console.FCTCPIPSession_<n>.logThis file logs the TCP/IP connection to the VTC Emulator (FC) service.These logs are automatically purged: up to 5 or 10 occurrences of these files of limited size are produced in around-robin fashion.Installation.log is written by the BackPak SETUP.EXE installer.LB<label>.log is written by the various services accessing the storage of virtual volumes.A file is written per labeled virtual volume. For “unlabeled volumes”, the file name is NL<pseudo-label>.log.These logs are written only if the tracing is enabled in BBSL.OPT and in very specific cases, such as when errorsare detected during the checking of the integrity of a tape volume stored through the TSM API.These files are not purged from old entries. Detailed tracing (more than level 1) must not be kept enabled forlong periods of time.MESMessageLog_<n>.logThis file forwards local messages to the NonStop EMS and is a complement to EVMessageLog_<n>.These logs are automatically purged: up to 5 or 10 occurrences of these files of limited size are produced in around-robin fashion.ScriptControllerBackupNskSession_<n>.logThis file forwards local messages to the NonStop EMS and is a complement to EVMessageLog_<n>.ScriptControllerLog_<n>.logThis file provides messages written by the Script controller handling BACKUP requests.ScriptControllerLogR_<n>.logThis file provides messages written by the Script controller handling RESTORE requests.ScriptControllerRestoreNskSession_<n>.logThis file forwards local messages to the NonStop EMS and is a complement to EVMessageLog_<n>.\Script\<data-store-id>\ sub-directories


Each executed Windows script leaves its output in a file located in a sub directory named according the DataStore ID of the involved virtual volume: \Script\DataStoreId\.The log file is named according executed script with a suffix from #1 to #1000, in order to re-use the samefiles and avoid cleanup tasks.These logs contain the messages output by the Enterprise Backup clients run by the scripts.Example:C:\ProgramData\ETINET\VTC\Log\\Script\WIN1\

ADMIN_BACKUP.CMD#1#EMULFC_BACKUP.CMD#1#EMULFC_BACKUP.CMD#2#EMULFC_RESTORE.CMD#1#

C:\ProgramData\ETINET\VTC\Log\Script\WIN2\EMULFC_BACKUP.CMD#1#EMULFC_BACKUP.CMD#2#EMULFC_RESTORE.CMD#1#

TSM API Log and Traces

For the used in conduit mode with the IBM Tivoli Storage Manager API, consult the appropriate documentation.C:\ProgramData\ETINET\VTC\Log\DSIERRORLB<label>.logIt is the TSM API log for operations related to the tape volume <label>.These logs are always created and left empty if there is no error.TSM API TraceThe TSM API can produce very detailed traces. If directed to the WINDOWS system disk, these traces can be lar-ger than the data processed and can make the server crash.The level of trace and the trace file is controlled by the DSM.OPT file used for tape emulation. The setting isdynamic; each load request will initiate a new session with the TSM API.In the distributed sample DSM.OPT, these commented options control the trace:*TRACEFLAG INSTR_API GENERAL*TRACEFLAG ALL,-NLS*TRACEFILE d:\trace\dsmtrace1.txtRemove the ‘*’TRACEFLAG INSTR_API GENERAL will produce less traces than ALL,-NLS.

Logs in the Workstation

The UI sends occasional messages to the Windows Event logging facility and saves them in a log named Back-PakUILog or BackPakUI Events.It also keeps a log of all exchanges between the UI and a Domain. The files are located in C:\Pro-grammData\ETINET\UI\Log and are named following this convention: TCPIPSession_ DOMAINENAME#.log,where DOMAINENAME# is a domain name with which the UI communicates, and the # represents a sequentialfile number (from 1 to 5).Case Information for Product SupportTo document a case for Product Support certain tools are used to collect the necessary information.These tools must be executed in each system in order to produce a set of (one or more) files.

l The information must always be collected from the NonStop hosting the Domain.l If the tape application was running on a peripheral NonStop system, the information must be collected


from this system as well.l For issues with tape emulation or storage, the information must be collected on the VTC involved.

All files produced using these tools must be sent to Product Support.

Collecting Data on the NonStop

In the main NonStop system \NSK1 of the domain:VOLUME <domain-installation-subvol>LOAD /KEEP 1/ BBSETUP MACROSBB000_COLLECT TARGET <domain-trace-subvol>[,TIME <time-of-incident>][, COLLECTOR $process][, LISTALL yes|no]]

Parameters:TARGET Subvol

Required sub-volume where the files will be created. It is recommended to specify the trace sub-volume configured in the domain

[TIME <yyyy-mm-dd [hh:mn[:ss]]>]This is optional; it shows the time of an incident that will be used as a basis from which to extractEMS messages.The messages produced from 24 hours before this time and up to one hour after will be extracted.The current time is used as a default value.00:00:00 is the default when a date is specified without time of day.

[COLLECTOR process]Optional; it is the EMS collector process name from which the messages will be extracted.$0 is used as default value.

[LISTALL yes|no]LISTALL YES produces the list of the PAK content (i.e. send the LISTALL parameter to the BACKUP pro-gram).NO is used as the default value.

In a peripheral NonStop system \NSK2 of the domain:VOLUME <event-extractor-installation-subvol>LOAD /KEEP 1/ \NSK1.<domain-installation-subvol>.BBSETUPLOAD /KEEP 1/ \NSK1.<domain-installation-subvol>.MACROSBB000_COLLECT TARGET \NSK1.<domain-trace-subvol>, & TIME <time-of-incid-ent>

On each NonStop, BB000_COLLECT must be executed in the sub-volume where a program BBEXT is located. Themacro will output the name of two files to send:

----> Two files to pick up:----> binary file \ETINIUM.$DATA05.BPAKTRC.COL222P----> text file \ETINIUM.$DATA05.BPAKTRC.COL222A

Collecting Data on the VTC

To start the collecting process on a VTC system, use the BackPak Collecting Ticket Information option avail-able via the start button.In 2012 R2 use the search option in the Start panel, type BackPak and select the collecting option.


The collected data can be specified in a dialog window presented for verification and confirmation. The defaultparameters are appropriate for most cases.

Windows System FrameFrom … To … Period for selecting the Windows Event LogsSystem System Windows Event LogApplication Application Windows Event LogSecurity Security Windows Event LogMsInfo32 Report produced by Microsoft tool msinfo32.exe

Virtual Tape Controller Software FrameFrom … To … Period for selecting the BackPak Event LogsVirtual Tape Controller VTC Event Log


VTC Script Controller VTC Script Controller Event LogBackPakUIlog UI Client Event Log, all files in C:\ProgramData\ETINET\UI\Log

Save Information to FrameDirectory Where the Zip File Will Be CreatedThe file name is auto-generated by the log collection tool.

The location should not be the same as the one used for the configuration and logs (by default,saves its configuration files and logs them under the current logged user Documents folder).

A PowerShell log is displayed along with the collection of the various data elements. MSiNfo32 can require sev-eral minutes.


MESSAGESEMS is the console for the HPE NonStop tape system. EMS serves as well as:

l console for NonStop componentsl partial logs duplicate system of the MS-Windows components

This manual lists the messages that can be logged in the EMS or displayed by the Web user interface. Mes-sages are displayed with a prefix that identifies the message origin, the message number, and a letter report-ing the event severity:I Information / Normal completionW WarningE ErrorF Fatal errorA Program ABENDIn addition, the important messages are highlighted as Alert messages.

The severity is just an indication of the result of an elementary action and it might not be rep-resentative of the final importance of the message. For example, a failed tape load is not critical ifthe load is automatically retried successfully a short time afterward. But a warning reporting a lowstorage space condition may prove to be critical.

The Alert Messages can be chosen by Configuration, by Domain Page, or by Alert Window.Alert Messages are chosen by selecting the highlighted messages.In addition, the Alert Window can duplicate all the Alert Messages with the single message number 3171 forselection and action, such as email by a tier-party software monitoring the EMS.

Message Prefix

Origin Message Prefix

VT Controller [VTC]-[domain]-[severity][msgNumber]

Domain Manager [domain]-[severity][msgNumber]

EMS Extractor [$processName]-[severity][msgNumber]

Where:[VTC] is the VT Controller ID,[domain] is the Domain ID[severity] is the severity letter I,W,E,F or A[$process name] is the EMS Extractor process name[msgNumber] is the message number from 1 to 5 digits

Below are samples for the three formats of message prefix, involving the domain BBOX, the VTC BB1, and theEMS extractor process $BBEXT:

BBOX-BB1-I103 Service started (VTC Virtual Tape Devices)

BBOX-W3186 Automatic unload of volume ZXE042 that was loaded since2016-04-21 11:48:53 on \ETINIUM.$VX31301 that is free. Application pro-cess \ETINIUM.0,232 started on 11:48:34 is no longer running.


$BBEXT-E3007 MountId: \MONT.974. No available virtual device to mountLMW108. W3125 Error communicating with VT Controller(s): HAPPY.

Technical interface to EMS messagesAll messages are identified with the EMS and with the following attributes:

l Subsystem owner = ETINET

l Subsystem number = 100

l Subsystem version = 100

l Message number = as documented in the column ‘Number’ of the table of messages building this doc-ument.

There is no EMS token beyond the identification of messages.The BackPak distribution set contains a filter for the HPE EMS distributor filter to extract all tape related mes-sages from HPE tape subsystems and from the ETI-NET BackPak. This filter is used in an OBEY file and a macrofile:OBEY OEMS Extraction of tape related messages to a disk file.RUN OEMS2 Extraction of tape related messages to the home terminal of a TACL session.

MessagesIn the table below are listed all the error messages, identified by an event message number and a descriptivetext. The Explanation and the Action columns are for user's reference only.

EventMessageNumber

Text ExplanationAction /Comment

1 %1. An error occurred in the VTController during theRead/Write to a virtualvolume.

TSM DataStore: Refer tothe IBM Tivoli Messagesmanual.Windows file DataStore:Refer to the Microsoft doc-umentation.

103 Service started (VTC Admin). The service implementingthe administrative service inthe VT Controller has star-ted.

None.

104 Service stopped (%1). A service stopped in the VTController.

None.

106 Could not initialize WinSockDLL, error %1.

Internal error at servicestart-up in a VT Controller.

Contact Product Support.

107 Service handler is not Internal error at service Contact Product Support.


installed. start-up in a VT Controller.

108 Service is not installed: %1,%2 (%3).

Internal error at serviceinstallation in a VT Controller.


109 Service is not updated: %1(%2).

Internal error at Windowsservice installation in a VTController.


110 Access Service error: %1(%2).



111 Service RegKey error: %1(%2).



112 Service cannot start. There isno %1 target mode adapterfound on the server.

Warning message indicatingthat the SCSI (or FC) servicecannot start because no cor-responding SCSI (or FC) hard-ware/driver was found onthe server.

None, if the server doesn’tcurrently have the hard-ware corresponding to theservice that cannot start.(The service should ideallynot be configured for Auto-matic start-up in Windows).If the hardware is presentand the corresponding ser-vice cannot start, refer tothe Installation Guide toreview hardware and thedriver installation step.

113 Error while initializing per-formance counters: %1 (%2)- %3.

The internal performancemonitoring is not functional.Other functionality is not affected.

Search for other error mes-sages in the Windows EventLogs.

114 Error starting service %1:(%2) - %3.

Internal error occurring whilestarting the service specifiedin %1 position.

Search the code (%2) inthis document for appro-priate explanation andaction.

115 %1 target mode adapterinstallation does not con-form to server model spe-cification.

Technician installed AttoHBA in wrong PCIe slot.

Technician needs to re-install HBA in accordancewith installation Field spe-cification manual.


116 Catch an unhandled excep-tion in initialization of %1.%1 may not be available untilVTC server restart is com-plete.

Internal error occurring whilestarting the service after asoftware upgrade. Featurespecified in %1 position willnot be available until theserver restarts.

Schedule a restart of theserver as-soon-as possible.

117 Only HOST, FC or EXTERN porttypes are allowed in VTR con-figuration.

VTR limitation. Start the VTC ManagementConsole and modify porttype that is not in com-pliance with the VTR.

118 Maximum of 2 FC port typesare supported in VTR con-figuration.

VTR limitation. Start the VTC ManagementConsole and disable unusedports by setting them tothe HOST type.

119 Maximum of 8 virtual tapedevices are supported in VTRconfiguration.

VTR limitation. Start the VTC ManagementConsole and modify numberof virtual devices to reachmaximum support.

120 Maximum of 1 Domain is sup-ported in VTR configuration.

VTR limitation. Start the VTC ManagementConsole and modify numberof Domain addresses toreach maximum support.

999 Error code: %1, Reason: %2,Other information: %3.

Technical information aboutan error returned by the Win-dows operating system.

Search for other error mes-sages in the Windows EventLogs.

1001 Guardian error %1 from %2%3.

A Guardian procedure callfailed.

Refer to the Guardian Pro-cedure Errors and MessagesManual.

1002 AWAITIOX completes witherror %1, %2 tag %3.

Guardian AWAITIOX pro-cedure call failed.


1003 AWAITIOX completes withwarning %1, %2 tag %3.

Guardian AWAITIOX pro-cedure call ended with awarning.


1004 Abort in %1 %2, error code%3 %4.

Severe internal error. Refer to the Guardian Pro-cedure Errors and MessagesManual.


1005 No memory available for %1. Memory allocation failed. Contact Product Support.

1006 Unexpected tag %1. Internal error. Contact Product Support.

1007 Guardian Error %1 detail %2from %3 %4.

A Guardian procedure callfailed.


1008 Internal limit %ld reached for%s. %s".

A program limitation hasbeen reached.


1009 Missing tag %s in %s. An XML tag is missing in atransaction.


1101 Warning: trace file %1unavailable, errno: %2.

Error accessing the DomainManager trace file.


1102 Unable to open|read|writefile %s '%s' error %ld.

Error accessing a standardC/stream file.


1103 BB000_ COLLECT producedthe binary file %s and textfile %s.

Information reporting theresult of BB000_ COLLECTmacro initiated through theUI.

Note the file's name tosend to Product Supportalong with the error codenumber.

1104 BB000_ COLLECT failed. %sfile name not found in theoutput file %s.Browse the Utilities log fileconfigured in the domainpage (currently %s).

Error while executing theBB000_ COLLECT macro ini-tiated through the UI.

The cause of error must besearched in the executionoutput.The execution output is spe-cified in the domain con-figuration as Log Outputwith the default value$NULL.

1105 BB000_ COLLECT can only berun from TACL prompt onthe Peripheral node %swhere the EMS Extractor didnot yet run successfully.

For a peripheral node, theBB000_ COLLECT macro can-not be initiated through theUI until BBEXT has been run.

Execute BB000_COLLECT at TACL prompt when thedefault subvol is the install-ation subvol in the peri-pheral node.

1106 %s %s version %s (serial%sxx.xx) is incompatible withDomain Manager version %s

Components were installedfrom products that do nothave the same distributionchannel

Complete the installation ofa single package.


1501 *** SQLCA display of SQLstatement at: BBDBM_Get_Tapefile_fileid.#2.616 of pro-cess \MONT.$Z0RC.*** ERROR from SQL [6008]:Statistics or partitions for atable were not available, sothe access path chosenmight not be the best avail-able.*** ERROR from SQL [-3015]:Syntax error

Error messages generatedby SQL

Refer to the HPE NonStopSQL/MP Messages Manual.Some messages can besolved by the user, as in themessage [6008] (exampleshown opposite).

1502 SQLCA struct version %d,error nbr=%d, SQLCA over-flow=%d, %s, %ld, %d

Possible complement to mes-sages 1501 above

See message 1501.

1508 SQLCAGETINFOLIST error %ditem %d

Error retrieving SQL info toproduce message 1502

Use as a complement tomessage 1501.

2001 Idle session terminates. TCP/IP session started butdid not receive a command.

None, if no other symptomsappear

2002 Timeout during processingstate.

No reply from a Guardian ora VT Controller servicebefore the configured Pro-cessing Timeout value.

Verify if the NonStop oper-ating system and the tapesubsystem ($ZSVR,MEDIASRV, TMFSRV) areoperating normally.Contact Product Support, ifthe timeout cannot beexplained.

2003 Config file %1 unavailable. The BBSVCFG file is not avail-able.

Check that the file createdis not locked by an applic-ation outside of the DomainManager.Check the Guardian User IDin session has authorized toaccess this file.

2499 Invalid XML attribute: %s in%s.

Error parsing an XML syntax. Contact Product Support.

2500 XML attribute %s not foundin %s.

Error parsing an XML syntax. Contact Product Support.


2501 XML parse error in %1 line%2 col %3: ‘%4’.

An XML syntax error is detec-ted at the specified location.

Manual editing of XML syn-tax: Fix the syntax.BBSVCFG updated by theDomain Manager:Contact Product Support.

2502 Unknown element name %1in %2

An XML tag is not known bythe Domain Manager

Verify if all components ofthe domain are at the sameversion: BBSV, BBEXT onNonStop, UI, VTC services.Manual editing of XML syn-tax: Fix the syntax.BBSVCFG updated by theDomain Manager:Contact Product Support.

2503 Invalid %1 in %2: %3 Invalid content for an XMLtag


2506 End tag %1 does not matchstart tag %2 in %3.

Invalid XML syntax.Most often a consequence ofa previous error.


2507 Unexpected element name%1 as root in %2.

An XML document name isunknown.


2508 Config file %s not availablefor rewrite, errno: %Id.

Guardian error when access-ing the configuration fileBBSVCFG for update.

Check the error code, thefile definition and the secur-ity attributes.

2509 Cannot save the current con-fig file in the backup file %s,errno: %Id.

Guardian error when savingthe previous version ofBBSVCFG.

Check the error code, thefile BBSVCFGO definitionand the security attributes.

2510 Cannot re-open config file%s for backup, errno: %Id.

Guardian error when savingthe previous version ofBBSVCFG.


2511 Config file updated. Backupin %s.

The Domain configurationfile BBSVCFG has beenupdated.

None.


2512 EXPAT %s error %ld. Internal parsing XML syntax. Contact Product Support.

2601 Maximum number of TCP/IPoutput buffers exceeded %1.

Internal buffers for thesocket reply are insufficient.


2602 Out of memory to allocateoutput buffer.

Internal buffers for thesocket reply, are insufficient.


2603 Socket error %1 on %2. TCP/IP error. Refer to the HPE NonStopTCP/IP ProgrammingManual. Socket errors.

2604 Socket error %1 on com-pletion of %2

TCP/IP error. Refer to the HPE NonStopTCP/IP ProgrammingManual. Socket errors.

2605 Program parameter missing:accept address

The Domain Manager doesnot receive the expectedparameter from theLISTNER.


2606 TCP accept address ‘%1’should contain a dot



2607 TCP accept address ‘%1’should be numeric



2608 TCP accept address ‘%1’rejected by inet_addr()



2609 Inbound socket closed whenprocessing %1

The TCP/IP client closed thesession before receiving thereply.Might be caused by a Webbrowser session abruptlyclosed.

None, if no other symptomshows up.

2610 Unable to solve TCP/IPaddress name %s, geth-ostbyname() error %d

The TCP/IP configuration inuse does not resolve theaddress name.

Check the spelling of theaddress name.Check the configuredTCP/IP DEFINEs.


2611 Socket error %1 at connectto address %2 port %3

Unable to establish a TCP/IPsession with the specificaddress.

Refer to the HPE NonStopTCP/IP ProgrammingManual.Check spelling of addressand port.Check configured TCP/IPDEFINEs.

2612 Socket error 3504 onsocket_nw(), check if the con-figured TCP process name isqualified by an invalid nodename.

A socket IO completed abnor-mally.

Check the TCP/IP settingfor =TCPIP^PROCESS^NAMEin the domain con-figuration, VT Controllerpage.

2613 Invalid data length %ureceived on socket %s. %s.

Invalid data in the com-munication stream.


2614 Socket error %d when ini-tiating connection to address%s port %s.

Communication error Check the TCP/IP con-nectivity from the NonStopto the specified address.

2615 Unable to solve TCP/IPaddress name %s, get-addrinfo() error %ld - %s.

Communication error Check the TCP/IP con-nectivity from the NonStopto the specified address.

2616 Exceeded limitation. %s A product limitation isexceeded. Limitations varydepending on the VTRproduct.Number of VTC servers in theconfiguration exceeds themaximum of 2.The number of NonStopnodes in the configurationexceeds the maximum of 2.

Remove the unauthorizedconfiguration.

2617 Deletion of Volume %s rejec-ted. Volume has not expiredaccording to the originalexpiry date %s. To delete any-way, specify 'force' in the UIVolume Delete confirmationwindow.

Safety check prevents dele-tion of a volume that hasbecome SCRATCH before itsupcoming expiry date.Actual test is done on theexpiry date in the first tapeheader HDR1 seen by theVTC during the backup.However, deletion can belegitimate, for example when

This safety check can bebypassed in the UI using theVolume deletion con-firmation page.There is no bypass in thebatch macro BB017_ FREE_EXPIRED that deletes theexpired storage (by select-ing SCRATCH volumes).Volumes skipped by BB017


a user deletes a backup thathas become useless byMEDIACOM DELETETAPEFILE… making a volumeSCRATCH in DSM/TC beforeits anticipated expiration.

must be deleted in the UIusing the options Force andDelete storage.See the User's Manual fordetails on the Volume Dele-tion procedure.

3001 Volume not found in catalog%1 %2.

A volume label to mount orprocess is not found in thecatalog.

None. Volume is not Man-aged by .

3002 Device %s.%s is not managedby the Domain.

A device object of a com-mand is not in the domainconfiguration.

It should not happen in astable configuration.Restart the web session orthe EMS Extractor.

3003 Invalid device %1 for mount-ing virtual volume %2

Cannot mount a virtualvolume on a real tape device.

Check TAPE DEFINE of thetape application. If spe-cified, both the device andthe volume should be eitherreal or virtual.

3004 Invalid volume label %1 to bemounted on a virtual device

Cannot mount a real volumeon a virtual tape device.

Check TAPE DEFINE of thetape application. If spe-cified, both the device andthe volume should be eitherreal or virtual.

3006 Volume must be specified in%s transaction

An operation cannot be pro-cessed because the volumelabel is missing.

Specify the tape volume.Use TAPECATALOG DEFINE,or specify a particularvolume label.

3007 MountId: %1.%2. No free vir-tual device to mount %3

No free device. Manual mount: Retry later.Automatic mount: None,the mount will be retried.

3008 MountId: %1.%2. Can notmount %3 on device %4:device not free

Device is not free. Manual mount: Retry later.Automatic mount: None,the mount will be retried.

3011 MountId: %1.%2. Error %3loading %4 on %5 %s

An error occurred in the VTController.

Fix error according to thetext message.If the problem cannot besolved, contact Product Sup-port.


3012 Device %1 unknown byDSM/TC

A Guardian device name inthe Domain configuration isunknown by DSM/TC.

Fix the Guardian devicename in the Domain Con-figuration.

3013 No virtual device defined innode %1 to mount %2

A mount command isreceived for a Guardian nodethat has no virtual device.

Check the Domain Con-figuration.Do not run BBEXT on aGuardian node that has novirtual device.

3015 VT Controller %1 in drive %2definition is unknown

Referential integrity error inthe Domain Configuration.


3016 MountId: %1.%2. Volume %3%4 is not defined for auto-matic load

Automatic load is rejectedbecause the volume was cre-ated with the attribute “Noautomatic load”.

Issue a manual mount.

3018 DataStore %1 recorded forvolume %2-%3 is unknown

The DataStore where avolume was stored is nolonger defined in the DomainConfiguration.

Define the DataStore in theDomain Configuration.

3019 Duplicate routes forDataStore %1, VT Controller= %2

Error in the Domain con-figuration.


3020 DataStore Id ‘%1’ is unknown Error in the Domain Con-figuration.


3021 MountId: %s. No active VTC isa route between the NSKnode and the DataStore %sfor mounting %s

The Domain Configurationdoes not contain an active VTController route to accessthe named DataStore.

Configure or activate a VTCthat:- has a tape device con-nected to the NSK nodewhere to mount the volumeis a route to theDataStore where thevolume was created.

3022 MountId: %s. MountId forvolume %s is no longerpending.

The tape mount id asso-ciated with a load request isnot in the list of pendingmounts in MEDIACOM.

Check if the application isstill running.

3023 MountId: %1.%2. %3(label)loaded on %4(device). %5.

A mount request was suc-cessfully executed.

None.


3024 Invalid user name or pass-word

A Guardian log on procedurefailed.

Check Guardian user nameand password.

3025 Add volume %1 label Type %2in pool %3 catalog %4 rejec-ted by MEDIASRV code %5.

An error occurred whileupdating a DSM/TC catalog.

Refer to the DSM/TC Man-agement Programming HPENonStop manual.

3026 Must be logged SUPER groupto execute this command

An error occurred whileupdating a DSM/TC or TMFcatalog.

Sign off using a GuardianUser ID on the UI.

3027 Adding volume %1 in pool %2of catalog %3 is rejected byDSM/TC

An error occurred whileupdating a DSM/TC catalog.No error code supplied.

Try to use MEDIACOM tocatalog the virtual volume.

3028 VT Controller %1 is unknown Referential integrity error inthe Domain Configuration.


3029 Volume %1 not added inDSM/TC catalog – invalidvolume catalog %2

Invalid volume catalog namein the Domain Configuration.

Fix the configuration ofVolume Group.

3030 Volume %1 not added inDSM/TC catalog – invalid pool%2

Invalid pool name in theDomain Configuration.

Fix the configuration of theVolume Group orcreate the missing poolusing MEDIACOM.

3031 Drive %1 declared invalid byMEDIASRV

Invalid Guardian device namein the Domain Configuration.

Fix the Guardian devicename or Guardian nodename in the VT Controllerdefinition.

3032 Volume group %1 is unknown Requested volume group isunknown in the Domain Con-figuration.


3033 Info volume %1 label Type%2 in pool %3 catalog %4rejected by MEDIASRV code%5

An error occurred whileaccessing a DSM/TC catalog.

Refer to DSM/TC Man-agement Programming HPENonStop manual.

3034 No available route toDataStore %1

There is no VT Controllerdefined as a route to the spe-cified DataStore, when cre-ating or deleting a volume.

Define a route to theDataStore in the Domainconfiguration.

3035 Numeric suffix in ‘%1’ not suf- When requesting the cre- Reduce the number of


ficient to compute %2 labels ation of a number ofvolumes, the label of the 1stvolume does not allow all therequested labels to be cre-ated.

volumes to create oruse more numeric char-acters at the end of the 1stlabel to be created.

3036 Unable to create %1 volumesstarting at label %2: %3-%4already exists in domain cata-log

One of the volume labels tobe created already exists inthe catalog of virtualvolumes.

Specify a series of labelsthat are not alreadyregistered as virtualvolumes.

3037 Invalid DataStore Id %1 involume group %2

Referential integrity error inthe Domain Configuration.


3038 Volume %1 not added inDSM/TC catalog – alreadyexists with label type %2 andstatus %3 in pool %4 ofvolcat %5

The creation of volumes thatmust also be in DSM/TCstops because a volume isalready cataloged with astatus other than SCRATCH.

Check the status of thevolume in DSM/TC.Create volumes with dif-ferent labels.

3039 TMF tapemedia %1 alreadyexists on node %2 withincompatible status ormedium (not SCRATCH or notTAPE)

The creation of volumes thatmust also be cataloged inTMF stops, because a volumeis already cataloged with astatus other than SCRATCH.

Check the status of thetape media in TMF.Create volumes with dif-ferent labels.

3040 TMF is not configured onnode %1

The Domain Configurationspecifies a TMF catalog on aGuardian Node that is notconfigured for TMF.

Check the TMF GuardianNode in the Volume Groupconfiguration.

3041 Add TMF media %1 on node%2 is rejected by TMFSERVEcode %3

The cataloging of volumes inTMF catalog is rejected byTMF.

Refer to the TMF Man-agement Programming HPENonStop Manual.

3042 Cannot start SPI %1 on node%2. Error %3

The Guardian node name ofthe Guardian tape catalogDSM/TC or TMF, is rejected by the NODENAME_ TO_NODENUMBER_ Proc call.

Fix the Volume Group defin-ition in the Domain Con-figuration.Check the node's name in the TMF Guardian node, orin DSM/TC Volcat that mustbe qualified by a Guardiannode.

3043 Info TMF media %1 on node%2 is rejected by TMFSERVE

Access to the TMF catalog isrejected.

Refer to the TMF Man-agement Programming HPE


code %3 NonStop Manual.

3044 Cannot communicate withnode %1 to start SPI %2

Access to the remote node isrejected by Expand.


3045 Invalid configuration forDomain Manager %1

The Domain Configuration isinvalid.


3045 The volume group %1 allowsonly TMF label type

A Volume Group is definedfor cataloging as TMF, butthe label type to create isnot TMF-type.

Modify the configuration ofthe Volume Group orcreate TMF label type.

3047 Volumes in the volume group%s are cataloged in DSM/TCor other tape catalog, onlylabeled volumes are allowed

A Volume Group is definedfor cataloging as DSM/TC,but the label type to createis Unlabeled.

Modify the configuration ofthe Volume Group orcreate volume label type:ANSI or BACKUP.

3048 Delete volume %1 in pool %2catalog %3 rejected byMEDIASRV code %4

An error occurred whileaccessing a DSM/TC catalog.

Refer to the DSM/TC Man-agement Programming HPENonStop Manual.

3049 Delete volume %1 in pool %2catalog %3 failed

An error occurred whileaccessing a DSM/TC catalog.No error code was supplied.

Try to un-catalog thevolume with a manual com-mand in MEDIACOM.

3050 Delete media %1 in TMF cata-log on node %2 rejected byTMFSERVE code %3

An error occurred whileaccessing a TMF catalog.

Refer to the TMF Man-agement Programming HPENonStop Manual.

3052 Uncommitted transaction isaborted

A TMF transaction did notend normally.

Verify the results of thelatest operation.

3053 %s SPI return-code %d in %s.%s

An error code is returned byan SPI program.

Refer to the TMF Man-agement Programming, orDSM/TC Management Pro-gramming HPE NonStopManual.

3054 Volume group assigned tovolume %s is unknown (%s)

There is a discrepancybetween the VT ControllerCatalog File (VOLUME) andthe Configuration File(BBSVCFG).

Use the Web UI to recreatethe Volume Group entry inthe configuration.

3055 Invalid action %s in service Internal error. Contact Product Support.


%s

3056 Volume unloaded fromdevice %s.%s. %s.A warning can be associated:"Automatic UNLOAD onvolume %s was performed.Virtual device %s is now deac-tivated."

Feedback for successfulload.

None, unless a warning isissued.The unload has been ini-tiated by the Domain Man-ager to free a device thatappears to be dys-functional.Check if the device is backto normal state – see mes-sage 5065.

3057 Error compiling regularexpression %s for %s pattern%s. %s

Internal error. Contact Product Support.

3058 Update of %s rejectedbecause it has been changedin parallel by %s at %s

In the Web UI, the updateddata was modified byanother user since the datawas read.

Restart the operation tocheck if the new data is stillcompatible with your tar-geted modification.

3059 Error for volume %s. Thevolume group %s allows onlyTMF label type

Creating TMF volumes in aVolume Group from TMF isforbidden.

Reserve TMF VolumeGroups for TMF volumes.

3060 Error for volume %s. Thevolume group %s catalogs inDSM/TC and allows onlylabeled volumes

It is not possible to createUnlabeled Tapes in a VolumeGroup defined for tape cata-loging with DSM/TC.

Use specific Volume Groupsthat do not catalog thevolumes to be created asUnlabeled Volumes.

3061 The status of TMF tapemedia%s on node %s must beSCRATCH or BAD and itsmedium must be TAPE toallow deletion.

It is not possible to delete avolume that contains a dumpaccording to the TMF cata-log.

Correct the volume label tobe deleted.If it is necessary to destroyan active TMF dump, useTMFCOM to un-catalog thevolume before the dump ordelete the tape media.

3062 MountId: %s.%Id. The volumelabel must be specified


3063 Invalid time stamp in %s. %s Internal error. Contact Product Support.

3064 Incomplete %s reply from%s.

Internal error or broken com-munication.

If the problem persists, con-tact Product Support.


3065 Version %d not supported fordocument %s

There is a version mismatchbetween ETI- NET productcomponents.

Verify the version ofinstalled components.

3066 The volume group %s doesnot allow TMF label type

TMF volumes can be createdonly in a Volume Group thatasks for media cataloging ina TMF Catalog.

Use specific Volume Groupsfor TMF Tapes, when aGuardian Node is specifiedfor TMF Cataloging.

3067 Invalid store type %d forstore %s or volume %s

A discrepancy occurredbetween the VOLUME file andthe configuration file.

Modify the Domain Con-figuration to allow the oper-ation to complete.

3068 DSM/TC Catalog status forvolume %s not (yet) appro-priate. LabelType %s,lbMethod %d, defineClass%d, catalogStatus %d

Unexpected status reportedby MEDIASRV.

Contact Product Support.Set the Volume Group toAuto- Scratch = False tobypass.

3069 MountId: %s.%Id. Tape labelmismatch, label in receivedrequest: %s, in pendingmount: %s

Internal error. Contact Product Support.Set the Volume Group toAuto- Scratch False tobypass.

3070 Info pool %s catalog %s rejec-ted by MEDIASRV code %d.%s

Error querying a pool. Check the error explanationreturned by MEDIASRV andincluded in the message.Refer to the DSM/TC Man-agement Programming HPENonStop Manual.

3071 Errors while analyzing thescratch status of virtualvolume %s. LabelType %s,IbMethod %d, defineClass%d. Auto- scratch notexecuted

Internal error disabling theauto-scratch feature.


3072 Virtual volume %s requestedin DSMTC volcat:%s pool:%s,associated with volumegroup %s defined withvolcat:%s and pool:%s. Checkconfiguration.

The catalog location of avolume that is being loadedis not the same in DSM/TC asin the Domain Configuration.

Update the Volume Groupconfiguration or recatalogthe volume(s) in DSM/TC tohave the Domain Con-figuration fit the DSM/TCcatalog.

3073 MountId: %1.%2. %3(label) A mount request was suc- None.


loading on %4(device). %5 cessfully initiated. If theDataStore is configured withscripting, the execution ofthe restore script mightdelay the completion of themount.

3074 Obsolete configuration tag'%s' in %s

The Domain Configurationcontains obsolete para-meters that block regularoperations.

Use the Web UI to edit theconfiguration, check theinterpreted configurationparameters and save theconfiguration with the newformat.

3075 Incompatible tags '%s' and'%s' in %s

An error is detected in theDomain Configuration.

Use the Web Interface tomodify the configuration.

3076 Obsolete configuration tag'%s' converted in %s - checkthe conversion.

When reading the DomainConfiguration by the WebUser Interface, obsoleteparameters are interpretedto be presented to the user.

Verify the parameters andupdate the configuration inthe new format through UI.

3077 The disk pool is missing inthe configuration ofDataStore %s.

An error is detected in theDomain Configuration.

Use the Web User Interfaceto modify the con-figuration.

3078 The password update of TSMnode %s by %s at %s is notregistered because of anewer update by %s at %s.

Updates of the TSM NodePassword are not sorted bythe Domain Manager in chro-nological order.

If connections to the TSMserver are rejected forauthentication error, usethe Web User Interface toreset the password in theDomain Configuration. Ifrequired, set a new pass-word in both the TSMserver and the Con-figuration.

3079 Unable to register theupdate of TSM node %s pass-word by %s at %s

Error prohibits the regis-tration of a new TSM Pass-word in the DomainConfiguration.

Fix any error logged in theprevious minutes, re-enterthe password in the DomainConfiguration.

3080 TSM Password is missing forstore %s.

The Domain Configurationcontains an incomplete TSMDataStore Definition.

Enter the TSM node andpassword in the con-figuration of the DataStore.


3081 Sign on is required to load %swithout association with amount request.

Unexpected control flowmakes the Domain Managerreject a load request.


3082 Unexpected unload of %s-%sat %s not registered in Back-Pak Domain. The unload isrelated to the operation %sat %s. The operation state inDomain is %s.

A VTC notifies the DomainManager that a volume hasbeen unloaded. But thisunload event is not com-patible with the currentstatus of the volume in thedomain. Therefore, theDomain Manager does notregister this unload.

Check the status of thevolume (Current Operation)in the domain catalog. Reset the Current Oper-ation, if required. Thestatus of the previous oper-ation might be lost.

3083 Message from %s %s %sreceived for the domain '%s',domain '%s' is expected.

There is a discrepancybetween the Domain Con-figuration and a VT Con-troller control message.

Make sure the Domain Idstored in all VT Controllers(entered in the “DomainAddress” after a Windowslog-in) is the same as theDomain ID entered in theDomain configuration.

3084 Volume %s not available, inuse by %s operation startedon %s.

A load or a materializationoperation is rejectedbecause the volume isalready in use.

If the Current Operationassociated with the volumeis out of sync, use the WebUser Interface to updatethe Volume in the VT Con-troller Catalog. (Reset thecurrent operation).

3085 VT Controller %s is not aroute to the store %s.

The VT Controller specifiedfor a Virtualization/ Mater-izalization cannot access theDataStore holding theinvolved virtual volume.

Check the Domain Con-figuration and retry.

3086 Access to volume %s deniedto %s.%s, %s

An operation on a volume isrejected because the userhas not the required author-ization.

Check the volume ownerand access authorizationsin the Web User Interface.Eventually, update thissecurity settings on thevolume to bypass the error.Review the default accessauthorizations in theVolume group and the TAPE


DEFINE of the applicationwriting the volume (specialkeyword bbox-secure=rwc).

3087 The config dir is missing inthe configuration of route%s to DataStore %s

The configuration of aDataStore in the Domain Con-figuration is incomplete.

Complete the Domain Con-figuration.

3088 MountId: %s. Invalid BBOX-SECURE specification in theDEFINE mount message: %.

Invalid authorization spe-cification.

Refer to the ProductDescription chapter of theControl of access to virtualvolumes section.

3089 Invalid session key receivedfrom %s %s. Key length=%ld.%s


3090 RSA error using public key ofrequester %s. %s


3091 RSA error using public key ofserver %s. %s.


3092 RSA error using public key ofrequester %s. %s


3093 Encryption error %s Internal error. Contact Product Support.

3094 Volume %s is member of thevolume group %s definedwith DSMTC volcat %s andpool %s, but the tape volumeis found in DSMTC volcat:%spool:%s. Check the con-figuration.

Inconsistency between thestate of a volume in DSM/TCand the state of the volumein the domain catalog andconfiguration.

Make sure the Domain Con-figuration (specially theVolume groups) cor-responds to the Guardiantape catalogs.

3095 Volume %s is member of thevolume group %s definedwith DSMTC volcat %s andpool %s, but the tape volumeis not found in DSMTC cata-log. Check the configuration.

Discrepancy between thestate of a volume in theGuardian subsystem and thestate of the volume in the VTController catalog and con-figuration.

Make sure the VT Controllerconfiguration (especiallythe Volume groups) cor-responds to the Guardiantape catalogs.

3096 Volume %s is a member ofthe volume group %s definedwith TMF catalog %s, but the

Discrepancy between thestate of a volume in theGuardian subsystem and the

Make sure the VT Controllerconfiguration (specially theVolume groups) cor-


tapemedia is not found inthe TMF catalog. Check con-figuration.

state of the volume in the VTController catalog and con-figuration.

responds to the Guardiantape catalogs.

3097 Hash mismatch. Internal error. Contact Product Support.

3098 Hash error on %s: %s Internal error. Contact Product Support.

3099 Volume %s label %s alreadyexists in the domain catalog.

A virtualization is rejectedbecause the virtual volumealready exists in .

None.

3100 VTC %s is deactivated in theDomain Configuration.

An operation is rejectedbecause the specified VT Con-troller is disabled by con-figuration.

Enable the specified VT Con-troller or use a differentone.

3101 Volume %s label %s status%s in %s must be catalogedand idle before being vir-tualized, to be consistentwith volume group %s

A virtualization is initiatedfor a volume that is not cata-loged as specified in theVolume group.

Fix the Volume group con-figuration.

3102 VTC %s did not reply to a Con-nect Message

A message is rejected by aVT Controller, most probablybecause of IP filtering.

Check the Domain addresspage in the Web page /Ad-min of this VT Controller.Check the MS WindowsEvent Viewer.

3102 Library %s did not reply to aConnect Message.

A message is rejected by theBBLM process of this library.

Check for other EMS mes-sages related to this BBLMprocess.Restart the BBLM process.

3104 Invalid version of %s VOLUMEfile: '%d', expected: '%d'.

Discrepancy between the ver-sion of the VOLUME data fileand the running BBSV pro-gram.

Check the installation /up-grade that has been justexecuted.

3114 Pending mount request notfound for the volume %s

The Domain Managerreceives a mount requestthat is no longer in the list ofMEDIACOM pending mounts.

Check the EMS log toidentify why the mountrequest was canceled.Resubmit the job.

3115 Invalid store type %d in cata-log record to write for the vir-tual volume: %s-%s.



3119 Current operation (%s) ofvolume %s reset in the cata-log of virtual volumes.

A user resets the currentoperation by using the Webuser interface.The MVS datasets arereleased. Any running trans-fer with the same tapevolume is not impacted. There should normally be norunning transfer when a userresets the current operation.

None.

3120 Volume %s manuallyunloaded.

A manual unload is com-manded by the Web userinterface, forcing can-cellation of any runningtransfer.

None.

3122 The configuration ofDataStore %s contains aninvalid Guardian User ID pat-tern: '%s'

Syntax error in BBSVCFG file. Modify the Guardian User IDpattern using the Web userinterface.

3123 MountId: %s. Guardian UserID %s not authorized toaccess the DataStore %s(volume %s)

The User ID running the tapeapplication is not authorizedto access the DataStore.

Update the security tableof the DataStore using theWeb user interface.

3124 VT Controller %s returnedcode %ld to the query of DEXP configuration

The discovery of DE XPvolume in a VTC does notwork.

Check the connection tothe XP Array.

3125 Error %d on %s: %ld unusabledrives %

This message is embedded inmsg 3227 reporting a failedload.It reports an error occurringwhen the Domain Manager isnot able to get the status ofusable tape drives from aVTC (or Library MediaChanger Controller).The number and names ofthe first tape drives are unus-able because this error code.

Refer to the detailed errormessage in the EMS log.

3129 START_XFER CONVERSION'%s' should be 'ASCII-EBCDIC'

Invalid CONVERSION Para-meter.

Check CONVERSION para-meter.


or 'JIS-EBCDIC' (%s.%s %s)

3142 MountId: %1.%2. DE-XP error%3 loading %4 on %5 %6. %7.Load to be retried

A VT Controller is not able toaccess a DE XP volume.Other routes configured inthe DE XP volume will betried.The failed load will be retriedat the same frequency asthe “busy drive” condition.

1- Force the discovery of DEXP volumes by the VT Con-trollers, by inquiring in thelist of DE XP volumes of thedomain through the Webuser interface, DataExchange tab.Check if the volume is seenby the VT Controller tryingto load a virtual media.2- Have the DE XP volumesreconnected to the properVTC(s).

3146 Info volume %s labelType %ldin pool %s catalog %sreceives error %d fromMEDIASRV. %s.

Access to DSM/TC volumeinformation returns an error.

Analyze the MEDIASRV return-code.

3147 Remaining volumes in %s %swill be skipped.

While processing a batch ofvolumes, a severe erroroccurs, preventing any morevolume of the same DataStore to be processed.This message follows otherspecific error message(s).

Solve the error conditionbefore re- executing thebatch.

3150 BBCMD stops retrying send-ing a '%s' message to theDomain Manager after %ldretries.

The retry limits specified infile EZXSETUP/BBSETUP arereached. BBCMD and the cur-rent TACL macro end witherror.

Check the cause of errorsin previous messages andin EMS log.

3153 No automatic unload ofvolume %s, after an unre-quested load on %s.%s. %s.

The EMS message #640 'UNREQUESTED ANSI TAPE' islogged, but the state of theunrequested volume is notconsistent.

Verify the conditions of cur-rent transfer.To get rid of an unre-quested load, use theUnload command on theHome page of the Web userinterface. This will unloadthe volume, reset the cur-rent operation of thevolume and de-allocate theMVS datasets.


3156 MountId: %s. Device '%s'requested to load %s is notfree, or not on an active VTCthat is a route to theDataStore %s.

The device requested to loada volume is not emulated bya VTC that is active and thatis a route to the DataStoreorthe drive is not free.

Check the Domain con-figuration:- the VTC is a route to theDataStore associated tothe tape volume- the VTC is active.Check the status of thedrive in the Status nodepage.

3157 VTC %s rejects the unloadingof volume on device %s.%swith error %ld %s.

An unload command is rejec-ted by the VTC.

Check the error conditionreported in the message.

3158 Completion of operation (%s)of volume %s can not be com-municated to the MVS Agentthat has allocated the data-set (s). Current operationchanged to POST_TRF.

A communication error pre-vents sending the transfercompletion data to the MVS.The MVS dataset is stilllocked and the MVS audit fileis not updated.

When the communicationswith MVS are re- estab-lished, use the Web userinterface to reset the cur-rent operation of the tapevolume.This will unlock the MVSdataset and register theactual completion (maybe afailure or a success) of thetransfer in the MVS auditfile.

3159 State of volume %s does notmatch. VTC reports %s. Domain Manager reports %s.Device %s.%s.

Discrepancy between statesin the Domain Manager andstates in a VTC.The processing of the cur-rent event might be aborted.

Check possible other mes-sages in EMS.Check the state of theinvolved volume and devicein NSK MEDIACOM in theDomain catalog.To clear inconsistent con-ditions:- restart the device in SCF- use the Web user inter-face to reset the currentvolume operation.

3160 Volume loaded on device%s.%s does not match.Guardian reports volume'%s'. Domain Managerreports volume '%s'.

Discrepancy between statesin the Domain Manager andthe Guardian Tape System.The processing of the cur-rent event might be aborted.

Check possible other mes-sages in EMS.Check the state of theinvolved volume and devicein NSK MEDIACOM in the


Domain catalog.To clear inconsistent con-ditions:- restart the device in SCF- use the Web user inter-face to reset the currentoperation of the volume.

3161 Invalid license code=%ld %s. The domain license key isinvalid.


3162 Domain license will expiresoon on %s.

Warning when the licenseexpiry date is close.


3163 Domain license has expired%s.

A VTC operation occurs whenthe license has expired. Theoperation can be rejecteddepending on the license con-text.


3164 License violation-%ld %s. The configuration or attemp-ted operation does not com-ply with the license key.


3165 Automatic unload of volume%s. Volume was loaded since%s on %s.%s that is nowfree.

A volume has been loadedfor an extended period oftime without being used by aNonStop application.

None, if no other symptom.

3166 Invalid %s parameters. Key-word '%s' is unknown.

Invalid TACL program para-meters.

Verify the macro or pro-gram parameters.

3167 Invalid %s parameters. Valuemissing for keyword %s.



3168 Invalid %s parameters. '%s' isnot a valid value for %s: %s.



3169 Invalid %s parameters. %sparameter is missing.



3170 Parameter #%ld (value '%s')cannot be translated in mes-sage #%ld from %s.

Error in formatting a mes-sage logged by a VTC to EMS.



3171 Alert triggered by message:'%s'.

An error was indicated byanother EMS message that isconfigured to be doubled bythe Alert Message.

Check the included originalmessage and any otherrelated errors in EMS.If the alert is not necessary,disable the alert for thiskind of original message inthe Domain Configuration,Domain Page and AlertsLink.

3172 Tape device '%s' is unknownin domain %s. See message#%ld from %s.

A message logged by a VTCto EMS names a virtualdevice that is not configuredin the Domain.

Check the configuration ofthe Domain and the SCFdevice definition.There might be nothingwrong if there are severalDomains sharing a VTC, butnot sharing all devices.To suppress these mes-sages, edit the Domain Con-figuration, Domain WebPage, changing EMS verb-ose to false.

3173 storage space purge ofexpired tape volumes. %ldvolumes in catalog, %ldvolumes purged (or “to bepurged”).

Completion of the free-up ofstorage allocated to tapevolumes expired in DSM/TCand TMF.

None.

3174 Virtualization not available toData Store %s type %s withDomain access %s.

A domain cannot update aData Store that is notPRIMARY.

Run the Virtualization fromthe Owner's Domain.

3175 Load for output is forbidden.Volume %s is in a %s DataStore (%s).

RESTRICTED and SECONDARYData Stores can execute onlyrestores, not backups.

Run the backup in thePRIMARY Domain.orChange the domain accessconfigured for the DataStore to PRIMARY.

3176 The Domain access to thevolume cannot be changedfor %s. (Domain access toData Store is %s).

The changeRESTRICTED/OWNER to avolume is forbidden.

Verify if the Data Storedomain access is appro-priate.Refer to the User's Manual.

3179 MountId: %s. Dump type The TMF dump type is not In case of a Load :


(Audit/Online) is missing forTMF volume %s.

found (Load) or not enteredby user (Virtualization).Load is executed, but theparameter %BBOX_ TMF_TYPE% is not set in theBackup script.Virtualization is rejected.


For Virtualization: enterdump type for the oper-ation.

3181 MountId: %s for volume %s.%s while querying applicationprocess %s.%d,%d. Mountautomation is disabled.

A tape application processcannot be queried.Several load / unload auto-mations are disabled.

Modify security andresource errors to allowregular functionality.Contact Product Supportfor other errors.

3182 MountId: %s for volume %s.Previous error in accessingVOLUME prevents the record-ing of the volume sequenceand any future pre-load.

Informative message. Refer to the previous error.

3183 MountId: %s for volume %s.Pre-load of next volume %sis enabled.

Informative message.Pre- load is executed onlywhen the current volume isused by the application.

This message is displayedonly when EMS verbose isset to "true" in the DomainConfiguration.

3184 MountId: %s for volume %s.No next volume to pre-load.

Informative message.The volume is the last of amulti-volume set.


3185 Pre-load was generated for%s, but did not completebefore the unload of the pre-vious volume %s. Pre-load iscanceled.

Informative message.Regular load request willapply.

None.

3186 Automatic unload of volume%s that was %s since %s on%s.%s that is free. Applic-ation process %s.%d,%d star-ted on %s is no longerrunning.

Informative message. None.

3187 Automatic unload of volume%s that was pre-loaded since%s on %s.%s that is free. Pre-

Informative message None


vious volume %s #%l in theset is unloaded since %s.

3188 Domain Manager did notreply to a ConnectDM mes-sage.

A NonStop client cannotreach the Domain Managerover TCP/IP.

Check for previous TCP/IPerror messages in EMS.Check the TCP/IP setup.

3189 Hashed message key in %srequest is invalid. Requestfor %s is rejected.

Error message on invalid key(issued for security reasons).


3190 Redefining and reloading thealternate keys of volume file%s.

At first use, after an upgradeof NonStop programs, theVOLUME file is modified tomatch the new software ver-sion.

Wait for FUP to completethe LOADALTFILE operation.FUP is started with TERMand OUT set to $ZHOME.

3191 MountId: %s. Error %ld load-ing %s on %s %s (insufficientstorage) %s

Disk space shortage in a Win-dows files Data Store.

The load will be retriedaccording to the busycheck- retry- interval parameterin the BBEXTCFG file.Evaluate the disk space forthe paths configured forthe Data Store.

3192 %s in %s has an invalid value'%s' and is ignored

To interpret according to theembedded parameters.

Action depends on eachmessage.

3193 Pre-load %s reel #%ld as con-tinuation of %s.

Informative message.Pre-load is attempted.


3194 %s is missing in the con-figuration of EMC XBSADataStore %s.

XBSA configuration is incom-plete.

Complete the XBSA con-figuration.

3195 No statistic record writtenfor volume %s.

An error prevented therecording of statistics for anoperation.

Check for previous EMSmessage from .

3196 Current operation (%s) ofvolume %s reset by errorrecovery in the catalog of vir-tual volumes

A volume is locked by a cur-rent operation in the catalogof virtual volumes (VOLUME

None.


file). The state of thevolume, the tape applicationthat requested it and theVTC that loaded it do notallow a regular unload. Reset-ting the state of the volumecan free both the volumeand the tape device in whichthe volume was mounted.Once the volume state isreset, the tape device can beused by other operations.

3197 BB020_ RESERVE DRIVE %s:cannot specify both NONEand a volume class.

Syntax error in the BB020_RESERVE TACL macro.

Modify the CLASS para-meter of BB020_RESERVE

3198 BB020_RESERVE: DRIVE para-meter missing

Syntax error in the BB020_RESERVE TACL macro

Specify the DRIVE para-meter of BB020_RESERVE.

3199 BB020_ RESERVE DRIVE %s:drive not found in the con-figuration.

Specification error in theBB020_RESERVE TACL macro

Check the device name con-figured in the Domain.The device must be con-figured in an active VTC.

3200 BB020_RESERVE DRIVE %s:volume class %s not found inthe configuration.

Specification error in theBB020_RESERVE TACL macro.

Check the Volume classesconfigured in Volumegroups.

3201 BB020_ RESERVE DRIVE %s:maximum number of volumeclasses (%ld) exceeded.

Internal limit exceeded Contact Product Support.

3202 BB020_RESERVE DRIVE:CLASS parameter missing

Syntax error in the BB020_RESERVE TACL macro.

Specify the CLASS para-meter of BB020_RESERVE.

3203 Drive %s now reserved tovolumes class(es) %s.

Feed back of the BB020_RESERVE macro.

None.

3204 BB020_RESERVE_DRIVE: %lddrives updated, %ld driveslisted.

Feedback of the BB020_RESERVE macro.

None.

3205 MountId: %s for volume %s.VTC %s returns busy storagecondition: %s

A busy condition is returnedby the Data Store.

The load will be retriedaccording the busycheck -retry-interval parameter in


the BBEXTCFG file.Check for previous EMSmessage from .Check the Windows Applic-ation log.

3206 Invalid %s parameters.Comma must be followed byspace in '%s'

Invalid syntax Modify the syntax enteredby user.For any other errors,Contact Product Support.

3207 MountId: %s for volume %s.This BACKUP volume hasbeen written, unloaded, andis now being reloaded by thesame process. Check care-fully the backup outputreport and the volumes cata-logued in DSM/TC for thisbackup.

This is probably the result ofa disk error when BACKUPcannot back up a completepartitioned file.In a multi-volume backup, atape 'back- space' isexecuted up to a previousvolume that must bereloaded.When the volumes are cata-loged in DSM/TC, someinvalid volumes that shouldbe SCRATCH might stay cata-logued for the tape file.

Be sure to prepare a cor-rect restore by the fol-lowing check.If the volumes catalogedfor the TAPEFILE do notmatch the list of volumesdisplayed in the BACKUPreport, the RESTORE shouldbe executed without thetape catalog, but with thelist of volumes identified inthe BACKUP report.Some explanatory notesshould be associated withthis BACKUP.For TSM APPI Data Stores,the number of TSM objectsin this volume becomesunknown and the validationof the expected number ofTSM objects will not beexecuted at restore time.Ref message “E6005 Incon-sistency was found in TSMobjects”.

3208 MountId: %s. Device reser-vations prevents %s to load%s.

The volume to load has avolume class that preventsits loading because of devicereservations.

In the web application,query the volume toidentify its volume class.Query and eventuallymodify the device reser-vation in the configurationof the VTC.


3210 The domain configurationdoes not contain any activeVTC or library attached tonode '%s'

A “Node Status” query in theUI has no data to return, asthere is no tape drive con-figured for this node.

Verify the domain con-figuration that may havechanged between two quer-ies.

3211 There is no backup script con-figured in Data Store %s.

Execution of backup script isrequested in the web applic-ation, but there is no backupscript configured in the DataStore.

Configure a backup script inthe Data Store.

3212 Backup script submitted toVTC %s for volume %s.

Backup script requested bythe web application are sub-mitted.

None.

3213 Volume %s was %s since %son %s.%s. A different volume%s is now loaded on %s.%s.Operation of volume %s isassumed aborted and its cur-rent operation is reset.

Inconsistent volume stateprevented its loading.

Verify the operationsinvolving the specifiedvolume label.

3214 Pre-load for volume %s con-tinuation of %s is not ini-tiated. %s loaded by themountid %ld was toorecently unloaded on %s.

A Pre- load is not executedbecause the volume wasloaded or unloaded in thelast two minutes.

Pre-load is normally set forlong restore scripts.In case of quick re-use ofthe same volume, it is pre-ferrableto wait for the reg-ular mount request fromthe tape application.

3215 StoreId must be specified in%s transaction.

The store id is required, butnot provided.

Enter the store ID.

3216 Data Store type of %s mustbe WINDISK.

This function is reserved forWindows Data Store typefiles.

Use this function only forWindows file Data Stores.

3217 %d%% of Windows diskspace used in store %s. Storehas reached the warninglevel %d%%. %s MB are used.%s MB are free.

Result of the macro BB022_CHECK_SPACE.The current disk usage hasreached the warning levelconfigured in the Data Store.

Install additional disk spaceby executing 0BB017.

3218 Disk path %s in Store %s isnot accessible.

Result of the macro BB022_CHECK_SPACE.

Log in to Windows on a VTCwith the Windows account


The path is unavailable tosoftware.

password configured in theData Store.Test access on the con-figured path name.Verify connectivity andsecurity issues.

3219 "Free space (%s MB) in %s isnot enough for writing a fullvolume (%s MB) in volumegroup %s.

Result of the macro BB022_CHECK_SPACE.The maximum volume size ofthe Volume group does notfit in the disk with thelargest free space in theData Store.

Review the maximumvolume size.Install new disks.

3220 %s {backup|copy} scriptshave been submitted in theData Store %s to VTC(s): %s.%s.

Backup script (s) have beensubmitted.One submission is countedper virtual volume.The VTCs that received therequests are listed.

None.

3221 File %s.* in diskPath %s con-figured for Store %s doesnot belong to domain %s

Unexpected files are mixedwith the Windows files con-taining images of virtualvolumes.

Do not store unrelated filesin either Windows dir-ectories or shares con-figured to a Data Store.

3222 No valid reply to %s requestfrom VTC %s, volume %sloading is assumed to bebeing processed.

The Domain Manager hassuccessfully sent a LOADcommand, but did not getthe reply.assumes the load is suc-

cessful and does not retry.

Verify the operations onthe volume label.Eventually, reset thevolume and load it manu-ally.

3223 Data Store %s must be con-figured with PRIMARYdomain access.

The function is reserved forregular Data Stores, pro-hibited with RESTRICTED andSECONDARY Data Stores.

None

3224 BB023: %s backed up Win-dows files have beendeleted. Deleted size: %sbytes.

Summary of execution ofmacro BB023_ DEL_BACKEDUP

None

3225 Normal job ended. A TACL macro finished. None


3226 Internal status %s preventedthe use of drives free inNonStop. %s.%i devices LOADING($device1, $device- 2…) %idevices RESERVED ($device3,$device4…)

This message is embedded inmsg 3227 reporting a failedload.Msg 3226 explains whydevices FREE in NSK can notbe used for loading a volume.Possible status can be: “LOADING”: a restore script isrunning in the VTC.“LOADED”: the VTC is replyingREADY to host polling, wait-ing for tape NSK tape recog-nition from the in NSK host.“INACTIVE” : the host did notpoll the virtual device withinthe configured timeout."NOT CONFIGURED” : thedrive is not configured in theVTC.“UNLOADING” : VTC is stillunloading a volume.“LICENSE OVERFLOW” : thenumber of licensed ports isreached, the device isanother port that exceedsthe license key limitations.

Some status’ (LOADING,LOADED, UNLOADING) areexpected to be normalstatus, thus preventing aload to execute.Status LOADED andUNLOADING should not belonger than 1 minute.Other status is reported bythe message 3230 andrequires investigation.Some FREE devices mightalso not be eligible becausethey don’t emulate therequested media type.

3227 MountId: %s. No availableresource to mount %s. %s.

The loading of a virtualvolume on any device failsfor the specified reason.

Action depends on thereason for failure.For a load request for out-put, the load will always beretried.

3228 MountId: %s. Cannot mount%s on device %s

The loading of a virtualvolume on a specific devicefails for the specified reason.

Action depends on the fail-ure reason.For a load request for out-put, the load will always beretried.

3229 Creating file %s The Domain Manager (re)-creates a missing file in theinstallation NSK subvol.

OPER file containing onlytemporary status can berecreated at will.The re- creation of otherfiles requires stopping thetape operation and carrying


out an investigation.

3230 MountId: %s. Loading %simpossible on device %sbecause of the internalstatus %s in VTC %s.

An abnormal internal statusprevents a load from execut-ing.

Investigate the error.

3231 %ld drives not usablebecause of volume classreservations.

This message is embedded inmsg 3227 reporting a failedload.

None.

3232 MountId: %s. Loading %s on%s %s exceeds license limits.%s. Load to be retried.

This message is embedded inmsg 3227 reporting a failedload.The number of active portshas reached the number oflicensed ports on this VTC.Or the number of activedriveencryptions has beenreached.If available, the load will beattempted in another VTC.

None.

3233 MountId: %s. Data Storeerror loading %s on %s %s.%s. Load to be retried

The VTC rejects a loadrequest for a reason relatedto the Data Store, but theload request can be retriedon another VTC.

Verify the reason of error.

3234 Domain license violation.DEFINE =TCPIP^HOST^FILE(%s) not allowed when alicensed VTC address is sym-bolic (%s).

License rule violation. Do one of the following:l Remove any

=TCPIP^HOST^FILEDEFINE from the con-text of the TCP/IPLISTNER or in theVTC configurationpage.

l Request an ETINETlicense that containsthe VTC host namerather than analternate DNS name.

l Request an ETINET


license that containsa numeric IP addressand enter thisaddress in the VTCconfiguration of theDomain.

3235 %s rejected by VTC / Library%s. Error code %ld - %s

VTC or Library Changer Con-troller rejects a Domain Man-ager request.

Analyze the error reason.Unsupported transactionname is the symptom ofmismatching versions.

3237 %s accepted with warning by%s %s. Error code %ld - %s

VTC accepts a Domain Man-ager request, but issues awarning.

Analyze the warning errorcode and text.

3238 MountId: %s. Unavailableresource to mount %s. %s".

An unavailable resource pre-vents a load from achievingcompletion.

Analyze the reason forerror. Mount requests rejec-ted with this message num-ber are retried soon(busycheck-retry-interval).

3239 Data Store type of %s mustbe WINDISK or LUMINEX.

Operation not supported forData Stores types differentfrom WINDISK and LUMINEX.

None.

3240 Domain version %s receives%s from %s with mis-matched version %s.

Version mismatch betweencomponents.

Verify program versions(VPROC pgm-name on NSK).

3241 No virtual device of an activeVTC is configured for node%s.

A load request is issued froma NonStop node that has nodevice configured in an act-ive VTC.

Define a virtual device forthe node.Eventally re-activate inact-ive VTC.

3242 Additional queries executedto refresh the operationalstatus of node %s.

In certain situations, forexample, when the con-figuration has been modifiedor the EMS Extractor hasstopped, the information isnot available. The externalentities must be queried:- NSK MEDIASRV- VTCs- Library Changer Controllers.

Restart EMS extractor andcheck EMS to see whetherthere are error messagesrelated during extractorrestart.


3243 EMS Extractor %s for node%s is not running or not iden-tified

BBEXT program is not run-ning.There will be no automaticmount.

Start the EMS Extractor onthe indicated NSK node.

3244 Unload rejected. Volume %sassumed loaded on device-e=%s by mountId=%ld, isrecorded in operation %s,device=%s, mountId=%ld

An unload does not execute,because the volume is nomore in the expected state.

None

3246 Pre-load for volume %s con-tinuation of %s is not ini-tiated. %s contains less than%s bytes of data.

Pre-load does not execute ifthe volume to pre-load hasless than 1 MB ofdata.

None

3247 Volume label %s was loadedon %s by the other domain%s.

A VTC contacted to produce aweb status page, reportsthat a loaded volume doesnot belong to the queryingdomain.This occurs when twodomains share the sametape drives.

Make sure the two domainsdeliberately share tapedrives.

3248 MountId: %s. Identicalrequest to load %s wasrecently executed (load/un-load on %s) %s. Request isrejected.

Two requests look identical,the second one is simplyrejected.It occurs in special con-ditions: for example, whenthe request comes fromMEDIASRV before comingfrom the EMS. It occurs alsowhen retries are executedafter another operationalerror.

There is normally nothingto fix.Double check the correctloading of the volume forthe tape application.Verify if there are otherEMS Messages reportingerror.

3249 MountId: %s. Request for %srejected because applicationprocess %s.%d,%d started%s is not found (%s)

A load request is ignoredbecause the correspondingapplication process is notfound.

There is normally nothingto fix. The application mighthave disappeared beforethe mount request is pro-cessed.Double- check that themount request does notstay pending.


3250 Length %ld of attribute %s isinvalid. %s. (value '%s')

An XML attribute has an unex-pected length.This might occur if files unre-lated to are present in Win-dows directories configuredin a Data Store.

Examine the unexpectedvalue.Contact Product Support ifany clarification is required.

3251 Physical tape device %s isnot configured in VTC %s.

An operation is attempted ona physical tape device that isnot defined in the VTC con-figuration.

In the Domain con-figuration, verify the list ofphysical tape devicesattached to the VTC.

3252 More than %ld tape devicesare configured. Devices inexceeds are ignored.

Automatic mount is limitedto a maximum number oftape devices.Devices in excess areignored. The initial maximumis 256 devices.

If a site requires more than256 devices contactProduct Support.

3253 Domain license violation.Physical media Virtualization/ Materialization is notlicensed.

Virtualization / Mater-ialization must be licensed tobe used.


3254 Physical device %s in %saccessed as LEGACY devicefor Virtualization / Mater-ialization that is not licensedfor LEGACY.

Physical tape devices thatare not explicitly supportedby a Windows driver must beaccessed in LEGACY mode. TeLEGACY mode requires a spe-cial license option.

Change the tape device fora device supported byMicrosoft Windows,orContact Product Support.

3255 DSM/TC pool %s in catalog%s does not exist.

A pool name is not known byDSM/TC.

Verify the configuration ofthe volume group and theDSM/TC pool names.

3256 DSM/TC pool %s in catalog%s is defined with APPENDON, that is incompatible withAuto-scratch ON in the Back-Pak volume group %s %s.

Inconsistency in the volumegroup configuration.

Change the DSM/TC pool toAPPEND OFF. “APPEND is not effectivewith virtual tapes and Back-Pak space management.”As a second choice, removeauto- scratch in the Back-Pak volume group.Volume groups for LibraryManagement do not offerAuto-scratch.


3258 Unload %s from drive %s.%srejected. The tape drivestatus %s accordingMEDIACOM does not allowunloading.

A manual unload is rejectedbecause the drive status inSCF does not allow this oper-ation.

Wait for the device which isno longer used by any tapeapplication, before retrying.Restart the drive in SCF toclean a frozen state.

3260 Function reserved to LIBRARYstore type, prohibited to %sthat is %s type.

Unexpected mismatchbetween function and DataStore type.


3261 Library %s is disabled in thedomain configuration.

A library cannot be pro-cessed because it is disabled.

Enable the library in theBackPak configuration tooperate it.

3262 The Bar-coded label is miss-ing in the library for element%s. Medium ignored.

Bar-code is not seen by thelibrary changer.

Verify printed bar- codesand bar- code reader ofphysical libraries.

3263 Maximum supported numberof slots %ld exceeded by lib-rary %s. Extra volumesignored.

A library inventory queryreturns more than 65535slots.


3264New location %s for volume%s in library %s. Previous loc-ation %s is overridden indomain catalog. %s

A library inventory queryreturns a location for avolume that is registered inanother slot in the BackPakcatalog.This should happen onlyafter operations not initiatedby BackPak.

None. BackPak catalog isupdated accordingly.

3265 Label '%s' in slot %s wasalready seen in the other slot%s of library %s. New occur-rence is ignored.

Several volumes have thesame bar-coded label.Only the 1st occurrence canbe labeled and operated byNSK tape applications.

Remove and relabel duplic-ates.

3266 SQL error %d (seq %d) from%s in %s.%s line %ld (syntaxloc %d) processed rows=%ld.

Technical error accessing anSQL data base.

Refer to the accompanyingEMS messages.

3267 Domain license violation.Catalog Sync option is notlicensed.

The license key registered inthe domain configurationdoes not allow catalog rep-lication.

Obtainan appropriatelicense key fromETI-NET.


3268 Cannot submit a catalogexport/import when one isalready running for DataStore %s. Process %s wasstarted on %s, %s volumesprocessed.

Only one batch process canrun at a time for a DataStore.

Wait for the end of the pro-cess.As a final step, abort theprocess by a TACL STOPcommand.

3269 Cannot execute this updateon Data Store %s when acatalog export/import is run-ning. Process %s was startedon %s, %s volumes pro-cessed.

The configuration of “domainaccess” and “active DataStore” cannot be updatedwhile an export or importcatalog batch process is run-ning.


3270 Cannot delete the Data Store%s when a catalog export/im-port is running. Process%s.%s was started on %s, %svolumes processed.

A Data Store cannot beremoved from the con-figuration while an export orimport catalog batch processis running.


3271 Data Store %s is inactive. An activity is attempted on aData Store configured asinactive.

This is normally the expec-ted result.Activate the Data Store inthe domain configuration.

3272 Volume %s is in an inactiveData Store (%s).

Most activities, especiallyvolumes loading in tapedrive, are rejected when aData Store is configured asinactive.

This is normally the expec-ted result.Activate the Data Store inthe domain configuration.

3273 CATALOG EXPORT process %sstarted to export the cata-logs of Data Store %s. Out-put report sent to %s.

A batch catalog EXPORT pro-cess starts.

None.

3274 Catalog export/import pro-cess cannot be initiated: %smissing in the Data Store %sconfiguration.

The configuration prohibitsstartin catalog export /im-port operation.

Review the configuration ofthe Data Store for CatalogSync in the domain.

3275 %s is invalid as report spe-cification for catalog exportprocesses of Data Store %s.

The process cannot startbecause its report spe-cification is not configuredcorrectly.

Review the “Export reportlocation” in the con-figuration for Catalog Syncof the Data Store.


3276 %s is invalid as report spe-cification for catalog importprocesses of Data Store %s.

The process cannot startbecause its report spe-cification is not configuredcorrectly.

Review the “Import reportlocation” in the con-figuration for Catalog Syncof the Data Store.

3277 MountId: %s. AUTO-SCRATCHrejected because the 1sttapefile in volume %s has notexpired.

A volume to load for outputon a drive has not expired inDSM/TC or TMF.The AUTO- SCRATCH pro-cedure is skipped: the cur-rent volume is searched inthe Data Store rather thanre-created as empty volume.

None.

3278 Catalog %s %s process %saborts. %s Report in %s.

An import/exports batch pro-cess aborts because of anerror.

Look for the errors issuedright before this one.

3279 %s exported %s catalogs forData Store %s (%s volumesprocessed). Report in %s.

An import/export batch pro-cess ends.

No action required.Look at the identified con-trol report.

3283 %s volumes in Data Store %shave been detached fromthe domain %s catalog.

A Data Store detach ends,reporting how many volumeshave been removed form thedomain catalog.

None.

3285 Catalog %s process %s forData Store %s: volume %serror %ld - %s.

An error occurred in theimport or export of catalogentries related to a volume.

Analyze the error details.If the error condition can befixed, resubmit the catalogexport or import.

3286 Process %s started forIMPORTING %s of Data Store%s. Output report sent to %s.

A catalog import starts in thebackground.

None.

3287 Invalid %s parameters. End-ing quote missing for '%s'.

The parameter for a TACLprocess is invalid.

TACL parameters are nor-mally generated by Back-Pak macro or othercomponent.Review the parameters ofthe BackPak macro.Contact Product Support.

3288 The number of %s SPI serv-ers exceeds the maximum of

The number of concurrentMEDIASRV processes to label

Reduce the number ofdrives to use for a library


50. library volumes is limited. labeling process.

3289 Labeling volume %s in pool%s catalog %s (drive %s,media type %s) rejected byMEDIASRV code %d. %s %s

The equivalent of aMEDIACOM command LABELTAPEVOLUME is rejected.

Analyze the MEDIASRVreturn-code and associatedtext in the message.HPE Reference:DSM/Tape Catalog Man-agement ProgrammingManual.

3290 Labelling not catalogedvolume %s (drive %s, mediatype %s) rejected byMEDIASRV code %d. %s.

The equivalent of aMEDIACOM command ADDTAPELABEL is rejected.

Analyze the MEDIASRVreturn-code and associatedtext in the message.HPE Reference:DSM/Tape Catalog Man-agement ProgrammingManual.

3291 Delete volume %s in pool %scatalog %s rejected byMEDIASRV code %d. %s.

The equivalent of aMEDIACOM command DELETETAPEVOLUME is rejected.The volume status does notallow its deletion.

Analyze the MEDIASRVreturn-code and associatedtext in the message.HP Reference:DSM/Tape Catalog Man-agement ProgrammingManual.

3292 Unload drive %s.%s rejected.The library %s does not seeany bar-coded media in thisdrive.

The media changer does notsee any volume in the driveto unload.

Verify the status of librarydrives in the UI, Node statuspage.Restart the drive in SCF toensure a fresh status onthe NSK side.

3293 Media move %s in library %sfrom %s to %s rejected%ld-%s.

The move of a media in a lib-rary, such as a load or amove to an I-E slot, is rejec-ted.

Analyze the message at theend of this message.

3294 Library %s rejects the Invent-ory command %ld-%s.

The library inventory query isrejected.

Analyze the message at theend of this message.

3295 Media move in library %sfrom %s to %s is invalid %s.

An “illegal” media move isattempted.

Analyze the message at theend of this message.Use the BackPak web UItoGet the library invent-ory that will resync the


slots location stored in theBackPak inventory.

3296 Volume %s is no longerloaded in a drive of library%s, unload command notexecuted.

The volume to unload is nomore reported as loaded bythe library changer.

Verify the status of librarydrives in the BackPak webUI, Node status page.Restart the drive in SCF toensure a fresh status onthe NSK side.

3297 Unload %s initiated throughthe NonStop tape drive.

A volume unload is executedfrom the NonStop host.This should trigger a librarymove of the media to a stor-age slot.

Verify in the UI, Node StatusPage, that the drive is actu-ally unloaded soon.Repeat the manual unloadif the drive stays IDLE(volume is loaded, but inac-cessible from the host).

3298 Volume %s is catalogued involcat %s pool %s with mediatype %s, but is configured byvolume group %s as type %s. Media type inconsistencymight prevent loadedvolumes from being accep-ted by $ZSVR.

NonStop tape systemrequires that the media typecatalogued for volumes inDSMTC must match the tapedrive type.When labeling new volumes,sorts the volumes accordingto the media type configuredin the volume group. This oneshould match the type oftape drives in the library.

To ensure the appropriatemedia type is assigned tovolumes labeled by Back-Pak, verify the con-figuration of the volumegroup.

3299 There is no unknown volumeto label in library %s.

A labeling process is initiatedin a library that does not con-tain any appropriate volume,i.e. volume that is bothunknown in the catalog andhas a valid bar-coded label.

Before beginning thelabeling operation:

l insert new media inthe library

l delete the volumesto re-label in theBackPak library

3300 %s process %s.%s initiatedto process %ld volumes in lib-rary %s.

A ‘LABELING’ or ‘MOVE TO IE’,or ‘MOVE FROM IE’ process isinitiated in the background.

None.

3301 Cannot initiate a %s processuntil the end of the %s pro-cess %s.%s already running

A ‘LABELING’ or ‘MOVE TO IE’,or ‘MOVE FROM IE’ processcannot be initiated.

Wait until the end of eachprocess before initiatinganother process.


for the same Data Store %s.

3302 Maximum number of labelingdrives %ld is invalid.

A library volumes labelingprocess is initiated with aninvalid number of drives.

Re-issue the command witha number of drives,numeric, non-zero, and notgreater than the number ofdrives configured for the lib-rary.

3303 Labeling TMF volume %s(drive %s) rejected byTMFSRV code %d. %s.

The equivalent of a TMFCOMcommand ADD TAPEMEDIA isrejected.

Analyze the TMFSRV return-code and associated text inthe message.HP Reference:TMF Management Pro-gramming Manual.

3304 s.%s labeled volume %s(#%ld/%ld) on %s in volumegroup %s. Volume is beingunloaded.

A library volume has justbeen labeled successfully byMEDIASRV or TMFSRV.The volume is being movedto a storage slot.

None.

3305 %s process %s.%s processed%ld volumes in library %s.

A ‘LABELING’ or ‘MOVE TO IE’,or ‘MOVE FROM IE’ processhas been completed.

None.

3306 No tape drive available tolabel volumes for Data Store%s.

It is impossible to use therequested number of drivesfor concurrent labeling.This happens when:- there are not enoughdrives connected to the NSKhost executing the label com-mand.- drives are down.- drives are used by otherapplication.This condition prevents thelabeling process to start.Once the labeling processstarted, this condition ini-tiates an infinite loop ofretries after 3 minutes delay.

If the labeling process star-ted, usually no action isissued.To allow the process tostart:- verify the status of drivesin the web UI Node StatusPage.- manage to have at leastone available drive on theNSK node that holds theDSMTC/TMF catalog.

3308 Timeout labeling %s on drive%s.%s, Volume group %s.

A MEDIASRV or TMFSRV pro-cess started to label a single

Search for EMS messagesissued by the NonStop tape


volume did not completeafter 10 minutes.

system, DSMTC or TMF, onthe NSK node holding theDSMTC/TMF catalog.

3309 SPI command to label volume%s (on drive %s) abortedwith error %d.

Severe error occurred whenreading theMEDIASRV/TMFSRV reply.

Analyze the Guardian filesystem error code reportedin this message.Search for EMS messagesissued by DSMTC or TMF, onthe NSK node holding theDSMTC/TMF catalog.

3310 %s Process %s.%s aborting.%s.

A LABELING or other back-ground process stops pro-cessing any more volumesbecause of a severe error.

Search for other EMS mes-sages on the node runningthe process (the Domain) orthe node that holds theDSMTC/TMF catalog.

3311 No more empty %s slot in lib-rary %s. Volume %s will beleft in %s slot.

A ‘LABELING’ or ‘MOVE FROMIE’ process does not find anyfree storage slot.A ‘MOVE TO IE’ process doesnot find any free IE slot.

The media is not moved.After a label, the mediathat was in IE slot and can-not be moved to a storageslot is simply moved backto its IE slot.

3312 Busy library %s did not replyto a %s message.

The BBLM process of a librarycannot reply to a requestbecause it is already busyexecuting another request.

On the web UI Node statuspage, the last known statusis reported.Action requests failed. Loadrequests that failed will beretried by the EMSExtractor.

3313 Only %d%% of SCRATCHvolumes available in volumegroup %s. Volume group hasreached the warning level of%d%%. %ld volumes areSCRATCH out of %ld volumesin the volume group.

A warning level (not enoughSCRATCH volumes) is detec-ted in the batch TACL macroBB024_ LIB_ SYNC or BB022_CHECK_SPACE.

Verify if DSMTC daily tapeexpiration is working prop-erly.Verify the TMF con-figuration.Add volumes in the library.

3314 TMF tapemedia %s alreadyexists in TMF catalog of node%s.

A TMF volume to label isalready existing in the TMFcatalog.

Use TMFCOM INFOTAPEMEDIA to ensure themedia with this label does


not contain any valid data.If the volume must belabeled, remove it fromtheTMF catalog by TMFCOMDELETE TAPEMEDIA.

3315 Invalid path for volume %s. Volume converted with (trun-cated path or dummy path).

Message issued by BB015,converting a volume catalogto a BackPak catalog.A virtual volume stored inWindows disk Data Store isregistered with an invalidWindows disk path.

None.If the volume must berestored by the restorescript before it is rewrittenby the product new version,a manual action will berequired.

3316 EMS Extractor for node %s isnot maintaining the oper-ational status in OPER file.Additional status querieswere executed.

Status of tape drives andmount requests are normallymaintained in the OPER fileby the EMS Extractors, forlighter processing of webrequests.In some conditions, forexample when the con-figuration has been modifiedor the EMS Extractor hasstopped, the information isnot available and externalentities must be queried:- NSK MEDIASRV- VTCs- Library Changer Controllers.

Be sure the EMS Extractoris running correctly.Restart and check for errormessages in EMS.

3317 Labeling volume %s failed:%s.

An error occurred in avolume labeling.

Refer to the end of mes-sage.

3318 Labeling volume %s skipped,current location %s notacceptable.

The current slot location inlibrary is not acceptable forlabeling.Occurs when the volume isalready loaded in a drive.

If the volume must belabeled, unload it, and re-issue the labeling process.

3319 Labeling %s volume %s (drive%s) rejected by SPI with code%d-%s. Retry #%d toexecute (%d retries max-imum).

The return- code ofMEDIASRV or TMFSRV to alabel command indicates afailure while writing labels tothe tape drive.Automatic retries should

If the maximum number ofretries was reached:

l be sure the labelingparameter “Over-ride” is checked.


overcome the error. l be sure the volumeis not already catao-loged in TMF /DSMTC.

l consider discardinga physical media.

3321 Error %ld %s the export des-tination %s '%s'. Export ofData Store %s catalogs abor-ted.

The configured destinationof Catalog Export is invalid.

Depending on the reportedGuardian error code, retryor edit the export con-figuration.

3322 Data Store %s is configuredwith %s domain access,SECONDARY domain access isrequired for importing cata-logs.

The Data Store domainaccess does not allow Cata-log import operations.

Change Data Store id orconfiguration.

3323 %s is invalid as catalogexport %s destination forData Store %s.

A catalog export destinationmust be a valid subvol name.

Change the export des-tination.

3324 %s is invalid as catalogimport %s source for DataStore %s.

A catalog import sourcemust be a valid subvol name.

Change the import source

3325 Error %ld %s the importsource %s '%s'. %s import ofData Store %s catalogs abor-ted.

The configured source ofCatalog import is invalid.

Depending on the reportedGuardian error code, retryor edit the export con-figuration.

3326 Unexpected file %s file-code%d in Catalog import sourcefor Data Store %s, fileignored (%s).

A file in the sub- volumesource of a catalog import orcatalog import status doesnot conform to nomen-clature of files created bythe Catalog export process.

Identify the file and moveit.Reserve a subvol for thestaging area of each DataStore.

3327 There is no completed FULLcatalog export available in%s for Data Store %s (error%ld).

Cannot access the full exportsummary file.

Modify the access to FULLfile or re- execute a FULLexport.

3328 Error %ld opening, read-ing…the import source %s

Unsuccessful access to acatalog export file.

Modify the access to thefile and retry.


'%s' for Data Store %s. Delete the file to allowother files to be processed.

3329 Volume %s received fromdomain=%s node=%sexportid=%s cannot beimported for local Data Store%s (reason)

An export file cannot be pro-cessed on the secondaryside.

Examine the reason forerror.

3330 Deletion of unreferencedvolumes is not executed atend of the FULL catalogimport for Data Store %s.Errors during the import, orthe number of volumes toimport (%ld) did not matchthe number of volumesexported (%ld) by domain-n=%s node=%s exportid=%s.

Deletion of obsolete volumeson the seocndary site isexecuted only at the end of aFULL import, but deleting thevolume unreferenced by theFULL import.The deletion is not executedif:- errors occurred in theimport.- the number of volumescomputed at export time andimport time does not match.

Fix the errors if possible.Re- execute FULL exportand import (without includ-ing DSM/TC DISKFILEentries) to delete obsoletevolumes.

3331 Export summary file (FULL orUPDATE file) not available insource %s. Catalog import ofData Store %s aborted.

The not available file pre-vents the import from pro-cessing.

Fix error if possible.If not, re-execute export.

3332 Primary volume group %s isnot configured in the localsecondary domain %s forData Store %s. For thisgroup, volumes to import willbe rejected.

The configuration of sec-ondary side contains avolume group that does notexist on primary side.

This volume group con-figuration will be uselesswhile the Data Store isSECONDARY. The only wayto add a volume in aSECONDARY Data Store isthe catalog import process.

3333 Secondary volume group %sof Data Store %s has no cor-respondence in the remoteprimary domain %s, wheregroup %s in Data Store %s ismissing. For this group, novolume should come fromthe primary domain.

The configuration of theprimary side contains avolume group that does notexist on the secondary side.

Configure the volume groupon the secondary side, ifthe volumes of this groupmust be imported.Enter the proper primaryVolume group Id in the con-figuration of the Volumegroup on the secondaryside.


3334 Catalog type discrepancybetween primary and sec-ondary domains for DataStore %s. For this group,volumes to import will becataloged in catalog only.

The catalog type (NONE,DSMTC, TMF, QTOS..) ofprimary and secondaryvolume groups do not match.

The volume will be impor-ted in the list of volumes,but no action done inDSM/TC.

3335 Invalid export id %s in %s. Fileignored.

The export-id (a time stamp)read in an export file isinvalid.This file looks corrupted andis ignored.

Contact Product Support.Re-execute export.

3337 Invalid content of catalogexport summary file %s.

A summary file (UPDATE orFULL) is invalid.

Examine the reason oferror included in the mes-sage.

3338 Invalid content of catalogexport volume file %s.(reason)

A volume export file isinvalid.

Examine the reason oferror included in the mes-sage.

3340 Too many BBEXT timers, %s%s timer not added.

The number of timers man-aged by the EMS Extractorfor the domain is too large.Processing continues withoutall timers.

Contact Product Support.Monito the pending exportsin the PRIMARY Data StoreCatalog export status page.Eventually submit andmanually export updates.

3341 Invalid BBEXT timer ignored(id=%d, delay=%ld).


3342 %s imported %s catalogs forData Store %s (%s volumesprocessed). Report in %s.

A catalog import processcompleted.

Check the named summaryreport.

3343 The DSM/TC catalog exportfor volume %s failed (errorcode %ld). DSMTC inform-ation omitted in the expor-ted data.

Error during the extractionof DSMTC volume inform-ation.The export stays pendingand will be retried.

Check for other EMS mes-sages issued by .Eventually, update theexport configuration toreduce the retry frequencyuntil the problem is fixed.Eventually, issue a FULLexport after fixing an errorcondition.

3344 The DSM/TC catalog import Error during the update of Check for other EMS mes-


for volume %s failed. Localpool &s in volcat %s is notavailable (error code %ld).

DSMTC volume information. sages issued by .Eventually, retry the sameimport after fixing theerror condition.

3345 The DSM/TC catalog importfor volume %s is rejected. Volume currently in use bythe DSM/TC with status %s.

Cannot alter the DSM/TCinformation about a volumethat is INUSE or SELECTED.

Wait until no Data Storevolume is used by any tapeapplication, before retryingthe same import.

3346 The DSM/TC catalog importfor volume %s is rejected.Error %ld returned byMEDIASRV %s.

The import of DSM/TCinformation failed whenquerying the SQL subvolumefor the DSM/TC data base.

Examine the return-code ofMEDIASRV.Verify the volcat and filecatnames in the volumegroups.

3347 The DSM/TC catalog importfor volume %s is rejected. Invalid imported data %s.%ld.

The import of DSM/TCinformation failed.

Examine the information inthis message and other pos-sible EMS messages.

3348 The DSM/TC catalog importfor deleting DSM/TC entriesfor unreferenced volume %sis rejected. %s.

The removal of a tapevolume through MEDIASRVfailed.

Examine the information inthis message and other pos-sible EMS messages.

3349 Primary Data Store %s can-not be detached from thedomain when there are cata-log updates to be exported.Catalog export is pending forvolume %s (%ld volumes arepending).

The Data Store Detach oper-ation is rejected.The Data Store is configuredfor exporting its catalog andsome volumes are pendingto be exported.

Finalize the catalog exportfor the Data Store beforedetaching it from thedomain.

3350 DSM/TC DISKFILE catalogexport for volume %s failed.%s (error code %ld). DSM/TCDISKFILE information omittedin the exported data.

Exporting the DISKFILEentries failed.The export stays pendingand will be retried.

Check for other EMS mes-sages.Eventually, update theexport configuration toreduce the retry frequencyuntil the problem is fixed.Eventually, issue a FULLexport after fixing an errorcondition.

3351 DSM/TC DISKFILE catalogimport for volume %s is

Exporting the DISKFILEentries failed.

Check for other EMS mes-sages.


rejected. %s. %ld. Retry the same importafter fixing an error con-dition.

3352 Error %ld opening report '%s'for %s process.\n.

A process cannot open anoutput file.

Examine the Guardian errorcode.

3353 Report filename is missingfor %s process.

The output configurationparameter is missing for aprocess.

Add a report spooler loc-ation or file name to theconfiguration (catalogexport or import).

3354 Adding volumes in aSECONDARY Data Store %s isnot allowed. Volumes mustbe created by the Catalogimport function.

The definition of the tapevolumes of a SECONDARYData Store can only be acopy of the definition of thevolumes in the cor-responding PRIMARY DataStore.

Retrieve the volumes defin-ition from a primary site,using catalog export /import functions.

3355 Primary and secondaryvolume groups cannot havethe same DSM/TC VOLCAT%s. DSM/TC data will not beimported for Volume group%s. This check can be dis-abled in the Catalog importconfiguration.

The same DSM/TC volcatbetween primary and sec-ondary sites is not allowed.

Change the DSM/TC volcatand filecat on the sec-ondary side.If the DSM/TC catalog name(that must be qualified bynode name) is the same,change the Data StoreImport configuration toenable “Import to the sec-ondary system which is dif-ferent from the primarysystem, but it shares thesame node name as theprimary system”.

3356 Invalid or unqualified DSM/TCfilecat name %s.

The DSM/TC filecat con-figured in a SECONDARYvolume group must be qual-ified by a node name, andknown by the MEDIASRV run-ning on this node.

Modify the volume groupconfiguration ofSECONDARY volume groups.

3357 Invalid or unqualified DSM/TCvolcat name %s.

The DSM/TC volcat con-figured in the volume groupmust be qualified by a nodename and known by the

Modificy the volume groupsconfiguration.


MEDIASRV running on thisnode.

3358 The DSM/TC not updated forvolume group %s. InvalidDSM/TC pool '%s'. %s.

The pool name configured ina volume group is not a validDSM/TC pool name.

Change the name of theDSM/TC pool or volcat inthe volume group con-figuration.If a MEDIASRV return-codeis reported in this message,look up for return- codeexplanations in theHPE manual DSM/TC Man-agement ProgrammingManual.

3359 The DSM/TC filecat %s asso-ciated with the volume group%s is the default filecat inthe system MEDIADEFS. Thisis forbidden when the DataStore is configured tochange the node of the filename of the DISKFILE entries,to import in the DSM/TC.

The Data Store Catalogimport configuration con-tains settings to change thenode part in the file namesof backed-up disk files.This is forbidden when thedisk file names to import arecataloged in the defaultFILECAT.

Consult the BackBox Cata-log Sync Option manual.Create a separate FILECATto receive DISKFILE entrieswhose disk file name isaltered.

3360 Info mediadefs for node %srejected by MEDIASRV code%d. %s.

Unable to execute the pro-grammatic equivalent of theMEDIACOM command INFOMEDIADEFS.

Look up for return- code explanations in the HPEDSM/TC Management Pro-gramming Manual.

3361 Domain configuration file(BBSVCFG) invalid or not avail-able. %s.

The domain configuration isnot accessible.

Look for the error details inthe message.

3362 Cannot extract DISKFILEs to%s, %s %s is missing.

The DISKFILEs cataloged inDSM/TC for a volume cannotbe read in the DSM/TC data-base.

Analyze the error detail.Verify the presence ofDISKFILE entries throughMEDIACOM INFO DISKFILEcommands.Restart the catalog exportoperation.

3363 LABELING process %s.%s ini-tiated to process %ldvolumes in library %s on %ddrives.

A labeling process is initiatedin the background for a tapelibrary.

None.


3364 %s process %s.%s processed%ld volumes successfully outof %ld in library %s.

A library batch /backgroundprocess reaches completion.

If the message shows thatall volumes were not pro-cessed, look for other EMSmessages to identify failedvolumes and the reason forerror.

3365 DSM/TC access disabled forvolume group %s. Invalid file-cat '%s'. %s.

The initial configuration val-idation of a catalog importdetects a configuration errorfor a volume group asso-ciated with the DSM/TC.

Verify the volume groupconfiguration in thedomain.A DSM/TC file catalog mustbe associated with thevolume group that is asso-ciated with the DSM/TC anda SECONDARY Data Store.

3366 Function not implemented.%s %s.

The software version cannotexecute the operation.

This might be displayed byintermediate / beta ver-sions.

3367 Invalid action '%s' on mountrequest %s.%ld.

The MEDIACOM verb to applyon a mount request is invalid.


3368 Mount request %s.%ldunknown in MEDIACOM.

A MEDIACOM action cannotbe applied because themount request is no morepending in MEDIACOM.

The mount request couldhave disappeared. Querythe node status again.

3369 %s command successfullyexecuted on mount request%s.%ld %s.

A MEDIACOM command suchas REJECT, was applied onthe mount request.

None.

3370 Domain license warning. Thenumber of configured ports(%d SCSI ports, %d FC ports)for VTC %s address %s,exceeds the licensed limits(%d SCSI ports, %d FC ports).

The license will not allow con-current use of all configuredports.Ports can be configured bey-ond license limits, only for“fail-over” purposes.This is displayed in EMS whenthe domain configuration isupdated.

None.

3371 Error loading Back-boxDeviceStatus reply from%s: port %d for device LUN%d target %d not known by

A VTC rejects a requestbecause it refers to aport/device that is notdefined by the internal VTC

In the UI, on VTC con-figuration page, verify thatthe domain configurationmatches the internal VTC


VTC. configuration (FCConfig.txtor VTConfig.txt).

configuration.Verify if the SCF device con-figuration matches also(check WWN).If necessary, modify FCCon-fig.txt or VTConfig.txt in theVTC.

3372 No drive is configured. A status query in the Back-Pak UI has no data to return,as there is no tape drive con-figured.

Have a virtual tape driveminimally configured in anon- disabled VTC beforequerying the status.

3373 MountId: %s. Volume %s stillnot loaded after %d minutes,exceeds the configured warn-ing threshold of %d minutes.Request time was %s.

The configured maximumdelay for loading a tapevolume has been reached.

Analyze EMS messagessince the mount request inthe node where the volumeis requested. If the DomainManager is running inanother node, also checkthe EMS in this other node.Adjust the maximum mountdelay in the domain con-figuration Domain Page.

3374 %ld drives not supporting %smedia type.

While searching a tape drivefor replying to a loadrequest, some drives werenot eligible because of notsupporting the requestedmedia type.This is a sub- messageincluded in message #3227.

Verify the media type in thedomain configuration,Volume Group Page.If DSM/TC, verify the mediatype of the TAPEVOLUME.

3375 Domain configuration haschanged. Configuration ver-sion cached in the UI session:%s, new version of %s con-figuration: %s.

During a BackPak UI session,the domain configurationhas been changed byanother session.

The UI manages this con-dition internally by issuingadditional “Get Config”requests.If the condition is visible,query the configurationagain to be sure the cacheis updated.

3376 Deleting volume %s that isstuck in drive %s.

BackLib: a volume is detec-ted to be registered in Back-Box as a result of a failedlabeling operation.

Verify the status of thevolume in the library.The BackPak Storageadmin page should show it


The volume is deleted fromthe BackPak catalog.

as an unknown volume can-didate to be labeled. Re-ini-tiate the labeling.

3377 Device %s.%s status unavail-able from MEDIASRV.

The status of a tape drivecannot be retrieved fromMEDIASRV; the drive cannotbe used for loading a volume.

Verify if the tape drive isconfigured in SCF.

3378 %ld drives not free inNonStop.

This is a sub- messageincluded in message #3227,reporting the number oftape drives that cannot beused for loading a volume,because of their status inSCF/MEDIACOM.

None.This is just additionalinformation to understandwhy a mount request is notprocessed.

3379 MountId: %s. Loading %s on%s %s exceeds encryptionlicense limits.

A mount request is rejectedbecause the license limitsare already reached by con-current operations (numberof ports, number of encryp-tion drives).

Wait for end of concurrentbackups and restores; auto-matic retries will use afreed up drive.

3381 MountId: %s. Volume %s isrequested outside the con-trol of the DSM/TC that isassociated with its volumegroup %s. It should berequested through aTAPECATALOG DEFINE, not adefine class of %s. Severalerrors can occur.

A volume assumed to becataloged in the DSM/TC isrequested by something dif-ferent from a TAPECATALOGDEFINE.A mount for output will berejected by the DSM/TC.A mount for input might failbecause the Windows files ofa SCRATCH volume do notexits.

Volumes associated withthe DSM/TC should be usedthrough OBEY files andTAPECATALOG DEFINE’s.

3382 Domain license warning. Thenumber of configured encryp-tion drives (%d) for VTC %saddress %s exceeds thelicensed number of encryp-tion drives (%d).

The license will not allow con-current use of all configuredLTO4 drives.LTO4 drives can be con-figured beyond license limitsonly for fail-over purposes.This is displayed in the EMSwhen the domain con-figuration is updated.

None.


3383 Pre-load for volume %s con-tinuation of %s is not ini-tiated. Volume alreadyloaded on drive %s.

In the restore from a multi-volume backup, the nextvolume is already loadedwhen pre- load is about toexecute.Pre-load is just not executed.

None.

3384 MountId: %s. Media %s notfound in slot %s of library%s. Library inventory run-ning.

BackLib: a media to load isregistered as "out of the lib-rary" in BackBox or not foundin the expected library slot.A library inventory is ini-tiated, after which the loadwill be retried.

Check for the retry out-come in EMS.

3385 Virtualization initiated on %lddevices in VTC %s. %s.

A virtualization of physicalmedia is either initiated orrejected.

Be sure the first media isalready loaded or will beloaded before the timeout.

3386 Materialization [not] initiatedin VTC %s on device %s. code%ld %s.

A materialization of virtualmedia is either initiated orrejected.

Be sure the media isalready loaded or will beloaded before the timeout.

3387 Renaming old statistics file%s (reclen %ld) to %s, torecreate it with new reclen%ld.

A upgrade changes the max-imum record length of thestatistics file, requiring tosplit the current statisticsfile into two files.The old format is renamedwith a special name that willstill be considered by theselection for the statisticsreports.The new format will receivenew statistics records.

After some version changesback and forth, it may hap-pen that the special filealready exists and therename failure is reportedwith error 10 in the EMS.In this state, statistics areno more accumulated untilthe current file is recreatedwith RECLEN 4000.The current file can also besimply deleted; and thenext event will recreate thecorrect current file.

3388 Deletion of old statistics file%s %s.

A statistics file is deletedaccording to the retentionconfigured in the UI domainpage.

None.

3389 Error in domain con-figuration hash: %s. Con-figuration protected by hash



is reset. Try/retry updatingthe domain configuration.

3390 User %s (%s) not authorizedto update the protected con-figuration item '%s', thatonly %s and %s user ids canmodify.

The software reserves themodification of a few con-figuration items to some spe-cific user-ids.

For information about aspecific item, refer to theproduct user manual.Sign on in the UI with thespecified user-id.

3391 BBSV was runningSUPER.SUPER. Full SIGNONfor user %s executed even if'Run interactive processesunder SIGNON user ID' is un-checked.

BBSV was runningSUPER.SUPER. Full SIGNONfor user %s executed even if'Run interactive processesunder SIGNON user ID' is un-checked.

Refer to the product usermanual.

3392 The status of the DSM/TCtapevolume %s on node %s is%s. It must be SCRATCH orBAD to allow deletion.

A BackLib labeling processfinds an entry already exist-ing in the DSM/TC or TMF.Such entries are deleted tobe recreated by the labelingprocess, only if their status isSCRATCH or BAD.

This volume is not (re)labeled.

3393 Invalid Key Manager ID %s. A Key manager ID is unknownin the domain configuration.

Configure the missing KeyManager or remove the ref-erence to it.

3395 Global availability of Key Man-ager %s: error/warn-ing/success.

Summary result of the func-tionality of a Key Manager.

Examine the detail of thetest reply, error messagesand test report.

3396 Client for Key Manager %stype %s is not configured (orVLE drives not connected) forVTC %s that is route to %sfor Volume group %s.

When the encryption isenabled for a Volume group,all VTCs that are routes tothe associated Data Storemust be able to join the KeyManager, i.e they must be aclient for this Key Manager.This test is made for allVolume Groups and failed forthe specified Volume Group.

Add a VTC client or a VLECLIM client connected toone of the VTC virtualdrives to the configurationof this Key Manager.

3397 %s is defined as a Client tothe Key Manager %s, butthere is no VTC with this

A VTC is defined as a KeyManager client, but does notexist anymore in the con-

Configuration corruption.Remove the Key Managerclient or define the VTC.


name. figuration as a VTC.

3398 Device %s %s.%s (%s)reserved for HP VLE, is notUP (status %s).

In the VTC domain con-figuration, a tape device isset for HPE VLE but is notusable because it is not UP.

Start the device in SCF andverify that the VTC reportsit as FREE in the UI Statuspage or the VTC con-figuration page.

3400 No encryption on VolumeGroup %s Data Store %s forNonStop %s using the KeyManager %s.

There is no possible load ofencrypted volumes for thespecified Volume Group.

See other error messagesreported by the Key Man-ager test page.

3401 MountId: %s. Decryptingvolume %s using Key Man-ager ‘%s’ is impossible: KeyManager %s not configured.

A Mount Request is rejectedbecause the Key Managerrequired to read anddecrypt the volume is notconfigured in the Domain.

Configure the Key ManagerID associated with thisvolume.

3402 MountId: %s. Encryptingvolume %s in group %s usingKey Manager ‘%’s isimpossible: Key Manager notconfigured.

A mount request is rejectedbecause the Key Managerrequired to encrypt and writethe volume is not configuredin the Domain.

Configure the Key ManagerID associated with thisVolume Group.

3403 MountId: %s. Impossible todecrypt volume %s using theKey Manager %s %s whenthe Volume group %s is con-figured for writing using thedifferent Key Manager %s%s.

A mount request is rejectedbecause, when HPE VLE isinvolved, the same Key man-ager must be used for boththe decryption (Key man-ager associated to thevolume) and the encryption(Key manager associated tothe Volume group).

Modfify the configuration.

3404 Timeout, more than %ldseconds executing %s com-mand '%s' on node %s.

A query has been submittedby starting a NonStop sys-tem utility that does not endin expected time.

If this symptom is explainedby a temporary systemglobal state, retry the com-mand.

3405 %ld drives without client toKey Manager %s for decrypt-ing.

Part of a message #3227 “Noavailable resource tomount…”.Some drives cannot be usedbecause they are not asso-

If HPE VLE devices aredown, start them using SCF.


ciated with any Key Managerclient: no VTC Client and noVLE CLIM Client.

3406 %ld drives not connected toan expected VLE CLIM, or nonLTO4 request.

Part of a message #3227 “Noavailable resource tomount…”.Some drives cannot be usedas VLE drives because theyare not on a CLIM that is con-figured as a client to the KeyManager or because thevolume media is not LTO4type.

If HPE VLE must be used,ensure that:- The Volume group is con-figured for LTO4- If DSM/TC, the volumesare cataloged as LTO4 tapevolumes.

3407 No ETI-NET Key Manager cli-ent configured for Key Man-ager %s %s.Encryption/decryptionimpossible.

In “VTC ONLY” Key Managersetup, a VTC client must beconfigured in the Key Man-ager for all VTCs that areroutes for the encryptedvolumes.

Modify the configuration.

3408 No client in VTC %s for KeyManager %s %s (no VTC cli-ent configured and no driveconnected to VLE CLIMs).Encryption/decryptionimpossible.

In “VLE INTEROPERABILITY”setup, VTC clients and/orCLIM clients must be con-figured in the Key Manager.

Modify the configuration.If some or all clients areVLE CLIM, verify that themedia type of the volumesis LTO4 in the DSM/TC andin the Volume group.

3409 No drive in the domain is cur-rently connected to VLE CLIM%s.

A VLE CLIM is configured as aKey Manager client, but nodrive is set for encryption inSCF and connected to thespecified CLIM.

3410 Key Manager %s is notneeded to encrypt newbackups for any VolumeGroup (but might still berequired to decrypt oldvolumes that were encryptedwith different Volume Groupconfiguration).

A Key Manager ID is no morereferred by any specificVolume Group.But it might still be referredby a Volume that was encryp-ted with a different VolumeGroup configuration; i.e. thekey server might contain theencryption key required torestore it from this TapeVolume.

The report BB038 can bechecked to verify thevolumes whose encryptionkey is stored in this KeyManager.The deletion of the KeyManager can also beattempted: the deletion willbe rejected if any volume ofthe domain still needs thisKey Manager.


3411 Some Volume Groups haveno connectivity at all to theKey Manager %s.

Encrypted backups areimpossible for some VolumeGroups. Even if there are sev-eral VTCs routes to the DataStore, none of the VTCs canconnect to the Key Manager.

Verify the configuration inthe Domain.

3412 %ld VLE drives not usablewithout HP VLE encryption onLTO4 media.

Part of a message #3227 “Noavailable resource tomount…”.Some drives configured forVLE in SCF cannot be usedbecause the volume mediatype is not LTO4 or becausethey are not associated witha CLIM that is defined as aVLE CLIM client for the KeyManager.

3413 Volume %s was encryptedwith Key Manager %s that ismissing in the configuration.Volume is cataloged locally,but restore is impossibleuntil %s is configured in thelocal domain.

A Key Manager is missing inthe configuration, making avolume impossible todecrypt.

Configure the missing KeyManager in , the key clientsand the server.

3414 Primary Volume Group %s isconfigured for Key Manager%s that is missing in the localdomain configuration.Decryption of replicatedvolumes will be impossibleuntil the Key Manager is con-figured.

A Key Manager is missing inthe local domain where aCatalog Import is executing.The imported volumes can-not be decrypted until theKey Manager is configuredunder the displayed Key Man-ager ID.

Configure the missing KeyManager in , the key clientsand the server.

3415 Primary Volume Group %s isconfigured for %s Key Man-ager %s while local VolumeGroup %s is configured forthe different Key Manager%s. logical Key Manager IDsare usually identical whenpointing to replicated KeyManagers.

There is a mismatch on theKey Manager ID while a Cata-log import is executing.The local Volume Group doesnot refer to the same KeyManager ID as the primaryVolume Group.

This is a warning.It is expected that the KeyManagers on both primaryand secondary sides areeither identical or mirrored.Use the same Key ManagerID for best results.


3416 VTC %s has no encryptiondrive authorized in the Back-Pak license.

A VTC that is routed for aVolume Group requiringencryption is not licensed forencryption (by the license).

No virtual drive presentedby this VTC can be used forloading the volumes of thisVolume Group.If no other VTC is licensed,these volumes cannot beoperated at all.

3418 Key Manager %s cannot bedeleted, as it is needed bythe Volume Group %s.

An attempt to delete a KeyManager is rejected becauseit is still used.

None.

3419 Key Manager %s cannot bedeleted, as it is needed bythe volume %s and other %ldvolumes.

An attempt to delete a KeyManager is rejected becauseit is still needed to restoreOld Volumes.

The report OBB038 can beused to list all volumesencrypted with a key storedin this Key Manager.

3420 Automatic change to theDomain configuration: Hostname for VTC %s changedfrom '%s' to '%s'.

A connection to a VTC revealsa new host name that mustbe registered in the domainconfiguration.

Check the license key.

3421 The DSM/TC must be rep-licated to a dedicated cata-log. %s %s cannot be thereplication target for VolumeGroup %s %s, because it isalso updated by VolumeGroup %s. This check can bedisabled in the 'Catalog SyncImport' page of the DataStore configuration.

The DSMCT volcat or filecatconfigured for a SecondaryData Store or for associatedVolume group is also used byanother secondary Data Store or by local backups (i.e.Primary Data Store).The different sources updat-ing this catalog creates arisk of collision onTAPEVOLUME labels and onTAPEFILE fileid, leading todata corruption in theDSM/TC.

If the user is able to manu-ally control the combinedTAPEVOLUME and TAPEFILEin the merged catalog, thenthis option can be disabledin the Data Store Catalog.Import configuration of theData Store by selecting“Allow to store replicatedDSM/TC entries in a localDSM/TC catalog that is notdedicated to this rep-lication (i.e. merged withother replications or withlocal backups)”.

3422 Error %ld while opening FULLfile in the export destination'%s'. Export of Data Store%s catalogs aborted.

Guardian rejects the openingof the control file in theexport staging area.

Check the Guardian errorcode and the file name(FULL - qualified by theexport destination).The most common error isthat the remote export des-tination is not available.Wait for the reconnected


Expand to resubmit FULLexport.

3423 Data Store %s has no routewith functional encryptionfor Key Manager %s.

No VTC configured as a routeto the named Data Store canpresent a virtual tape withfunctional encryption.

Modify configuration (orwait for VTCs to be star-ted).

3424 VTC %s is not an active routefor any Volume group refer-ring the Key Manager %s. KeyManager client connectivityfrom %s is not needed toencrypt new backups, butmight be required to decryptold volumes that wereencrypted with differentVolume Group con-figurations.

A VTC is configured as a cli-ent of the Key Manager. Thisclient is not needed for anynew backups in this domain,but it might be needed forRestore.

This may be a valid inter-mediate option while theimplementation of encryp-tion is not completed.Do not forget to enable theencryption in the VolumeGroups.

3425 Error %ld %s for? the import-export staging %s '%s'.

IO error occurring duringaccess to the import-exportstaging area.

Refer to the Guardian ErrorMessages Manual on howto fix this error.

3426 %ld drives without client toKey Manager %s for encrypt-ing.

Part of a message #3227 “Noavailable resource tomount…”.Some drives cannot be usedbecause they have no con-figured client to the KeyManager identified by theVolume Group.

3427 Error %ld %s '%s' containingresult of command '%s'.

Error when executing aNonStop utility to query theNonStop configuration.The message names the diskfile given as an “OUT” file tothe utility.

When the error code is spe-cifically 40, refer to ErrorTriggering a NonStop Utility

3428 Error reading '%s' containingthe result of command '%s':%s.

Error when analyzing the out-put of a NonStop utilityreporting a NonStop con-figuration.

Contact ETI-NET support.


3429 Anomaly getting tape con-figuration from %s: %s. %s.

Error or warning when ana-lyzing the output of aNonStop utility reportingNonStop configuration.

Case “ Host lun %ld in clim%s from climcmd lunmgr --print was not memorizedfrom scf info clim”:A tape drive was discoveredby a CLIM, but not definedas a TAPE in SCF. This mightbe:- left as is,- ‘fixed’ by a TAPE definedin SCF,- ‘fixed’ by reducing thenumber of supported vir-tual drives in the FCCon-fig.txt file of the VTC (it isnecessary to restart theEmulator Windows).Case “VLE tape %s returnedby STATUS TAPE was notstored from INFO CLIM”:Discrepancy was foundbetween two query out-puts. Retry once, beforecontacting Product Support

3430 %ld VLE drives not connectedto the CLIMs associated withthe Key Manager %s.


Fix the configuration of theKey Manager.

3431 %ld drives reserved for expli-cit allocation only, or do notmatch explicit allocation.


None. When a drive withoutreservation becomesunloaded, the load will besuccessful.

3432 Special character ‘%s’ in '%s'is forbidden for %Store ID".

The syntax of the enteredvalue is not supported.

Enter a value without thespecial character.

3433 No Volume Group in thedomain configuration refersto a tape catalog in node %s.

A virtualization is submittedby searching the tape cata-logs in a given node, but theconfiguration does not referto any specific tape catalogin this node.

Verify the tape catalog spe-cified in the configurationof all possible VolumeGroups.

3435 Volume %s label type %s was A virtualization is submitted Verify the tape catalog spe-


not found in the NonStoptape catalogs configured inthe Domain for node %s.

by searching the tape cata-logs, but the volume with spe-cified label and label typewas not found.

cified in the configurationof all possible VolumeGroups.

3436 The catalog type of Volumegroup %s is %s. The VolumeGroup must be NOTCATALOGUED when it is adefault group after a searchin NonStop catalogs.

A virtualization is submittedby searching the tape cata-logs and a default VolumeGroup is specified forvolumes not found in thecatalog.This default Volume grouppoints to a tape catalog,when it should be specifiedfor NON- CATALOGEDvolumes.

Choose a default VolumeGroup configured for Nocatalog.

3437 Media type of volume %schanged from %s to %s in %s%s, to match the con-figuration of the VolumeGroup %s.

A new volume is registered inthe BackBak domain from anentry in the DSM/TC.The media type of theDSM/TC TAPEVOLUME isupdated to match theVolume Group configuration.

Data provided for inform-ation purposes only.

3438 Unexpected MEDIACOM replyto command '%s': %s.

A command was issuedthrough the MEDIACOM pro-gram, but the received replyis not one expected by thesoftware.

If the received messagereply does not provide caseresolution, contact ProductSupport.

3439 Unexpected status '%s' inQTOS catalog %s for volume%s, assumed to be '%s'.

An unexpected value is foundfor a volume status in theQTOS catalog.


3440 Volume %s is a member ofthe Volume Group %sdefined with the QTOS cata-log %s, but the label is eithernot found at all or found withan unexpected status in theQTOS catalog. Check con-figuration.

An error is detected whenaccessing the QTOS catalogto obtain the status of atape volume.

Verify the configuration ofthe Volume Group.Subsequently delete thevolume in the Bac Domainthat was deleted in theQTOS.

3441 The status %s of volume %sin the QTOS catalog %s does

A QTOS volume is deleted inthe Domain, but the volume

Verify the content of thevolume in the QTOS.


not allow deletion. Deletionrequires the status SCRATCH,BAD or UNKNOWN.

is still present in the QTOSand it looks like it contains anon-expired backup.

Update the status or deletethe volume in the QTOS toallow deletion in .

3442 Volume %s with labels %sand status %s is found in %s(Volume Group: %s), whilesearching labels %s andstatus %s. This mismatchedcatalog entry is ignored andsearching continues in othercatalogs.

A virtualization is submittedwhen searching the tapecatalogs.During the search, half-matches are found andignored.

To achieve a successfulsearch, all labels, labeltypes and status mustmatch the cataloged entry.If there is an inconsistencywhen searching / checkingall labels, label types andstatus, bypass this checkand configure the VolumeGroup for non- catalogedvolumes.

3443 Volume %s with labels %sand status %s is found in %s(Volume Group: %s) amongother catalogs. All occur-rences of catalog entries areignored.

A virtualization is submittedwhen searching the tapecatalogs.There are multiple matches.

A single match must befound for a successfulsearch.Remove the extra VolumeGroups or update their con-figuration for “ non- cata-loged volumes”.

3444 Cannot materialize on thedevice %s in VTC %s. Devicesemulated by VTC are for vir-tualization only.

It is not possible to achievematerialization on a devicethat is directly connected toa third-party VTS.

Attach a physical drive formaterializations.

3445 Automatically importing theSCRATCH volume %s reques-ted by a backup, and found inthe NonStop catalog %s,(Volume Group: %s).

$ZSVR issued a mountrequest for an unknownvolume in the Domain. If theAutoScratch option is on anda tape volume with a namenot defined in the , but in aMediacom Pool associatedwith a volume group, thatvolume will be added to thecatalog in the specifiedvolume group.The volume is automaticallyadded to .


3446 Errors or warning detectedwhile verifying the access tostorage of Data Store %s.

A verification of the storageavailability was executed anderrors were detected.

Verify all messages gen-erated in the EMS duringthe operation, as various


Check in Storage Admin pageand in EMS.

The current operation (a cre-ation of tape volumes, forinstance) might be suc-cessful, but the configuredresources may not be fullyavailable.For example, one of the VTCscannot access a file server.

errors / message numbersmay be present.Test the access to the DataStore in the Storage Adminpage, by successively choos-ing all routes to the DataStore.

3447 Process %s initiated toimport %s from the catalog%s (Volume Group %s).

An “Import from Tape Cata-log” was initiated by the UI toregister volumes in the Back-Pak Domain, already knownin a NonStop tape catalog.The process will run in thebackground.

Data provided for inform-ation purposes only.Verify the messages in EMSup to the end message#3448.

3448 Process %s import from thecatalog %s to Volume Group%s ended. %s volumes werecreated in , %s volumes weremigrated from other VolumeGroups.

An “Import from Tape Cata-log” has been completed.

Data provided for inform-ation purposes only.Verify the number of pro-cessed volumes.

3449 Cannot import volumes fromcatalog %s to Volume Group%s because the has no inter-face with this catalog type.

An “Import from Tape Cata-log” is initiated from a tapecatalog that is not supportedby .

None.

3450 NonStop session started on%s exceeds the maximum of240 minutes. Session ended.

A domain activity reachesthe maximum duration.This applies specially to theUI pages with Auto-Refresh.

None.

3453 Volume %s is requested inVolume Group %s linked withthe QTOS catalog %s vault%s. %s. Auto- scratch notexecuted.

A QTOS volume is requestedby a mount request andthere is a mismatch betweenthe and QTOS.The auto-scratch function isnot executed.

Verify that the vault spe-cified in the Volume Groupmatches the QTOS vault.

3454 MountId: %s. Label requestedwas %s, label %s is nowrequested by $ZSVR. %s".

While a mount request ispending, $ZSVR re-evaluatesthe label to load for thissame Mount Id.



3455 Migration of volume %s,from Volume group %s andData Store %s, to Volumegroup %s and Data Store %s.

An “Import from Tape Cata-log” was initiated for aVolume Group.A tape volume is alreadyknown in the catalog, butwith a different VolumeGroup.The tape volume is re-assigned to the new VolumeGroup.

Verify that this result is theexpected result.Eventually, modify the con-figuration of the VolumeGroups and re- excute the“Import from Tape Cata-log”.

3456 Error exporting a DISKFILEwritten on several volumes.Error %ld %s %s destinationfile '%s', Data Store %s. Export continues, MEDIACOMRECOVER might not work.

During a catalog export, anerror occurs for a DISKFILEwritten on several tapevolumes.When the result of this oper-ation is imported in the sec-ondary site, the DISKFILEsplit in two tape volumesmight be incompletely cata-loged.This will not affect the exe-cution of the RESTORE pro-gram.MEDIACOM RECOVER mightnot work, depending on thedisk files to restore.


3457 Unload %s from drive %s.%srejected. The volume status%s does not allow unloading.

Incompatible actions. After related operationcompleted:1. Verify the drive status inthe UI, Status Node page.2. Verify the status of thevolume In the Volume Listpage.

3458 MountId: %s. Automatic loadfor volume %s disabled aslong as the migration to is%s in Volume Group %s.

Mount request automationdisabled by the VolumeGroup configuration setting“Migrate to BackPak”.

None, if the result obtainedis the expected result.

3459 Error %d %s output OBEY file%s preparing virtualizationjob for Volume Group %s.

File access error in Vir-tualization automation.

Specify another OBEYFILEname.

3460 OBEY file %s successfully pre- The preparation of a vir- None.


pared to virtualize %ldvolumes in Volume Group %s.

tualization has completed.

3461 '%s' is an invalid output des-tination for %s: %s.

A configured output isinvalid. The syntax is invalidor the included processname is not a running pro-cess.

Review the output spe-cification or start therequired process.

3462 %ld is not a valid base tocompute a series of tapelabels.

When creating tape volumes,the base to compute thenext label can be only 10, 16or 36.

This is normally a userselection in the UI.Verify that the UI and theDomain Manager BBSV areof the same version.

3463 Obsolete domain con-figuration elements will beremoved at next con-figuration update: %s.

Information provided afteran upgrade.

Keep track of the reportedelement names until thenew environment is fullyverified. If Product Supportis contacted, provide thisinformation.

3464 VTC %s is not an availableroute to DataStore %s. %s.

A VTC cannot be connectedby TCP/IP for sending controlmessages.

Search for previous errormessages in EMS.

3465 Operation %s on Data Store%s: volume %s skippedbecause it belongs to %s %srather than the expected %s.

A batch job run for a WINDISKDataStore hit a volume thatdoes not belong to the expec-ted Data Store or VolumeGroup.This happens when differentData Stores point to thesame disk directories.

Create distinct directoriesfor different Data Storesand move the proper Win-dows files in the proper dir-ectory.

3466 %s rejected for multipleerrors, verify all messages.

Indication that the UIreceives a list of warnings orerror messages.

Verify all messages beforecontinuing in the UI.

3467 File %s not found. It will notbe recreated empty becauseit is accessed in read-onlymode.

Operational files such as theBackPak catalog VOLUME arerecreated empty when notfound.This creation is not executedwhen the file is accessed forread only.

Use a function thataccesses the file in theupdate mode to have thefile recreated.For the VOLUME file, createa new virtual volume.


3468 '%s' is not a valid sub-volumefor %s (%s).

A Guardian disk subvolumespecified in the configurationis invalid.

Enter a valid sub-volume.

3469 Guardian node '%s' is invalidor not available. Cannotverify if the serial number islicensed.

The named node cannot bequeried to get its serial num-ber.Actual license validation ispostponed.

Double- check the nodename for which virtual tapedevices are configured (Con-figuration tab, VTC page).

3470 License key missing in thedomain configuration.

The license key is not yetentered in the configuration.

In the UI, Configuration,Domain page, enter thelicense key as provided byProduct Support.

3471 Invalid DSM/TC volcat '%s' orpool '%s' for Volume Group%s.

The configuration contains aVolume Group with an invalidDSM/TC volcat & pool.

Use MEDIACOM to validatethe volcat and pool names(volcat must be qualified bythe node name).Use the UI to fix the VolumeGroup configuration.

3472 SSL %s on %s socket with %s%s fails. Error %ld, %s.

A call to the NonStop SSL lib-rary for the specified socketis rejected.

Use the returned code andtext with the doc-umentation of the SSL pro-vider.

3473 SSL %s on %s %s fails. Error%ld.

A call to the NonStop SSL lib-rary is rejected.

Use the returned code andtext with the doc-umentation of the SSL pro-vider.

3474 Define %s %s is missing. A DEFINE is missing in the pro-gram TACL environment.

Refer to the doc-umentation of the programissuing the message.

3475 Error %ld %s the bbsetup file'%s'.

An error occurred in the read-ing of the BBSETUP file.

Update the NonStop envir-onment to allow the accessto BBSETUP.

3476 Error parsing the bbsetupfile '%s, section %s': %s.

The TACL macro syntax can-not be parsed.

TEDIT BBSETUPto verify the syntax of TACLmacro sections.

3477 Domain configuration %supdated by %s.

Information only. The domainconfiguration has been

No specific action required.


updated by the specifieduser.

3478 Catalog %s.VOLUME updatedby %s. %ld volume (s) %s,from %s to %s.

Information only. The Back-Pak catalog virtual volumeshas been changed by the spe-cified user.

No specific action required.

3479 SSL library error %ld (= %s)on socket %ld %s %s %s,remote addr:%s port:%s, %s.

A socket action through theNonStop SSL library returnedan error.

Interpret errors > 0 as reg-ular NonStop socket error.Interpret errors < 0 asOpenSSL error or errorfrom the NonStop SSLproduct.

3480 File %s is not available, error-r=%d. (%s).

A NonStop file is not availble. Update the NonStop envir-onment to allow access toBBSETUP.

3481 TCP/IP connection with SSLfrom %s %s is rejected.Domain Manager BBSV notset for SSL.

The Domain Manager BBSVthat is not set for SSLreceived a SSL request.

Enable SSL in the NonStopprograms (macro BB051_RELINK) or disable SSL inthe client UI or VTC.

3482 %ld drives not running on thesame CPU %s as the tapeapplication.

Mandatory CPU affinity can-not be respected.

Wait for a free tape IOP run-ning on the requested CPUor modify the NSK profile inthe Domain configurationto remove the CPU affinityobligation.

3483 Error %ld in %s reply by VTC%s - %s.

A VTC returns an error codeto a Domain Managerrequest.

Refer to the code and textreturned by the VTC.

3484 NSK tape {virtualization |materialization} waiting %sminutes for an input tape tobe loaded on drive %s.

BB055 programs wait for aninput volume to be loaded.

Load a volume to virtualize(or to materialize).

3485 NSK tape {virtualization |materialization}: inputvolume %s (labels %s) isloaded. %s.

The volume to duplicate isidentified.

None.

3486 NSK tape {virtualization | BB055 program acquired its None.


materialization} ready tocopy volumes from %s to %s.Volume Group is %s.

parameters and it can openthe two tape drives.

3487 NSK tape {virtualization |materialization} of volume%s (labels %s) successful. %s%s data and %s file- markscopied.

Successful end of a volumecopy; copied data size andfile-marks are displayed.

None.

3488 NSK tape {virtualization |materialization} of volume%s UNSUCCESSFUL. %s %s.%s MB data copied.

The copy of a volume failedfor the specified reason.

Analyze the error descrip-tion.

3489 NSK tape {virtualization |materialization} is idle. Stopsafter waiting %s minutes fora tape to be loaded on drive%s.

Timeout waiting for an inputvolume to be loaded.

None.Eventually, set the waittime as needed by the“PARAM IDLEWAIT minutes”.

3490 NSK tape {virtualization |materialization} aborts %s%s.

The copy aborts for the spe-cified reason.

Analyze the error descrip-tion.

3491 NSK tape {virtualization |materialization} skippinginput volume %s.

This message followsanother error message,reporting why the volume willnot be copied.

None.Load the next input volumeafter this skipped volumehas been unloaded.

3492 Domain license violation.Device %s directly connectedto VTS in %s for Vir-tualization / Materialization,is not licensed.

The feature is not licensed. Contact Product Support toobtain an appropriatelicense key.

3493 Client %s %s %s (messageversion %d) does not supportthe configured %s requiringversion %s.

A back-level component con-nects to the Domain Man-ager.

Upgrade the client com-ponent.

3494 Server %s %s %s (version %s)does not support the con-figured %s requiring version%s.

The Domain Manager con-nects to a VTC that is back-level.

Upgrade the server com-ponent.


3495 NSK tape virtualization /materialization ends. %svolumes successfully copiedfor %s %s. %s volumesskipped.

BB055 tape copy reports theend of the processing.

None.

3496 DSMTC DISKFILE catalogimport for volume %s doesnot fit in a single TMF trans-action. Commit forced after%s DISK FILES.

Catalog import forces a com-mit before the end ofTAPEFILE, according to thesetting in Catalog import con-figuration page.

If the import processabends, use MEDIACOM todelete the incompletelyregistered TAPEFILE beforeresubmitting the CatalogImport.

3497 No path configured in theCopy Pool of the Data Store%s for running the Copy Syncprogram.

The Data Store configurationis inconsistent.

Either remove the CopySync request in theadvanced Data Store con-figuration or add a path inthe Copy Pool of the DataStore configuration.

3498 {Backup|copy} scripts will besubmitted for Data Store %s%s by process %s.

The scripts will be submittedin the background by theDomain Manager running inNonStop.

None.

3499 {Backup|copy} script sub-mission for %s rejected by%s with error %ld - %s.

A script cannot be submittedfor the included error text.

Analyze the reason for theerror. After correction,resubmit for a volumethrough the Volume detailpage or for the whole DataStore through the StorageAdmin Page.

3501 CONNECT to BB-DOMAINSERVER failure, error %1.

The EMS Extractor failed toconnect to the Domain Man-ager.

Refer to the HPE NonStopTCP/IP ProgrammingManual. Socket errors.

3502 WRITE to BB_DOMAINSERVER failure, error %1.

The EMS Extractor failed toconnect to send data to theDomain Manager.

Refer to the HPE NonStopTCP/IP ProgrammingManual. Socket errors.

3503 READ from BB_DOMAINSERVER failure, error %1.

The EMS Extractor failed toconnect to read data fromthe Domain Manager.

Refer to the HPE NonStopTCP/IP ProgrammingManual.Possibility of socket errors.


3505 Domain Manager reply: %s. A GET Pending Mounts to theEMS Extractor, was rejectedby the Domain Manager.

Refer to the reply messageof the Domain Manager.

3506 Max Retries (%1) reached forload request %1 on %2. Nomore retries.

The number of retriesreached the max- failsafe-retries configured for theEMS Extractor.

Check the status of virtualdevices.Check the BBEXTCFG con-figuration file.

3507 MAX-PENDING-MOUNTS(%1)reached.

An internal limit wasreached.


3508 BBEXT must be started by auser in SUPER group, currentuser: %1.

The EMS Extractor must rununder a User ID in the SUPERgroup.

Restart BBEXT with a UserID in the SUPER group.

3509 Running BBEXT requiresinfile: run BBEXT/in BBEXTCFG,name/ .

BBEXT needs a configurationfile in its standard input.

Check the TACL RUN com-mand or the SCF definitionthat registers BBEXT as apermanent process.

3510 Unable to get required para-meter from EMS- event: %1error, ignoring this mount.

BBECT is unable to extract atape-related event from theEMS.

None, if no other symptomsoccur.

3511 %s loaded in VTController at%s for mount request %ld,but the request is stillpending. Load being retried.

A volume load was suc-cessful, but the mountId isstill in the list of pendingmounts.A new attempt is executed.

Check the outcome of theretry.

3512 Loading of %s initiated inVTController at %s forrequest %ld, but the requestis still pending.

A volume load was suc-cessfully initiated, but themountId is still in the list ofpending mounts.A restore script was initiated,but did not complete suc-cessfully yet.

Check the log of therestore script.

3513 BBEXT config error: %s. There is an error in theBBEXTCFG file.

Refer to the BBEXT sectionof the Installation chapter.

3514 BBEXT cannot open EMS fil-ter file %s, errno=%d.

The EMS filter that reducesthe traffic between the EMSdistributor and BBEXT cannotbe opened.

Verify the EMS filter filename in the file BBEXTCFGand the file security.The distributed EMS file is


named EMSFILT1.

3516 Pre-load for volume %ld %scontinuation of %s is not ini-tiated. %s was alreadyrequested on %s by themount-id %ld.


None.

3517 EMS Extractor started fordomain %s (BBEXTversion).


None.

3518 Invalid label type %d asso-ciated with mount request%ld volume %s in MEDIASRV.

Unexpected code for thelabel type in a mount requestdescription provided byMEDIASRV.

Report the warning toProduct Support.Verify the correct volumeloading for the tape applic-ation.Subsequently, load thevolume through the webapplication.

3519 Mount request %ld for %snot sent to Domain Managerbecause of previous errors.

Refer to previous EMS mes-sages.

Verify the correct volumeloading for the tape applic-ation.Subsequently, load thevolume through the webapplication.

3521 Mount request %ld is can-celed/rejected: automaticunload of %s.

An EMS message reports themount request is rejected byMEDIACOM, or canceledbecause the tape applicationstopped.An automatic unload is gen-erated to free the device, incase it is already loading orloaded.

None.

3522 Automatic unload of %s thatpreloaded for a tape applic-ation process that is nolonger running (%s.%d,%dstarted on %s).

The EMS Extractor detects acase where a loaded/loadingvolume will never be used bya tape application, con-sequently not unloaded afterusage.An automatic unload is gen-erated.

None.


3523 Unable to extract %s tokenfrom EMS event #%d %s,event ignored.

Error parsing an EMS event. Contact Product Support.

3524 Unable to process the mountrequest %d with the reques-ted label '%s'. Requestignored.

is not able to process anentry in the list of pendingmount requests reported byMEDIASRV.

If this request needs to beprocessed by , contactProduct Support.

4003 Error [rc] in #DEFINESETATTR[attrname] [value]

Error returned by the TACLfunction #DEFINESETATTR.

Refer to the HPE documentTACL reference manual.

4500 %s: Invalid Msg Key detected. A TCP/IP message receivedby the library manager BBLMprocess has become cor-rupted.

Verify proper TCP/IP oper-ations on the NonStop sys-tem (s) running BBSV andBBLM programs.If the problem persists, con-tact Product Support.

4501 %s: Cannot find the SCSI IOPin the list.

Internal error in library oper-ations.

Contact Product Support.Verify the configuration ofthe library in the Domain.Restart BBLM.

4502 Cannot find the DTE address%d.

A library media move reques-ted to load a volume refersto an invalid drive address.


4503 Tape drive busy. Cleaning inProgress.

A request is rejected by thelibrary changer that isalready busy with anotherrequest.

Automated load requestswill be retried.Re-issue the manual com-mands request “load/un-load”.

4504 Volume not present in the lib-rary.

A request is rejectedbecause the volume is not inthe library.

Use the web UI to ‘Get thelibrary inventory’ that willresync the slots locationstored in the inventory.Re-issue the command.

4505 Destination Element Address%d is Already Full.

Destination of a librarymedia move is invalid.



4506 Source Element Address %dis Empty.

Source of a library mediamove request is invalid.


4507 The volume is still used bythe tape drive. Eject thevolume first.

A library changer action isrejected because the volumeis still used by the NonStophost.

Wait until the tape applic-ation unloads the volume.Then use the web UI Nodestatus page to unload thevolume.

4509 Source Element Address %ddoesn't contain the volume%s.

The library inventory storedin the BackPak catalog doesnot match the actual libraryinventory.


4510 %s: malloc error - %s. Internal error. Verify that the NonStopmemory management oper-ates normally.Contact Product Support.

4511 The device connected to theSCSI IOP is not a MEDIACHANGER".

The device configured in theBackPak Domain to controlthe media changer is not con-nected to a media changer.

Use the web UI to veri-fy/update the Open SCSIdevice name.Verify the SCF configurationand cable connections.

4512 %s: File system error (%d)occurs while communicatingwith process %s.

Severe error occurred in com-munication with the OpenSCSI device IOP (mediachanger).

Search for EMS messagesissued by the Open SCSI IOP.Restart the Open SCSIdevice in SCF.

4513 %s: File system error (%d)with BUFFER- status (%d)occurs while communicatingwith process %s.

Severe error occurred in com-munication with the OpenSCSI device IOP (library mediachanger).

Search for EMS messagesissued by the Open SCSI IOP.Restart the Open SCSIdevice in SCF.

4514%s: Detecting error whileparsing READ ELEMENTSTATUS".

Error in the parsing of a replyof the library media changer.

Search for diagnostics onthe library console.Search for EMS messagesissued by the Open SCSI IOP.Restart the Open SCSIdevice in SCF.


4515 %s is DOWN. The “open SCSI” device con-trolling a library mediachanger is down.

Restart the “open SCSI”device in SCF.

4516 Volume movement from %sto %s %s is prohibited by theMEDIA CHANGER model.

A media move is rejected bythe library media changer.


4517 %s does not exist on this sys-tem.

The “open SCSI” device con-trolling a library mediachanger does not exist.

In SCF, define and start the“OPEN SCSI” device namedin the library configuration.

4518 %s: Guardian error %d on%s".

Severe error occurred in com-munication with the “openSCSI” device IOP (mediachanger).

Search for EMS messagesissued by the “open SCSI”IOP.Restart the “open SCSI”device in SCF.

4522 An operator intervention isrequired to make %s.%daccessible

Informational status repor-ted by the library changerand forwarded in the Back-Pak web UI Library Man-agement page diagnosticarea.

Investigate at the libraryconsole level.

5000 Error %1 starting the TapeEmulator.

Error at service start-up in aVT Controller.


5001 Error opening the con-figuration file (%1): %2.

The internal configurationfile of a VT Controller is notavailable.


5002 Configuration file containsinvalid parameter (%1).

The internal configurationfile of a VT Controller isinvalid.


5003 Error loading SCSI DLL (%1). Internal error at VT Con-troller start-up.


5004 Error creating the VirtualTape Infrastructure.

Internal error at VT Con-troller start-up.


5005 Error creating the StorageInfrastructure.



5006 Error processing the startsequence of the Tape Emu-




lator.

5007 Device has no entry in con-figuration file (%1).



5008 Device %1.%2 already in useby tape %3.

A load request is rejected bythe VT Controller because avolume is already mountedon the virtual device.

Manual load: Choose analternate device, or retrylater.Automatic load: Wait forautomatic retries.

5009 Error malloc for storage(%1).

Internal error in VT Controllerat load time.


5010 Error opening the WINFILEstorage (%1-(%2)).

“Open” rejected by the Win-dows file system in the VTController.

Refer to the appropriateMicrosoft documentation.

5011 Error reading the WINFILEstorage (%1-(%2)).

“Read” rejected by the Win-dows file system in the VTController.


5012 Error writing the WINFILEstorage (%1-(%2)).

“Write” rejected by the Win-dows file system in the VTController.


5013 Error in the root structure ofthe WINFILE storage (%1).

The indexed Windows file forthe specified virtual volumeis corrupted.


5014 Device not in use. A SCSI command wasreceived for a device thathas no volume loaded.

The device is ready to loada volume.

5015 Device not found for tape%1.

A VT Controller received aload or an unload commandfor a device not defined inthe VT Controller internalconfiguration.


5016 Error deleting the WINFILEstorage (%1-(%2)).

Delete file rejected by theWindows filesystem in theVT Controller.


5017 Error getting disk free spaceon %1 (%2).

Impossible to get theamount of free space ondisk.

If the error occurs on alocal disk, contact ProductSupport.


For WINFILE storage, the VTController will assume thatthere is enough free spaceto write the volume to pro-cess.

For remote disks, checkauthorizations and func-tionality of non- Windowsservers.

5018 Error getting full path nameon %1 (%2).

Impossible to get full pathname of a disk location forWINFILE.

Check the syntax and avail-ability of the Master pathand Data paths configuredin the DataStore.

5019 Missing Open Arguments for%1.


5020 Not enough free disk spacefor %1.

There is not enough diskspace for the operation.

Refer to the storage soft-ware to verify the freespace.

5021 Label type (%1) not sup-ported for %2.


5022 Tape %1 already in use byanother device.

The volume is already usedby another device.

Try a manual load.If the problem re- occurs,restart the VTC wheneverpossible.

5023 Error getting the file size of%1 (%2).

Error getting attributes of adisk file in a WINFILEDataStore.

Contact Product Support.For remote disks, checkauthorizations and func-tionality of non- Windowsservers.

5024 Cannot launch thread ²%1²(%2) for Storage (%3).


5025 Error executing the script[%1] (%2) for Storage (%3).

Error in script execution. Log on to the operating sys-tem in the VT Controller tocheck:The Windows Event Viewer.The log of the script.

5026 Maximum launch of [%1]reached for Storage (%2).

Error in script execution. Log on to the operating sys-tem in the VT Controller tocheck:1. The Windows EventViewer.2. The log of the script.


5027 Error No TSM scripting forStorage (%1).

Scripting is not supported forTSM Data Stores.

Remove scripting from theconfiguration of TSM DataStores.

5028 Error setting environmentvariable %1 (%2) for Storage(%3).

Error setting a named Win-dows parameter for thescript execution.

Check that the name andvalue of the parametersconfigured for theDataStore are syntacticallyvalid for Windows.

5029 The script [%1] has been sub-mitted for Storage (%2).

A script is stared in the VTController.

None.

5030 The script [%1] terminatedwith code %2 - %3 for Stor-age (%4).

A script has ended.If the script terminated withcode 0, the message will bemarked as informative. If notequal to 0, the message willbe marked as an error.

If the message is markedas an error, search thecode by (%2) and look forthe appropriate explan-ation and action.

5031 Error %1 starting the TapeEmulator Administration.


5032 Device (%1) has no SCSI activ-ity.

A command is received on adevice that has no SCSI activ-ity.

Verify the SCSI target Ids inthe configuration.

5033 Multiple copies (%1) foundfor the file (%2).

There are multiple copies ofthe same virtual volume inthe disk pool of a Windowsfile DataStore.

Verify the version of thefiles, leave only an index file(*.IND) and a data file(*.DAT) for a given volume.

5034 The file was not found (%1). The Emulator does not find afile for a virtual volume of aWindows file DataStore.

Restore the two files (*.INDand *.DAT) of the virtualvolume.

5035 There is no valid data path inthe pool for (%1).

All disk paths configured forthe pool of a WindowsDataStore are invalid.No operation is possible.

Restore the availability ofthe paths orconfigure a new path thatwill receive the SCRATCHvolumes to be written andthe volumes to be restoredby the restore script.

5036 An invalid path [%1] is still Windows DataStore: the file 1. Restore the disk path,


configured for (%2). of a virtual volume cannot beaccessed because the path isinvalid. The Emulator doesnot search in alternate loc-ations because the path isstill configured.

or2. Remove the path fromthe pool configuration toallow the Emulator searchin other paths of the poolor3. Execute the restorescript.

5037 Wrong path found [%1],expected path [%2] for (%3).

Windows DataStore: a filewas found in an unexpectedpath.

Path provided is not good. Move the proper file in theexpected location.

5038 Invalid path in Configuration[%1].

A path configured in a Win-dows file DataStore isunavailable or invalid.

Restore the disk path orremove it from the con-figuration. This will allowthe VTC Emulator to searchfor the cataloged files inalternate locations.

5039 File not found on Load for(%1).

Windows DataStore: a file isnot found.

Restore the file.

5040 Processing stops due tovolume load operation error(%1) for (%2).

A volume load fails. A pos-sible reason is that a restorescript does not completewith return-code zero.

Refer to the log of thescript. Modify the error con-dition or manually executethe restore.

5041 WRITE operation is deniedfor (%1).

A WRITE operation isreceived through the SCSIbus to a volume loaded witha “Read Only” attribute.

This symptom can show upif a volume is mounted viathe Stand Alone Load Webpage as the NonStop applic-ation tries to write on thevirtual volume.Have the mount request forregular tape activity solvedeither automatically by theEMS Extractor or by themanual load that is avail-able through the DomainManager.

5042 A Volume Load Operation hasbeen canceled for (%1).

An Unload command cancelsthe execution of a loadvolume.

None.


5043 Running [FetchData] oper-ation for (%2).

A pre-fetch operation is star-ted for loading a virtualvolume kept in a TSMDataStore.

None

5044 Cannot %1 tape device %2 :%3.

A VIRTUALIZE / MATERIALIZEsession fails on action repor-ted at the %1 position.

If reported as an error:1. Check the identificationof the device in MS Win-dows.2. Check the MS WindowsEvent log and the GuardianEMS log.3. Reset the tape device.

5045 Materializing virtual volume%1 ended with error.

A Volume MATERIALIZE oper-ation failed.

Check the Windows Eventlog and the Guardian EMSlog for previous errors.

5046 Materializing virtual volume%1 ended successfully.

A Volume MATERIALIZE oper-ation completes successfully.

Take the media out of theWindows device.

5047 Error getting object from[%1] (%2) for Storage (%3).

Error accessing data in aTSM server.

Refer to the followingsoftware documentation:IBM Tivoli Messages manual.

5048 Error sending new TSM pass-word in [%1] (%2) for Storage(%3)

A TSM password renewalfails.

Refer to the followingsoftware documentation:IBM Tivoli Messages manual.

5049 Error sending end of volumein [%1] (%2) for Storage (%3).

The notification to theDomain Manager if the endof an operation fails.

Using the Web User Inter-face, check in the Volumedetail if any current oper-ation is still registered. Ifso, verify the actual statusof the volume. If the cur-rent operation is incorrect,reset it (Volume details,Edit button, Reset currentoperation).

5050 Materializing virtual volume%1 started successfully.

A Volume MATERIALIZE oper-ation is successfully initiated.

None.

5051 Virtualizing physical volume%1 started successfully.

A Volume VIRTUALIZE oper-ation is successfully initiated.

None.


5052 Virtualizing physical volume%1 ended with error.

A Volume VIRTUALIZE oper-ation failed.

Check the MS WindowsEvent log and the GuardianEMS log for previous errors.

5053 Virtualizing physical volume%1 ended successfully.

A Volume VIRTUALIZE oper-ation completes successfully.

None.

5054 The physical volumes %1label match user's entry.

The label of a physicalvolume to import matchesthe user entry.

None.

5055 The physical %1 volume %2label does not match user'sentry.

The label of a physicalvolume to import does notmatch the user entry.

Unload and reload theproper volume on the tapedrive attached to the VTController.

5056 The physical tape device %1doesn't support %2 features.

The tape drive attached to aVT Controller for import/-export operations misses arequired feature.

Install proper device.

5057 (%1) VT Controller cannotreach the MVS Volume %2.

The DEXP MVS volume is notvisible in Windows or theaccess to this volume is rejec-ted by FAL.

Verify the configurationand status of the DEXPvolumes for the VTC.Display the list of DE XPvolumes from the Web userinterface to verify the listof DEXP volumes seen bythe VTC after an auto-redis-covery.

5058 (%1) EZX Discovery error: %2. Error while discovering thelist of DE XP volumes in thelist of physical devices thatare recognized by the Win-dows operating system.

Verify the configurationand status of the DEXPvolumes for the VTC.

5059 Device %1 BUSY while check-ing usage of tape %2.

A volume load is rejectedbecause a virtual tape deviceis busy.

Retry the operation.

5061 Virtual Tape Device %1STARTED.

The VTC Emulator reportsthe successful start of thenamed NSK tape devicewhich occurs at the first SCSIcommand sent by the NSK

None.


tape system.

devices not configuredin the domain will be listed byinternal ID, i.e.:‘port FC- 1 lun 3’ (Deviceunknown in domain)rather than:\NODE1.$TAPE03

5062 Virtual Tape Device %1STOPPED.

The VTC Emulator reportsthe normal stopping of thenamed virtual device and itoccurs when the serviceshuts down.

‘port FC-1 lun 3’ (Deviceunknown in domain)rather than \NODE1.$TAPE03

None.

5063 Virtual Tape Device %1DOWN.

For the named virtual device,the VTC Emulatorencountered an error con-dition that cannot berecovered without restartingthe virtual device. The hostwill send a bus reset.To recover a normal state ofthe tape applications usingany device on the same buswill abort and the host willthen try to reconnect to alldevices of the bus.

Resubmit the tape applic-ation(s).If message 5061 does notshow for the nameddevice and the NSK tapesystem continues to reporta device error, STOP thedevice in SCF and reset theVTC as soon as possible.(Reset will depend on cur-rent work schedule and theperformance of otherdevices).

5064 Virtual Tape Device %1REACTIVATED.

The VTC emulator receivedagain SCSI activity from thehost for a device that wasinternanlly disabled becauseof a lack of SCSI activity.

Devices not configured inthe domain will be listed byinternal ID, i.e.:‘port FC- 1 lun 3’ (Deviceunknown in domain)

None


rather than:\NODE1.$TAPE03

5065 Virtual Tape Device %1DEACTIVATED.

The VTC emulator has notreceived any commandsfrom the host for 3 minutes.This will cause rejection ofload commands from theDomain Manager.This EMS message is mostoften followed by anotherEMS message from the NSKtape system reporting a tapeIO error (timeout).

This state is not harmful ifthe device is not in use andnot needed.Check that the device waslater (message 5064)enabled or check inter-actively by SCF STATUS$drive.The message 5064 canshow up several hourslater.If the device stays dis-connected, then the VTCmust be reset.

5066 Unexpected old version %1of file %2 found.

A pre-V1.60 Windows file wasfound in a Windows fileDataStore.

None. The VTC emulator willchoose the file with theproper time stamp anddelete the other files.

5067 Deleting duplicate or olderfile %1.

An obsolete Windows file in aWindows file DataStore isdeleted.

None.

5068 Unexpected index file %1found. Found: %2 Search for%3.

An unexpected version of theindex file is found in WindowsDataStore.

The unexpected file is notused by the emulator. Theproper version might befound later in the oper-ation.If the operation failsbecause the proper versiondoes not exist, it is possibleto force the VTC to use theexisting version.This can happen after oper-ational difficulties atbackup time or when thecatalog (NSK VOLUME file)has been restored from anold backup and does notcontain the latest timestamps.


To force the VTC to accepta Windows file:- disable the time stampcheck for the volume- disable the time stampcheck in the configurationof the Data Store, if numer-ous volumes are involved.

5069 Unexpected %1 data file %2found. Found: %3 Search for%4.

An unexpected version of thedata file is found in WindowsDataStore.

See message 5068.

5070 (%1) About to LOAD volume%2 on virtual device %3.

A LOAD request has beenreceived by the VTC.

None. Message displayed only inthe VTC event log.

5071 (%1) About to UNLOADvolume %2 on virtual device%3.

An UNLOAD request has beenreceived by the VTC.

None. Message displayed only inthe VTC event log.

5072 Unknown Last Update IndexPath for volume %1.

The VTC receives a LOADrequest that does not con-tain the location of the Indexfile the last time it was writ-ten.

The VTC cannot execute theRestore script.If a Windows file restore isrequired, the user musteither update the volume inthe Web User Interface toenter the Last Update IndexPath that will be used asthe original file name to berestored or manuallyexecute the restore.

5073 Script configuration error:%1 - %2.

The script file is not availableto the VTC.The action, load request orvolume deletion is rejected.

Check the filename of thescript in the domain con-figuration.

5074 Configuration error for DataStore %1.

A configuration item includedin a request to the VTC isinvalid.

Check the Data Store pagein the domain con-figuration.

5075 Error loading configurationfile %1 - %2.

Cannot load the specifiedconfiguration file in %1.

Verify the existence of thefile. %2 details the errorencountered.


5076 The commit elapsed time(%1 sec) exceeds warningthreshold time (%2 sec) for%3.

Elapsed time to execute acommit (file IO flush for Win-dows file Data Store) is verylong.

For Windows file DataStore: reduce the value ofMEGBYTES_ COMMIT_THRESHOLD in the fileBBSL.OPT of the VTC.For TSM API Data Store:verify the TSM envir-onment.

5077 There is only num_of_bytesbytes free space left, lessthan num_ of_ percent oftotal space

The Disk Space UnloadThreshold configured in theData Store is reaching thefree space limit.

Verify the free space in theData Store and manage thespace if more space isneeded.

5078 There is not enough diskspace to virtualize physicalvolume %1.

The Volume VIRTUALIZE oper-ation fails because there isnot enough space to importa physical media.

Verify the free space in theData Store.

5079 The virtual volume %1 is full. Normal end of volume pro-cessing.

This message is not shownin EMS.No action required.

5080 The capacity of the virtualvolume %1 is too small.

An import fails because themaximum size of the virtualvolume is too small.

Verify the maximumvolume size configured inthe Volume Group.

5081 Data Store IO is still activewith volume %1.

Re-use of the same volumelabel before the completionof the previous operation.

Check that the samevolume label is not used bydifferent domains sharingthe same Data Store orsame VTC.Check the status of theData Store.

5082 The script [%1] has been sub-mitted for Storage (%2) ondevice %3.


None.

5083 Device still unloading. A volume cannot be loadedor unloaded because theunloading of the previousoperation did not complete.

For regular automaticmount requests, wait forautomatic retry.Before attempting amanual mount request,wait for one minute, thenrun an auto-entry.


5084 The VOLUME %1 was notfound.

TSM API Data Store: the con-tainer of the volume is notfound in a load operation.

Load for output with auto-scratch enabled: the filespace will be recreated.Load for input:- Verify that the Node nameand FileSpace spe-cifications have notchanged in the con-figuration.- Verify the state of objectsin the TSM server.Autoscratch not enabled: tobe used, the volume mustbe deleted and re-created.

5085 Error getting disk volumeinformation on %1 (%2).

Windows disk Data Store:Error getting disk inform-ation for free space whenchecking and optimizingchoice of disk path.

The path is consideredinvalid.

5086 Not enough free disk spacefor %1. Space required: %2bytes.

Windows disk Data Store:There is not enough freespace to load the volume andguarantee space for the max-imum volume size.

The volume load is rejected.

5087 Cannot append to a volumecreated before V1.63 (%1).

Different data version incom-patibilities.There is an incompatibilitybetween version 1.63 and anearlier version that preventsappending data to a virtualvolume.

Copy (tape to tape) the con-tent of the older virtualvolume to a new virtualvolume and create it usinga version 1.63 (or higher).The content data can thenbe appended to the new vir-tual volume.

5088 Device has no SCSI activity. An attempt to load a virtualvolume on an inactive VTCDevice was made by theDomain Controller.This can be caused by:

1. A crossed cablingport.

2. A bad VT Controller port/device con-

Verify the VT Controller con-figuration.Verify the cabling.Reset the Router\Tape IOprocess\VTC.


figuration.

3. A communicationerror betweenNSK\Router\VTC.

5089 Received SCSI activity onundefined device %1.

The NSK host systemattempts to communicatewith an un- configured VTC.device.

Verify if the Tape IO Pro-cess is configured to talkwith the correctLUN\DeviceId.Verify that theLUN\DeviceId is defined inthe FcConfig\VtConfig file inthe VTC server.

5090 Attempt to %1 a 0 byteslength DATA record (%2).

Severe internal error. Contact Product Supportand provide the Event Mes-sage text.

5091 The maximum number of act-ive SCSI ports allowed byLicense %1 is exhausted.Load operation for tape %2is rejected.

The limitations of the licensekey number have beenreached.

Verify that the properlicense key has beenentered in the domain con-figuration.The license number of thecreation date is displayed inclear text at the beginningof the license key.

5092 The maximum number of act-ive FC ports allowed byLicense %1 is exhausted.Load operation for tape %2is rejected.

The limitations of the licensekey number have beenreached.

Verify that the properlicense key has beenentered in the domain con-figuration.The license number of thecreation date is displayed inclear text at the beginningof the license key.

5093 Virtual Tape Device %1REINITIALIZE after a SCSI BUSRESET.

The VTC internally re- ini-tializes all devices of the bus,possibly canceling any cur-rent activity on the drive because it received a BUSRESET.

If NSK tape applicationshave been aborted, resub-mit.If the problem re- occurs,analyze EMS logs $0 and$ZLOG.

5094 Virtual Tape Device %1REINITIALIZE after a SCSI

The VTC internally re-ini-tializes the device, possibly

If an NSK tape applicationwas aborted, resubmit.


TARGET RESET. canceling any current activityon the drive because itreceived a TARGET RESET.

If the problem re- occurs,analyze EMS logs $0 and$ZLOG.

5095 Virtual Tape Device %1REINITIALIZE after an ABORTTASK.

The VTC internally re- ini-tializes the device, possiblycanceling any current activityon the drive because itreceived an ABORT TASK.

If an NSK tape applicationhave been aborted, resub-mit.If the problem re- occurs,analyze EMS logs $0 and$ZLOG.

5096 Unexpected data file %1found. Found: %2 Search for%3.

A data file is not found in theexpected path, the originalpath is still available and thetime stamp validation is dis-abled.The conditions above pro-hibit usage of the found datafile.

Re-enable the time stampchecking in the Data Storeand the time stamp for thespecific volume.If time stamp checkingmust be disabled, move thedata file to the expectedpath.

5097 Unexpected end of data forVOLUME %1.

Data of the named volume isnot found or ends unex-pectedly.

Search for previous EMSmessages that mightexplain why data readingdid not start orwhy itstopped prematurely.Without error in the read-ing process, the data repos-itory is likely to becorrupted or truncated.

5098 Starting exporting data fromvirtual volume %1 to physicalvolume %2.

In an export operation, databegins to be written to thephysical media.

None.

5099 Starting importing data fromphysical %1 volume to virtualvolume %2.

In an import operation, databegins to be written to thevirtual volume.

None.

5100 Cannot [enable|disable] com-pression of physical tapedevice %2. Current settingwill be used.

In an export operation,attempt to enable or disablephysical tape device com-pression failed. The exportoperation will continue usingthe current device setting.

None.

5101 Physical Tape Device %1 is In an export/import oper- 1. Investigate the prob-


not found in the VTC con-figuration.

ation, a pre-configured TapeDevice cannot be found inthe VTC hardware mapping.This can happen if the deviceis powered off or had beenre-configured (connected toanother HBA port, Targetid/LUN change).

lem using the DeviceManager to see ifthe device is still vis-ible.

2. Power on the deviceif the power is off.

3. Using the WEB inter-face, go to the VTC’sadvanced con-figuration screenand delete and re-add it in the PhysicalTape DevicesAttached list.

5102 The license does not allowVIRTUALIZE/MATERIALIZEoperation to use physicaltape %1 in raw access.

A physical drive that is nothandled by a native Windowsdriver can be used in rawmode only if the license keycontains this specific option.


5103 Cannot append to a volumecreated before %1 (%2).

The difference of file formatbetween versions does notallow the append operation.

Have the volume rewrittenfrom the beginning (normaltape write) with the latestversion. Append will be pos-sible afterwards.

5104 Catch an unhandled excep-tion while %1 volume %2. Thevolume and/or tape device%3 may not be reusable untilVTC services restart.

“Unhandled error” happenswhile loading or unloading avirtual tape drive.

Log on to the VTC thatreported the error.Restart VTC services whenall tape activity has beencompleted.Report the error log andthe Windows Event ViewertoProduct Support.

5105 Catch an unhandled excep-tion while executing script%1.

“Unhandled error” happenswhile executing a script.

Log on to the VTC thatreported the error.Verify the script executioninto the script output.Report the error log andthe Windows Event Viewerto Product Support.


5106 Volume Level Encryption notactivated for Virtual TapeDevice %1.

A volume created under aVolume Group set usingencryption through VLE- Cli-ent has been mounted on avirtual tape device not con-figured with the VolumeLevel Encryption in SCF.Configuration mismatch.

Action 1:Activate the VLE supportfor the specific TAPE devicein SCF. Refer to the HPENonStop Technical doc-umentation for the VolumeLevel Encryption activation.Action 2:In the UI Key Manager con-figuration page, click theTest button.

5107 The maximum number of act-ive encryption /decryptiondevices allowed by License%1 is exhausted. Load oper-ation for tape %2 is rejected.

Limitation of the license keynumber has been reached.

Verify the proper licensekey has been entered in thedomain configuration.The license number of thecreation date is displayed inclear text at the beginningof the license key.

5108 Starting VIRTUALIZE sessionon tape device %1.

A physical tape devicereserved for VolumeVIRTUALIZE operation(s).When submitting the vir-tualization request, the phys-ical tape device will remainreserved until no media isloaded for the amount ofminutes users are allowed.

Mount a media in the phys-ical device.

5109 Ending VIRTUALIZE sessionon tape device %1.

The physical device isreleased.

None.

5110 Starting MATERIALIZE ses-sion on tape device %1.

A physical tape devicereserved for VolumeMATERIALIZE operation(s).When submitting the mater-ialization request, the phys-ical tape device will remainreserved until no media isloaded for the amount ofminutes users are allowed.

Mount a media in the phys-ical device.

5111 Ending MATERIALIZE sessionon tape device %1.

The physical device isreleased.

None.


5112 Opening virtual volume %1for %2 operation aborted:%3.

A MATERIALIZE / VIRTUALIZEoperation abort because thesystem cannot use the vir-tual volume.

Investigate the errorreported

5113 Label recognition on physicalvolume aborted: %1.

The physical media is eithernot labeled or not readable.

If the media is not labeled,restart the operation usingthe non- labeled option orremove the media.If the media is not read-able, investigate the repor-ted error.

5114 Virtual Tape Device %1 can-not be used by the VolumeLevel Encryption.

A volume created under aVolume Group not configuredfor encryption has beenmounted on a virtual tapedevice configured with theVolume Level Encryption inSCF.Configuration mismatch.

Action 1:Disable the encryption sup-port of the Volume Groupand select the VLE support for the specific TAPE devicein SCF. Refer to theNonStop Technical doc-umentation for the VolumeLevel Encryption activation.Action 2:Activate the encryption inthe configuration. Seerelated encryption con-figuration information in:E4.07 User Manual

5115 Session with Key Manager Id%1 for volume %2 aborted:%3.

Network problem, con-figuration problem or authen-tication problem.Explanation is given in thedisplayed message.

Investigate using the Testfunctionality against theKey Manager ID in the KeyManager configurationpanel.

5116 Bad DATA record position(%1) %2.


5117 Unexpected legacy formatdata file %1 found.

A data file is not found in theexpected path; the originalpath is still available, but it isan old occurrence of thedata in a legacy format.The conditions above pro-hibit usage of the found data

None.The file will be deleted ifthe load is successful.


file.

5118 Unable to impersonate useraccount %1: %2.

Failure of a Windows log inwith the account & passwordconfigured in the Data Store.

Depending on the reportederror text, either:- Update the account / pass-word in the Data Storepage of the UIor- Update the Windowsaccount definition.

5119 Cannot start moving DataStore %1 files from Sparepool to Storage pool : %2.

The MOVING operation hasfailed to start.

Log on to the VTC serverwhere used for the MOVINGoperation and troubleshootthe reason for %2.MOVING operation will needto be restarted manually inthe Admin screen.If no resolution, contactProduct Support.

5120 Start moving Data Store %1files from Spare pool to Stor-age pool.

Data provided for inform-ation purposes, indicatingthat file MOVING operationshave been started for theData Store identified by %1.

None.

5121 Start moving virtual volume%1.

Data provided for inform-ation purposes, indicatingthe MOVE operation on thevirtual media identified by%1.

None.

5122 Moving virtual volume %1ended with error - %2.

Indication that the MOVEoperation on the virtualmedia failed.

Log on to the VTC serverwhere used for the MOVINGoperation and troubleshootthe reason for %2.MOVING operation will needto be restarted manually inthe Admin screen.If no resolution, contactProduct Support.

5123 Moving virtual volume %1ended successfully.

Data provided for inform-ation purposes, indicating

None.


that the MOVE operation hasbeen successfully completed.

5124 Moving Data Store %1 filesfrom Spare pool to Storagepool completed.

Data provided for inform-ation purposes, indicatingthat the MOVE operation hasbeen successfully completed.

None.

5125 Error in (%1) operation forvolume %2: %3.

Operation identified by %1,failed.

Log on to the VTC serverwhere used for the MOVINGoperation and troubleshootthe reason for %3.The operation will need tobe restarted.If no obvious resolution,contact Product Support.

5126 Storage type not licensed. Attempt to use Storage typenot part of the license sale.


5127 Storage type undetermined. Attempt to use Storage typenot part of the license sale.


5128 Error in GetStorageConfigfor %1: %2.

The attempt to get the DataStore %1 failed.

Validate the reason for %2and retry the operation.

5129 The script [%1] cannot bemodified. The script will notbe launched.

Preset script has beenexternally modified

Re-install VTC software.If the pre- defined scriptcannot execute under thespecific setup and requiresa modification, contactProduct Support.

5130 USB disk not allowed in VTRConfiguration [%1].

VTR limitation. Use the BackBak UI toremove the path from theStorage pool in the DataStore configuration and dis-connect the USB drive.

5131 Windows de- duplication isnot allowed in VTR Con-figuration [%1].

VTR limitation. Disable NTFS De-duplicationfor the specified path.

5136 There is only num_ of_bytesbytes free space left.No enough free space avail-

The Virtual Tape VolumesThreshold configured in theData Store is reaching the

Verify the free space in theData Store and manage thespace if more space is


able for virtual tape volumes. free space limit. needed.

6000 (BBSL) %1 (%2). Error reported by the Win-dows software implementingthe DataStore (such as TSMAPI).

Refer to software doc-umentation:IBM Tivoli Messages manual.

6001 Cannot Initialize the API toTSM storage library (%1)).

The Tivoli Storage ManagerAPI returned an error.

Refer to the IBM Tivoli Mes-sages manual.

6002 (BBSL Retry) %1 (%2). A Data Store TSM APIreturned an error code for aprocess that can be retried.A retry is attempted onceevery minute. A message isissued every 5 minutes.

Check for error messagesin the TSM server activitylog.A tape media may beunavailable.

6003 (BBSL) %1 (Requested datawill require MEDIA LIBRARYaccess).

A TSM retrieve operation isstarted and the TSM serverindicates that objects are ona sequential media.

None.The operation may takelonger than expected.

6004 (BBSL) Data Store commandoverlap transaction timeout(%1).

The Data Store responsetime is too long for SCSI emu-lation.

The SCSI command is rejec-ted with an IO error codebefore the NonStop tapeprocess times out.

6005 Inconsistency was found inTSM objects of volume (%1).Check the volume log file fordetail.

The volume just read seemsto be invalid.

At the load time of a volumeto be read (restored), thequery of the TSM serverdetected an inconsistency inthe list of objects for thevolume (reported as a warn-ing). The load will be rejectedonly if the restore wasrequested for a SECONDARYData Store. In this case, thevolume will be considered asbeing replicated and the loadwill be rejected; then, retried

Verify if the specific error#3207 occurred at backuptime.Check the specific log \lo-g\LBvvvvvv.log.Check if the expiry of theTSM Management Class isnot infinite – or at leastaccommodates the longestretention needed.For other cases, provide theVTC and the log file cor-responding to the volumelabel and EMS messagesand contact Product Sup-port.


later.At the time of a volumeunload that has been justwritten (backup), the queryof the TSM server has detec-ted an inconsistency in thelist of objects for the volume(reported as an error).Internal VTC logging is tem-porary and it is forced tokeep details about the errorin a file name (such as \lo-g\LBvvvvvv.log, that containsthe volume label).

6006 Errors happened in TSM ses-sion for %1 TSM objectschecking during UNLOADoperation. Reason: %2.

The consistency check can-not be executed after avolume has been rewritten.

Re- execute the backup toincrease the backup reli-ability.

6007 (BBSL) %1 (%2). Warning reported by the Win-dows software implementingthe DataStore (such as TSMAPI).

Refer to the following soft-ware documentation:IBM Tivoli Messages manual.

6008 Incomplete Data file found:%1.

While attempting to mount avirtual volume, the VTC founda DATA file that is consideredincomplete. The reason isreturned in the message andthe volume will be mountedif the reason is considered tobe a warning.

Investigate the reason forerror as given in the errormessage.

6009 Incomplete Index file found:%1.

While attempting to mount avirtual volume, the VTC founda IND file considered to beincomplete. The reason isgiven in the returned mes-sage and the volume will bemounted if the reason is con-sidered as a warning.

Investigate the reason forerror as given in the errormessage.

6010 Unexpected TSM objects for%1 found: %2.

An unexpected version of theindex file is found (TSMDataStore).

The unexpected volume isnot used by the emulator.


The reason is given in thereturned message.

This can happen after oper-ational difficulties at thetime of backup, or whenthe catalog (NSK VOLUMEfile) has either beenrestored from an oldbackup and does not con-tain the latest timestampsor TSM objects have notbeen replicated yet on theDR site TSM server. In thiscase, the load will beretried later.To force the VTC to accepta volume:- Disable the time stampcheck for the volume.- Disable the time stampcheck in the configurationof the Data Store, if numer-ous volumes are involved.

6011 Variables Internal error. Contact Product Support.

6012 Error while creating volume%1 - %2.

Report of an error while cre-ating a specific volume (%1).

Investigate the reasonreturned in the message(%2).

6013 Error while deleting volume%1 - %2.

Report of an error whiledeleting a specific volume(%1).

Investigate the reasonreturned in the message(%2).

6014 Error while loading volume%1 - %2.

Report of an error while load-ing a specific volume (%1).

Investigate the reason forerror, as given in thereturned error message(%2).

6015 Volume %1 will be written onSPARE path %2.

Indicates the usage of aSPARE pool path instead of aSTORAGE pool path definedin the Data Store con-figuration.

Move the data to theSTORAGE pool when theSTORAGE pool is next avail-able.

6016 Volume %1 will be read fromSPARE path %2.

Indicates the usage of aSPARE pool path instead of aSTORAGE pool path defined

Move the data to theSTORAGE pool when theSTORAGE pool is next avail-


in the Data Store con-figuration.

able.

6017 Volume %1 will be read fromCOPY path %2.

Message data provided forinformation purposes.

None.

6018 Missing retention inform-ation in volume %1. (%2).

A volume deletion is rejectedbecause the original volumeexpiry date cannot bedouble-checked.

Refer to Event MessageNumber 2617.

6019 %1 has not expired againstexpiration date in HDR1 (%2).

A volume deletion is rejectedbecause the double-check ofthe original volume expirydate has failed.

Refer to Event MessageNumber 2617.

7000 Label VOL1 is missing forstorage (%1)).


7001 Label HDR1 is missing forstorage (%1)).


7002 Modifying a volume label isnot allowed. Storage (%1)).

The VT Controller does notallow the re-labeling of a vir-tual volume with a differentlabel.

Re- labeling is only sup-ported to get rid of non-expired data files on a vir-tual volume.The regular procedure is todelete a virtual volume andthen recreate it.

8000 Cannot create directory %1with system error %2 (%3).

The creation of a disk sub-directory is rejected by Win-dows.

Modify the error conditiondescribed in themessage and resubmit orwait for next execution of ajob scheduled in NetBatch.

8001 Cannot delete file %1 withsystem error %2 (%3).

The deletion of a disk file isrejected by Windows.

Modify the error conditiondescribed in themessage and resubmit orwait for next execution of ajob scheduled in NetBatch.

8002 Error during restore: code%1 (%2).

Files restored for verificationfailed.

Modify the error conditiondescribed in the message, resubmit or wait for nextexecution of a job sched-


uled in NetBatch.

8003 Error during verification forvolume %1: code %2 (%3).

Files restored don’t matchthe original files.

Modify the error conditiondescribed in the messageand resubmit or wait fornext execution of a jobscheduled in NetBatch.

8004 The task to clean Data Store%1 is finished.


None.

8005 The cleanup task for DataStore %1 is already running.

Cannot start a new cleanuptask as long as one is alreadyrunning.

Wait for the current task toend or end it before restart-ing a new task.

8006 Error during verification: %1. Files restored do not matchoriginals.


8007 Delete related files of %1volumes under path %2.%nThe list of deletedvolumes:%n%3.


None.

8008 Clean job was submitted forData Store %1. It is sub-mitted as a long- run back-ground process for thestorage which do not supportArchive Bit set/reset.


None.

8009 Purge operation for volume%1 is started.


None.

8010 Purge operation for volume%1 is finished.


None.

8011 There is not enough space torestore the files of virtualvolume %1 at location %2.Need free space %3.

The restore failed becauseof lack of space.



8012 Difference: %s. Files restored do not matchoriginals

Modify the error conditiondescribed in the message,resubmit or wait for nextexecution of a job sched-uled in NetBatch.

8013 The task to clean Data Store%1 is started.


None.

8014 Cannot find complete volumefiles (IND,DAT) for the fol-lowing volumes: %1.

One or both volume files(DAT, IND) of the listedvolumes cannot be foundunder the paths of the stor-age/spare pool.

Manually fix the error con-dition described in thegiven message.

8015 Information message sentfrom BBOXLOG command

Information on a NonStopnode sent to theEMS subsystem.

See BBOXLOG – Logs a Mes-sage in NonStop EMS sec-tion in the BackBoxVTC Scripting Optionmanual for more inform-ation.

8016 Warning message sent fromBBOXLOG command

Warning on a NonStop nodesent to the EMS subsystem.


8017 Error message sent fromBBOXLOG command

Error on a NonStop nodesent to the EMS subsystem.


8018 Information message sentfrom Data Store Path cleanfunction.

Information on the DailyCleanup task ( collected inthe OBB017 OBEY file).

For more details on theDaily Cleanup see the sec-tion Daily Cleanup (OBB017)in the BackBox User'sManual.

8019 Warning message sent fromData Store Path clean func-tion

Warning on the Daily Cleanuptask ( collected in theOBB017 OBEY file).

For more details on theDaily Cleanup see the sec-tion Daily Cleanup (OBB017)in the User's Manual.


8020 Error message sent fromData Store Path clean func-tion

Error on the Daily Cleanuptask ( collected in theOBB017 OBEY file).

For more details on theDaily Cleanup see the sec-tion Daily Cleanup (OBB017)in the User's Manual.Contact Product Supportfor troubleshooting.

8999 For loading the volume %s,manually restore %s to %s(original server was %s).

The ‘restore script’ Manual_Restore.cmd requests Win-dows files to be restored bythe operator.

Use the appropriate back-end software to restore thespecified files (originalnames) to the specified loc-ation.Notice the server request-ing the action might not bethe original sever.The files must be restoredexactly where specified. Ifnot, cancel the restore andresubmit it.

10000 Error during XML Parsing: %1%2.


10001 The requested function(%1)is not supported.


10002 Compatibility Error, (%1) ver-sion (%2) is not supported.

There is a version mismatchbetween VT Controller com-ponents.

Verify the installation.

10003 IPService error: %1 (%2) - %3. Internal error. Contact Product Support.

10004 IPService warning: %1 %2. An IP error code has beenreported.

Verify the operations run-ning at the same time. Ifany additional IP errorcodes are present, contactProduct Support.

10005 IPClient error: %1 (%2) - %3. Internal error. Contact Product Support.

10006 IPClient warning: %1 %2. An IP error code has beenreported.

Verify the operationsexecuted when the erroroccurred.If any additional IP errorcodes are present, contactProduct Support.


10100 Error parsing the DomainAddress Configuration file(%1) (%2).


10101 Domain Address Con-figuration list has not beenrefreshed due to con-figuration error, and oldDomain list remains active.

VTC Services cannot reloadthe configuration file afterDomain address update. Itwill retry.

Contact Product Support ifmessage persists for morethan 10 minutes.

10102 Domain Address Con-figuration list has been suc-cessfully refreshed from theupdated configuration file.

The update of the DomainTCP/IP address (es) is beingpropagated.

None.

10103 Connection from %1 hasbeen rejected due to aDomain Address Filteringsecurity alert.

The VT Controller receives acontrol message from anaddress that is not in the listof the Domain TCP/IPaddress(es).

Verify the source address(‘from’).If there is a valid alternateaddress of the NonStopserver running the DomainManager, add it in theDomain address page.

10104 Coul retrieve the registry keyfor the Domain Address Con-figuration file.


10105 Domain Address Con-figuration file access error:%1.


10106 Error loading the DomainAddress Configuration file.Use VTC Management Con-sole to manage the list.

The VTC has no Domain Man-ager address which to for-ward web requests andunsolicited messages to.VTC installation is incom-plete.

Enter Domain address.Refer to the VTC Install-ation.

10107 Domain Address Con-figuration List is empty.

The VTC has no Domain Man-ager address which to for-ward web requests andunsolicited messages to.VTC installation is incom-plete.

Enter Domain address.Refer to the VTC Install-ation.

10200 Error parsing the VTC License Internal error caused by an Contact Product Support.


file (%1) (%2). invalid license.

10201 VTC License information hasbeen successfully refreshedin the configuration file.


None.

10202 Error decoding VTC Licensefile (%1) (%2-%3).

Invalid license. Contact Product Support.

10203 VTC License file access error:%1.

Reason for error described in%1.


10204 No VTC License file found. Message data provided forinformation purposes.

Install the license file onthe server.

10205 Server Disk Capacity doesnot match the VTC License.

Factory message caused byan invalid license.

Install the valid license.Contact License Support.

10206 Server characteristics don'tmatch the VTC LicenseProduct ID or Model.

Message received throughuse of an invalid license.

Install a valid license.Contact License Support.

10207 VTC license will expire on %1. The valid VTC license willsoon expire.

Contact License Support.

10208 VTC license has expired %1. The VTC license has expired. Contact License Support.

10209 VTC license violation -%1(%2).

Attempt to use the VTCserver outside the scope ofthe license.


10210 No valid VTC License key. No license or an invalidlicense file on the VTC server.

Contact License Support toset up a valid License install-ation.

10211 NonStop node not licensedfor this VTC.

Attempt to connect the VTRto an unlicensed NonStopNode.


10212 No NonStop node in thelicense.

No license or an invalidlicense file on the VTC server.

Contact License Support toarrange installation of avalid License.

11001 Cannot %1 with VTC %2, %3. Error inBBBACKUP/BBRESTORE.

Check reported error in theVTC:.the script log..Windows eventviewer.


11002 Script Error, CMD Syntax: %1. Error in parameters syntaxof BBBACKUP/BBRESTORE.

Verify the script command.

11003 Execution for %1 failed. Error inBBBACKUP/BBRESTORE.


11004 ScriptClient ends before files being completelybacked-up / restored.

Time out inBBBACKUP/BBRESTOREbefore a sub-script initiatedby the Script controller backsup or restores the file.

Check in the script the val-ues ofBBOX_SCRIPT_TIMEOUTSearch for reasons of slowexecution in the sub-scriptlogs.

11011 Script <script name> startedfor <action> <counter> files.

Script controller:Starting of a sub-script hasbeen reported.

None.

11012 <action> <fileName> hasfailed <counter> times, willretry.

Script controller:The backup, copy or retrievalof a file has failed, and willretry after the configureddelay.


11013 <action> <fileName> hasfailed after maximum retries

Script controller:The backup, copy or retrieveof a file has failed and it is nomore retried.


11014 Start script: %1 encounterserror in creating temporarydirectory/file: %2 (%3).

Script controller:error starting a sub-script.

Check reported error in theVTC:.the script log.Windows eventviewer.

11015 Script: %1 has finished %2.%3 files were restored; %4 files were NOT restored,total size of restored files =%5 Kbytes,startTime= %6 ,endTime=

Script controller:Completion of a restore sub-script and associated stat-istics.

None.


%7.

11016 Script: %1 has finished %2.%3 files were backed up; %4files were NOT backed up,total size of backed up files=%5 Kbytes,startTime= <time>,endTime= <time>.

Script controller:Completion of a backup sub-script and associated stat-istics.

None.

11017 Script: %1 started failed for%2 %2 files.

Script controller:Error in the execution of asub-script.


11018 Script Controller: Script pro-cess is timed out. Obsoletefiles {0} are removed fromthe {1} FileList.

Script controller canceled asub-script that reached max-imum allowed executiontime.Names of files to be pro-cessed in the sub-script arelisted.

Analyze the log of the sub-script to understand thereason for the unexpectedlog execution elapsed time.Eventually, modify thetimeout value (24 hours bydefault) by setting theparameter BBOX_SUBSCRIPT_TIMEOUT in thescript.

11019 Script: %1 has finished %2.%3 files were copied; %4 fileswere NOT copied, total sizeof copied files= %5 Kbytes,startTime= <time>,endTime= <time>.

Script controller:Completion of a copy poolsync sub-script and asso-ciated statistics.

None.

11020 Error when adding jobs:Script Controller function isnot configured in DataStore%1.

Script controller: a script exe-cution is requested or a DataStore is not configured forScript Controller.

Through the UI, update theData Store advanced con-figuration to enable ScriptController usage.This may require a newlicense key as the ScriptController is controlled by alicense key from version04.02.

15000-15999

Specific messages sent fromcustomized script(s) to EMS.

Messages reserved forscripts sent to EMS.

Check script logs fordetails, if needed.


20000 Script execution timed out. A script controlled by atimeout is canceled.Deletion scripts are con-trolled by a timeout.

Analyze the reason fortimeout in the Windows logof the script execution.For delete scripts initiatedby the macro BB017_FREE_EXPIRED, revise the macroparameterSCRIPT-TIMEOUT.

20001 Script execution was can-celed by user.

As result of a volume manualunload, a script is canceled.

None.

20002 Script execution is com-pleted.

A script stops executing andreturns to 0. The script exe-cution is considered as suc-cessful.

None.

20003 Service cannot launch thescript.

The VTC services encounter asystem error that prohibitsthe launch of the script. Thescript has not beenexecuted.

Log on to the VTC whichreported the error and ana-lyze the reason for theerror in the WindowsEvents Log.Contact Product Support.

20004 Service encounters a systemerror in script management.

The VTC services cannotdetermine the success or thefailure of the script exe-cution.

Log on to the VTC whichreported the error.Verify the state of thescript execution from thescript output and takeappropriate action if thescript failed. Analyze thereason for the error in theWindows Events Log andreport the error to ProductSupport.

20005 The script execution fails andreport error code (%1) - %

A script stops executing,returns a failure code andthe script execution is con-sidered to be a failure.See the Code return (%1).

Log on to the VTC whichreported the script exe-cution failure and analyzethe script output failurecode and reason for error.

20006 The script execution forLUMINEX storage fails.

A script stops executing andthe script execution is con-

Log on to the VTC whichreported the script exe-


sidered as a failure. cution failure and analyzethe script output failurecode and reason for error.

20007 Deleted script cannot startfor volume %1. Reason: %2.

The VTC Admin servicesencountered an error thatprohibits the launch of thescript.

Analyze the reason forerror, fix and re-submit.Contact Product Support.

20050 The current block size is notsupported by the physicaltape device

The physical tape drive usedto IMPORT a volume cannotsupport the block size usedby the application (default is64K).

Decrease the block sizeassociated with the phys-ical tape drive.To update the block size,log on to the Domain andgo to the VT ControllerAdvanced Properties Con-figuration page.

20051 The current block size is tooshort to hold a completerecord of data from the phys-ical tape volume.

The physical tape drive usedto IMPORT a volume has ablock size too small to read adata record from the phys-ical tape volume.

Increase the block sizeassociated with the phys-ical tape drive.To update the block size logon to the Domain and go toVT Controller AdvancedProperties Configurationpage.

20052 Configuation file containsinvalid parameters.

The VtConfig.txt, FcConfig.txt or AdmConfig.txt file con-tains an invalid parameterthat prevents the specifiedservice to start correctly.

Log on to the VTC thatreported the error and ana-lyze the reason for theerror in the WindowsEvents Log.

20053 Another service instance isstill active.

A previous stop of the ser-vice doesn’t complete suc-cessfully and part of theprevious instance is still act-ive.

When all tape activity hasbeen completed, restartthe Windows Server.Contact Product Support ifthe problem is not solvedafter restarting the server.

20054 Initializing the service infra-structure.

Internal error or systemresources are insufficient for the required task(s).


20055 Initializing FC-SCSI interface. Internal error or hard-ware/software installation



issues.

20056 The volume is not movedbecause its disk locationregistered in the domain isnot in the spare pool.

A restore has been per-formed when the Storagepool was not available. Therestore has used the Sparepool as a destination.The MOVE has skipped thisvolume because it has notbeen written as a BACKUP.

Validate that the propervolume version is backedup by an EBS.Remove manually the files(DAT and IND).

20057 Unexpected older file found%1.

An older generation of theBACKUP in the Spare pool hasbeen found.

None.Files will be automaticallydeleted.

20058 Cannot identify the volumebecause multiple Index orData files exist in the DataStore.

A multi-copy of a BACKUP inthe Spare pool (while theTime stamp Check has been disabled) has been found.The system cannot selectwhich virtual media is the cor-rect one.Operator action required.

Troubleshoot the problemto locate appropriate vir-tual media.

20059 Error during send messageto Event Viewer throughAsynclog service.

Internal error or systemresources are too low.


20060 Share access test as failed:(%1) %2.

The Storage Admin pagereports an error while test-ing the Data Store useraccess against the share andshare folder.Error number and detail areshown in %1 and %2.

Correct the reported error.In case of “Access denied”,validate the Share per-mission and/or the NTFSpermission.

20061 Folder access test as failed:(%1) %2.

The Storage Admin pagereports an error while test-ing the Data Store useraccess against the des-tination folder.Error number and detail areshown in %1 and %2.

Correct the error reported.In case of “Access denied”,validate the NTFS per-mission of the destinationfolder.

20062 Create/Write file access testas failed: (%1) %2.

The Storage Admin pagereports an error while test-

Correct the error reported.In case of Access denied ,


ing the Data Store useraccess against the des-tination folder.Error number and detail areshown in %1 and %2.

validate the NTFS per-mission of the destinationfolder.

For external NAS, theSMB portion of the servermay not be able to respondproperly and an NAS rebootmay be required.

20063 Delete file test as failed:(%1) %2.

The Storage Admin pagereports an error while test-ing the Data Store useraccess against the des-tination folder.Error number and detail areshown in %1 and %2.

Temporary files (.TMP) mayrequire to be manuallydeleted in the target folder.Report the error to ProductSupport.

20100 Bad or missing VTC Licensefile.

Invalid license or no licenseinstalled.

Install a valid license or con-tact License Support.

20101 Invalid VTC License Key. Invalid license or no licenseinstalled.

Install a valid license or con-tact the License Support.

28005 Message from Domain Man-ager is rejected and theoperation <OPERATION> isnot supported.

Internal error, software ver-sion mismatch.


28007 Dataset locked successfullyfor <DOMAIN>: <VOLUME>, <NUMDS>-<DSN>.

Successful lock at the begin-ning of transfer.

None.

28008 Dataset unlocked suc-cessfully for DSN <DSN>from <DOMAIN> usingvolume <VOLUME>.

The end-of-transfer unlockis successful.

None.


APPENDIXCommon and Special Cases

Tape Subsystem Reset Procedure

This procedure is applicable in cases where the tape subsystem infrastructure (ZSERVER and DSM/TC) seemsimpacted by severe operational difficulties: the $ZSVR volume recognition does not execute correctly and theDSM/TC does not reply properly to given commands.

This procedure is not a replacement of the HPE documentation for managing HPE NonStop components, but ahelp in resetting the whole NonStop tape system, including the components.

The Reset procedure below resets the tape subsystem of a single NonStop node, but some components can beshared with remote nodes which do not show the same level of possible operational difficulties.

As a consequence of this procedure, some of the tape system components on the other nodes might have tobe reset.

Reset Procedure:

1. Log in with SUPER.SUPER.

2. Stop the EMS Extractor(s)

STOP $BBEXT, or SCF ABORT PROCESS $ZZKRN.#BBEXT3. Exit any MEDIACOM session; issue a Session Logout in all UI instances.

4. Stop any tape application, except TMF audit dumps.

5. Wait for any TMF audit dump to end or abort.

6. Stop the Guardian ZSERVER process

STOP $ZSVR7. Stop processes related to DSM/TC

STATUS *, PROG $SYSTEM.SYS*.MEDIA*8. If the previous command shows only MEDIACOM, MEDIASRV and MEDIADBM programs, stop them by

either:

STATUS *, PROG $SYSTEM.SYS*.MEDIA*, STOPorStop individually, all occurrences of MEDIACOM, MEDIASRV and MEDIADBM.

9. Stop all tape devices.

10. SCF (to get the SCF prompt)

RESET TAPE $*, FORCE (reply Y to confirmation questions).11. Wait until all tape IOPs are stopped. This operation could take more than 20 minutes

SCF STATUS TAPE $*


12. Stop any program instance

VOLUME <backpak-installation-subvol>STATUS *, PROG * (to check processes that will be stopped by next command)STATUS *, PROG *, STOP

13. Reboot the servers.

14. Wait for an EMS message reporting the starting of the Emulator Windows service from all .

15. Restart ZSERVER and $XDMS:

$XDMS is usually restarted by the OBEY file starting $ZSVR.The following is a sample of the OBEY file content for $ZSVR.run $system.system.zserver &/name $zsvr,nowait,in $zhome,out $zhome,term $zhome, &pri 199,cpu 0/1delay 5 secondsmediasrv /name $xdms,nowait, in $zhome,out $zhome, &term $zhome, cpu 0 /autostop -1

16. Restart all devices: SCF START TAPE $*

17. Check EMS for normal starting of tape drives.

18. Verify that MEDIACOM is working properly:

mediacom info mediadefsmediacom statusmediacom info volcat *mediacom info filecat *

19. Access the detailed status of each node in the UI:

(on the home page, node name link)On the detailed status page, verify the tape drives are FREE from both points of view: NonStop and BackPak .

20. Start the EMS Extractor(s).

21. Start a tape application.

Procedure Complements for Other Nodes

If the Domain Manager also serves a peripheral node, the only component to reset on the other node is:l The EMS Extractor connected to the local domain.

If is emulating specific tape drives and is also emulating additional tape drives on one or more other nodes, thecomponents to reset on these other nodes are the following:

l The tape applications using tapes managed by the local domain.

l The EMS Extractor connected to the local domain.

l The tape drives connected to shared with the node (to reset the tape system).


TCP/IP Connection Errors from the NonStopErrors might happen when the Domain Manager connects to a Windows server or when a secondary NonStopprocess (BBEXT, or a TACL macro) connects to the Domain Manager.

Using the Guardian TELNET is an often helpful way to clarify the diagnostics. For example, to exercise the loop-back connection from BBEXT or a TACL macro to the Domain Manager, set or verify that the TCP/IP processname of the TACL context is the one in BBEXTCFG (for BBEXT) or in BBSETUP (for the macros):

$DATA15 BPAK 1> info define =TCPIP^PROCESS^NAMEDefine Name =TCPIP^PROCESS^NAMECLASS MAPFILE \ETINIUM.$ZTC2

Connect to the Domain Manager as follows:

$DATA15 BPAK 2> telnet 127.0.0.1 4561

A socket error 4127 for example will return this reply:

TELNET Client - T9558H01 - (10MAY07) - (IPMAAG)Copyright Tandem Computers Incorporated 2004Trying...telnet: connect: Connection refused

A successful connection to the Domain Manager will return this reply below. Enter anything (ex: allo), to exit:

TELNET Client - T9558H01 - (10MAY07) - (IPMAAG)Copyright Tandem Computers Incorporated 2004Trying...Connected to 127.0.0.1.Escape character is '^]'.allo<?xml version='1.0' encoding='US-ASCII'?><Reply xmlns='http://www.etinet.com/xmlns/backbox' ><ReturnCode><Severity>Error</Severity><Code>2501</Code><MessageText>E2501 XML parse error in Inbound socket line 1 col 0: 'syntax error'.</MessageText></ReturnCode></Reply>Connection closed.Connection closed by foreign host.

Error 190 on a NonStop Virtual Tape DriveThis is the most frequent error reported by the HPE tape system at installation time. It can also be generatedas a reply to the SCF START TAPE $xxx command or later during regular operations.

Error 190 means a failure to establish correct communication with the tape emulator in the VTC over the FC orSCSI connection.


For Any Connection:l VTC Emulator (FC or SCSI) Service on the Server has not been started (check in the Windows Service

Manager).

l As noted in the various connections given below, the cause of error 190 can be a cable connected to thewrong port. The UI Configuration > VTC page can be used to automate the matching between the SCFdefinitions and the internal configuration, especially with FC connections that provide WWN to matchthe host and VTC ports.

Important: When disconnecting and reconnecting SCSI cables, the should be powered down, AND beforeeach action all virtual tape devices should be STOPPED and DELETED in SCF, then re-ADDED and STARTED aftercompletion of the action.

For FCSA/VIO Connections:l Incorrect LOCATION (NSK port) PORTNAME (LUN) specified in the SCF ADD command.

l Optical cable is plugged into the wrong port on the Server or the NonStop system (this can be easilydone, particularly if cables have not been labeled at both ends before being laid under a raised floor).

l Optical connector is not fully seated in the receptacle on the Server or the NonStop system. (The con-nector should be securely snapped in to the transceiver socket and not move if wiggled.

l The cable's Transmit/Receive optical conductors are crossed over (reversed) in one of the connectors.Ensure that the transmitting light beam emitted by the ATTO port isn't connected with the NonStoptransmitting port.

l The optical cable is defective (try substituting a known good cable if possible.)

For CLIM Connections:

l Incorrect CLIM name or CLIM logical LUN number is specified in the SCF ADD command.

The procedure for mapping the LUNs in the CLIM will have already given confirmation whether or not aconnection is functioning properly.

For SCSI Connections:

l Incorrect LOCATION (NSK port) or DEVICEID (SCSI Target address) specified in the SCF ADD command.

l SCSI cable plugged into the wrong port on the VTC or the NonStop system (this can be easy to do, par-ticularly if cables have not been labeled at both ends before being laid under a raised floor).

l SCSI connector is not fully seated in the receptacle on the VTC or the NonStop system (check that theplugs' jack screws are fully screwed into the standoffs and are not cross-threaded due to not beinginserted straight. The SCSI connector should not move if wiggled).

l Bent pins in one of the SCSI cable plugs (unplug and examine carefully with a magnifying glass).

l VTC SCSI Emulator Service on the has not been started (check the Windows Services Manager).


l SCSI Target Driver has not been installed and started (check the Windows Device Manager, activateShow Hidden Devices, and check under Non-Plug-And-Play Devices).

l SCSI cable is bad (try substituting a known good cable if possible).

For SCSI Connections to S-Series via a Bridge:

l Log into the Bridge Web Console and verify that the Bridge initiator FC status is "online". Troubleshoot ifnot.

l Validate that the SCSI cables are connected to the correct NonStop systems.

l Log into the Bridge Web Console and reboot the system. Retry the SCF START tape drive.

l Troubleshoot SCSI cables.

$BBEXT EMS Extractor Abend at Start-upJust after the programs are installed or replaced, the first start-up of BBEXT might abend with errors such as:

- “Filter table conversion error: -17, File: $SYSTEM.BPAK.EMSFILT1”

- In EMS: “$BBEXT-F1001 Error 70 from second FILE_OPEN_ on EMSDIST”

The root cause of these errors is a security issue when EMSDIST is started for the first time by BBEXT after theinstallation and EMSDIST interprets the EMS filter provided with the : EMSFILT1. The exact security require-ment is not yet known.

A bypass is to run BBEXT in a different context that will avoid the security issue. Once this BBEXT start-up is suc-cessful, stop BBEXT and restart it as originally pre-defined. This has been a successful bypass at all customersites reporting this kind of error.

To bypass security issues and obtain a first successful run:

l Do not start BBEXT as a permanent application PROCESS defined in SCF $ZZKRN, but by using the OBEYfile OEXT.

A process cannot be started by the TACL with a process name that is already configured in a $ZZKRNpermanent application process - even if this process is not running. It may thus be necessary to changethe process name $BBEXT in OEXT.

l Execute OEXT with SUPER.SUPER.

DSM/TC Tape Volume Jammed INUSE or SELECTED StateAfter some abnormal processing on tape volumes cataloged in DSM/TC, the tape volume might be stuck INUSEor SELECTED after the tape application has stopped.

When this happens, a retry on the same volume is rejected because it is “already in use”. The HPE KnowledgeBase documents a TACL command that is not described in the regular NonStop manual.


1. Be sure there is no other tape application running: stop the EMS Extractors and wait for the unload oftapes currently being accessed.

2. Enter this command at the TACL prompt logged with a user in the SUPER group: MEDDEM 27.

3. Verify the status of the volume:

MEDIACOM INFO TAPEVOLUME <label>, POOL *

Refer to the HPE NonStop Knowledge Base for further explanation.

$ZSVR or MEDIACOM HangWhen there are several tape connection errors during setup activities, sometimes just when SCF DELETE TAPEis executed while there is some TAPE activity, $ZSVR and MEDIACOM might hang and the tape system must bereset.

The symptom below is a strong indication of a tape system that must be reset.

18:33 \ETIWLAB INSPECT - Symbolic Debugger - T9673D40 - (08AUG05) System \E18:33 \ETIWLAB Copyright Tandem Computers Incorporated 1983, 1985-199918:33 \ETIWLAB INSPECT TRAP 0 - Illegal address reference18:33 \ETIWLAB 252,00,00049 $ZSVR #DELETE^DEVICE + %1120I

Windows Disk File Being Used by Another ProcessA VTC might not be able to load a virtual volume, because the corresponding Windows disk file in a WINDISKData Store because the file is being in use and the VTC cannot open it.

Sample EMS message reporting this condition:

2016-12-07 12:52:39 \P05.$BBEXT ETINET.100.100 3011 $BBEXT-E3011 MountId: \P05.848. Error 3205 load-ing V11768 on WSRV2379 $BTAP21 E3205 MountId: \P05.848 for volume V11768. VTC WSRV2379 returnsbusy storage condition: (BBSL) Error opening the WINFILE storage (\\WSRV2379\P05_DS00_E\LBV11768.DAT- (The process cannot access the file because it is being used by another process)

A Windows disk file can be open using one of the following:

- A script configured in the Data Store is still executing, backing up or restoring this file.

- Another tool configured to duplicate the image of virtual volumes is processing the file.

- An Antivirus running in the is configured to scan the images of virtual volumes.

The Antivirus are normally configured to avoid the scan of virtual volumes.

- Two Domains load the same virtual volume by accessing the same Windows disk file.


ABORT TASK Reported by the VTC EmulatorWith severe error conditions in the Tape Emulator (for example, a failure to write the image of virtual volumesinto the Data Store) the tape application will often abort.

The error recovery in the SCSI protocol is then reported by the Tape Emulator in the Windows Event Viewer, Vir-tual Tape Controller log, with the following type of message:

10/16/2016 2:05:48 AM VTC Emulator (FC) Information None 5095 N/A STLTTAPEP2 Virtual Tape DevicePort00-Target00-Lun00 REINITIALIZE after an ABORT TASK

To analyze the error condition and to fix it, browse the NonStop EMS messages, the Windows Event Viewerlogs, and the Windows log produced by the (VTLog.log or FCLog.log).

The ABORT TASK is just a log of error recovery that does not need special consideration for an FC connection.

For a SCSI copper connection, as soon as possible, it is recommended to stop all tape devices in the NonStopSCF, re-boot the server, and restart the tape devices in the SCF.

Error Triggering a NonStop UtilityNonStop utilities, mainly SCF, MEDIACOM and CLIMCMD, are occasionally started by the Domain Manager whenno public SPI interface is available. There are currently two such cases:

- In the UI > Configuration > VT Controller ID > Add Devices Automatically > Refresh.

- During the load of a tape volume catalogued in the DSM/TC, the media type is updated in the DSM/TC tomatch the media type configured in the Volume group of .

Domain Manager could time out waiting for the result in the OUT file of the utility.

EMS shows error messages such as:

E3427 Error nn opening <file-name> containing result…E3404 Timeout, more than <nn> seconds .. waiting for file <file-name> …Actual example: E3404 Timeout, more than 300 seconds waiting for file\ETINIUM.$DATA06.SUPOPER.CTMP0078. Context: INFO ADAPTER $ZZSTO.*, DETAIL; STATUS ADAPTER$ZZSTO.*, SACS

The TACL output or the TERM of these utilities is sent to the file configured in the Domain page: “Utilities Log”assigned to $NULL by default. The second exploration is to assign “Utilities Log” to a spooler location, thenreproduce and check the spooler output.

For Advanced Users Only:There are several Domain Manager parameters that are not available through the UI, but that can be patchedby TEDIT BBSVCFG (when regular procedures cannot solve a problem triggering a NonStop utility such as SCF orCLIMCMD from the UI).


Patching BBSVCFG by TEDIT is normally reserved for HPE support, but for specific errors, it might also be car-ried out by a customer executing the SCF.

Before patching, make sure to:l Have saved the configuration through the UI to get the XML tags and default values of the latest Back-

Pak version in the BBSVCFG file.

l Have saved BBSVCFG before the manual patch.

The special parameters related to the execution of NonStop utilities are below:<SubProcessInFile>$ZHOME</SubProcessInFile><SubProcessHometerm1>$TRM0.#A</SubProcessHometerm1><SubProcessHometerm2>$ZHOME</SubProcessHometerm2><ScfShortWait>30</ScfShortWait><ScfLongWait>300</ScfLongWait>

<SubProcessInFile> An alternative to $ZHOME could be $YMIOP.#CLCI, or a virtual terminalsuch as $VHS.

<SubProcessHometerm1>: Used only by very old systems before Gxx. A possible alternative is aspooler specification such as $S.#BPAK.HOMETERM.

<SubProcessHometerm2>: Used only for all Gxx, Hxx and Jxx systems. A possible alternative is aspooler specification such as $S.#BPAK.HOMETERM.

<ScfShortWait>: Maximum number of seconds waiting for the shortest commands suchas SCF PROBE PROCESS $NCP, TO *.

<ScfLongWait>: Maximum number of seconds waiting for longest commands such asSCF STATUS ADAPTER $ZZSTO.*, SACS

Devices Connected Through SCSI Bridge Don’t Reconnect After Server Main-tenanceContext

Maintenance has been performed on the server that required either rebooting the server or stopping andrestarting the VTC (FC) Emulator service. At the service restart time, although the NonStop TAPE devices asso-ciated with the virtual devices were not stopped, one or more symptoms may have appeared:

l Automatic load failed with a NO RESOURCE available cause.

l In SCF, TAPE operations failed with error:

o STORAGE E-00010 File system error: 40, call: WRITEREADX, file: $ZNET

o STORAGE E00045 I/O process is busy.

l NonStop TAPE device (s) appear (s) FREE but Virtual Tape device status is INACTIVE or ACTIVATED formore than 30 seconds in the Status for NonStop node page in the User Interface.


Solutionl Make sure the Bridge firmware is at revision (or higher):

o etinet.SFC4200.v3.01.13.rc1 (Sep 20 2012 09:21:29)

l Log on to the Bridge Web console and select the Reboot System from the Bridge Control and thenacknowledge the request. Wait for the login screen to re-appear.

WARNING from SQL [6008]: Statistics …This warning can occasionally be reported by a Catalog Sync Export or Import process accessing a DSM/TC cata-logue.

This warning does not invalidate the process results. HPE manuals explain how to avoid this message using theSQLCI UPDATE STATISTICS command. It is recommended to run it on all tables of the VOLCAT and the FILECAT.

Some SQL operations (DDL) are not allowed during the UPDATE STATISTICS and it is safest to avoid using theDSM/TC catalog while running the UPDATE STATISTIC. i.e., no tape activity, no MEDIACOM session, and no UI.

The operator must be allowed to read the mention table and to update the SQL catalog (metadata tables inthe subvol).

> MEDIACOM INFO VOLCAT *(To get the volcat-subvol name)> VOLUME volcat-subvol> SQLCI>> UPDATE ALL STATISTICS FOR TABLE table-name NO RECOMPILE;(to execute for tables VOLUME and VTOFC)> MEDIACOM INFO FILECAT *(To get the filecat-subvol name)> VOLUME filecat-subvol> SQLCI>> UPDATE ALL STATISTICS FOR TABLE table-name NO RECOMPILE;(to execute for tables DFTOV, DISKFILE, TAPEFILE, TFTOV, CONFIG)

Shares and Files Access

Disk Shares

The disk storage is provisioned and the shares are created by tools that depend on the file server technology.As network access protocol, CIFS is preferred over NFS. The security must allow full access to the Windowsaccount which will be entered in the Data Store configuration.

The firewalls between the application in the VTCs and the file server must allow the CIFS traffic.

Sub-Directories

A Data Store is a group of disk locations that will store a set of virtual volumes. Each location will be entered asa fully qualified disk directory name in the URL notation (\\server\share[\sub-directory..]\).


At least a dedicated directory must be created for each future Data Store entity. Volumes belonging to dif-ferent Data Stores must not be located in the same path.

Multiple locations are created to spread the Data Store over several servers and/or several physical disks.

Local Disks

Accessing the disk through their drive letter must be avoided. If there is any chance there will be more than asingle VTC in the environment, it is recommended to define shares on the directories created for BackBox orVTR and configure the Data Store location by using the share URL (\\VTC1\WIN1), rather than using directorynames qualified by a disk letter (D:\WIN1).

File Access Security

The VTCs will execute an MS-Windows non-interactive login using the account & password specified in the DataStore entity of the Domain configuration.

To create Windows Files Data Store Users and to grant them certain privileges refer to the appropriateMicrosoft documentation and procedures.

The account can be a local account (all VTCs must have this same account & password), or a MS-Windowsdomain account.

The file security for all files in all directories of the Data Store must allow full access to the Data Storeaccount.

To create Windows Files Network Shares on a VTC Server follow the appropriate procedure described onthe Microsoft Windows web site.

Troubleshooting Copy Pool SyncEMS messages indicate the progress of copying and reporting of any errors:

15:00 \ETINIUM GCR101EA-TINTIN-I5030 The script [... es\ETINET\VTC\Scripts\Co15:06 \ETINIUM GCR101EA-I3498 Copy scripts will be submitted for Data Store G15:06 \ETINIUM GCR101EA-TINTIN-E8014 Cannot find complete volume files(IND,DA15:06 \ETINIUM GCR101EA-I3220 1 Copy scripts have been submitted in data stor15:06 \ETINIUM GCR101EA-TINTIN-I5029 The script [... es\ETINET\VTC\Scripts\Co15:07 \ETINIUM GCR101EA-TINTIN-I5030 The script [... es\ETINET\VTC\Scripts\Co

Script output is generated to troubleshoot execution problems.

The output can be found on the VTC server that executed the script in a log folder with the same name as theData Store.

To find the script log folder, first search the Default Folder and then navigate to:C:\ProgramData\ETINET\VTC\Log\Script\<DataStoreName>


***** SCRIPT output execution for LOAD operation - Request Timestamp 2016-07-17T13:43:29 *****...C:\Program Files\ETINET\VTC\Scripts\CopySync>CopySync.exeStart CopySync process for volume LBECPS04**** Error: There is no remote storages defined in the copy pool in the con-figurationof DataStore GCR-WIN1ETI_COPYPOOLC:\Program Files\ETINET\VTC\Scripts\CopySync>if ERRORLEVEL 1 (echo "Ending in error"time /texit 1

BackBox®E4.07...

Documents

Transcript of BackBox®E4.07...