• When mounting the wrong VSN for a catalog, the
labelled tape mount request does not post error message to (re)mount. (509299)
the job.output:
Expected VSN and the observed VSN read from the input volume do not match.
This error condition has no override option.
• Delete tape dataset ALWAYS prompts for catalog DSN deletion when deleting from the Area or Line level, even if the dataset is a non-catalog dataset. (513058)
• Writing to an external VSN but mounting an internal (catalog) SL tape may result in a tape overwrite. (508654) This could happen if an attempt is made to write to an external VSN list and the wrong labeled tape is mounted. This tape happens to be a library tape and it was
overwritten when the operator chose to override the error. Upon review of the code, this is possible ONLY if: 1) The bypass label processing switch is set.
2) The bypass vsn processing switch is set.
3) And the PROMAX_TOPCAT_HOME environment variable is not set or is set incorrectly.
work-around: The possibility of this happening may be
avoided by setting the configuration flag: AEEJ
• Modifying TopCat attribute MPOOLNAM does not add additional volumes to the media pool. (510442)
• Java.config from Solaris REMHOME install has incorrect port (SOLARIS). (513309)
When running a remote tape job to a Solaris machine, the user gets the following error message:
RUNTIME NOTE: FAILED SOCKET RECIEVE ON HOST:[sparky. TapeNotificationClient: Exception = Connection refused to host: [cruiser:1111];
nested exception is:
java.net.ConnectException: Connection refused
work-around: The $REMHOME/etc/java.config uses a port of 1111
for Opcon, this should be 1099 by default.
• Convert_device.txt2tts script is setting REMHOME improperly. When converting an existing device.txt that has and ’fclient.exe’ stanza to be converted to a
REMHOME path. You will want to delete this from your new device.tts. The REMHOME setting is similar to a PROMAX_HOME setting which does not include a sys/exe’ in the path. (513332)
• Config_file explanation for device.tts line is unclear. When editing the ’device file’ stanza in the
PROMAX_HOME/etc/config_file, either your HOME directory or PROMAX_HOME/etc will be prepended to your device file name. Typing an explicit path will not work. (513331)
• DEVICE.TTS: If the hostname entered in the device.tts file does not match the results from the command uname -n ProMAX will return an error:
Unable to make socket connection between client and ProMAX This is most often caused when fully qualified hostnames are used. (513479)
• In the TTS online Documentation Basic Configuration section, the description for TMHOST is
’TMHOST="terminal:0.0" This is the location to display the mount messages issued for this device. If this is not supplied, mount message are sent to the location of the User Interface where the job was submitted. If a user is using a remote tape drive, the default mount location only works if the DISPLAY environment variable is set to ’hostname:0.0’ If this variable is left to the default of ’:0.0’, the mount message actually goes to the machine with the tape drive attached. (513523)
• SGI ONLY: The REMOTE_TAPE_HOME /port/bin/ scripts for TAPE_REQUEST and TAPE_NOTIFICATION look for ’hostname’ and ’rsh’ under /bin rather than ’/usr/bsd/hostname’ and ’/usr/bsd/rsh’ which is standard on most SGI installs. The work-around is to edit these scripts to match the correct paths on your system. (513363)
• Remote Tape AIX only: In the case where the remote tape device is attached to an AIX system that does not
contain a full ProMAX installation you may get the
following error message when trying to access the device: ERROR: UNABLE TO CONNECT TO IO2 CLIENT PROGRAM
We believe this is due to a library missing from the remote tape distribution The work-around is to do a full ProMAX AIX install or at least the ../sys/lib directory. (303623)
• ShowCat: The documentation does not explain that in order to run this program $PROMAX_HOME/port/bin and $PROMAX_HOME/sys/bin must be in the users search path. Otherwise users will get an error saying promaxpath not found. (513506)
• The NREW (no rewind) parameter in the device.tts file is not being honored. Use NREW + NUNL to bypass the rewind and eject behavior. (514411,515409)
• SGI Only: The "Process Killed" message is NOT coming to the Opcon Tape Notification window when user kills a job from the ProMAX UI "Notification Window". (136556) • When a user cancels a job from the ProMAX UI, the
Process Killed message does not show up in opcon. The work-around is to notification and tape request files. (145230)
Add "export THREADS_FLAG=native" to both the following files: $PROMAX_HOME/port/bin/TAPE_NOTIFICATION
$PROMAX_HOME/port/bin/TAPE_REQUEST
• AIX Only: The proclient binary distributed in the tar-file under $PROMAX_HOME/port/misc/remote_tape. Does not work. Contact [email protected] for the correct version
• LINUX Only: A local device name with less than 8 characters causes additional characters to append to name causing jobs to fail with error message: (148604)
FATAL TAPE SYSTEM RUNTIME ERROR:
A matching logical device name: [LOCAL8MMX] was not found in the DEVICES file.
The device.tts shows: