Using the OS/2 Lotus Notes Backup Agent
There are three sources for messages:
The messages in this section are for the Lotus Notes Backup Agent.
- The term "database" refers to a Lotus Notes database.
- The term "notes" and "documents" are used interchangeably.
ANS0900I
Notes Agent completed.
Explanation: The dsmnotes command completed successfully.
System Action:
The program completes.
User Response: Not Applicable.
ANS0901S
Cannot allocate memory.
Explanation: An attempt was made to allocate memory but failed.
System Action:
Processing stops.
User Response: Check the LOG.DSM file for further details about the failure.
ANS0903E
I/O error opening file.
Explanation: An I/O error occurred when an attempt was made to open one of the supporting
files (for example: a trace file or log file). This message does
not suggest an I/O error in a Lotus Notes database.
System Action:
Processing stops.
User Response: Check all supporting files, including the log file, and trace file.
Consider updating the environment variables in the NOTES.INI file to
avoid using the problem file or check access permission on the file.
ANS0904E
I/O error writing to a file.
Explanation: An I/O error occurred when an attempt was made to write to a supporting file
like a trace file or log file. This message does not suggest an I/O
error in a Lotus Notes database.
System Action:
Processing stops.
User Response: Check all supporting files, including the log file, and trace file.
Consider updating the environment variables in the NOTES.INI file to
avoid using the problem file and also Check your available disk space.
ANS0905S
Error getting current working directory
Explanation: An error occurred while trying to retrieve the current working
directory.
System Action:
Processing stops.
User Response: Check the LOG.DSM file for any further details on the specific
error. There may be an error in your operating system since it cannot
determine your current working directory.
ANS0907E
Error in getting file system information.
Explanation: An error is encountered when an attempt is made to obtain file system
information for the drive on which the Lotus Notes database resides.
System Action:
Processing stops.
User Response: Check the drive on which the Lotus Notes database you are processing
resides. Be sure that the volume has a label and your disk is
attached. Check the LOG.DSM file for details about
the error.
ANS0908E
Error getting database volume label.
Explanation: An error is encountered when an attempt is made to obtain the volume label of
the drive on which the Lotus Notes database resides.
System Action:
Processing stops.
User Response: Check the drive on which the Lotus Notes database you are processing
resides. Be sure that the volume has a label and your disk is
attached.
ANS0909E
Error in parsing options.
Explanation: A general parsing error occurred on a dsmnotes command.
Either you entered too many path names, a hyphen (-), or an equal
(=) sign is missing in the option.
System Action:
Processing stops.
User Response: Check the syntax of the command. Correct the syntax and reissue the
command.
ANS0910E
Invalid option keyword.
Explanation: An invalid option keyword is specified on a dsmnotes
command.
System Action:
Processing stops.
User Response: Identify and correct the invalid keyword. Then reissue the
command.
ANS0912E
The specified password is too long.
Explanation: The ADSM password you entered is too long.
System Action:
Processing stops.
User Response: If you are resetting a new ADSM password, you need to choose a shorter
password. If you are entering a current ADSM password, check that the
password is correct. If the password is correct but the problem still
occurs, ask your ADSM administrator to reset your password to a new
value. If you do this, choose a shorter password.
ANS0913E
An invalid option value is specified.
Explanation: An invalid value is specified for an option on a dsmnotes
command.
System Action:
Processing stops.
User Response: Identify and correct the invalid value. Then reissue the
dsmnotes command.
ANS0914E
Required keywords are missing.
Explanation: One or more required keywords are missing from the dsmnotes
command.
System Action:
Processing stops.
User Response: Identify and check the proper syntax and provide the missing keywords and
values. Then reissue the dsmnotes command.
ANS0915E
An invalid date is entered.
Explanation: An invalid date value is entered. Either the syntax of the value is not
correct, or an actual value (for example, "45" for month) is invalid.
System Action:
Processing stops.
User Response: Identify and correct the invalid date value. Refer to the User's
Guide of the corresponding platform for the correct date syntax.
ANS0916E
An invalid time was entered.
Explanation: An invalid time value is entered. Either the syntax of the value was
not correct, or an actual value (for example, "75" for hour) was
invalid.
System Action:
Processing stops.
User Response: Identify and correct the invalid date value. Refer to the User's
Guide of the corresponding platform for the correct time syntax.
ANS0917E
Usage: dsmnotes <action> <options> <db pathname>
Explanation: No parameters are specified on the dsmnotes command. Some
parameters are required such as action parameter and database name
parameter.
System Action:
Processing stops.
User Response: Refer to the User's Guide of the corresponding platform for the correct
syntax of your command, including required parameters. Correct the
syntax and reissue the command.
ANS0918E
dsmnotes action (1st parm) is unrecognized.
Explanation: A syntax error is made on a dsmnotes command. The first
parameter on the command is generally used to identify what kind of action is
to be performed , but this first parameter on the command was not recognized
as a valid action. An example is INCR for incremental backup.
System Action:
Processing stops.
User Response: Refer to the User's Guide of the corresponding platform for the correct
command syntax. Correct the syntax and reissue the command.
ANS0919E
Usage: dsmnotes incr <options> <db pathname>
Explanation: A syntax error occurred on the incremental backup command.
System Action:
Processing stops.
User Response: Refer to the User's Guide of the corresponding platform for the correct
syntax. Correct the syntax and reissue the command.
ANS0920E
Usage: dsmnotes restore <options> <db pathname>
Explanation: A syntax error occurred on the incremental backup command.
System Action:
Processing stops.
User Response: Refer to the User's Guide of the corresponding platform for the correct
syntax. Correct the syntax and reissue the command.
ANS0921E
Usage: dsmnotes restdel <options> <db pathname>
Explanation: A syntax error occurred on the restore deletion stubs command.
System Action:
Processing stops.
User Response: Refer to the User's Guide of the corresponding platform for the correct
syntax. Correct the syntax and reissue the command.
ANS0923E
Database path name is invalid.
Explanation: The given path name does not resolve to a valid Lotus Notes database file
name.
System Action:
Processing stops.
User Response: Validate that the given path name is correct. If wildcard symbols are
used, refer to the User's Guide of the corresponding platform for the
correct usage of these symbols. Also check for defaulting to the Lotus
Notes data directory to ensure that the path name is not defaulting
incorrectly.
ANS0924E
Cannot restore to original database.
Explanation: An attempt is made to rebuild a Lotus Notes database from backup copies of
notes, but the original database file is specified as the target
database.
System Action:
Processing stops.
User Response: Choose an original name for the target database. The name cannot belong
to an existing file.
ANS0925E
--days value cannot be negative (OS/2).
The days value cannot be negative (AIX and Windows NT).
Explanation: Only a positive number of days can be specified.
System Action:
Processing stops.
User Response: Either specify a positive number of days or let the system default to restore
all the deleted documents that it can identify.
ANS0926E
Cannot open database.
Explanation: An attempt to open a Lotus Notes database was unsuccessful.
System Action:
Processing stops.
User Response: Check the LOG.DSM file for more information about the
error. Verify the path name of your database. If the path name
is correct, then verify the database itself to ensure that it can be opened
through the Lotus Notes workspace.
ANS0928I
Restore of Note(s) done.
Explanation: Restoration of one or more notes is successful.
System Action:
The program completes successfully.
User Response: None.
ANS0929E
User interrupted operation.
Explanation: The user has interrupted the operation (for example, by pressing an interrupt
key such as <Ctrl C>).
System Action:
Processing stops.
User Response: None.
ANS0930I
Database rebuild done.
Explanation: Database rebuild from backup copies of notes is successfully completed.
System Action:
The program completes successfully.
User Response: None.
ANS0931E
Cannot log errors.
Explanation: An attempt is made to initiate error logging, which includes either opening or
creating a LOG.DSM file. The attempt failed.
System Action:
Processing stops.
User Response: Check the LOG.DSM file to see why it cannot be opened or
created.
ANS0932I
No matching data on server.
Explanation: An attempt was made to query one or more backup copies of notes on the ADSM
server, but:
- No copies existed or
- An attempt is made to merge the data notes (documents) from the ADSM
server into the original database, but no data notes existed.
System Action:
The program ends.
User Response: If you believe that some matching data should exist on the server, check your
database path name to ensure that you are using the correct database file
name. If the -merge keyword is used, your database might
only have nondata notes (documents).
ANS0933E
The days value is invalid.
Explanation: The days value is either negative or greater than 65535.
System Action:
Processing stops.
User Response: Use correct days value.
ANS0934E
ADSM new passwords do not match.
Explanation: An attempt is made to change the ADSM password through the Lotus Notes
workspace, but the two new ADSM passwords that are entered did not
match.
System Action:
Processing stops.
User Response: Retry the command with matching new ADSM passwords.
ANS0935E
This Notes database file not on server.
Explanation: Either the given database file is not backed up on the ADSM server, or the
database file space is removed from the ADSM server.
System Action:
Processing stops.
User Response: Check:
- The name of the database to ensure that it is the correct database
- The DSM.OPT file to ensure that you are accessing the
correct ADSM server.
You can ask the ADSM administrator to check the filespaces for your
node. A database name is equivalent to a filespace.
ANS0936E
This action is not allowed on a remote database.
Explanation: The action you tried to perform is not allowed on a database that is not
local.
System Action:
Processing stops.
User Response: If the action is not allowed through the Lotus Notes workspace interface, but
allowed through the command line interface, then use the appropriate
dsmnotes command. An alternative is to complete the action
on the appropriate machine.
ANS0937E
Cannot enter new database name (OS/2). Must restore
to original database (AIX and Windows NT).
Explanation: You are not allowed to enter a new target database name for this restore
operation.
For OS/2, refer to the dsmnotes restore -FROMDATE option
in the User's Guide.
System Action:
Processing stops.
User Response: If your interface is the Lotus Notes workspace, then replace the database name
in the entry field with blanks. If your interface is a command, then do
not specify a target ("-TO") database.
ANS0938E
Database name required.
Explanation: Enter a database name.
System Action:
Processing stops.
User Response: Enter the database name.
ANS0939I
No deletion stubs in database.
Explanation: There are no deletion stubs in the given database.
System Action:
The program ends.
User Response: If there are no deletion stubs in the database to initiate the restore, then
you may need to rebuild the database by restoring the older version of the
database file. You can do this through the ADSM client.
ANS0940E
Some options are mutually exclusive.
Explanation: Some of the options specified are mutually exclusive. For
example:
- For OS/2, the options -MERGE=NO, -TO, and -FROMDATE
cannot be specified simultaneously. The reason for this is because a
new target database might not be operable if some documents (such as view and
form design documents) are excluded.
Design documents are normally backed up with the initial incremental, and
not subsequently modified. In this situation, allowing the FROMDATE
option would cause some design documents to be excluded when creating the new
database.
- For AIX and Windows NT, the options -MERGE and -TO are
mutually exclusive. The reason for this is because a new target
database cannot be specified for a merge.
System Action:
Processing stops.
User Response: Correct the syntax of the command and then reissue the command.
ANS0941E
Invalid date/time range.
Explanation: An invalid date or time range is given. For example, the TO time is
earlier than the FROM time.
System Action:
Processing stops.
User Response: Correct the date or time range and rerun the program. Be sure that all
year, month, day, hour, and minute values are in the correct order and are
valid values.
ANS0942E
No notes chosen.
Explanation: An attempt is made to restore a note or notes, but no notes documents were
chosen.
System Action:
Processing stops.
User Response: On the Lotus Notes workspace, select the notes to be restored by placing a
checkmark next to the notes.
ANS0944E
dsmnotes errors occurred.
Explanation: Errors occurred on one or more databases.
System Action:
The program partially completes.
User Response: Check the LOG.DSM file for further details about the
failure.
ANS0947E
Error initializing Notes.
Explanation: Error occurred while initializing the Lotus Notes runtime system.
System Action:
Processing stops.
User Response: Check the Lotus Notes environment. Try to bring up your Lotus Notes
workspace if you have not already done so. Also, check the
NOTES.INI file to see if it has the correct setup for the
Lotus Notes Backup Agent. Refer to the user's guide of the
corresponding platform.
ANS0948E
Pathname is a directory.
Explanation: An attempt was made to restore a single database, but the pathname that is
specified is a directory.
System Action:
Processing stops.
User Response: If you want to restore a single database, make sure that your database name
ends with a ".nsf" extension.
ANS0950E
Data on server has an invalid version.
Explanation: Data structure for the application is not compatible with the data that is
stored on the ADSM server.
System Action:
Processing stops.
User Response: Check the user's software version.
ANS0951E
Lotus Notes error: <error_code> occurred.
Explanation: A Lotus Notes error occurred, but the Lotus Notes Backup Agent was not able to
translate the error code into a valid Lotus Notes Error Message.
System Action:
Processing stops.
User Response: The supported Lotus Notes version is 4.50 for AIX and Windows NT, and
4.52 or above for OS/2. You probably have a down level Lotus
Notes software installed on your system. Check with your Lotus Notes
administrator for assistance.
ANS0952E
ADSM error: <error_code> occurred.
Explanation: An ADSM error occurred, but the Lotus Notes Backup Agent is not able to
translate the error code into a valid ADSM error message.
System Action:
Processing stops.
User Response: Check with your ADSM administrator for assistance.
ANS0953E
No license or license expired.
Explanation: You do not have a valid Lotus Notes Backup Agent license, or your license has
already expired.
System Action:
Processing stops.
User Response: Refer to the User's Guide of the corresponding platform or call the IBM
sales representatives for license information.
ANS0955E
Database IDs do not match.
Explanation: An attempt is made to back up a database that has the same path and name as a
database that is previously backed up to the ADSM server. These two
databases have the same name, but they have different database IDs. As
a result, they are treated as two different databases.
System Action:
Processing stops.
User Response: Rename the database to be backed up. If the database that is previously
backed up in the ADSM server is no longer needed, ask your ADSM administrator
to delete the database's filespace on the server.
ANS0956E
The ADSM password is needed.
Explanation: An ADSM password is required.
System Action:
Processing stops.
User Response: If the ADSM PASSWORDACCESS PROMPT option in the option file is used, you are
required to enter the password by using the -adsmpw
keyword.
If the ADSM PASSWORDACCESS GENERATE option is used, issue the dsmnotes
change command with appropriate parameters to create a password
file. Refer to the User's Guide of the corresponding platform for
the correct syntax usage.
ANS0957E
An operation is already active.
Explanation: An active restore operation is being processed.
System Action:
Processing stops.
User Response: Wait for the active restore operation to complete before starting a second
one.
ANS0958E
Usage: dsmnotes change -adsmpw=old -newadsmpw=new
Explanation: The syntax of the dsmnotes change command is incorrect.
System Action:
Processing stops.
User Response: Use correct syntax. Refer to the User's Guide of the corresponding
platform for the correct syntax.
ANS0959I
ADSM password changed.
Explanation: The ADSM password is changed successfully.
System Action:
The program completes successfully.
User Response: None.
ANS0960E
Cannot write data over data in buffer.
Explanation: An attempt is made to overwrite valid data in the buffer.
System Action:
Processing stops.
User Response: Check the integrity of the database by opening it in the Lotus Notes
workspace. If the database opens successfully, reissue the
command. If the error is persistent, contact the IBM technical
support.
ANS0961E
Database not allowed.
Explanation: A database name is not allowed with this command.
System Action:
Processing stops.
User Response: Remove the database name and reissue the command.
ANS0962E
Filespace not allowed
Explanation: A filespace name is not allowed with this command.
System Action:
Processing stops.
User Response: Remove the filespace name and reissue the command.
ANS0970I
Processing log file Logname.
Explanation: The Lotus Notes Backup Agent's log file is being processed.
System Action:
The program continues.
User Response: None.
ANS0971E
Too few parameters.
Explanation: One or more parameters are required.
System Action:
Processing stops.
User Response: Refer to the User's Guide of the corresponding platform for the correct
number of parameters. Enter the correct number of parameters and
reissue the command.
ANS0972E
Too many parameters
Explanation: Too many parameters were passed to the command.
System Action:
Processing stops.
User Response: Refer to the User's Guide of the corresponding platform for the correct
number of parameters. Enter the correct number of parameters and
reissue the command.
ANS0973E
Invalid parameter: parameter.
Explanation: An invalid parameter is entered.
System Action:
Processing stops.
User Response: Correct the invalid parameter. Reissue the command.
ANS0974E
No log file is specified.
Explanation: The Lotus Notes Backup Agent's log file is not entered.
System Action:
Processing stops.
User Response: Enter a fully qualified Lotus Notes Backup Agent log file, then reissue the
command.
ANS0975E
No log database is specified.
Explanation: The Lotus Notes log database is not entered.
System Action:
Processing stops.
User Response: Enter the Lotus Notes log database (usually log.nsf).
Refer to the user's guide of the corresponding platform for further
information.
ANS0976E
Error opening the log database DBname.
Explanation: The specified log database cannot be opened.
System Action:
Processing stops.
User Response: Verify the path name of your log database. If the path name is correct,
verify the log database itself to ensure that it can be opened through the
Notes workspace.
ANS0977E
Error getting the mode of log database DBname.
Explanation: The program cannot verify that the input log database is a valid
database.
System Action:
Processing stops.
User Response: Verify the path name of your log database. If the path name is correct,
then verify the log database itself to ensure that it can be opened in the
Notes workspace.
ANS0978E
DBname is not a Lotus Notes database.
Explanation: An invalid database has been specified.
System Action:
Processing stops.
User Response: Verify the path name of your log database. If the path name is correct,
verify the log database itself to ensure that it can be opened in the Notes
workspace.
ANS0979E
Error closing log file Logname: system
error code.
Explanation: An I/O error occurred when an attempt is made to close the Lotus Notes Backup
Agent's log file.
System Action:
Processing stops.
User Response: Check the access permission on the Lotus Notes Backup Agent's log
file.
ANS0980E
Error deleting log file Logname: system error
code.
Explanation: An I/O error occurred when an attempt is made to delete the Lotus Notes Backup
Agent's log file.
System Action:
Processing stops.
User Response: Check the access permission on the Lotus Notes Backup Agent's log
file.
ANS0981E
Error getting log file start time.
Explanation: The program is not able to interpret the first date/time stamp in the Lotus
Notes Backup Agent's log file. The first date/time stamp format
either does not match the date/time stamp format of your operating system, or
it is corrupted.
System Action:
Processing stops.
User Response: For consistency reasons, the date/time stamp format of the log file must match
the date/time stamp format of your operating system. Check the locale
of your operating system to ensure that you have matching date/time stamp
formats.
ANS0982E
Error getting log file end time.
Explanation: The program is not able to interpret the last date/time stamp in the Lotus
Notes Backup Agent's log file. The last date/time stamp format
either does not match the date/time stamp format of your operating system, or
it is corrupted.
System Action:
Processing stops.
User Response: For consistency reasons, the date/time stamp format of the log file must match
the date/time stamp format of your operating system. Check the locale
of your operating system to ensure that you have matching date/time stamp
formats.
ANS0983W
Too large a record in log file.
Explanation: One of the records in the Lotus Notes Backup Agent is too large, or there is
no carriage return character in the log file.
System Action:
Program continues.
User Response: If the command is successful, check the log database to ensure that the
correct record was added to the database. If the command fails, verify
that the data in the Lotus Notes Backup Agent's log file is valid.
ANS0984E
Error opening the log file Logname: system
error code.
Explanation: An I/O error occurred when an attempt is made to open the Lotus Notes Backup
Agent's log file.
System Action:
Processing stops.
User Response: Verify the path name of the log file. Also check the access permission
on the log file.
ANS0985E
Error closing the database DBname: system
error code.
Explanation: An I/O error occurred when an attempt is made to close the log
database.
System Action:
Processing stops.
User Response: Check the access permission on the log database.
ANS0986I
Log file Logname successfully
written to DBname.
Explanation: The Lotus Notes Backup Agent's log file is successfully written to the
log database.
System Action:
The program completes successfully.
User Response: None.
ANS0987E
Log file Logname NOT written
to DBname.
Explanation: The Lotus Notes Backup Agent's log file is not written to the log
database due to error.
System Action:
Processing stops.
User Response: Check the error messages that preceded this message.
ANS0988I
Log file Logname deleted.
Explanation: The Lotus Notes Backup Agent's log file is deleted because the
--d option is used.
System Action:
The program completes successfully.
User Response: None.
ANS0989E
Log file Logname was NOT deleted,
due to error.
Explanation: You used the option --d, but the Lotus Notes Backup
Agent's log file is NOT deleted due to error.
System Action:
Processing stops.
User Response: Check the error messages that preceded this message.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]