Filter
Top Products
Backup Server Error Messages 5.1.2 - 6.89.2
734
5.17.2 2 Cannot get the character set currently in use.
Explanation: The remote Backup Server could not
set the character set to its default setting for the initial
connection from a client of the local Backup Server.
5.18.2 2 Cannot set character set `%1!' in the login record.
Explanation: The remote Backup Server could not
set the character set to the set specified by the remote
connection.
5.19.2 2 Cannot get the language currently in use.
Explanation: The remote Backup Server could not
set the language to its default setting for the initial
connection from a client of the local Backup Server.
5.20.2 2 Cannot set language `%1!' in the login record.
Explanation: The remote Backup Server could not
set the language specified by the remote connection.
5.21.2 2 Remote DUMP/LOAD is not allowed when
interfacing to a stripe for device `%1!'.
Explanation: An unexpected condition, possibly
fatal to the session, has occurred. Error may have
occurred with any or all of usage, environment, or
internal logic.
6.28.1 1 Dumpfile name `%1!' section number %2! mounted on
%3! `%4!'
Explanation: This message has a critical role. It
contains the file name assigned to the archive file at
dump time. If the dump goes to a multifile volume, the
user or the application must record the dumpfile name
in persistent storage and specify it at load time in order
to locate the file for loading from the multifile archive.
If the dumpfile name is lost, it will be necessary to scan
the tape off- line with the commands given under
message 4.12.2 to locate the dumpfile name.
6.29.1 1 unnamed dumpfile, section number %1! mounted on
device `%2!'
Explanation: Dumpfile name is lost. See above
message.
6.30.1 1 Device %1!: Volume cataloguing complete.
Explanation: This is an informational message
indicating that the
load with listonly command has
completed successfully for the specified archive
device.
Number Severity Text and Explanation