Virtual TapeServer 6.04.02 for NonStop Servers Release Notes

Known Issues | 12
cartridges will result. This could cause other pools to disappear, cartridges to display
incorrectly or not appear. (TL-1039)
WORKAROUND: Review cartridges restored in this manner when there might be
conflicts with existing cartridges. You can rename the cartridges from the command line
(log in as the bill user) or delete duplicate cartridges.
 Using the Import/Export interface results in an error in encr_key.log. Invoking
an import or export results in the “Error: missing device specification!” error in
encr_key.log. This appears when a pool, a single encrypted tape, or single non-encrypted
tape is selected. The message is benign and can safely be ignored. (TL-1035)
 Cartridges created in a batch show the same creation time in the event log. (TL-
996)
 Files may accumulate in /var/spool/clientmqueue, possibly filling up the file
system. Mail generated on the local system is stored in /var/spool/clientmqueue until
sendmail or other mail transfer agent picks it up for delivery. The current configuration
runs logwatch every day, which generates email output for delivery to root. Any crontab
errors will generate additional mail that will accumulate in the queue directory. (TL-865,
EAR 3395)
WORKAROUND: Monitor this directory and delete unneeded files from time to time.
 Virtual tape names must be unique. If virtual tape names are not unique, unexpected
results can occur in the VTS interface. For example, an error message might be displayed
after attempting to mount one of the tapes whose name is not unique. (TL-199, TL-219)
 Request to mount cartridge fails if a currently mounted cartridge is unmounted
by another process while VTS is processing the mount request. If a request is
issued to mount a cartridge in a virtual tape drive where another cartridge is mounted,
the request is ignored if the mounted cartridge is unmounted while VTS is processing the
mount request. (TL-368)
WORKAROUND: Attempt to mount the cartridge again.
 To disable ISC, two parameters must be set. The
ems_InterSystemCommunication_hosts and interSystemCommunication_enable
parameters must be set to indicate that ISC should be disabled. Otherwise, ISC will still
be enabled. (TL-240)
WORKAROUND: To disable ISC, set these parameters in the VTS configuration file:
interSystemCommunication_enable="NO"
ems_InterSystemCommunication_hosts=""
Then, stop ISC from the Supervisor Functions page.
 No activity or a “hung” command occurs when an import request is issued to a
physical drive that is unavailable. If a physical drive is unavailable (powered off,
cable disconnected, and so on), VTS does not properly handle the error and a timeout does
not occur, causing VTS to hang and require a reboot. (TL-61)