Messages


Chapter 16. Tivoli Data Protection for Lotus Notes (0900-0999)

The messages in this section are for the Tivoli Data Protection for Lotus Notes.

Notes:

  1. The term "database" refers to a Lotus Notes database.
  2. The term "notes" and "documents" are used interchangeably.

For further information, refer to the following documents:



ANS0900Idsmnotes completed.

Explanation: The dsmnotes command completed successfully.
System Action: The program completes.
User Response: Not Applicable.



ANS0901SCannot 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.



ANS0903EI/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 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.



ANS0904EI/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 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. Also check your available disk space.



ANS0905SError 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.



ANS0907EError in getting file system information.

Explanation: An error was encountered when an attempt was made to obtain the file system information for the drive on which the Notes database resides.
System Action: Processing stops.
User Response: Check the drive on which the 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.



ANS0908EError getting database volume label.

Explanation: An error was encountered when an attempt was made to obtain the volume label of the drive on which the Notes database resides.
System Action: Processing stops.
User Response: Check the drive on which the Notes database you are processing resides. Be sure that the volume has a label and your disk is attached.



ANS0909EError in parsing options.

Explanation: A general parsing error occurred on a dsmnotes command. Either you entered too many path names, or 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.



ANS0910EInvalid option keyword.

Explanation: An invalid option keyword was specified on a dsmnotes command.
System Action: Processing stops.
User Response: Identify and correct the invalid keyword. Then reissue the command.



ANS0912EThe specified password is too long.

Explanation: The TSM password you entered is too long.
System Action: Processing stops.
User Response: If you are resetting a new TSM password, you need to choose a shorter password. If you are entering a current TSM password, check that the password is correct. If the password is correct but the problem still occurs, ask your TSM administrator to reset your password to a new value. If you do this, choose a shorter password.



ANS0913EAn invalid option value was specified.

Explanation: An invalid value was 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.



ANS0914ERequired 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.



ANS0915EAn invalid date was entered.

Explanation: An invalid date value was entered. Either the syntax of the value was not correct, or an actual value (for example, "45" for month) 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 date syntax.



ANS0916EAn invalid time was entered.

Explanation: An invalid time value was 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.



ANS0917EUsage: dsmnotes <actions> <options> <db pathname>

Explanation: No parameters were 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.



ANS0918Edsmnotes action (1st parm) is unrecognized.

Explanation: A syntax error was made on a dsmnotes command. The first parameter on the command is generally used to identify what kind of action is to be performed (for example, "INCR" for incremental backup), but this first parameter on the command was not recognized as a valid action.
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.



ANS0919EUsage: 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.



ANS0920EUsage: 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.



ANS0921EUsage: 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.



ANS0923EDatabase path name is invalid.

Explanation: The given path name does not resolve to a valid 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 Notes data directory to ensure that the path name is not defaulting incorrectly.



ANS0924ECannot restore to original database.

Explanation: An attempt was made to rebuild a Notes database from backup copies of notes, but the original database file was 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.



ANS0926ECannot open database.

Explanation: An attempt to open a 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 Notes workspace.



ANS0928IRestore of Note(s) done.

Explanation: Restoration of one or more notes was successful.
System Action: The program completes successfully.
User Response: None.



ANS0929EUser 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



ANS0930IDatabase rebuild done.

Explanation: Database rebuild from backup copies of notes was successfully completed.
System Action: The program completes successfully.
User Response: None.



ANS0931ECannot log errors.

Explanation: An attempt was 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.



ANS0932INo matching data on server.

Explanation: An attempt was made to query one or more backup copies of notes on the TSM server, but no copies existed or an attempt was made to merge the data notes (documents) from the TSM 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).



ANS0933EThe 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.



ANS0934ETSM new passwords do not match.

Explanation: An attempt was made to change the TSM password through the Lotus Notes workspace but the two new TSM passwords entered did not match.
System Action: Processing stops.
User Response: Retry the command with matching new TSM passwords.



ANS0935EThis Notes database file not on server.

Explanation: Either the given database file was not backed up on the server, or the database file space was removed from the server.
System Action: Processing stops.
User Response: Check the name of the database to ensure that it is the correct database, and check the DSM.OPT file to ensure that you are accessing the correct TSM server. You can ask the TSM administrator to check the filespaces for your node. A database name is equivalent to a filespace.



ANS0936EThis 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 Notes workspace interface, but allowed through the TSM Notes application client command-line interface, then use the appropriate dsmnotes command. An alternative is to complete the action on the appropriate machine.



ANS0937ECannot 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 documentation.
System Action: Processing stops.
User Response: If your interface is the 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.



ANS0938EDatabase name required.

Explanation: You are required to enter a database name.
System Action: Processing stops.
User Response: Enter the database name.



ANS0939INo 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 through the TSM client.



ANS0940ESome options are mutually exclusive.

Explanation: Some of the options specified are mutually exclusive. For example:
System Action: Processing stops.
User Response: Correct the syntax of the command and then reissue the command.



ANS0941EInvalid date/time range.

Explanation: An invalid date or time range was 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.



ANS0942ENo notes chosen.

Explanation: An attempt was 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.



ANS0944Edsmnotes 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.



ANS0947EError 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 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 Tivoli Data Protection application client. Refer to the user's guide of the corresponding platform.



ANS0948EPathname is a directory.

Explanation: An attempt was made to restore a single Database but the pathname specified was a directory.
System Action: Processing stops.
User Response: If you want to restore a single database, make sure your database name ends with a ".nsf" extension.



ANS0950EData on server has an invalid version.

Explanation: Data structure for the application is not compatible with the data stored on the server.
System Action: Processing stops.
User Response: Check the user's software version.



ANS0951ELotus Notes error: error_code occurred.

Explanation: A Lotus Notes error has occurred but the Tivoli Data Protection application client 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 NT, or 4.52 or above for OS/2. You probably have a downlevel Lotus Notes software installed on your system. Check with your Lotus Notes Administrator for assistance.



ANS0952ETSM error: error_code occurred.

Explanation: A TSM error has occurred but the Tivoli Data Protection application client was not able to translate the error code into a valid TSM error message.
System Action: Processing stops.
User Response: Check with your TSM Administrator for assistance.



ANS0953ENo license or license expired.

Explanation: You do not have a valid Tivoli Data Protection application client 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.



ANS0955EDatabase IDs do not match.

Explanation: An attempt was made to back up a database that has the same path and name as a database that is previously backed up to the TSM server. These two databases have the same name, but they have different database IDs. As a result, they were 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 TSM server is no longer needed, ask your TSM administrator to delete the database's filespace on the server.



ANS0956EThe TSM password is needed.

Explanation: A TSM password is required.
System Action: Processing stops.
User Response: If the TSM PASSWORDACCESS PROMPT option in the option file is used, you are required to enter the password by using the -adsmpw keyword.

If the TSM 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 to use.



ANS0957EAn 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.



ANS0958EUsage: 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.



ANS0959ITSM password changed.

Explanation: The TSM password has been changed successfully.
System Action: The program completes successfully.
User Response: None.



ANS0960ECannot write over data in buffer.

Explanation: An attempt was 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.



ANS0961EDatabase 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.



ANS0962EFilespace 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.



ANS0964EInvalid Notes Build Version.

Explanation: A wrong version of Tivoli Data Protection application client is being used.
System Action: Processing stops.
User Response: Check the Tivoli Data Protection application client Readme file to verify if the installed Tivoli Data Protection application client supports the current version of Lotus Notes on your workstation. Uninstall the current version of Tivoli Data Protection application client. Then reinstall and be sure to select the correct version of Tivoli Data Protection application client during the installation.



ANS0970IProcessing log file Logname.

Explanation: The Tivoli Data Protection application client's log file is being processed.
System Action: Program continues.
User Response: None.



ANS0971EToo 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.



ANS0972EToo 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.



ANS0973EInvalid parameter: parameter.

Explanation: An invalid parameter is entered.
System Action: Processing stops.
User Response: Correct the invalid parameter. Reissue the command.



ANS0974ENo log file is specified.

Explanation: The Tivoli Data Protection application client's log file is not entered.
System Action: Processing stops.
User Response: Enter a fully qualified Tivoli Data Protection application client log file, then reissue the command.



ANS0975ENo 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.



ANS0976EError 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.



ANS0977EError 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.



ANS0978EDBname. 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.



ANS0979EError closing log file Logname: system error code.

Explanation: An I/O error occurred when an attempt was made to close the Tivoli Data Protection application client's log file.
System Action: Processing stops.
User Response: Check the access permission on the Tivoli Data Protection application client's log file.



ANS0980EError deleting log file Logname: system error code.

Explanation: An I/O error occurred when an attempt was made to delete the Tivoli Data Protection application client's log file.
System Action: Processing stops.
User Response: Check the access permission on the Tivoli Data Protection application client's log file.



ANS0981EError getting log file start time.

Explanation: The program is not able to interpret the first date/time stamp in the Tivoli Data Protection application client'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 reason, 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.



ANS0982EError getting log file end time.

Explanation: The program is not able to interpret the last date/time stamp in the TSMConnect 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 reason, 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.



ANS0983WToo large a record in log file.

Explanation: One of the records in the Tivoli Data Protection application client 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 Tivoli Data Protection application client's log file is valid.



ANS0984EError opening the log file Logname: system error code.

Explanation: An I/O error occurred when an attempt was made to open the Tivoli Data Protection application client'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.



ANS0985EError closing the database DBname: system error code.

Explanation: An I/O error occurred when an attempt was made to close the log database.
System Action: Processing stops.
User Response: Check the access permission on the log database.



ANS0986ILog file Logname successfully written to DBname.

Explanation: The Tivoli Data Protection application client's log file has been successfully written to the log database.
System Action: The program completes successfully.
User Response: None.



ANS0987ELog file Logname NOT written to DBname.

Explanation: The Tivoli Data Protection application client's log file was not written to the log database due to error.
System Action: Processing stops.
User Response: Check the error messages that preceded this message.



ANS0988ILog file Logname deleted.

Explanation: The Tivoli Data Protection application client's log file was deleted because the "-d" option was used.
System Action: The program completes successfully.
User Response: None.



ANS0989ELog file Logname was NOT deleted, due to error.

Explanation: The user has used the option "-d" but the Tivoli Data Protection application client's log file was 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 ]