BackPak® H4.00 Troubleshooting and Messages Manual HP Part Number: 748417-002 Published: March 2014 Edition: G06.24, H06.06 or J06.
Legal Notice © Copyright 2013 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Table of Contents INTRODUCTION ............................................................................................... 4 TROUBLESHOOTING ......................................................................................... 4 SOURCE OF INFORMATION ................................................................................................................................. 4 Log in NonStop ...........................................................................................
Troubleshooting INTRODUCTION This manual applies to both BackBox and BackLib products. The TROUBLESHOTING chapter provides hints or procedures to handle abnormal events. Some frequent or special cases have dedicated documentation in this chapter. All BackPak numbered messages are described in the last chapter MESSAGES.
Troubleshooting running the BackPak domain manager, but attached to a different, peripheral node, get EMS from both nodes. Trace in NonStop It is possible to trace the BackPak domain internal activity in NonStop. The tracing is activated by the domain page configuration in the BackPak GUI by: - Setting the “Trace Level” to 1 Entering a “Trace Sub Volume” that will receive the trace files. This sub volume must be dedicated to receiving traces.
Troubleshooting Virtual Tape Controller is the name of the log in the MS-Windows Event logging The BackBox software writes to these Windows logs: Log name Source Virtual Tape Controller All Windows services, except the Script Controller VTC Script Controller Only the Script Controller BackPakUiLog Only a GUI running locally, can be found in a work-station. The provided message Event number corresponds to the message numbers documented in the next chapter of this manual.
Troubleshooting AdmLog.log is written by the “VTC Admin” service. It is controlled by C:\ProgramData\ETINET\VTC\Config\BBAdminAppCfg.xml. See the Appendix D in the BackBox User Manual. EndOperationLog_.log Messages about the forwarding of the tape unload events to the Domain manager on NonStop. These logs are automatically purged: up to 5 or 10 occurrences of these files of limited size are produced in a round-robin fashion. z EVMessageLog_.
Troubleshooting Note that this trace control works correctly only when a VTC receives activity (i.e. load requests) from a single BackPak domain; this might require to stop EMS Extractors of domains sharing the same VTC but have different trace setting for the VTC.. It is also possible to control the trace level in the file BBFcEmulAppCfg.xml. See the Appendix D in the BackBox User Manual. Installation.log is written by the BackBox SETUP.EXE installer. LB
Troubleshooting ScriptControllerRestoreNskSession_.log Messages about the forwarding of local messages forwarded to NonStop EMS. Complement to EVMessageLog_. \Script\\ sub-directories Each executed Windows script leaves its output in a file located in a sub directory named according the Data Store Id of the involved virtual volume: \Script\DataStoreId\.
Troubleshooting In the distributed sample *TRACEFLAG *TRACEFLAG *TRACEFILE DSM.OPT, these commented options control the trace: INSTR_API GENERAL ALL,-NLS d:\trace\dsmtrace1.txt Remove the heading * to un-comment a line. TRACEFLAG INSTR_API GENERAL will produces less traces than ALL,-NLS. Logs in the workstation The GUI produces occasional messages in the MS-Windows Event logging facility, in a log named BackPakUiLog.
Troubleshooting • For a case involving the tape emulation or the storage, the VTC involved by the operation must be collected. Then all produced files must be sent to the Product Support.
Troubleshooting The data to collect is specified in a windows presented for verification and confirmation. The default parameters are appropriate for most cases. “Windows System” frame From … To … Period for selecting the MS-Windows Event Logs 12 BackPak H4.
Troubleshooting System System MS-Windows Event Log Application Application MS-Windows Event Log Security Security MS-Windows Event Log MsInfo32 Report produced by Microsoft tool msinfo32.
Troubleshooting The default location of the zip file prepared by the collection tool is reachable by an entry in the Start menu 14 BackPak H4.
Troubleshooting Common and Special Cases Tape subsystem reset procedure This procedure is applicable in extreme cases, when the tape subsystem infrastructure (ZSERVER and DSM/TC) seems impacted by severe operational difficulties, when $ZSVR volume recognition does not execute correctly and DSM/TC does not reply properly to commands. This procedure is not a replacement to the HP documentation for managing HP NonStop components.
Troubleshooting 12. Stop any BackPak program instance VOLUME STATUS *, PROG * (to check processes that will be stopped by next command) STATUS *, PROG *, STOP 13. Reboot the VTC servers 14. Wait for EMS message reporting the starting of Emulator Windows service from all VTCs 15. Restart ZSERVER and $XDMS $XDMS is usually restarted by the obey file starting $ZSVR Sample obey file for $ZSVR, provided just as indication. run $system.system.
Troubleshooting the tape drives connected to VTCs shared with the node (to reset the tape system) TCPIP connection errors from the NonStop Errors might happen when the domain manager connects to a VTC Windows server, or when a secondary NonStop process (BBEXT, or a BackPak TACL macro) connects to the domain manager. Using the Guardian TELNET is an often helpful way to clarify the diagnostic.
Troubleshooting Error 190 on a NonStop virtual tape drive This is the most frequent error reported by the HP tape system at installation time as reply to the SCF START TAPE $xxx command, it can also happen later in regular operations. This has a number of possible causes, but in general it means a failure to establish correct communications with the tape emulator in the VTC over the FC or SCSI connection.
Troubleshooting • • • • • SCSI connector is not fully seated in the receptacle on the BackBox or the NonStop system (check that the plugs' jackscrews are fully screwed into the standoffs and are not cross-threaded due to not being inserted straight.
Troubleshooting DSM/TC tape volume stuck INUSE or SELECTED state After some abnormal processing on tape volumes catalogued in DSM/TC, the involved tape volume might be stuck INUSE or SELECTED after the tape application stopped. When this happens, a retry on the same volume is rejected because it is “already in use”. The HP Knowledge Base documents a TACL command that is not described in the regular NonStop manual. 1.
Troubleshooting Here are the possible “other processes” that can open the Windows disk file: - 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 VTC is configured to scan the images of virtual volumes; note Antivirus are normally configured to avoid the scan of virtual volumes.
Troubleshooting Actual example: E3404 Timeout, more than 300 seconds waiting for file \ETINIUM.$DATA06.SUPOPER.CTMP0078. Context: INFO ADAPTER $ZZSTO.*, DETAIL; STATUS ADAPTER $ZZSTO.*, SACS As always other messages in EMS should be first searched; for example SCF might report an explicit message while opening its IN file. The TACL output or the TERM of these utilities is sent to the file configured in the BackPak Domain page: “Utilities Log” assigned to $NULL by default.
Troubleshooting Recovery of encryption related errors Several errors related to the encryption configuration might happen, at initial installation or after numerous cases of changes or connection errors. The potential errors are likely to be a discrepancy in encryption configurations or a failed connection. Before considering any configuration changes, it is suggested to: 1. Trigger the set of verifications of encryption connectivity and configuration consistency in the BackPak UI.
Troubleshooting The BackPak UI Key Manager Test is strongly recommended after any configuration change on any encryption related platform. • Devices connected through SCSI Bridge don’t reconnect after VTC server maintenance Context Maintenance has been performing on the VTC server that required either rebooting the server or stopping and restarts the VTC (FC) Emulator service.
Troubleshooting > SQLCI >> UPDATE ALL STATISTICS FOR TABLE table-name NO RECOMPILE; (to do 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 do for tables DFTOV, DISKFILE, TAPEFILE, TFTOV, CONFIG) 25 BackPak H4.
Messages MESSAGES Introduction EMS is already the console for the HP NonStop tape system, it is also: o the console for BackBox/BackLib NonStop components o a partial duplicate of the logs of the BackBox MS-Winodws components This manual lists the messages that can be logged in EMS or displayed by the Web user interface.
Messages BBOX-BB1-I103 Service started (VTC Virtual Tape Devices) BBOX-W3186 Automatic unload of volume Z XE042 that was load ed since 2007-08-21 11:48:53 on \ETINIUM.$VX31301 that is free. Appl ication process \ETINIUM.0,232 started on 11:48:34 is no longer running. $BBEXT-E3007 MountId: \MONT.974. No available virtual device to mount LMW108. W312 5 Error communicat ing with VT Contro ller(s): HAPPY.
Messages List of BackPak messages Number 1 Text %1 Explanation Action An error occurred in the VT Controller during the Write or the Read to a virtual volume. TSM DataStore: Refer to the IBM Tivoli Messages manual. Windows file DataStore: Refer to the Microsoft documentation. 103 Service started (VTC Admin) The service implementing the administrative service in the VT Controller has started. None. 104 Service stopped (%1) A service stopped in the VT Controller. None.
Messages Number 112 Text Service cannot start. There is no %1 target mode adapter found on the server Explanation Warning message indicating that the SCSI (or FC) service can not start because no corresponding SCSI (or FC) hardware/driver was found on the server Action None if currently the server doesn’t have the hardware corresponding to the service that cannot start. (The service should ideally not be configured for Automatic startup in Windows).
Messages Number Text Explanation Action 1004 Abort in %1 %2, error code %3 %4 Severe internal error. Refer to the Guardian Procedure Errors and Messages manual. 1005 No memory available for %1 Memory allocation failed. Contact the Product Support. 1006 Unexpected tag %1 Internal error. Contact the Product Support. 1007 Guardian Error %1 detail %2 from %3 %4 A Guardian procedure call failed. Refer to the Guardian Procedure Errors and Messages manual.
Messages Number Text Explanation Action 1106 %s %s version %s (serie %sxx.xx) is incompatible with domain manager version %s. Components were installed from product that have not the same distribution channel Complete the installation of a single package 1501 *** SQLCA display of SQL statement at: BBDBM_Get_Tapefile_fil eid.#2.616 of process \MONT.
Messages Number 2003 Text Config file %1 unavailable Explanation The BBSVCFG file is not available. Action Check that the file is created, is not locked by an application outside the Domain Manager. Check the Guardian User ID in session has authorized acces to this file. 2499 Invalid XML attribute: %s in %s. Error parsing an XML syntax. Contact the Product Support. 2500 XML attribute %s not found in %s. Error parsing an XML syntax. Contact the Product Support.
Messages Number 2506 Text Explanation Action End tag %1 does not match start tag %2 in %3 Invalid XML syntax. 2507 Unexpected element name %1 as root in %2 An XML document name is unknown. Contact the Product Support. 2508 Config file %s not available for rewrite, errno: %Id Guardian error when accessing the configuration file BBSVCFG for update. Check the error code, the file definition, and the security attributes.
Messages Number Text Explanation Action 2604 Socket error %1 on completion of %2 TCP/IP error. Refer to the TCP/IP Programming HP NonStop manual. Socket errors. 2605 Program parameter missing: accept address The Domain Manager does not receive the expected parameter from the LISTNER. Contact the Product Support. 2606 TCP accept address ‘%1’ should contain a dot The Domain Manager does not receive the expected parameter from the LISTNER. Contact the Product Support.
Messages Number Text Explanation Action 2612 Socket error 3504 on socket_nw(), check if the configured TCP process name is qualified by an invalid node name. A socket IO completed abnormally. Check the TCPIP setting for =TCPIP^PROCESS^NA ME in the domain configuration, VT Controller pages 2613 Invalid data length %u received on socket %s. %s Invalid data in the communication stream. Contact the Product Support. 2614 Socket error %d when initiating connection to address %s port %s.
Messages Number 3005 Text Management of SCRATCH tapes not available Explanation An application TAPE DEFINE specified a SCRATCH volume. Action Management of SCRATCH tapes not available in the EZXGateway software. Use TAPECATALOG DEFINE, or specify a specific volume label. 3006 Volume must be specified in %s transaction An operation can not be processed because the volume label is missing. Specify the tape volume. MountId: %1.%2. No free virtual device to mount %3 No free device.
Messages Number Text Explanation Action 3015 VT Controller %1 in drive %2 definition is unknown Referential integrity error in the Domain configuration. Contact the Product Support. 3016 MountId: %1.%2. Volume %3 %4 is not defined for automatic load Automatic load is rejected because the volume was created with the attribute “No automatic load”. Issue a manual mount.
Messages Number Text Explanation Action 3026 Must be logged SUPER group to execute this command An error occurred while updating a DSM/TC or TMF catalog. Sign off using a Guardian User ID on the BackPak UI. 3027 Adding volume %1 in pool %2 of catalog %3 is rejected by DSM/TC An error occurred while updating a DSM/TC catalog. No error code supplied. Try to use MEDIACOM to catalog the virtual volume. 3028 VT Controller %1 is unknown Referential integrity error in the Domain configuration.
Messages Number 3035 Text Explanation Action Reduce the number of volumes to create, or Numeric suffix in ‘%1’ not sufficient to compute %2 labels When requesting the creation of a number of volumes, the label of the 1st volume does not allow all the requested labels to be created. 3036 Unable to create %1 volumes starting at label %2: %3-%4 already exists in domain catalog One of the volume labels to be created already exists in the catalog of virtual volumes.
Messages Number 3042 Text Explanation Action Cannot start SPI %1 on node %2. Error %3 The Guardian node name of the Guardian tape catalog, DSM/TC or TMF, is rejected by the NODENAME_TO_NODEN UMBER_ Proc call Fix the Volume Group definition in the Domain configuration. Check the node name in the TMF Guardian node, or in DSM/TC Volcat that must be qualified by a Guardian node. 3043 Info TMF media %1 on node %2 is rejected by TMFSERVE code %3 Access to the TMF catalog is rejected.
Messages Number Text Explanation Action 3052 Uncommitted transaction is aborted A TMF transaction did not end normally. Verify the results of the latest operation. 3053 %s SPI return-code %d in %s. %s An error code is returned by an SPI program. Refer to the TMF Management Programming, or DSM/TC Management Programming HP NonStop manual.
Messages Number Text Explanation Action 3060 Error for volume %s. The volume group %s catalogs in DSM/TC and allows only labelled volumes It is not possible to create Unlabelled tapes in a Volume Group defined for tape cataloging with DSM/TC. Use specific Volume Groups that do not catalog the volumes to be created as Unlabelled volumes. 3061 The status of TMF tapemedia %s on node %s must be SCRATCH or BAD, and its medium must be TAPE to allow deletion.
Messages Number 3068 3069 3070 Text Explanation DSM/TC Catalog status for volume %s not (yet) appropriate. LabelType %s, lbMethod %d, defineClass %d, catalogStatus %d Unexpected status reported by MEDIASRV. MountId: %s.%Id. Tape label mismatch, label in received request: %s, in pending mount: %s Internal error. Info pool %s catalog %s rejected by MEDIASRV code %d. %s Error querying a pool. Action Contact the Product Support. Set the Volume Group to Auto-Scratch = False to bypass.
Messages Number Text Explanation Action 3074 Obsolete configuration tag '%s' in %s The Domain configuration contains obsolete parameters that block regular operations. Use the Web UI to edit the configuration, check the interpreted configuration parameters, and save the configuration to store it in the new format. 3075 Incompatible tags '%s' and '%s' in %s. An error is detected in Domain configuration. Use the Web interface to fix the configuration.
Messages Number Text Explanation Action Check the status of the volume (Current operation) in the domain catalog. Reset the “Current operation” if required. The stats of last operation might be lost. Unexpected unload of %s-%s at %s not registered in BackPak domain. The unload is related to the operation %s at %s. The operation state in BackPak domain is %s A VTC notifies the domain manager that a volume is unloaded. 3083 Message from %s %s %s received for the domain '%s', domain '%s' is expected.
Messages Number 3086 Text Access to volume %s denied to %s.%s, %s. Explanation An operation on a volume is rejected because the user has not the required authorization. Action Check the volume owner and access authorizations in the Web User Interface. Eventually update this security setting on the volume to bypass the error.
Messages Number Text Explanation Action 3094 Volume %s is member of the volume group %s defined with DSMTC volcat %s and pool %s, but the tape volume is found in DSMTC volcat:%s pool:%s. Check configuration. Inconsistence between the state of a volume in DSM/TC and the state of the volume in the Domain catalog and configuration. Make sure the Domain configuration (specially the Volume groups) corresponds to the Guardian tape catalogs.
Messages Number 3102 Text Explanation VTC %s did not reply to a Connect message. A message is rejected by a VT Controller, most probably because IP filtering. Action Check the Domain address page in the Web page /Admin of this VT Controller. Check the MS Windows Event Viewer. 3102 Library %s did not reply to a Connect message. A message is rejected by the BBLM process of this library. Check for other EMS messages related to this BBLM process. Restart the BBLM process.
Messages Number 3108 Text Explanation Action MountId: %s. Volume %s. Equal sign missing after keyword '%s' in the mount message of TAPE DEFINE.. A load request is rejected because an unexpected content of the TAPE DEFINE. Check the bbox-secure syntax in the TAPE DEFINE comment. 3109 MountId: %s. Volume %s. MVS Dataset name '%s' exceeds 44 characters in the mount message of TAPE DEFINE.
Messages Number 3114 Text Pending mount request not found for the volume %s Explanation Action The Domain Manager receives a mount request that is no more in the list of MEDIACOM pending mounts. Check the EMS log to identify why the mount request was cancelled. Resubmit the job. 3115 Invalid store type %d in catalog record to write for the virtual volume: %s-%s. Internal error. Contact the Product Support.
Messages Number Text Explanation Action 3120 Volume %s manually unloaded. A manual unload is commanded by the Web user interface, cancelling any running transfer in hard way. None. 3121 Current operation (%s) of volume %s not reset because of error in communication with EZX MVS Agent that has allocated the dataset(s) An attempt to “Reset current operation" of the volume by the Web user interface is rejected because of an error in the communication with the MVS Agent.
Messages Number Text Explanation Action 3128 "EZX_START_XFER FILE ID '%s' missing or invalid (%s.%s %s) FILE ID is a mandatory parameter. Check FILE ID contains a valid MVS DSN. 3129 START_XFER CONVERSION '%s' should be 'ASCIIEBCDIC' or 'JIS-EBCDIC' (%s.%s %s) Invalid CONVERSIN Parameter. Check CONVERSIN parameter. 3130 Error computing MVS track capacity for MVS volume %s, EZX volume %s. %s Internal error. Contact the Product Support. 3131 MountId: %s.
Messages Number Text Explanation Action 3137 Error computing MVS dataset allocation for disk %s, EZX volume %s. %s Internal error. Contact the Product Support. 3138 MVS dataset %s allocated for transfer through EZX volume %s for %s.%s %s. %s Successful lock of MVS dataset when processing a mount request. None. 3139 Estimated data size to send (%s MB) requires the creation of %ld MVS datasets. Maximum number of datasets %s is %ld. EZX volume %s for %s.%s.
Messages Number 3142 Text MountId: %1.%2. DEXP error %3 loading %4 on %5 %6. %7. Load to be retried Explanation A VT Controller is not able to access a DE XP volume. Other routes configured in the DE XP volume will be tried. The failed load will be retried at the same frequency as the “busy drive” condition. Action 1- Force the discovery of DE XP volumes by the VT Controllers, by inquiring the list of DE XP volumes of the domain through the Web user interface, Data Exchange tab.
Messages Number Text Explanation 3150 BBCMD stops retrying sending a '%s' message to the Domain Manager after %ld retries. The retry limits specified in EZXSETUP/BBSETUP file are reached. BBCMD and the current TACL macro end with error. Check the cause of errors in previous messages and in EMS log. 3151 VOLUME or STOREID must be specified to free an MVS dataset.
Messages Number Text Explanation Action 3155 EZX_START_XFER R_RECFM=%s R_LRECL=%ld R_BLKSIZE=%ld: {DCB-error-text}. Volume %s (%s.%s %s) The consistency check failed on the DCB parameters (RECFM, LRECL,BLKSIZE) of the MVS dataset. Error is specified by the DCBerror-text. Check the DCB parameters of the EZX_START_XFER macro. 3156 MountId: %s. Device '%s' requested to load %s is not free, or not on an active VTC that is a route to the DataStore %s.
Messages Number Text Explanation Action 3159 State of volume %s does not match. VTC reports %s. Domain manager reports %s. Device %s.%s Discrepency between states in the domain manager and states in a VTC. The processing of the current event might be aborted. Check possible other messages in EMS. Check the state of the involved volume and device in NSK MEDIACOM, in the BackPak domain catalog.
Messages Number Text Explanation 3165 Automatic unload of volume %s. Volume was loaded since %s on %s.%s that is now free. A volume is loaded since too long without being used by a NonStop application. None if no other symptom. 3166 Invalid %s parameters. Keyword '%s' is unknown. Invalid TACL program parameters. Verify the macro or program parameters. 3167 Invalid %s parameters. Value missing for keyword %s. Invalid TACL program parameters. Verify the macro or program parameters.
Messages Number 3172 Text Explanation Tape device '%s' is unknown in domain %s. See message #%ld from %s. A message logged by a VTC to EMS names a virtual device that is not configured in the BackPak domain. Action Check the configuration of the BackPak domain and the SCF device definition. There might be nothing wrong if there are several BackPak domains sharing a VTC, but not sharing all devices.
Messages Number Text Explanation Action 3178 VOLUME scan: another scan is still executing. New scan skipped EZX-Gateway product: The execution of a VOLUME scan exceeded the delay between two scans. Revise the parameter VOLUME-SCAN-interval in BBEXTCFG 3178 Disk model mismatch for EZX volume %s Dataset %s. MVS volume %s is model %s, DataStore %s is configured for model %s EZX-Gateway an MVS disk was found with 3380 geometry when 3390 is expected, or vice-versa.
Messages Number 3183 Text Explanation Action MountId: %s for volume %s. Pre-load of next volume %s is enabled Informative message. MountId: %s for volume %s. No next volume to pre-load. Informative message. The volume is the last of a multi-volume set. This message is displayed only when EMS verbose is true in the Domain configuration. Pre-load was generated for %s, but did not complete before the unload of the previous volume %s. Pre-load is canceled. Informative message.
Messages Number 3190 Text Explanation Action Redefining and reloading the alternate keys of volume file %s. At first usage after an upgrade of NonStop programs, the VOLUME file is modified to fit with the new software version Wait a minute for FUP to complete the LOADALTFILE operation. FUP is started with TERM and OUT set to $ZHOME. Refer to the V1.6x to V1.62 Upgrade manual 3191 MountId: %s.
Messages Number Text Explanation Action 3197 BB020_RESERVE DRIVE %s: can not specify both NONE and a volume class. Syntax error in the BB020_RESERVE TACL macro Modify the CLASS parameter of BB020_RESERVE 3198 BB020_RESERVE: DRIVE parameter missing Syntax error in the BB020_RESERVE TACL macro Specify the DRIVE parameter of BB020_RESERVE 3199 BB020_RESERVE DRIVE %s: drive not found in the configuration.
Messages Number 3206 3207 Text Explanation Invalid %s parameters. Comma must be followed by space in '%s' Invalid syntax MountId: %s for volume %s. This BACKUP volume has been written, unloaded and is now being reloaded by the same process. Check carefully the backup output report and the volumes cataloged in DSM/TC for this backup. This is very probably the result of a disk error when BACKUP can not back up a complete paritionned file. Action Fix syntax entered by user. Contact the Product Support.
Messages Number Text Explanation Action 3210 The domain configuration does not contain any active VTC or library attached to node '%s'. A “Node Status” query in the BackPak GUI has no data to return, as there is no tape drive configured for this node. Verify the domain configuration, that might have changed between two queries 3211 There is no backup script configured in data store %s.
Messages Number 3218 Text Disk path %s in Store %s is not accessible. Explanation Result of the macro BB022_CHECK_SPACE. The path is unavailable to BackPak software. Action Login in Windows on a VTC with the Windows account / password configured in the Data store. Test access on the configured path name. F connectivity and security issues "Free space (%s MB) in %s is not enough for writing a full volume (%s MB) in volume group %s. Result of the macro BB022_CHECK_SPACE. Revise the maximum volume size.
Messages Number Text Explanation 3224 BB023: %s backed up Windows files have been deleted. Deleted size: %s bytes Summary of execution of macro BB023_DEL_BACKEDUP None 3225 Normal job end A TACL macro finished None 3226 Internal status %s prevented the use of drives free in NonStop. %s. This message is embedded in msg 3227 reporting a failed load. Some status (LOADING, LOADED, UNLOADING) are expected normal status preventing a load to execute.
Messages Number Text Explanation Action (see above the version for BackLib) 3226 Internal status %s prevented the use of drives free in NonStop. %s. %i devices LOADING ($device1, $device-2…) %i devices RESERVED ($device3, $device4…) This message is embedded in msg 3227 reporting a failed load. Msg 3226 explains why some devices FREE in NSK can not be used for loading a volume. Possible status can be: “LOADING”: a media is still being moved by the robotic to a drive.
Messages Number 3229 Text Creating file %s Explanation Action The BackPak domain manager (re) creates a missing file in the BackPak installation NSK subvol. OPER file contains only temporary status, can be recreated at will. The re-creation of other files requires ito stop the tape operation and investigation. 3230 MountId: %s. Loading %s impossible on device %s because of the internal status %s in VTC %s. An abnormal internal status prevents a load to execute. Investigate the error.
Messages Number 3234 Text Domain license violation. DEFINE =TCPIP^HOST^FILE (%s) not allowed when a licensed VTC address is symbolic (%s). Explanation License rule violation. Action Do one of these: - Remove any =TCPIP^HOST^FILE DEFINE from the context of the TCPIP LISTNER or in the VTC configuration page. - Request a ETINET license that contains the VTC host name rather than an alternate DNS name.
Messages Number 3241 3242 Text Explanation Action No virtual device of active VTC is configured for node %s A load request is issued from a NonStop node that has no device configured in an active VTC Define a virtual device for the node. Additional queries executed to refresh the operational status of node %s. Status of tape drives and mount requests are normally maintained in the OPER file by the EMS Extractors, for lighter processing of web requests.
Messages Number 3247 Text Volume label %s was loaded on %s by the other domain %s Explanation A VTC contacted to produce a web status page, reports that a loaded volume does not belong to the querying domain. Action Be sure the two domains share tape drives on purpose. This occurs when two domains share the same tape drives. 3248 3249 MountId: %s. Identical request to load %s was recently executed (load/unload on %s) %s. Request rejected MountId: %s.
Messages Number Explanation Action More than %ld tape devices are configured. Devices in exceeds are ignored. Automatic mount is limited to a maximum number of tape devices. Contact the Product Support.if a site requires more devices. 3253 Domain license violation. Physical media Virtualization / Materialization is not licensed. Virtualization / Materialization must be licensed to be used. Contact the Product Support.
Messages Number Text Explanation Volume %s is cataloged in volcat %s pool %s with media type %s, should be cataloged with the emulated media type %s since BackBox V2.06. Volume media type might have to be fixed by 'MEDIACOM ALTER TAPEVOLUME , TYPE LTO3, POOL ' before loaded volumes are accepted by $ZSVR. The tape drive type emulated by BackBox changed in the product life: - versions before V2.06 emulated 3490 drives - versions at/after V2.06 emulate LTO3 drives Unload %s from drive %s.
Messages Number 3262 Text The bar-coded label is missing in library for element %s. Medium ignored Explanation Bar-code is not seen by the library changer. Action Verify printed barcodes and bar-code reader of physical libraries. For virtual libraries, Generate 3263 Maximum supported number of slots %ld exceeded by library %s. Extra volumes ignored. A library inventory query returns more than 65535 slots. Contact the Product Support. 3264 New location %s for volume %s in library %s.
Messages Number 3269 3270 3271 3272 Text Explanation Cannot execute this update on data store %s when a catalog export/import is running. Process %s was started on %s, %s volumes processed The configuration of “domain access” and “active data store” cannot be updated while an export or import catalog batch process is running. Wait for the end of process. Cannot delete the data store %s when a catalog export/import is running. Process %s.
Messages Number Text Explanation 3276 %s is invalid as report specification for catalog import processes of data store %s The process cannot start because its report specification is not configured correctly. Revise the “Import report location” in the configuration for Catalog Sync of the data store 3277 MountId: %s. AUTOSCRATCH rejected because the 1st tapefile in volume %s is not expired A volume to load for output on a BackPak drive is not expired in DSM/TC or TMF.
Messages Number 3287 Text Invalid %s parameters. Ending quote missing for '%s'. Explanation The parameter for a BackPak TACL process is invalid. Action TACL parameters are normally generated by BackPak macro or other component. Revise the parameters of BackPak macro. Contact the Product Support. 3288 The number of %s SPI servers exceeds the maximum of 50. The number of concurrent MEDIASRV processes to label library volumes is limited. Reduce the number of drives to use for a library labeling process.
Messages Number Text Explanation Action 3293 Media move %s in library %s from %s to %s rejected %ld-%s. The move of a media in a library, such as a load or the move to an I-E slot, is rejected. Analyze the message at the end of this message. 3294 Library %s rejects the Inventory command %ld-%s. The query of the library inventory is rejected. Analyze the message at the end of this message. 3295 Media move in library %s from %s to %s is invalid %s. An illegal media move is attempted.
Messages Number 3298 3299 Text Explanation Action Volume %s is cataloged in volcat %s pool %s with media type %s, but is configured by volume group %s as type %s. Media type inconsistency might prevent loaded volumes from being accepted by $ZSVR. NonStop tape system requires the media type cataloged for volumes in DSMTC must match the tape drive type. To ensure the appropriate media type is assigned to volumes labeled by BackPak, verify the configuration of BackPak volume group.
Messages Number Text Explanation Action 3303 Labelling TMF volume %s (drive %s) rejected by TMFSRV code %d. %s The equivalent of a TMFCOM command ADD TAPEMEDIA is rejected. Analyze the TMFSRV return-code and associated text in the message. HP Reference: TMF Management Programming Manual 3304 s.%s labelled volume %s (#%ld/%ld) on %s in volume group %s. Volume is being unloaded. A library volume has just been labeled successfully by MEDIASRV or TMFSRV. None. 3305 %s process %s.
Messages Number 3307 Text Concurrent activity on library %s prevents any update of the BackPak catalog of volumes. Explanation A LABELING or other background process prevents any query of the library inventory. Action Wait for the end of background process. The volume location in BackPak catalog cannot be resync with the library inventory. 3308 Timeout labelling %s on drive %s.%s, Volume group %s. A MEDIASRV or TMFSRV process started to label a single volume did not complete after 10 minutes.
Messages Number 3312 3313 3314 Text Busy library %s did not reply to a %s message. Explanation Action The BBLM process of a library cannot reply to a request because it is already busy executing another request. On the web UI Node status page, the last known status is reported. Only %d%% of SCRATCH volumes available in volume group %s. Volume group has reached the warning level of %d%%. %ld volumes are SCRATCH out of %ld volumes in the volume group.
Messages Number 3316 Text Explanation EMS Extractor for node %s is not maintaining the operational status in OPER file. Additional status queries were executed. Status of tape drives and mount requests are normally maintained in the OPER file by the EMS Extractors, for lighter processing of web requests. Action Be sure the EMS Extractor is running correctly. Eventually restart it and check for error messages in EMS.
Messages Number Text Explanation Action 3321 Error %ld %s the export destination %s '%s'. Export of data store %s catalogs aborted. The configured destination of Catalog export is invalid Depending on the reported Guardian error code, retry or edit the export configuration 3322 Data store %s is configured with %s domain access, SECONDARY domain access is required for importing catalogs. The data store domain access does not allow Catalog import operations Change data store id or configuration.
Messages Number Text Explanation Action 3329 Volume %s received from domain=%s node=%s exportid=%s cannot be imported for local data store %s (reason) An export file cannot be processed on the secondary side. Examine the reason of error. 3330 Deletion of unreferenced volumes is not executed at end of the FULL catalog import for data store %s. Errors during the import, or the number of volumes to import (%ld) did not match the number of volumes exported (%ld) by domain=%s node=%s exportid=%s.
Messages Number Text Explanation Action 3334 Catalog type discrepancy between primary and secondary domains for data store %s. For this group, volumes to import will be cataloged in BackPak catalog only. The catalog type (NONE, DSMTC, TMF, QTOS..) of primary and secondary volume groups does not match. The volume will be imported in the list of BackPak volumes, but no action done in DSM/TC. 3335 Invalid export id %s in %s. File ignored. The export-id (a timestamp) read in an export file is invalid.
Messages Number Text Explanation Action 3341 Invalid BBEXT timer ignored (id=%d, delay=%ld). Internal error. Contact the Product Support. 3342 %s imported %s catalogs for data store %s (%s volumes processed). Report in %s A catalog import process completed. Check the named summary report. 3343 DSMTC catalog export for volume %s failed (error code %ld). DSMTC information omitted in the exported data Error during the extraction of DSMTC information about a volume.
Messages Number Text Explanation Action 3348 DSMTC catalog import. Deleting DSMTC entries for unreferenced volume %s is rejected. %s The removal of a tapevolume through MEDIASRV failed. Examine the information in this message and possible other EMS messages. 3349 Primary data store %s cannot be detached from the domain when there are catalog updates to be exported. Catalog export is pending for volume %s (%ld volumes are pending).
Messages Number Text Explanation Action Primary and secondary volume groups cannot have the same DSM/TC VOLCAT %s. DSM/TC data will not be imported for Volume group %s. This check can be disabled in the Catalog import configuration. Same DSMTC volcat between primary and secondary sites is not allowed. Change DSMTC volcat and filecat on the secondary side. 3356 Invalid or unqualified DSM/TC filecat name %s.
Messages Number 3359 Text Explanation The DSM/TC filecat %s associated to volume group %s is the default filecat in the system MEDIADEFS. This is forbidden when the data store is configured to change the node of the file name of DISKFILE entries to import in DSM/TC. The data store Catalog import configuration contains settings to change the node part in the file names of backed-up disk files. This is forbidden when the disk file names to import are cataloged in the default FILECAT.
Messages Number 3365 Text Explanation Action DSM/TC access disabled for volume group %s. Invalid filecat '%s'. %s The initial configuration validation of a catalog import detects a configuration error for a volume group associated to DSM/TC. Verify the volume group configuratioin in the domain. A DSM/TC file catalog must be associated to the volume group associated with DSM/TC and a SECONDARY data store. 3366 Function not implemented. %s %s. The software version canot execute this functionality.
Messages Number 3371 Text Erreur loading BackboxDeviceStatus reply from %s: port %d for device LUN %d target %d not known by VTC. Explanation A VTC rejects a request because it refers a port/device that is not defined by the internal VTC configuration (FCConfig.txt or VTConfig.txt). Action In the GUI, VTC configuration page, verify the domain configuration matches the internal VTC configuration. Verify SCF device configuration matches also (check WWN). Possibly fix FCConfig.txt or VTConfig.
Messages Number Text Explanation Action Domain configuration has changed. Configuration version cached in GUI session: %s, new version of %s configuration: %s. During a BackPak GUI session, the domain configuration was changed by another session in parallel. 3376 Deleting volume %s that is stuck in drive %s. BackLib: a volume is detected to be registered in BackPak as result of a failed Labeling operation; the volume is deleted from the BackPak catalog.
Messages Number 3381 3382 Text Explanation MountId: %s. Volume %s is requested outside the control of DSM/TC that is associated to its volume group %s. It should be requested through a TAPECATALOG DEFINE, not a define class of %s. Several errors can happen. A volume assumed to be cataloged in DSM/TC is requested by something different from a TAPECATALOG DEFINE. Domain license warning.
Messages Number Text Explanation 3386 Materialization [not] initiated in VTC %s on device %s. code %ld %s A materialization of virtual media is initiated, or rejected. Be sure the media is already loaded, or will be loaded before the entered timeout. 3387 Renaming old statistics file %s (reclen %ld) to %s, to recreate it with new reclen %ld.
Messages Number Text Explanation Action 3392 The status of DSM/TC tapevolume %s on node %s is %s. It must be SCRATCH or BAD to allow deletion. A BackLib labelling process finds an entry already existing in DSM/TC or TMF. Such entries are deleted to be recreated by the labelling process, only if their status is SCRATCH or BAD. This volume is not (re) labelled. 3393 Invalid Key Manager Id %s A Key manager ID is unknown in the domain configuration.
Messages Number Text Explanation Action 3400 No encryption on Volume group %s Data store %s for NonStop %s using the Key manager %s. There is no possible load of encrypted volumes for the specified Volume group. See other error messages reported by the Key manager test page. 3401 MountId: %s. Decrypting volume %s using Key manager ‘%s’ is impossible: Key manager %s not configured.
Messages Number 3405 3406 Text %ld drives without client to Key manager %s for decrypting. %ld drives not connected to an expected VLE CLIM, or non LTO4 request. Explanation Action Part of a message #3227 “No available resource to mount…”. If HP VLE devices are down, start them by SCF. Some drives cannot be used because they are not associated with any Key manager client: no VTC Client and no VLE CLIM Client. See also “Recovery of encryption related errors”.
Messages Number Text Explanation Key manager %s is not needed to encrypt new backups for any Volume group (but might still be required to decrypt old volumes that were encrypted with different Volume group configuration. A Key Manager ID is not more referred by any Volume group. 3411 Some Volume groups have no connectivity at all to the Key manager %s. Encrypted backup are impossible for some Volume groups.
Messages Number 3414 3415 3416 Text Explanation Primary volume group %s is configured for Key manager %s that is missing in the local domain configuration. Decryption of replicated volumes will be impossible until the Key manager is configured. A Key manager is missing in the local domain where a Catalog import is executing. Primary volume group %s is configured for %s Key manager %s while local volume group %s is configured for the different Key manager %s.
Messages Number 3421 3422 Text Explanation Action DSM/TC must be replicated to a dedicated catalogue. %s %s cannot be the replication target for Volume group %s %s, because it is also updated by Volume group %s. This check can be disabled in the 'Catalog Sync Import' page of the Data store configuration. The DSMCT volcat or filecat configured for a Secondary Data store or associated Volume group, is also used by another secondary Data store or by local backups (i.e. Primary Data store).
Messages Number Text Explanation Action 3425 Error %ld %s the import-export staging %s '%s' IO error occuring during access to the imporexport staging area. Fix according the Guardian error code and reported NonStop disk file name. 3426 %ld drives without client to Key manager %s for encrypting. Part of a message #3227 “No available resource to mount…”. See “Recovery of encryption related errors”.
Messages Number 3429 Text Anomaly getting tape configuration from %s: %s. %s. Explanation Error or warning when analysing the output of a NonStop utility reporting NonStop configuration. Action Case “ Host lun %ld in clim %s from climcmd lunmgr --print was not memorized from scf info clim”: A tape drive was discovered by a CLIM, but not defined as a TAPE in SCF. This might be: - left as is, - ‘fixed’ by defined a TAPE in SCF, - ‘fixed’ by reducing the number of supported virtual drives in the FCConfig.
Messages Number Text Explanation Action 3435 Volume %s label type %s was not found in the NonStop tape catalogues configured in the BackPak domain for node %s A virtualization is submitted with searching the tape catalogs, but the volume wit specified label and label type was not found Verify the tape catalogue specified in the configuration of all possible Volume groups 3436 The catalogue type of Volume group %s is %s.
Messages Number Text Explanation The status %s of volume %s in QTOS catalog %s does not allow deletion. Deletion requires the status SCRATCH, BAD or UNKNOWN. A QTOS volume is deleted in the BackPak domain, but the volume is still present QTOS and it looks to contain a non-expired backup. Verify the content of the volume in QTOS. Volume %s with labels %s and status %s is found in %s (volume group: %s), while searching labels %s and status %s.
Messages Number 3446 Text Errors or warning detected while verifying the access to storage of Data store %s. Check in Storage Admin page and in EMS. Explanation A verification of the storage availability was executed and errors were detected. The current operation, for example a creationj of tape volumes, might success anyway, but the configured resources are not fully available. For example, one of the VTCs cannot access a file server.
Messages Number 3453 Text Volume %s is requested in volume group %s linked with the QTOS catalog %s vault %s. %s. Auto-scratch not executed. Explanation A QTOS volume is requested by a mount request, and there is a mismatch between BackPak and QTOS. The auto-scratch function is not executed Action Verify the QTOS volumes are registered in Verify the QTOS volumes are registered in BackPak, eventually use the GUI “Import from Tape Catalog” .
Messages Number 3457 Text Unload %s from drive %s.%s rejected. The volume status %s does not allow unloading Explanation Incompatible actions Action After related operation completed: Verify the drive status in the BackPak GUI, Status Node page. Verify the status of the volume In the Volume List page 3458 MountId: %s.
Messages Number 3465 Text Explanation Action Operation %s on Data Store %s: volume %s skipped because it belongs to %s %s rather than the expected %s A batch job run for a WINDISK DataStore hoit a volume that does not belong to the expected Data Store or Volume Group . Create distinct directories for different Data Stores, and move the proper Windows files in the proper directory. This happens when different Data Stores point to the same disk directories.
Messages Number Text Explanation 3501 CONNECT to BBDOMAIN SERVER failure, error %1 The EMS Extractor failed to connect to the Domain Manager. Refer to the TCP/IP Programming HP NonStop manual. Socket errors. 3502 WRITE to BB_DOMAIN SERVER failure, error %1 The EMS Extractor failed to connect to send data to the Domain Manager. Refer to the TCP/IP Programming HP NonStop manual. Socket errors.
Messages Number 3512 Text Loading of %s initiated in VTController at %s for request %ld, but the request is still pending Explanation A volume load was successfully initiated, but the mount Id is still in the list of pending mounts. Action Check the log of the restore script. A restore script was initiated but did not complete successfully yet. 3513 BBEXT config error: %s There is an error in BBEXTCFG file. Refer to the BBEXT section of the Installation chapter.
Messages Number Text Explanation Action 3520 Invalid command received, length=%d, H'%s'. %s The EMS Extractor receives an invalid command. Obsolete. 3521 Mount request %ld is cancelled/rejected: automatic unload of %s. An EMS message reports the mount request is rejected by MEDIACOM, or canceled because the tape application stopped. None An automatic unload is generated to free the device, in case it is alreay loading or loaded.
Messages Number Text Explanation Action 4003 Error [rc] in #DEFINESETATTR [attrname] [value] Error returned by the TACL function #DEFINESETATTR. Refer to the HP document TACL reference. 4004 Expecting a remote MVS dataset name A parameter of the EZX_START_XFER TACL macro is invalid. Refer to the description of macro in this manual NonStop Application Interface section. 4005 DEFINE [defname] already exists The EZX_START_XFER macro cannot add the specified DEFINE name.
Messages Number 4500 Text %s: Invalid Msg Key detected Explanation A TCP/IP message between received by the library manager BBLM process is corrupted. Action Verify proper TCP/IP operations on the NonStop system(s) running BBSV and BBLM programs. Contact the Product Support. if the problem is repeated. 4501 %s: Cannot found the SCSI IOP in the list Internal error in library operations. Contact the Product Support. Verify the configuration of the library in the BackPak domain. Restart BBLM.
Messages Number 4506 Text Source Element Address %d is Empty Explanation Source of a library media move request is invalid. Action Use the BackPak web UI to ‘Get the library inventory’ that will resync the slots location stored in the BackPak inventory. Re-issue the command. 4507 The volume is still use by the tape drive. Please eject the volume first. A library changer action is rejected because the volume is still used by the NonStop host. Wait for the tape application unloads the volume.
Messages Number 4512 4513 4514 Text Explanation Action %s: File system error (%d) occurs while communicating with process %s Severe error occurred in communication with the Open SCSI device IOP (media changer). Search for EMS messages issued by the Open SCSI IOP. %s: File system error (%d) with BUFFERstatus (%d) occurs while communicating with process %s Severe error occurred in communication with the Open SCSI device IOP (library media changer).
Messages Number Text Explanation Action 4519 %s.%d is disabled Informational status reported by the library changer, and forwarded in the BackPak web UI, Library Management page, diagnostic area. Investigate at the library console – if needed. 4520 %s.%d is in abnormal state ASC (0x%02X) ASCQ (0x%02X) Error status reported by the library changer, and forwarded in the BackPak web UI, Library Management page, diagnostic area. Investigate at the library console. 4521 %s.
Messages Number 5003 Text Error loading SCSI DLL (%1) Explanation Internal error at VT Controller startup. Action Contact the Product Support. (OBSOLETE) 5004 Error creating the Virtual Tape Infrastructure Internal error at VT Controller startup. Contact the Product Support. (OBSOLETE) 5005 Error creating the Storage infrastructure Internal error at VT Controller startup. Contact the Product Support.
Messages Number Text Explanation Action 5013 Error in the root structure of the WINFILE storage (%1) The indexed Windows file for the specified virtual volume was corrupted. Contact the Product Support. 5014 Device not in use A SCSI command was received for a device that has no volume loaded. The device is ready to load a volume. 5015 Device not found for tape %1 A VT Controller received a load or an unload command for a device not defined in the VT Controller internal configuration.
Messages Number Text Explanation Action 5021 Label type (%1) not supported for %2 Internal error. Contact the Product Support. 5022 Tape %1 already in use by another device The volume is already used by another device. Try a manual load. Error getting the file size of %1 (%2) Error getting attributes of a disk file in a WINFILE DataStore. 5023 If the problem reoccurs, reset the VTC whenever possible. Contact the Product Support.
Messages Number Text Explanation Action 5028 Error setting environment variable %1 (%2) for Storage (%3) Error setting a named Windows parameter for the script execution. Check that the name and value of the parameters configured for the DataStore are syntactically valid for MS-Windows. 5029 The script [%1] has been submitted for Storage (%2) A script is stared in the VT Controller. None. 5030 The script [%1] terminated with code %2 - %3 for Storage (%4) A script has ended.
Messages Number Text Explanation Action 5036 An invalid path [%1] is still configured for (%2) Windows DataStore: the file of a virtual volume cannot be accessed because the path is invalid. The Emulator does not search in alternate locations because the path is still configured. Restore the disk path, or remove the path from the pool configuration to allow the Emulator search in other paths of the pool or execute the restore script.
Messages Number Text Explanation Action 5042 A Volume Load Operation has been cancelled for (%1) An Unload command cancels the execution of a load volume. None. 5043 Running [FetchData] operation for (%2) A pre-fetch operation is started for loading a virtual volume kept in a TSM DataStore. None 5044 Cannot %1 tape device %2 : %3 A VIRTUALIZE/MATERIALI ZE session fails on action reported at the %1 position.
Messages Number Text Explanation Action 5050 Materializing virtual volume %1 started successfully A Volume MATERIALIZE operation is successfully initiated. None. 5051 Virtualizing physical volume %1 started successfully A Volume VIRTUALIZE operation is successfully initiated. None. 5052 Virtualizing physical volume %1 ended with error A Volume VIRTUALIZE operation failed. Check the MS Windows Event log and the Guardian EMS log for previous errors.
Messages Number Text Explanation Action 5059 Device %1 BUSY while checking usage of tape %2 A volume load is rejected because a virtual tape device is busy. Retry the operation. 5060 Mismatch on MVS disk model received (%1) and model found (%1) The model of DE XP disk volume reported by the EZX MVS Agent does not match the model reported by the volume discovery executed in Win2003. Contact the Product Support.
Messages Number 5063 5064 Text Virtual Tape Device %1 DOWN Virtual Tape Device %1 REACTIVATED Explanation Action For the named virtual device, the VTC Emulator encountered an error condition that can not be recovered without restarting the virtual device. The host will send a bus reset. The tape applications using any device on the same bus will abort. The host will then try to reconnect to all devices of the bus to recover a normal state. Resubmit the tape applications.
Messages Number Text Explanation Action 5066 Unexpected old version %1 of file %2 found A pre-V1.60 Windows file was found in a Windows file DataStore. None. The VTC emulator will choose the file with the proper timestamp and delete other files 5067 Deleting duplicate or older file %1 An obsolete Windows file in a Windows file DataStore is deleted. None. 5068 Unexpected index file %1 found. Found: %2 Search for %3 An unexpected version of the index file is found (Windows DataStore).
Messages Number Text Explanation Action 5071 (%1) About to UNLOAD volume %2 on virtual device %3 An UNLOAD request has been received by the VTC. None. Message displayed only in the VTC event log. 5072 Unknown Last Update Index Path for volume %1 The VTC receives a LOAD request that does not contain the location of the Index file last time it was written. The VTC can not execute the Restore script.
Messages Number Text Explanation Action 5077 Reaching disk space unload threshold for %1 The end of volume processing is anticipated because the Disk Space Unload Threshold configured in the Data store is reached Verify the free space in the Data store 5078 There is no enough disk space to virtualize physical volume %1 The Volume VIRTUALIZE operation fails because there is not enough space to import a physical media Verify the free space in the Data store 5079 The virtual volume %1 is full Reg
Messages Number 5084 Text The VOLUME %1 was not found Explanation TSM API Data store: the container of the volume is not found in a load operation Action Load for output with autoscratch enabled: the filespace will be recreated. Load for input: - verify the Node name and FileSpace specifications has not changed in the BackPak configuration - verify the state of objects in the TSM server. Autoscratch not enabled: the volume must be deleted and re-created to be used.
Messages Number 5088 Text Device has no SCSI activity Explanation Action An attemp to load a virtual volume on an inactive VTC Device was made by the Domain controller.
Messages Number 5092 5093 5094 5095 5096 Text Explanation The maximum number of active FC ports allowed by License %1 is exhausted. Load operation for tape %2 is rejected. Limitations of the license key number have been reached. Virtual Tape Device %1 REINITIALIZE after a SCSI BUS RESET The VTC internally reinitializes all devices of the bus, possibly cancelling any current activity on the drive, because it received a BUS RESET. If NSK tape applications were aborted, resubmit.
Messages Number 5097 Text Unexpected end of data for VOLUME %1 Explanation Data of the named volume is not found, or ends unexpectedly. Action Search for previous EMS messages that might explain why data reading did not start, or stopped prematurely. Without error in the reading process, the data repository is likely to be corrupted or truncated. 5098 Starting exporting data from virtual volume %1 to physical volume %2 In an export operation, data begins to be written to the physical media.
Messages Number Text Explanation 5102 The license does not allow VIRTUALIZE/MATERIALI ZE operation to use physical tape %1 in raw access A physical drive that is not handled by a native Windows driver can be used in raw mode only if the license key contains this specific option. Contact the Product Support. 5103 Can not append to a volume created before %1 (%2). The difference of file format between BackBox versions does not allow the append operation.
Messages Number 5106 Text Explanation Volume Level Encryption not activate for Virtual Tape Device %1 A volume created under a Volume Group set using encryption through VLE-Client has been mounted on a virtual tape device not configured with the Volume Level Encryption in SCF. Configuration mismatch Action Action 1: Activate the VLE support for the specific TAPE device in SCF. Refer to the NonStop Technical documentation for the Volume Level Encryption activation.
Messages Number Text Explanation Action 5110 Starting MATERIALIZE session on tape device %1 A physical tape device reserve for Volume MATERIALIZE operation. The physical tape device will remain reserved until no media are loaded for the amount of minutes user allow when submitting the materialization reques.t Mount a media in the physical device 5111 Ending MATERIALIZE session on tape device %1 The physical device is released.
Messages Number 5114 Text Explanation Virtual Tape Device %1 cannot be used by the Volume Level Encryption A volume created under a Volume Group not configured for encryption, has been mounted on a virtual tape device configured with the Volume Level Encryption in SCF. Configuration mismatch Action Action 1: De-activate the encryption support of the Volume Group and sellect the VLE support for the specific TAPE device in SCF.
Messages Number 5118 Text Unable to impersonate user account %1: %2 Explanation Failure of an MSWindows login with the account & password configured in the Data store . Action Depending on the reported error text, - update the account/password in the Data store page of the bacpBox UI - update the Windows account definition 6000 (BBSL) %1 (%2) Error reported by the Windows software implementing the DataStore (such as TSM API, or DE-XP FAL). Refer software documentation. IBM Tivoli Messages manual.
Messages Number 6005 Text Inconsistency was found in TSM objects of volume (%1). Check the volume log file for detail. Explanation The volume just read looks invalid. At load time of a volume to be read (restore), the query of the TSM server detected a inconsistency in the list of objects for the volume. (reported as a warning) The load will not be rejected except in case the restore was request for a SECONDARY data store.
Messages Number 6008 6009 Text Incomplete Data file found: %1 Incomplete Index file found: %1 141 Explanation Action While an attempt to mount a virtual volume, the VTC found a DATA file considered incomplete. The reason is return in the message and the volume will be mounted if the reason is considered as a warning. Investigate the reason return in the message. While an attempt to mount a virtual volume, the VTC found a IND file considered incomplete.
Messages Number 6010 Text Explanation Action Unexpected TSM objects for %1 found: %2 An unexpected version of the index file is found (TSM DataStore). The unexpected volume is not used by the emulator. The reason is return in the message. This can happen after operational difficulties at time of backup, or when the BackPak catalog (NSK VOLUME file) has been restored from an old backup, and does not contain the latest timestamps, or TSM objects have not been replicated yet in the DR site TSM server.
Messages Number Text Explanation Action 6016 Volume %1 will be read from SPARE path %2 Indicate the usage of a SPARE pool path instead of a STORAGE pool path define in the Data Store configuration. Move the data to the STORAGE pool when the STORAGE pool would be available again. 6017 Volume %1 will be read from COPY path %2 Informative message None 7000 Label VOL1 is missing for storage (%1)) Internal error. Contact the Product Support.
Messages Number 8999 Text For loading the volume %s, please manually restore %s to %s (original server was %s) Explanation The ‘restore script’ Manual_Restore.cmd requests Windows files be restored by the operator Action Use the appropriate back-end software to restore the specified files (original names) to the specified location. Notice the server requesting the action might not be the original sever. The files must be restored exactly where specified. If not cancel the restore and resubmit it.
Messages Number Text Explanation Action 10100 Error parsing the Domain Address Configuration file (%1) (%2) Internal error. Contact the Product Support. 10101 Domain Address Configuration list has not been refresh due to configuration error, old Domain list remain active VTC Serviecs cannot reload the configuration file after Domain address update. Will retry. Contact the Product Support.
Messages Number Text Explanation Action 11001 Cannot %1 with VTC %2, %3 Error in BBBACKUP/BBRESTORE Check in the VTC that reported the error: .the script log. .Windows event viewer 11002 Script Error, CMD Syntax: %1 Error in parameters syntax of BBBACKUP/BBRESTORE Verify the script command 11003 Execution for %1 failed Error in BBBACKUP/BBRESTORE Check in the VTC that reported the error: .the script log. .
Messages Number Text Explanation Action 11016 Script: %1 has finished %2. %3 files were backed up; %4 files were NOT backed up, total size of backed up files= %5 Kbytes, startTime=
Messages Number 20003 Text Service cannot launch the script Explanation Action The VTC services encounter system error that prohebit the launch of the script. The script have not execute. Logon into the VTC who repport the error and analyze the reason of error in the Windows Events Log. Contact the Product Support. 20004 Service encounters a system error in script management The VTC services cannot determine the success or the failure of the script execution.
Messages Number Text Explanation Action The current block size is too short to hold a complete record of data from the physical tape volume The physical tape drive used to IMPORT a volume have a block size too small to read a data record from the physical tape volume Increase the block size associate to the physical tape drive. 20052 Configuation file contains invalid parameters The VtConfig.txt, FcConfig.txt or AdmConfig.
Messages Number Text Explanation Action 28002 EZX JOB from using volume is rejected, transfer direction is invalid Internal error. Contact the Product Support. 28003 EZX JOB from using volume is rejected, error allocating dsn () : Error in dynamic allocation of the MVS dataset. See possible other system error messages for the DSN being allocated in the BCOM MVS job log.
Messages Number Text Explanation Action 28008 Dataset unlocked successfully for DSN from using volume The end-of-transfer unlock is successful. None. 28009 Job domain , lock the dataset again A second successive lock comes for the same dataset and is accepted by the EZX MVS Agent. None. 28010 JOB from successfully created/queried - The Domain Manager prepared the dataset(s) to be involved in an EZX transfer. None.
