************************************************* ECO SUMMARY INFORMATION ************************************************* Release Date: Sept 20, 2006 Kit Name: SLS_VAXVMS_J029_E02_SERVER Kit Applies To: OpenVMS VAX V7.3 Approximate Uncompressed Kit Size: 70704 Blocks System Reboot Necessary: No Superseded Kits: SLS_VAXVMS_J029_E01_SERVER Checksum of Compressed Kit: 3288594027 Mandatory Kit Dependencies: None Optional Kit Dependencies: None Storage_Library_System_for_OpenVMS__________________ Release Notes Revision/Update Information: Software Version: Storage Library System for OpenVMS Version 2.9J-ECO02 Optional Software Version: DCSC for OpenVMS Version 3.2A ________________________________________________________________ September 2006 © Hewlett-Packard Development Company, L.P. 2006 The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Proprietary 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. DECconnect, HSZ, StorageWorks, VMS, and OpenVMS are trademarks of Hewlett- Packard Development Company. FTP Software is a trademark of FTP SOFTWARE, INC. PostScript is a registered trademark of Adobe Systems, Inc. RDF is a trademark of Computer Associates (CA). StorageTek is a registered trademark of Storage Technology Corporation. All other trademarks and registered trademarks are the property of their respective holders. Printed in the US _________________________________________________________________ Contents Preface................................................... v 1 Important Information About SLS 1.1 SLS New Features/Enhancements.................... 1-1 1.2 Installation Instructions for SLS Version 2.9J-ECO02....................................... 1-1 1.2.1 SLS V2.9J-ECO02 Saveset Information ........... 1-2 1.2.2 Rebooting Alpha and VAX Systems using RDF ..... 1-2 1.2.3 OpenVMS Version Specific Files for VAX Systems........................................ 1-2 2 Corrected Problems 2.1 Use of SLS$SYSTEM logical in STARTUP.COM even before the logical gets defined in LOADER.COM.... 2-1 3 Known Problems and Restrictions 3.1 Backup Fails when Executed on a Node that does not have a Directly Connected Media Robot........ 3-1 3.2 Remote Device Facility(RDF) Issues............... 3-2 3.3 STORAGE INVENTORY ACS/ADD Issue.................. 3-2 3.4 Save/Restore Operation may Fail while Using Multi-Volumes Sets............................... 3-2 3.5 Mixed Use of DECnet with DECnet-Plus in VMScluster....................................... 3-3 3.6 STORAGE ALLOCATE Operation may Fail with BADMTYPE......................................... 3-3 3.7 OpenVMS Version Restrictions..................... 3-3 3.8 SLS Version Restriction.......................... 3-4 3.9 DECnet-Plus Long Node Name Length Restriction.... 3-4 3.10 FILES-11 ODS-5 Filename Size Restriction......... 3-4 iii 3.11 Fatal Drive Error During a Restore Operation..... 3-4 3.12 Same Backup Operation On Same Day................ 3-4 3.13 Lost History Files............................... 3-5 3.14 Transferring Existing OpenVMS BACKUP Files....... 3-5 3.15 Do Not Set the Volume Length to Zero When Adding Volumes.......................................... 3-5 3.16 Drive Name Restrictions.......................... 3-5 3.17 STORAGE LOAD Command............................. 3-9 3.18 STORAGE SELECT Command........................... 3-9 3.19 Removing a Drive From ALLDEV..................... 3-9 3.20 STORAGE EXPORT CARTRIDGE Command................. 3-9 3.21 STORAGE IMPORT CARTRIDGE Command................. 3-10 3.22 FMS License Not Loaded........................... 3-10 3.23 Running Unattended Backup Operations............. 3-10 3.24 Full Volume Indicates WRONGDRIVE Error........... 3-10 3.25 Restore Operation Fails.......................... 3-10 3.26 SLS$SEARCH_HISTORY Routine Causes Error.......... 3-11 3.27 SBK Symbols may not be Available for PRE and POST Processing....................................... 3-11 4 Documentation Updates 4.1 References to OpenVMS V5.5-2 will be Removed..... 4-1 Tables 3-1 First Backup Operation ........................ 3-12 3-2 Second Backup Operation ....................... 3-13 iv _________________________________________________________________ Preface This document contains the following information: o SLS new features o Installation information o Corrected problems o Known problems and restrictions o Documentation Updates Intended Audience This manual is intended for OpenVMS system managers and should be used with the System Management Subkit of the OpenVMS documentation set. Conventions The following conventions are used in this guide: ___________________________________________________________ Convention__Description____________________________________ { } In format command descriptions, braces indicate required elements. You must include one of the elements. [ ] Square brackets show optional elements in command syntax. You can omit these elements if you wish to use the default response. v ___________________________________________________________ Convention__Description____________________________________ . . . Horizontal ellipsis points indicate the omission of information from a sentence or paragraph that is not important to the topic being discussed. Vertical ellipsis points indicate the omission . of information from an example or command . format. The information has been omitted . because it is not important to the topic being discussed. boldface Boldface type in text indicates the first type instance of terms defined in the Glossary or in text. italic Italic type emphasizes important information, type indicates variables, indicates complete titles of manuals, and indicates parameters for system information. Starting This type font denotes system response, user test . . . input, and examples. Ctrl/x Hold down the key labeled Ctrl (Control) and the specified key simultaneously (such as Ctrl /Z). PF1 x The key sequence PF1 x indicates that you press and release the PF1 key, and then you press and release another key (indicated here by x). n A lowercase italic n indicates the generic use of a number. For example, 19nn indicates a four-digit number in which the last two digits are unknown. x A lowercase italic x indicates the generic use of a letter. For example, xxx indicates any ____________combination_of_three_alphabetic_characters.____ Related Products The following related products are mentioned in this document: vi ___________________________________________________________ Product_______Description__________________________________ ABS ABS refers to HP Archive/Backup System for OpenVMS software. ABS OMT ABS OMT refers to HP Archive/Backup System for OpenVMS Management Tools software. HSM HSM refers to HP Hierarchical Storage Management for OpenVMS software. MDMS MDMS refers to HP Media Device and Management Services for OpenVMS software. OpenVMS Refers to the OpenVMS operating system. SLS SLS refers to HP Storage Library System for ______________OpenVMS_software.____________________________ vii 1 _________________________________________________________________ Important Information About SLS This release note contains information for Storage Library System on OpenVMS (SLS) Version 2.9J-ECO02. It highlights RDF qualification and a minor software problem corrected since the previous release of SLS (SLS V2.9J-ECO01). 1.1 SLS New Features/Enhancements The SLS Version 2.9J-ECO02 software provides the following new feature/enhancement: o Remote Device Facility (RDF) V4.3I is qualified to be used by SLS on OpenVMS Alpha V8.3. Use of RDF V4.3I by SLS on OpenVMS VAX V7.3 and OpenVMS Alpha V7.3, V7.3-1, V7.3-2, and V8.2 continues. 1.2 Installation Instructions for SLS Version 2.9J-ECO02 The SLS Version 2.9J-ECO02 installation kit contains SLS files for OpenVMS VAX V7.3, and OpenVMS Alpha V7.3, V7.3- 1, V7.3-2, V8.2, and V8.3. See Section 3.7 for the note on upgrading to a later version of OpenVMS after you have installed or upgraded SLS. To install SLS Version 2.9J-ECO02 software on your system, use the following commands: o Server Software $ @SYS$UPDATE:VMSINSTAL SLSE02J029 o Client Software $ @SYS$UPDATE:VMSINSTAL SLSCLIENTE02J029 Important Information About SLS 1-1 Important Information About SLS 1.2 Installation Instructions for SLS Version 2.9J-ECO02 1.2.1 SLS V2.9J-ECO02 Saveset Information SLS V2.9J-ECO02 kit contains the following savesets: o On OpenVMS VAX: o SLSE02J029.A - Common files and Release note o SLSE02J029.B - OpenVMS VAX executables o SLSE02J029.C - RDF kit for OpenVMS VAX o SLSCLIENTE02J029.A - Common files and Release note o SLSCLIENTE02J029.B - OpenVMS VAX executables o SLSCLIENTE02J029.C - RDF kit for OpenVMS VAX o On OpenVMS Alpha: o SLSE02J029.A - Common files and Release note o SLSE02J029.D - OpenVMS Alpha executables o SLSE02J029.E - RDF kit for OpenVMS Alpha o SLSCLIENTE02J029.A - Common files and Release note o SLSCLIENTE02J029.D - OpenVMS Alpha executables o SLSCLIENTE02J029.E - RDF kit for OpenVMS Alpha For additional installation information, see HP Storage Library System for OpenVMS Installation and Configuration Guide. 1.2.2 Rebooting Alpha and VAX Systems using RDF SLS engineering recommends that on installing RDF, you reboot both VAX and Alpha systems to use the new RDF driver image. 1.2.3 OpenVMS Version Specific Files for VAX Systems SLS Version 2.9J-ECO02 operates on VAX systems running OpenVMS version, V7.3 and on Alpha systems running OpenVMS versions, V7.3, V7.3-1, V7.3-2, V8.2 and V8.3. SLS uses OpenVMS version-dependent files according to the OpenVMS version in use on your VAX system. When SLS is installed, the installation procedure checks for the OpenVMS version on the VAX system and creates the version-dependent files for subsequent use. 1-2 Important Information About SLS Important Information About SLS 1.2 Installation Instructions for SLS Version 2.9J-ECO02 The version-dependent files are: o SLS$SYSTEM:BACKUPCMD-Vnn.CLD o SLS$SYSTEM:VMSBUXX-Vnn.EXE for OpenVMS Versions prior to V6.2 o SYS$MESSAGE:SLS$BACKUPMSG-Vnn.EXE for OpenVMS Versions prior to V6.2 Where: nn represents the two digits of the version number. ________________________ Note ________________________ Version-specific processing does not occur for Alpha systems. ______________________________________________________ Important Information About SLS 1-3 2 _________________________________________________________________ Corrected Problems The following problem has been corrected in SLS Version 2.9J-ECO02: 2.1 Use of SLS$SYSTEM logical in STARTUP.COM even before the logical gets defined in LOADER.COM Problem: The following error can occur when SLS is shutdown and restarted: %SLS-I-STARTUP, Starting SLS >> %DCL-I-SUPERSEDE, previous value of SLS$ROOT has been superseded >> %DCL-E-OPENIN, error opening SLS$SYSTEM:[cur def >> dir]SLS$BUILD_USSSHR.COM; as input -RMS-F-DEV, error in device name >> or inappropriate device type for operation %DCL-W-IVVERB, >> unrecognized command verb - check validity and spelling \SETUSR\ This problem is specific to SLS29J-ECO01 and occurs due to the following reason: The SLS$SYSTEM logical is deassigned when SLS is shutdown. So, when SLS is restarted, the SLS$SYSTEM logical must get defined automatically. But, even before the logical gets defined, SLS tries to use it to execute the SLS$BUILD_USSSHR.COM for building the SLS$USSSHR.EXE. Solution: The problem is fixed in this release. Corrected Problems 2-1 3 _________________________________________________________________ Known Problems and Restrictions The following sections describe the known problems and restrictions that exist in SLS Version 2.9J-ECO02: 3.1 Backup Fails when Executed on a Node that does not have a Directly Connected Media Robot In a typical TMSCP served split-rail cluster configuration, backup executed from a node that does not have a directly connected (local) media robot aborts displaying the "SLS- F-MRD_LOAD_FAIL" error message. This scenario is explained using the following example: Example: Assuming that Node A and Node B are in a cluster and access the same media library called "Test" that is split-rail configured. The media library "Test" has two drives called "Drive A" and "Drive B" and a media robot called "Robo G". Drive A" and "Robo G" are connected to Node A and only "Drive B" is connected to Node B. Both the drives are visible to both the nodes using TMSCP but the media robot is only visible to Node A. Hence, When a backup is executed on Node B, it fails with the "SLS-F- MRD_LOAD_FAIL" error message as "Robo G" is not visible to Node B for processing the media robot related requests. Work-around: Disable TMSCP and let the drives be accessed locally or remotely using RDF. Known Problems and Restrictions 3-1 Known Problems and Restrictions 3.2 Remote Device Facility(RDF) Issues 3.2 Remote Device Facility(RDF) Issues Modification of RDF tuning parameter (system logical name RDEV_WRITE_ GROUP_SIZE) as described in Chapter 7 of the MDMS Operations Guide may cause SLS to hang during save operations to a remote tape drive. The SLS subprocess performing the save operation hangs in an LEF state waiting i/o completion to/from the RDEV pseudo-device. This problem only occurs when the BLOCK_ SIZE specified for the save /restore operation is set to a high value in combination with decreasing the RDEV_WRITE_GROUP_SIZE system logical name. The hang appears to occur only when RDEV_WRITE_GROUP_ SIZE is approximately 1350 times smaller than the specified block size. 3.3 STORAGE INVENTORY ACS/ADD Issue The command $STORAGE INVENTORY ACS/ADD adds volume records to the database as expected, but it sets the volume Status Flag field to "DOWN" indicated the volume(s) are unavailable for use. Solution: This is an intended behavior dating back to the original implementation for DCSC-controlled ACS libraries. 3.4 Save/Restore Operation may Fail while Using Multi-Volumes Sets An SLS system save or restore operation using the VMS BACKUP engine may fail while attempting to load the continuation volume of a multi-volume volume set. This problem only applies for the Tx8nn DLT, TLZnL and 4mm DAT magazine loaders connected by dual-redundant HSJxx controllers. The following symptoms may occur: - Error message %SLS-F-MRD_UNLOAD_FAIL and SYSBAK terminates. - One or more entries in the system hardware error log file. 3-2 Known Problems and Restrictions Known Problems and Restrictions 3.4 Save/Restore Operation may Fail while Using Multi-Volumes Sets - Device and/or controller timeout resulting in HSJ controllers setting the device to "misconfigured and unavailable" as shown by the HSJ command SHOW Unit command (of the tape device). Comprehensive testing has isolated a problem in dual- redundant HSJ40 configurations when dual-pathing the loader device. As a workaround for that problem, ensure the loader device name is set to PREFERRED_PATH. A side-effect of the problem causes a tape drive to be set "misconfigured" as shown by the HSJ's SHOW command. Use the command: HSJ> CLEAR UNKNOWN container-device 3.5 Mixed Use of DECnet with DECnet-Plus in VMScluster The MDMS active/standby server process functionality is not supported in a VMScluster mixing some nodes running DECnet with other nodes running DECnet-Plus. 3.6 STORAGE ALLOCATE Operation may Fail with BADMTYPE The Storage Add Volume command allows creation of volumes with a media type that has not been defined in tapestart.com. Use of these volumes with the storage allocate command fails with: %sls-e-badmtype specified Workaround: Use media types that are defined in TAPESTART.COM 3.7 OpenVMS Version Restrictions SLS Version 2.9J-ECO02 is compatible with OpenVMS VAX V7.3 and OpenVMS Alpha V7.3, V7.3-1, V7.3-2, V8.2, and V8.3. ________________________ Note ________________________ If you upgrade your version of OpenVMS after installing or upgrading to SLS Version 2.9C, 2.9D, 2.9F, 2.9G, 2.9J, 2.9J-ECO01, or 2.9J-ECO02, you Known Problems and Restrictions 3-3 Known Problems and Restrictions 3.7 OpenVMS Version Restrictions should bypass OpenVMS V7.0 and directly upgrade to OpenVMS V7.3 before using SLS. ______________________________________________________ 3.8 SLS Version Restriction All nodes in the SLS configuration must be running the same version or higher. SLS Engineering recommends the customer be running version SLS 2.9J-ECO02. 3.9 DECnet-Plus Long Node Name Length Restriction SLS V2.9X does not support long node names. The node name length is restricted to six (6) characters. 3.10 FILES-11 ODS-5 Filename Size Restriction SLS Version 2.9J-ECO02 does not support files on ODS-5 volumes. 3.11 Fatal Drive Error During a Restore Operation Restriction: SLS splits a volume set when a fatal drive error occurs for a restore operation. Work-around: Upgrade to HP Archive/Backup System for OpenVMS (ABS) to solve this problem. The SLS SYSBAK process does not know whether it is saving or restoring data when the fatal drive error is encountered. The error handling assumes it is saving data. This will not be corrected for SLS. ABS is designed to handle this situation. 3.12 Same Backup Operation On Same Day If you submit a backup operation on NODE1 and then submit the same backup operation from NODE2 in the same cluster on the same day, SLS does not tell you the backup operation already has been done. 3-4 Known Problems and Restrictions Known Problems and Restrictions 3.13 Lost History Files 3.13 Lost History Files In the following situation, SLS is unable to restore files because of lost history entries: 1. You identify a volume for SLS to use that is a non-SLS volume that already contains save sets. 2. On the User Save screen, you enter a volume that is in the SLS volume database and is available for use. 3. On the same screen, you enter N for the /INIT qualifier value. 4. When you see an OPCOM message that indicates different volume label values are detected, you respond with CONTINUE. 3.14 Transferring Existing OpenVMS BACKUP Files If you try to transfer existing OpenVMS BACKUP files to SLS history files using SYSOLDTAPE.COM, you must specify an input parameter that contains a device name. For example, if you try to use SYSOLDTAPE with SLS user backup history files, SYSOLDTAPE will not translate the logical name in the VMS BACKUP command for the user backup and fails. 3.15 Do Not Set the Volume Length to Zero When Adding Volumes When using the ADD VOLUME or ADD VOLUME SERIES screens on the Maintenance Menu, if the volume has no length, make sure the LENGTH field is not zero (0). If you allow a zero (0) in this field, the volume may never be selected for allocation. 3.16 Drive Name Restrictions Performing a STORAGE SELECT command that involves a drive list containing a remote RDF characteristics value that map to many different drives caused the RQ process to stall. Because SLS restricts the length of a drive list to a maximum size of 256 characters. the stall was caused when an expanded drive list (see the following discussion) overflowed temporary storage and corrupted the stack. This portion of the problem has been fixed. However, the size restriction on the drive list still exists. Known Problems and Restrictions 3-5 Known Problems and Restrictions 3.16 Drive Name Restrictions Drive_List_Size_Restriction: To correct the overflow problem, it is necessary for SLS to truncate the drive list. A drive list cannot exceed 256 characters. If SLS must truncate a drive list, a DRIVELISTTRUNC message is displayed as an OPCOM message. As a result, the drives truncated from the drive list are never selected. The following discussion explains how SLS handles drive lists and describes the ways that a drive list can become too large: 1. Local RDF characteristic name-At RQ startup time, the drive list defined in a media triplet in the file TAPESTART.COM is evaluated and expanded if an RDF characteristic name references the local node. For example, the following media triplet is defined for NODEA: $ MTYPE_24 := TK70K $ DENS_24 := $ DRIVES_24:= NODEB::$3$MIA1:,3480,NODEB::$3$MIA1: In this example, the 3480 element does not include a node name, thus indicating that this is a local logical name or RDF characteristic name. If a drive is local, the translation of the RDF characteristic name is done locally at startup time to create a full, expanded drive list. The drive list in the media triplet contains 36 characters. The following devices are defined in the CONFIG_ NODEA.DAT file: device $1$RMT0: RMT0 device $2$MUA0: MUA0 device $2$MUA1: MUA1 device $2$MUA2: 3480 device $2$MUA3: 3480 device $2$MUA4: 3480 When SLS detects that the 3480 is an RDF characteristic name, it substitutes that name (3480) with the list of drives that match the name. In this example, the new drive list for MTYPE_24 becomes: NODEB::$3$MIA1:,$2$MUA2:,$2$MUA3:,$2$MUA4:,NODEB::$3$MIA1: 3-6 Known Problems and Restrictions Known Problems and Restrictions 3.16 Drive Name Restrictions Result: The drive list has increased to 58 characters. With the correction of the overflow problem, an expanded drive list that exceeds the 256 byte limit is truncated. Any drives that are truncated from the drive list are never selected, even though they were specified in the media triplet. Solution: Calculate the expanded drive list at RQ startup time based up on the previous example. Adjust as necessary (local RDF characteristic name use only). Make sure that any expanded drive list does not exceed the 256 character limit (including commas). If the RDF characteristic name in the previous example had been NODEB::3480 (not local), SLS would not expand the drive list at RQ startup time. 2. Remote RDF characteristic name-When a STORAGE SELECT command is performed on a drive list that contains a remote reference to an RDF characteristic name, the results of the expansion process may be more severe. For example, the following media triplet is defined for NODEA: $ MTYPE_24 := TK70K $ DENS_24 := $ DRIVES_24:= NODEB::$3$MIA1:,NODEB::3480,NODEB::$3$MIA1: The following devices are defined in the CONFIG_ NODEB.DAT file: device $1$RMT0: RMT0 device $2$MUA0: MUA0 device $2$MUA1: MUA1 device $2$MUA2: 3480 device $2$MUA3: 3480 device $2$MUA4: 3480 The following example selects a drive from NODEA: $ STORAGE SELECT DRV /MEDIA=TK70K Known Problems and Restrictions 3-7 Known Problems and Restrictions 3.16 Drive Name Restrictions SLS rotates the drive selection, but eventually selects the NODEB::3480 drive. When the NODEB::3480 drive is selected, the RQ process on NODEB expands the 3480 RDF characteristic name (described in Item 1.). The drive list returned to NODEA is: $2$MUA2:,$2$MUA3:,$2$MUA4: Note: Because SLS is only dealing with the NODEB::3480 drive name, no other drives from the drive list are included. Because a remote select is being performed, the RQ process on NODEA performs an additional expansion of the drive list and appends the node name to each drive specified in the list: NODEB::$2$MUA2:,NODEB::$2$MUA3:,NODEB::$2$MUA4: Notice that the size of the drive list has almost doubled. It is easy to see how quickly 256 characters can be exceeded. As described in Item 1., if the drive list exceeds 256 characters, the drive list is truncated causing some drives never to be selected. Solution: Calculate the expanded drive list for each RDF characteristic name that maps to multiple drives. Based on the example shown here, adjust as necessary to make sure that any expanded drive list does not exceed the 256 character limit (including commas). ___________________ Recommendation ___________________ For drives that are directly connected to the local system, include either the allocation class or the local node name prefix in the drive name specification. This ensures that enough space is allowed for the drive list and it will not be truncated. Perform the necessary calculations (previously described) and make sure that any internally- generated, expanded drive lists do not exceed the 256 character limit. Adjustments may have to be made in the CONFIG_node.DAT file and possibly in the file TAPESTART.COM to get an adequate configuration. 3-8 Known Problems and Restrictions Known Problems and Restrictions 3.16 Drive Name Restrictions Even though the stall problem is corrected, these adjustments are still necessary to prevent truncation. ______________________________________________________ 3.17 STORAGE LOAD Command On Alpha systems, if you use any SCSI devices (for example, TZ867 or TLZ06) to load tapes using the STORAGE LOAD command, you must initialize these tapes and provide them with a label before using them. Otherwise, the STORAGE LOAD command fails with a "%SYSTEM-F-DRVERR, fatal drive error." 3.18 STORAGE SELECT Command When you submit a STORAGE SELECT command for a drive that has been removed from the ALLDEV list using the STORAGE REMOVE DRIVE command, and you later add the drive back into the ALLDEV list, the drive may not be found. Also, a continuous stream of OPCOM requests may be displayed. 3.19 Removing a Drive From ALLDEV When you remove the drive from the ALLDEV list, SLS records the state of the drive and cannot use the drive until the state is changed. If you respond too rapidly to OPCOM messages after the STORAGE ADD DRIVE command is submitted but before SLS has updated the drive's state, the STORAGE ADD DRIVE command appears ineffective. To avoid this problem, wait to see the drive retained message before you reply to the OPCOM message with the previously unavailable drive or add the drive back into the ALLDEV list before starting the backup operation. 3.20 STORAGE EXPORT CARTRIDGE Command If you issue a STORAGE EXPORT CARTRIDGE command to a TL820 and the cartridge is not in the slot, but the SLS volume database says the cartridge is in the slot, the RQ process may terminate with an ACCVIO. This means the volume database is not synchronized with physical reality. This often means someone moved the cartridge through some means outside of SLS control. Known Problems and Restrictions 3-9 Known Problems and Restrictions 3.21 STORAGE IMPORT CARTRIDGE Command 3.21 STORAGE IMPORT CARTRIDGE Command If you issue a STORAGE IMPORT CARTRIDGE command to a TL820 and supply a volume name, the volume name must match the physical label on the volume. If the physical label (bar code) does not match the name specified in the command, the cartridge may not be ejected; the cartridge needs to be physically removed from the robot. In this instance, SLS does not update the volume database. 3.22 FMS License Not Loaded When there is no FMS license loaded and OPCOM LICENSE checking is enabled, security alarms are generated when any menu is invoked. These alarms have no impact on SLS /MDMS operations and they should be ignored. 3.23 Running Unattended Backup Operations When using SLS with magazines and running unattended backup operations, make sure the magazine database and volumes in the magazine are consistent. Otherwise, if SLS is expecting a specific volume label and finds another one during the unattended operation, SLS overwrites the label. 3.24 Full Volume Indicates WRONGDRIVE Error In cases where an SLS backup operation begins on a volume that has been used already and has very little space left, SLS may signal a WRONGDRIVE error and abort the backup operation. This is a protection mechanism to keep the history files from becoming corrupt. The backup should be restarted, preferably beginning with a different volume. 3.25 Restore Operation Fails When using the Restore screen, if you leave the Volume ID field blank and submit the restore operation for execution, the restore operation fails with one of the following messages: %DCL-W-INSFPRM, missing command parameters %SYSTEM-F_IVDEVNAM, invalid device name Work-around: 3-10 Known Problems and Restrictions Known Problems and Restrictions 3.25 Restore Operation Fails To correct this problem, be sure that either the Volume ID field contains a value before you submit the restore request or use the STORAGE RESTORE command. The Restore screen requires an entry in the Volume ID field. Unfortunately, the design of the form allows you to terminate the form (to submit the Restore request) before entering the Volume ID field. This allows the Volume ID field to remain blank. Although the Volume ID field has a "Response Required" attribute, the attribute is validated only when the field is terminated and not when the entire form is terminated from some other location. 3.26 SLS$SEARCH_HISTORY Routine Causes Error When using the SLS$SEARCH_HISTORY routine, a file specification that contains a node name or a device name may generate an error. For example, a specification of *::*:[*...]*.*;* or *:[*...]*.*;* generates the following error: %RMS-F-SYN, file specification syntax error 3.27 SBK Symbols may not be Available for PRE and POST Processing Although it is documented that certain SBK symbols are available to the PRE and POST processing routines, this is not always true. Use of these symbols can cause the following error message to display: DCL-W-UNDSYM Note: SYSBAK uses a combination of local and global symbols. Example: The first backup operation of the day for a given .SBK file was performed on a specific directory, was a selective backup operation (not a full backup operation), and produced the results shown in Table 3-1. Known Problems and Restrictions 3-11 Known Problems and Restrictions 3.27 SBK Symbols may not be Available for PRE and POST Processing Table_3-1__First_Backup_Operation__________________________ POST Symbol______________PRE/First___PRE/Each____POST/Each___/Last DISK local DISK global FILES local C[1] C C FILES global NODE local C C C C NODE global FIRST local FIRST global HISTORY local C C HISTORY global LAST local LAST global LISTING local C C LISTING global N_REELS local C N_REELS global P1 C C C C P2 blank C C blank P3 blank C C blank SAVESET local C C SAVESET global STARTED local C STARTED global STATUS local C STATUS global STOPPED local C [1]C_indicates_that_the_symbol_is_defined_correctly._______ (continued on next page) 3-12 Known Problems and Restrictions Known Problems and Restrictions 3.27 SBK Symbols may not be Available for PRE and POST Processing Table_3-1_(Cont.)__First_Backup_Operation__________________ POST Symbol______________PRE/First___PRE/Each____POST/Each___/Last STOPPED global SUMFN local SUMFN global SBK_Symbols_________C___________C___________C___________C__ The second backup operation of the day for the same .SBK file was performed on a specific directory, was a selective backup operation (not a full backup operation), and produced the results shown in Table 3-2. Note: The results of this test were determined by editing the summary file from the first backup and placing bogus data in for each of the symbols. Table 3-2 shows which symbol assignments are for the second backup operation and which symbol assignments are from the first backup operation. Table_3-2__Second_Backup_Operation_________________________ Symbol________________PRE/First___PRE/Each____POST/Each___POST/Last DISK local X[2] X X DISK global X X X FILES local C C C FILES global X X X NODE local C[1] C C C NODE global X X X FIRST local X X X FIRST global X X X [1]C_indicates_that_the_symbol_is_defined_correctly._______ [2]X indicates that the symbol is defined but the definition is incorrect. The symbols value is from the first backup operation of the .SBK file. (continued on next page) Known Problems and Restrictions 3-13 Known Problems and Restrictions 3.27 SBK Symbols may not be Available for PRE and POST Processing Table_3-2_(Cont.)__Second_Backup_Operation_________________ Symbol________________PRE/First___PRE/Each____POST/Each___POST/Last HISTORY local C C X HISTORY global X X X LAST local X X X LAST global X X X LISTING local C C X LISTING global X X X N_REELS local X C X N_REELS global X X X P1 C C C C P2 blank C C blank P3 blank C C blank SAVESET local C C X SAVESET global X X X STARTED local X C X STARTED global X X X STATUS local X C X STATUS global X X X STOPPED local X C X STOPPED global X X X SUMFN local X X X SUMFN global X X X SBK_Symbols___________C___________C___________C___________C 3-14 Known Problems and Restrictions 4 _________________________________________________________________ Documentation Updates The following section describes the documentation changes that will be updated in the respective guides when the engineering team plans for a major release: 4.1 References to OpenVMS V5.5-2 will be Removed References to OpenVMS V5.5-2 will be removed as this version is no longer supported by SLS. o Guide to be updated: SLS Installation Guide o Sections to be updated: o Section 4.4 - Configuring SLS to work with Specific VMS Versions o Section 4.4.1 - Version-Specific Files Documentation Updates 4-1