The specified file space (domain) is incorrect or does not exist on the workstation.

Processing stopped.

Retry the operation specifying an existing domain (drive letter or file system name).

The number defining the correspondence between drive letter or file (domain name) and volume label is not known to the server.

Processing stopped.

Report the program error to your service representative.

The selected drive does not have a label.

Tivoli Storage Manager is unable to do the requested operation without a drive or label entered.

If the drive is a floppy drive, place a disk with a volume label in it and retry the operation. If the disk is a hard drive, ensure the drive has a volume label, and retry the operation.

The selected drive has a duplicate volume label. Because Tivoli Storage Manager uses the volume label to keep track of backup/archive information, it cannot back up or archive files from a drive with a duplicate volume label.

Tivoli Storage Manager cannot select the drive.

If the volume needs to be available to the system, exit Tivoli Storage Manager, and assign a volume label to the drive. Restart Tivoli Storage Manager and retry the operation.

The file or directory being restored or retrieved from the server cannot be written to because the destination is write locked. Another operation might have the file open and will not allow it to be updated.

File skipped.

Either determine which operation has the file write locked, or restore the file to another name or location.

The file being processed for backup, archive or migrate no longer exists on the client. Another process deletes the file before it can be backed up, archived or migrated by Tivoli Storage Manager.

File skipped.

None.

You specified an incorrect directory path.

Processing stopped.

Correct the syntax specified on the call and retry the operation.

Access to the specified file or directory is denied. You tried to read from or write to a file and you do not have access permission for either the file or the directory.

Processing stopped.

Ensure that you specified the correct file or directory name, correct the permissions, or specify a new location.

File is temporarily unavailable.

File skipped.

Check and see if file is locked by other process. If not, retry the command.

No more files can be restored or retrieved because the destination disk is full.

Processing stopped.

Free up disk space, or restore or retrieve the file to another disk.

An NFS file system becomes stale.

File system skipped.

Check the NFS mounted filesystem.

All file handles for your system are currently in use. No more are available.

Processing stopped.

Either free some file handles by ending other processes, or modify your system setup to allow for more files to be open at the same time.

The file being restored or retrieved exists.

File is replaced or skipped depending on client options.

None.

An internal system error occurred. A file operation failed because an invalid file handle was passed.

Processing stopped.

Report the problem to your system administrator, and then retry the operation.

An unknown and unexpected error-code occurred within the client program. This is a programming failure and the client program ends.

Processing stopped.

Retry the operation. If the problem continues, see your administrator.

An unexpected error occurred. This might be a low-level system or communication error that Tivoli Storage Manager cannot handle or recover from.

Processing stopped.

Retry the operation. If the problem continues, determine where the problem exists. See your system administrator for further help.

The current file cannot be opened to write to because it is currently being run by another operation.

File skipped.

Stop the operation that is running the file and retry the operation, or restore or retrieve the file to a different name or directory.

While trying to resolve the file name, too many symbolic links were found.

File skipped.

Ensure that you do not have a looping symbolic link for the file.

The file name specified is too long to be handled by Tivoli Storage Manager.

File is skipped.

See the appropriate Using the Backup-Archive Client book for the particular operating system, for the file names that are handled by Tivoli Storage Manager.

File system cannot be accessed because it is locked by the system.

Tivoli Storage Manager cannot complete the operation.

See your system administrator.

Tivoli Storage Manager tried to restore or retrieve a file, but it had an unknown format.

File skipped.

See your system administrator.

The file system/drive was not ready for access.

Processing stopped.

Ensure that the drive is available to Tivoli Storage Manager, and then retry the operation.

The drive was not available for access. A directory exists that does not have either a '.' or '..' entry.

Processing stopped.

Ensure that the drive is operational, and then retry the operation. If unsuccessful, have your service representative check the error log.

An error was found while reading from or writing to the file.

File skipped.

Check your system to ensure that it is operating properly. For OS/2, run CHKDSK /F for the failing drive which can be found in dsmerror.log.

An error was found while writing to the file.

File skipped.

Check your system to ensure that it is operating properly.

A file being backed up/restored or archived/retrieved exceeds system set limits for this user. Shown below are the filesize limits corresponding to various platforms.

AIX®

68,589,453,312 (64GB)

HP-UX

1,099,511,627,775 (1TB-1)

Linux

2,147,483,647 (2GB)

Mac pre-OS9

2,147,482,624 (2GB-1K)

Mac OS9

18,446,744,073,709,551,616 (16EB)

NetWare

4,294,963,200 (4GB -4KB)

NUMA-Q® DYNIX/ptx®

4.5 1,095,216,660,480 (1TB-4GB)

OS/390®

4,294,967,295 (4GB)

SGI

18,446,744,073,709,551,615 (16EB-1)

Solaris 2.6 or higher

1,099,511,627,775 (1TB-1)

Tru64 UNIX

1,099,511,627,776 (1TB)

UnixWare

2,147,483,647 (2GB)

Windows 95 (FAT16)

2,147,483,647 (2GB)

Windows 98 (FAT32)

4,294,967,295 (4GB)

Windows NT/2000 (NTFS)

17,592,185,978,880 (16TB-64K)

File skipped.

Ensure that the system limits are set properly.

You tried to restore or retrieve a file that has exceeded the maximum file size limitation on your system.

Tivoli Storage Manager cannot restore or retrieve the file.

Restore or retrieve this file on a system that supports the file size. See your system administrator.

An unexpected catastrophic program failure occurred, indicated by value.

Processing stopped.

Retry the operation. If the problem continues, see your system administrator or service representative.

The directory path for files being restored or retrieved cannot be created.

File skipped.

Ensure that you have the proper authorization to create the directory for file being restored or retrieved.

Tivoli Storage Manager tried to create a directory path, but is unable to because a file exists that has the same name as a directory.

Processing stopped.

Remove the file that has the same name as the directory. Refer to the last restore/retrieve operation and check all directories along the path.

The disk space allocated for the client owner is full.

Processing stopped.

Free up disk space and retry the restore or retrieve operation.

The path name specified plus the path name in the restored file name combine to create a name whose length exceeds the system maximum.

Processing stopped.

Specify a destination path that, when combined, is less than the system maximum.

A file that was flagged as compressed was not compressed, and the system failed.

Processing stopped.

See your system administrator to report this problem. This error is a system failure.

You are trying to restore a file that was backed up and compressed on another client workstation that had more memory than your client workstation. You cannot restore this file. When the file is restored, it is expanded and your workstation does not have enough memory.

Tivoli Storage Manager canceled the operation.

Obtain a machine with more memory and retry the operation.

An unknown error occurred. This might be a low-level system or communication error that Tivoli Storage Manager cannot handle or recover from.

Processing stopped.

Retry the operation. If the problem continues, determine where the problem exists. See your system administrator for further help.

You tried to restore or retrieve a file that is currently not available from the server.

Tivoli Storage Manager cannot restore or retrieve the file.

See your system administrator to determine why the file is unavailable and then try your operation again.

The active registry key cannot be saved.

Registry backup operation terminates.

See your system administrator.

The specified file-name was skipped during backup, archive, or migrate because it was changing during the attempt to process it.

Tivoli Storage Manager skipped the file.

If you want the file backed up, archived, or migrated retry the operation. If it fails, determine why the file is being changed. For more information on backing up, archiving, or migrating changing files, see your system administrator.

File system 'filespace name' is corrupted or contains one or more corrupted directories and cannot be processed.

File system is skipped.

Check your system to ensure that it is operating properly. For the Windows environment, run CHKDSK utility for the failing drive. More information about corrupted directories can be found in dsmerror.log.

Tivoli Storage Manager detects that the file system has exceeded its quota. No more data can be migrated out of this file system.

Tivoli Storage Manager will not migrate files from this file system.

Recall some files, or ask the system administrator to increase the quota for this file system.

The file system is full. No more free space or free inodes are available to be allocated for the transaction file that is needed when a file is being migrated or recalled.

Tivoli Storage Manager terminates the current operation for this file system.

Remove some files in the file system, and then run reconciliation. Retry the operation.

The filename, directory name, or volume label syntax is incorrect.

File skipped.

You need to check the disk for errors.

While processing the specified file on the workstation, another file name was encountered with a similar name which only differed in case. The Backup-Archive client does not allow names which differ only in case on this platform and cannot guarantee the integrity of the file, so the file is skipped.

This object will be skipped.

Rename the file in question to a unique name.

While processing the specified file on the workstation, another object name was encountered with a similar name which only differed in case. The Backup-Archive client does not allow names which differ only in case on this platform and cannot guarantee the integrity of the file, so the directory and all of the objects contained within it are skipped.

This object will be skipped.

Rename the file in question to a unique name.

You tried to read from or write to a file or directory that is corrupted. The corrupted file is skipped. If this is a directory, the objects contained in the directory and its subdirectories are skipped.

This object will be skipped.

Check your system to ensure that the filespace is not corrupted by using system tools like chkdsk (Windows) or fsck (UNIX).

The specified file-name was skipped during backup archive because the file could not be read.

Tivoli Storage Manager skipped the file.

Check your system to ensure that it is operating properly.

ENABLELANFREE option is set to YES for this session, but an attempt to establish LAN-Free connection failed.

The Tivoli Storage Manager client will failover to non LAN-Free support.

Review the Tivoli Storage Manager error.log for LAN-Free failures. Check your LAN-Free setup and verify that all components are working properly.

ENABLELANFREE option is set to YES for this session and the Tivoli Storage Manager client successfully established LAN-Free connection with server, after the LAN-Free connection was broken.

The Tivoli Storage Manager client will communicate with the server via LAN-Free.

Review the Tivoli Storage Manager error.log for LAN-Free errors. Check your LAN-Free setup and verify that all components are working properly.

The Deployment Manager process was started as a post schedule command. This is the first message from the Deployment Manager. The architecture of the client, schedule name, and domain name are identified at the beginning of the message text.

Deployment Manager continues to process.

None

The previous language pack has been uninstalled, and the installation of the new language pack failed.

Processing continues.

Check the technote for Microsoft Installer error code description: http://www-01.ibm.com/support/docview.wss?uid=swg21050782&rs=663

Check the install log on the client computer.

The operating system level of the client computer is no longer supported by the target level.

Processing stops.

Check the release documentation for information on supported operating system levels.

The installation image might be missing, corrupted, or there might be insufficient disk space on the client computer.

Deployment Manager stops.

Make sure that there is sufficient disk space on the client computer.

Make sure that all of the Windows self extracting client images on the client computer are valid.

None

Processing continues.

None

The previous client package has been uninstalled, and the installation of the new client package failed.

Processing stops.

Check the technote for Microsoft Installer error code description: http://www-01.ibm.com/support/docview.wss?uid=swg21050782&rs=663

Check the install log on the client computer.

After the automatic client deployment, the Tivoli Storage Manager client services failed to start.

Processing stops.

Log on to the client machine and check the backup-archive client error log.

The Deployment Manager determined that the deployment requires restarting the client.

Automatic restart is not enabled. The Deployment Manager process cancels the deployment.

The current client is not uninstalled or updated.

Deployment Manager cancels the client deployment and stops

Reschedule the client deployment.

None

Processing stops.

Reschedule the client deployment. Use a client package with the appropriate operating system platform.

None

Processing stops.

Refer to the Tivoli Storage Manager Backup-Archive Client documentation in the information center.

Reschedule the client deployment with an appropriate target level.

The client package for automatic deployment is invalid. In the client package, the API version does not match the Deployment Manager version.

Deployment Manager stops processing.

Please make sure that the installation package is valid.

The Deployment Manager process failed when setting up the client API.

Processing stops.

Check the error log on the client computer.

The Deployment Manager process failed when initializing the client API.

Processing stops.

Check the error log on the client computer.

The Deployment Manager failed to create a pipe for the standard output of the child process.

Processing stops.

Check the error log on the client computer.

The Deployment Manager could not determine whether all Tivoli Storage Manager processes were shut down successfully.

If automatic restart (autoreboot) is enabled, the Deployment Manager continues. If automatic restart is not enabled, Deployment Manager stops.

Reschedule with automatic restart (autoreboot) enabled.

The setup script was unable to retrieve the matching package from the server.

Processing stops.

Ensure that the client packages for all architectures are available on the server.

Deployment Manager failed to open a file containing required system information.

Processing stops.

Check the error log on the client computer.

The Deployment Manager relies on the information in this file to complete the client deployment.

Processing stops.

Check the error log on the client computer.

The results of querying the system information has taken longer than expected. This could be caused by either a slow system or becuase there is no password saved for the node.

If the password is not generated, processing stops and client deployment will not begin. If the system is slow, processing continues.

Ensure that "PASSWORDACCESS GENERATE" is set in the client options file and that a connection to the server has been made without being prompted for a password. Ignore the warning if the password has been generated.

The Deployment Manager encountered at least one error while parsing the post schedule command of the client deployment schedule.

Processing stops, and client deployment will not begin.

Check the release documentation for information on the format of the post schedule command of the client deployment schedule.

The previous client package has been uninstalled, and the installation of the new client package failed because the client computer is out of disk space.

Processing stops.

Check the technote for Microsoft Installer error code description: http://www-01.ibm.com/support/docview.wss?uid=swg21050782&rs=663

Check the install log on the client computer.

The previous language pack has been uninstalled, and the installation of the new language pack failed because the client computer is out of disk space.

Processing continues.

Check the technote for Microsoft Installer error code description: http://www-01.ibm.com/support/docview.wss?uid=swg21050782&rs=663

Check the install log on the client computer.

The deployment of the new backup-archive client will not be complete until the client computer is restarted. The restart is scheduled to happen immediately after all language packs are deployed.

The Deployment Manager process continues. The client computer will be shut down and restarted after all language packs are deployed, or immediately if there are no language pack to install.

None

The Deployment Manager needs to restart the client computer to complete the client deployment. It is possible the other messages provide details of the deployment.

The Deployment Manager process continues. The client computer will be shut down and restarted immediately after all language packs are deployed, or immediately if there are no language pack to install.

None

The Deployment Manager does not uninstall or update the current language pack. It is possible the other messages provide details of the deployment.

Processing stops. The client computer will be shut down and restarted immediately after all language packs are deployed, or immediately if there are no language pack to install.

Check the error log on the client computer. Manually deploy the language pack.

The Deployment Manager could not find the required installation image.

Processing stops. Client deployment will be cancelled.

Check the server's activity log or the scheduler log on the client computer. Reshcedule the client deployment.

The Deployment Manager failed to install one or more language packs. It is possible the other messages provide details of the installation.

The Deployment Manager process continues.

Check the error log and installation on the client computer. Identify the language packs that failed to install and manually deploy them.

The Deployment Manager is unable to log events to the server. It is possible the other messages provide details of the communications.

The Deployment Manager process continues. Events will be logged locally on the client machine only.

Check network connection and the error log on the client computer.

The setup script encountered an error while querying the Windows registry for [HKLM\SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient].

Processing stops, and client deployment will not begin.

Check the release documentation for information on supported Windows platforms and ensure the REG.EXE command is available on the client computer.

The setup script encountered warnings or errors while querying system information.

Processing continues. The Deployment Manager will check to see if required system information is available. Client deployment could be cancelled if required information is missing.

Check the error log of the backup-archive client for warning and error messages.

It is possible the setup script encountered a warning or error while querying system information.

Processing stops. Client deployment will not start.

Check the error log of the backup-archive client for warning and error messages.

It is possible the client deployment package is missing or corrupted.

Processing stops. Client deployment will not start.

Ensure that the client package is available and imported to the server correctly.

It is possible the client deployment package is missing or corrupted.

Processing stops. Client deployment will not start.

Ensure that the client package is available and imported to the server correctly.

The setup script is trying to retrieve the matching client package from the server.

Processing continues.

Ensure that the client packages for all architectures are available on the server.

It is possible the client package is not available on the server.

Processing stops.

Ensure that client packages for all architectures are available on the server. Check the backup-archive client error log for more detailed error messages.

The client package that was downloaded matches the processor architecture of the current client.

Processing continues.

None

The Microsoft Visual C++ redistributable package is required by the new client.

Processing stops.

Check the installation log file for names with "vcredist*.log" file in system temp directory.

The Microsoft Visual C++ redistributable package is required by the new client.

Processing continues.

none

The setup script could not start the client deployment process.

Processing stops.

Check the log files on the client computer for more details. Ensure the client package is not corrupted.

The setup script invokes the Deployment Manager to manage the deployment process.

Processing continues.

None

Processing stopped because the automatic client deployment feature does not support the installation of a client to a workstation that is already at its target level.

Your current backup-archive client is not affected.

Refer to the Tivoli Storage Manager Backup-Archive Client documentation in the information center.

Reschedule the client deployment with an appropriate target level.

The setup script encountered an error while querying the Windows registry for [HKLM\SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient\Scheduler Service].

Processing stops, and client deployment will not begin.

Check the release documentation for information on supported Windows platforms and ensure the REG.EXE command is available on the client computer.

Only one instance of client deployment manager can be active at a time. This client computer might be configured with multiple node names, but the new client code only needs to be deployed to one node per computer. Each client deployment instance can take a few minutes to complete.

Processing stops.

Ensure only one client deployment task is scheduled to run at a time.

The setup script failed to start the deployment manager as a scheduled task with the Windows "at" command.

Processing stops.

Ensure that the Windows Task Scheduler service is running. It is possible that the system event log contains more details about the failure. Reschedule the client deployment.

The deployment manager determined there was insufficient free disk space for the client deployment.

Processing stops.

Free up required disk space and reschedule the client deployment.

The previous client has been uninstalled, and the installation of the new client was not completed pending the restart of the client computer. The architecture of the client, schedule name, and domain name are identified at the beginning of the message text.

The Deployment Manager process completes.

Manually restart the client computer as soon as possible.

Restarting the computer is required to complete the client deployment. The architecture of the client, schedule name, and domain name are identified at the beginning of the message text.

The Deployment Manager process completes. The client computer will be shut down and restarted.

None

This is a generic warning message. It is possible the other messages provide details of the deployment. The architecture of the client, schedule name, and domain name are identified at the beginning of the message text.

The Deployment Manager process completes.

Check the warning messages from the server administration center, the server activity log, or error log on the client computer for more information.

This is a generic message that the client deployment was cancelled. The Deployment Manager does not uninstall or update the current client. It is possible the other messages provide details of the deployment. The architecture of the client, schedule name, and domain name are identified at the beginning of the message text.

Processing stops.

Check the warning messages from the server administration center, the server activity log, or error log on the client computer for more information.

This is a generic message that the client deployment failed. It is possible that other messages provide details of the failure. The architecture of the client, schedule name, and domain name are identified at the beginning of the message text.

Processing stops.

Check the warning messages from the server administration center, the server activity log, or error log on the client computer for more information.

This is a generic message that the client deployment was successful. It is possible that other messages provide details of the deployment. The architecture of the client, schedule name, and domain name are identified at the beginning of the message text.

The Deployment Manager process completes.

None

A scheduled event ended due to a connection failure. The scheduled event had to be restarted outside of its normal start-up window to continue the operation.

Be advised that there are multiple sessions associated with the scheduled event.

None.

An access denied error occurred while attempting to access NTFS security info rmation.

The object is skipped.

See your system administrator or bypass the failing check by using SkipNTSecu rity option.

The user account running Tivoli Storage Manager does not possess a required NT user right/pr ivilege for performing the current operation.

The object is skipped.

Your system administrator has the authority to grant the needed privilege.

Access to the specified file or directory is denied. You tried to read from or write to a file and you do not have access permission for either the file or the directory.

Processing stopped.

Ensure that you specified the correct file or directory name, correct the permissions, or specify a new location.

You tried to restore or retrieve a file that is currently not available from the Tivoli Storage Manager server.

Tivoli Storage Manager cannot restore or retrieve the file.

Try to restore or retrieve after the file was made available on the server. See your system administrator.

The specified directory is being used by another process. You tried to read from or write to directory that is currently being used by another process. The objects contained in the directory and its subdirectories are not backed up.

Processing stopped for that directory. If other files and directories were also specified in this backup, they are processed.

Ensure that you specified the correct directory name; Correct the permissions, or specify a new location. If the directory name is correct, retry the backup when no process has exclusive use of the directory.

This is a message sent by the application that you are currently running with Tivoli Storage Manager.

Tivoli Storage Manager logs the application message.

Refer to the documentation for the application that you are using.

This is a message sent by the application that you are currently running with Tivoli Storage Manager.

Tivoli Storage Manager logs the application message.

Refer to the documentation for the application that you are using.

This is a message sent by the application that you are currently running with Tivoli Storage Manager.

Tivoli Storage Manager logs the application message.

Refer to the documentation for the application that you are using.

This is a message sent by the application that you are currently running with Tivoli Storage Manager.

Tivoli Storage Manager logs the application message.

Refer to the documentation for the application that you are using.

The message text and inserts were too large to send to the server in the available internal buffer.

Refer to the local client error log for more information

None.

An internal error has occurred in an attempt to create a server database table. This message always accompanies another error message and provides more detail about that error.

The activity that generated this error fails.

Contact your service representative.

An internal error has occurred in an attempt to access a server database table. This message always accompanies another error message and provides more detail about that error.

The activity that generated this error fails.

If the server or storage agent is stopping in response to a HALT command and this message is encountered it can be ignored. Otherwise contact your service representative.

An internal error has occurred in an attempt to add data to a server database table. This message always accompanies another error message and provides more detail about that error.

The activity that generated this error fails.

Contact your service representative.

An internal error has occurred in an attempt to update data in a server database table. This message always accompanies another error message and provides more detail about that error.

The activity that generated this error fails.

Contact your service representative.

An internal error has occurred in an attempt to remove data from a server database table. This message always accompanies another error message and provides more detail about that error.

The activity that generated this error fails.

Contact your service representative.

An internal error has occurred in an attempt to access data in a server database table. This message always accompanies another error message and provides more detail about that error.

The activity that generated this error fails.

Contact your service representative.

An internal error has occurred in an attempt to access data in a server database table. This message always accompanies another error message and provides more detail about that error.

The activity that generated this error fails.

Contact your service representative.

An internal error was detected during transaction commit. This message should be preceded by another error message which provides more detail about that error.

The activity that generated this error fails.

Contact your service representative.

An error occurred while attempting to start a new transaction. Possibly there is not enough memory.

The activity that generated this error fails.

See the documentation for the operating system about how to increase memory for an application.

An error occurred while attempting to load the cryptography module.

The application will not start.

Verify that the ICC cryptography directory is located in either the application root directory or the directory specified in the platform specific environment variable (the DSMSERV_DIR for Unix platforms or the Windows registry).

The server has noted that the current system date is suspect. It is earlier than the server install date or has suddenly moved into the future by 30 days or more.

The server is disabled for client, server and administrative access. Most server processes will not execute.

If the current system date is not valid, reset the date. Use the ACCEPT DATE command to establish the current date as valid on the server. After executing this command, you can use the ENABLE SESSIONS ALL command to enable the server for sessions. Accepting an invalid date can cause any of the following problems: Premature deletion of data Excessive retention of data Scheduling problems Event record problems Password expiration problems.

The BEGINNODEID and ENDNODEID are both required to be specified or neither of them are required.

The server fails the command.

Reissue the command, specifying both BEGINNODEID and ENDNODEID, or neither of them.

Either the BEGINNODEID or the ENDNODEID is invalid because the value of the BEGINNODEID is greater than the ENDNODEID.

The server fails the command.

Reissue the command, specifying the ENDNODEID to be greater than the BEGINNODEID, or both to be equal.

The storage pool name specified has been specified more than once. The name occurs more than once in the COPYSTGPOOLS list, more than once in the ACTIVEDATAPOOLS list, or it has been specified in both lists.

The command fails.

Reissue the command specifying unique storage pool names.

The NUMBER parameter is required for the FORMAT LFVOLUME COMMAND when the LFVOLUMEFORMATCOUNT option is set to 0.

The command is not executed.

Either reissue the command with the NUMBER parameter or else use the the SETOPT command to change the LFVOLUMEFORMATCOUNT value.

The server waits for all previous parallel commands started by the script to complete. When all previous parallel commands are complete, the server allows the script to continue. The script can attempt to start more parallel commands.

The server waits for all previous parallel commands before allowing the script to continue.

If you need to start more parallel commands than the script limit allows, modify the script to invoke multiple scripts in parallel, each of which can start multiple parallel commands, up to the script limit.

The server waits for all previous parallel commands started by the script to complete. When all previous parallel commands are complete, the server allows the script to continue. The script can attempt to start more parallel commands. If the limit is exceeded, the command will run serially.

The server waits for all previous parallel commands before allowing the script to continue.

Reduce the number of parallel commands or scripts that are running on the server at any one time.

The archive data retention protection state cannot be changed while the server contains any backup, archive, or space-managed data.

Processing continues.

In order to change the archive data retention protection state, the server must contain no backup, archive, or space-managed data. Either re-initialize the server database, or delete all stored data and try the command again.

The client options INCLUDE and EXCLUDE are not valid and have been replaced by the combined INCLEXCL. If INCLUDE and EXCLUDE are used in client option sets, use the INCLEXCL option along with the specific include or exclude option that you want the clients to use.

The option is ignored and is not sent to the client. The server continues processing.

Client options INCLUDE and EXCLUDE are not valid; use the INCLEXCL option along with the specific include or exclude option that you want the clients to use.

The client option is not supported by this server and should be deleted from the client option set.

The option is ignored and is not sent to the client. The server continues processing.

Delete the option from the option set. Check the documentation for a possible replacement for the option.

The archive data retention protection state has been set.

Processing continues.

None.

The specified command is not allowed when archive data retention protection is enabled on the server.

Processing continues.

None.

A previously defined node cannot be assigned to a new domain when archive data retention protection is enabled on the server.

Processing continues.

None.

The specified device type is not allowed when archive data retention protection is enabled on the server.

Processing continues.

None.

The specified object can not be deleted because:

• Archive retention protection is enabled and the object's retention period has not elapsed, or
• The object is part of a deletion hold.

Server operation continues.

None.

The specified file space cannot be deleted because it contains one or more objects that must be retained for one of the following reasons:

• Archive retention protection is enabled and the object's retention period has not elapsed.
• The object is part of a deletion hold.

The file space is not deleted.

None.

The specified volume cannot be deleted because it contains one or more objects that must be retained because of one of the following:

• Archive retention protection is enabled and the object's retention period has not elapsed.
• The object is part of a deletion hold.

Processing continues.

None.

The specified command is not allowed when data retention protection is enabled on the target server.

Processing continues.

None.

At server startup, the server discovered that a previously started database upgrade operation did not complete successfully. To complete the database upgrade, specify the UPGRADEDB parameter when starting the server.

Processing continues.

Check the server error messages on console to determine the reason the previous database upgrade did not complete successfully. Correct the problem, and perform the database upgrade again, if possible. If the problem cannot be corrected, contact your service representative.

The requested database upgrade operation completed successfully.

Processing continues.

None.

There is no space to write data to the server recovery log.

The activity that generated this error fails.

To increase the amount of log space available to the server, evaluate the directories and filesystem assigned to the ACTIVELOGDIR, ARCHIVELOGDIR, and ARCHFAILOVERLOGDIR. An out of log space condition may occur because the ACTIVELOGDIR location is full. Alternatively, an out of log condition may occur if the log files in the ACTIVELOGDIR which are no longer active can not be archived to the ARCHIVELOGDIR and ARCHFAILOVERLOGDIR locations. If necessary, a larger ARCHIVELOGDIR or ARCHFAILOVERLOGDIR can be specified by updating this option in the dsmserv.opt file and then restarting the server.

There is no space to write data to the server database.

The activity that generated this error fails.

To increase the amount of database space available to the server, an authorized administrator can add database volumes by using the DEFINE DBSPACE command. Once additional space has been added for the database, the server database manager will automatically extend into that space and use it.

The server cannot obtain enough memory to create the object named.

The activity that generated this error fails.

See the documentation for the operating system about how to increase memory for an application.

The error specified by error string occurred when the server attempted to load module modname

Server operation continues, but the function provided by the module is not available.

Refer to the error string and correct the condition causing the load to fail.

Warning: warning string

Server operation continues, but standard input is not available.

If the server was started in the background, there is no error, or else standard input is in an error state.

The server periodically performs maintenance on the database tables. The maintenance processing allows the database to update statistics used to determine how to best access a given table. The maintenance processing will periodically process all tables for the server. And during other processing cycles, it will only process those tables that have changes such as inserts, updates, or deletes for records in that table.

Server operation continues.

No user action required.

The server periodically performs maintenance on the database tables. The maintenance processing allows the database to update statistics determine how to best access a given table. The maintenance processing will periodically process all tables for the server.

Server operation continues.

No user action required.

An internal error has occurred in an attempt to allocate storage for the requested number of database rows indicated.

The activity that generated this error fails.

Contact your service representative.

The command has been issued with an invalid number of primary logs.

Server installation stops.

Reissue the command with a valid number of primary logs.

During DB2® development cycle. This command/function has been temporarily disable.

System operation continues.

None.

The command was successful.

The server performs the command.

None.

The command fails if either of the nodes do not exist, or if the administrator issuing the command does not have sufficient authority.

The server fails the command.

Verify that both nodes exist and that the administrator has sufficient authority, then issue the command again.

The command was successful.

The server performs the command.

None.

The command fails if the administrator issuing the command does not have sufficient authority.

The server fails the command.

Check the help for the command and verify that the administrator has either system or unrestricted policy authority; then issue the command again.

The command failed because one of the nodes has not been defined to the server.

The server fails the command.

Verify that both nodes have been defined to the server and then issue the command again.

The command failed because a proxy relationship between the two nodes already exists.

The server fails the command, but does not change the existing association.

None.

The command failed because a node cannot have a proxy relationship defined to itself.

The server fails the command.

None.

The command failed because one of the nodes has not been defined to the server.

The server fails the command.

Verify that both nodes have been defined to the server, and then issue the command again.

No proxy relationships were found.

None.

None.

The command failed. The requested filespace was deleted concurrently with the command.

The server will fail the command.

Retry the command.

The server could not open the object specified due to the error encountered while decrypting the password.

The server will fail the related command or action.

Reset the password using the appropriate UPDATE command and retry the failing command or action.

The server was unable to start the database manager.

The server operation terminates.

If the server is not able to run without the database manager. Evaluate recent changes to the server machine and the available system error logs to try to determine the cause of the failure.

The server was successfully able to start the database manager.

The server operations continue.

None.

The server database manager is already running.

The server continues startup.

None.

The number of active data pool names that can be specified with the ACTIVEDESTINATION parameter is limited to 10, and the names entered with this parameter must be unique.

The command fails.

Reissue the command specifying unique active-data pool names.

The number of active data pool names that can be specified with the ACTIVEDESTINATION parameter is limited to 10, and the names entered with this parameter must be unique.

The command fails.

Reissue the command specifying unique active-data pool names.

The storage pool specified is not an active-data pool. Only active-data pools are allowed to be specified in the ACTIVEDESTINATION parameter.

The command fails.

Reissue the command specifying ten or fewer active-data pool names.

An error occurred during the specified table operation for the table indicated.

The activity that generated this error fails.

If there were no operational failures as a result of issue, then this was anticipated and the server was able to continue appropriately. If this resulted in a failure for a client session or server process, this information is needed to help diagnose the issue. In the even of a failure, please contact your IBM® service representative for further assistance.

An error occurred during the specified table operation for the table indicated.

The activity that generated this error fails.

If there were no operational failures as a result of issue, then this was anticipated and the server was able to continue appropriately. If this resulted in a failure for a client session or server process, this information is needed to help diagnose the issue. In the even of a failure, please contact your IBM service representative for further assistance.

The database server detected a deadlock situation and rolled back the outstanding work on this statement handle. When server processes encounter a database deadlock, they usually reattempt the work that was in progress when the deadlock was encountered. Not all processes can explicitly try an operation again. For example, migration and reclamation will eventually be tried again. However, something such as a delete volume run in a macro will only be tried again if the delete command is reissued either in the macro or the command line.

The work being done on the statement handle is rolled back. Some processes will attempt to retry the request. Others will just stop. Server operation continues.

If a process can retry (like migration), then monitor the re-try attempt to see if it succeeds or not. If the process or command is not able to retry on it's own, then reissue the command or macro that caused the action to occur.

Display a client object, such as a file or directory, that uses a long fully qualified name. The name is displayed in smaller segments until the entire name is shown. The segment numbers are incremented from 1 to N until all the segments for this object name are displayed.

The fully qualified name for this object is displayed.

None.

Display a segment of a message insert that was too long to be displayed within the specified message. There may be one or more segments displayed for a given message insert.

The entire message insert segment is displayed.

None.

The dbReturnCode, dbState, and dbCode are displayed as supplemental information. This information should be used in conjunction with any other database error or warning messages issues to assist with diagnosing a given issue.

The activity that generated this error fails.

None. This is supplemental information corresponding to another database error or warning message issued.

The database server detected an insufficient memory condition and rolled back the outstanding work on this statement handle.

The work being done on the statement handle is rolled back. Server operation continues.

See the documentation for the operating system about how to increase memory for an application.

Inventory file expiration processing started processing for the node name and filespace name indicated. For this node name and filespace name the indicated copygroup and object types are currently being evaluated.

Inventory file expiration continues.

This message is for informational purposes only and is only displayed if the expiration processing is executed with QUIET=NO.

Inventory file expiration processing finished processing for the node name and filespace name indicated. For this node name and filespace name the indicated copygroup and object types were evaluated. And the ending statistics show the number of objects examined, deleted, retrying and those that failed to be processed.

Inventory file expiration continues.

This message is for informational purposes only and is only displayed if the expiration processing is executed with QUIET=NO.

Server expiration processing ran for the indicated number of minutes.

None.

None.

Analyst authority is not supported for servers at V6.1 or later.

The operation continues.

None.

The TSM server encountered an error from which it cannot recover, and the server is halting. Other messages will be issued along with this message indicating the specific error conditions which have occurred.

The server halts.

Follow the instructions indicated in any associated messages, then start the server.

The TSM server encountered an error on the database and needs to issue a DB2 RESTART DB to the database manager. All connections to the database server are severed, and uncompleted operations are aborted. The TSM server will then restart the database and attempt to continue. If the database manager cannot be restarted, the TSM server will halt. Other messages may be issued along with this message indicating the specific error conditions which have occurred.

The server continues, or if it cannot restart the database, it halts.

If the server is able to recover, no action is needed, except to restart operations that were aborted. However, if the server cannot recover, it will halt. Follow the instructions indicated in any associated messages, then start the server. If the server still cannot be started, manually issue the DB2 RESTART DB command, then attempt to start the TSM server again.

The TSM server encountered an error on the database and will take action to determine the type of error and whether or not it can recover from the error.

Server processing continues.

This is an information message. As the TSM server attempts to resolve the error, it might issue other messages. Follow the instructions indicated in any associated messages.

The TSM server encountered an error performing the specified database action. This error caused the action to fail and prevented the server from being able to continue.

Server processing terminates, the requested action fails.

Review other messages issued to determine the actual error and then take steps to remedy that failure before retrying the operation.

The TSM server encountered an error while performing the specified action. Specifically, the server database did not have sufficient memory to communicate with the server database or was unable to acquire the memory needed for the server buffer pools.

Server processing terminates, the requested action fails.

In most cases, this indicates a lack of available resources on the system. This may be a lack of physical resources or it may be an environment setting that prevents the server from having access to the needed resources. For instance, on Linux systems, this may be caused by the SHMMAX value (maximum allowed shared memory) being set too low. On Linux, this can be viewed using the command "ipcs -l". Similarly, for Linux, this value can be increased using the command "sysctl -w kernel.shmmax=nnn" where nnn is the new maximum memory value to assign to be used for shared memory. As a general recommendation, this value should be set to approximately 1.25 GB or higher depending upon the actual physical memory (RAM) available on that system.

There are no more available connections to the server database.

The activity that generated this error fails.

To increase the number of database connections available to the server, the DB2 administrator can modify the IDBACK parameter in the DSNzPARM settings.

The space assigned to the server database, the recovery log, or instance directory has been exhausted.

The server terminates.

Review the filesystems or other space assigned to the server for the database, recovery log or instance directory. If the space assigned to the database is full, restart the server and add additional database space using the EXTEND DBSPACE command or use the DSMSERV EXTEND DBSPACE utility. If the server ACTIVELOGDIR is full, update this server option to a new location that has space available for the server to use for logging changes to the database. If the server instance directory is full, remove unneeded files or else extend this filesystem.

Please note that the server should be configured with the database, activelog, and archivelogs using different directories and storage devices. For example, if the database and activelog are configured to use the same directory and underlying storage device, this may adversely impact performance. This may also compromise the server's ability to manage the database and active log space effectively. Similarly, the server's instance directory should also be monitored and managed with some amount of space available. The server instance directory is used to record and log some server and database actions.

The command fails.

Define the active-data pool to a domain using the ACTIVEDESTINATION parameter on either the DEFINE DOMAIN or UPDATE DOMAIN command.

If the server is starting, then the user ID under which the dsmserv process is running does not have authority to start the database manager. If the server is running, it does not have sufficient authority to perform the server operations.

The server process ends, and the server stops if it is running.

Ensure that the user ID under which the server is running is authorized to start the database manager. Take the following actions:

• Log in to the user ID for your Tivoli Storage Manager instance and start the server.
  • To run the server using the root user ID on a UNIX system, add the root user ID to the primary group of the Tivoli Storage Manager instance user ID.
  • Or, to run the server using the instance user ID on a UNIX system, when using the automatic start, specify the -u option when you start the server.

The server attempted to open the database, but it was not found by the database manager. If this occurs immediately after formatting a new database, it could mean the format operation failed.

The server process ends.

Ensure that you format the database before starting it the first time. Ensure that all database and log directories are online and available.

Could not find database manager license.

The server process ends.

Contact your service representative.

Database manager license has expired.

The server process ends.

Contact your service representative.

Expiration processing is currently evaluating information for backup sets for the node specified.

Inventory file expiration continues.

This message is for informational purposes only and is only displayed if the expiration processing is invoked with QUIET=NO.

Expiration processing has finished processing backup sets for the node specified.The ending statistics show the number of objects examined, deleted, and those that failed to be processed.

Inventory file expiration continues.

This message is for informational purposes only and is only displayed if the expiration processing is invoked with QUIET=NO.

The specified REPAIR EXPIRATION command was issued from the server console. This command cannot be issued from the server console because the administrator must be prompted to continue processing the command.

The server ignores the command and continues processing.

Issue the command from an administrative client.

The server is attempting to remove extraneous database entries for the specified volume.

TSM will attempt to remove the extraneous database entries for this volume.

Review the completion messages for this volume to determine if the removal of the extraneous database entries was successful or if an error was encountered.

The server successfully removed extraneous database entries for the specified volume.

System operation continues and future operations on the specified volume should work normally.

The server successfully repaired the specified volume.

The server was not able to remove extraneous database entries for the specified volume. This was due to contention with another server process or activity.

System operation continues and this volume still has extraneous database entries.

It is possible that future server activities or processes will select this volume and attempt to repair it. If this occurs and the future attempt is successful, no further action is needed. The server administrator should review the activity log for the time that the repair was attempted and try to determine what caused the contention. If you are unable to determine the cause of the contention of the problem persists, please contact your service representative for additional assistance.

The server was not able to remove extraneous database entries for the specified volume.

System operation continues and this volume still has extraneous database entries.

The server administrator should review the activity log for the time that the repair was attempted and try to determine the cause of the failure. If you are unable to determine the cause of the contention of the problem persists, please contact your service representative for additional assistance.

The server was not able to remove extraneous database entries for the specified volume because other database references to this volume exist.

System operation continues.

The volume repair operation for this volume is not able to take any action because other unexpected database references to this volume exists. For additional assistance contact your IBM service representative.

The amount of space allocated to the recovery log is shown.

None.

None.

The amount of space allocated to the database is shown.

None.

None.

The database volume shown has been varied offline because too many read errors have been encountered.

If available, a mirrored copy of the volume is used.

Correct the cause of the read errors.

The database volume shown has been varied offline because too many write errors have been encountered.

If available, a mirrored copy of the volume is used.

Correct the cause of the write errors.

The recovery log volume shown has been varied offline because too many read errors have been encountered.

If available, a mirrored copy of the volume is used.

Correct the cause of the read errors.

The recovery log volume shown has been varied offline because too many write errors have been encountered.

If available, a mirrored copy of the volume is used.

Correct the cause of the write errors.

During a write of a database page, an error occurred so that the page was not completely written to disk.

The failed I/O operation is retried on a mirrored volume.

See accompanying messages for information about the volume in error.

During a read of a database page, the page does not contain the expected page address.

The failed I/O operation is retried on a mirrored volume.

See accompanying messages for information about the volume in error.

During a write of a recovery log page, an error occurs so that the page is not completely written to disk.

The failed I/O operation is retried on a mirrored volume.

See accompanying messages for information about the volume in error.

During a read of a recovery log page, the page does not contain the expected page address.

The failed I/O operation is retried on a mirrored volume.

See accompanying messages for information about the volume in error.

During a write of an LVM internal page, an error occurs so that the page is not completely written to disk.

The failed I/O operation is retried on a mirrored volume.

See accompanying messages for information about the volume in error.

During a read of an LVM internal page, the page does not contain the expected page address.

The failed I/O operation is retried on a mirrored volume.

See accompanying messages for information about the volume in error.

At startup, the server cannot read the indicated file in order to obtain a list of disk volumes to mount.

Server initialization fails.

Use a text editor to recreate the file; it should contain one line with the name of a single log or database volume. Then restart the server.

An error occurs trying to update the disk definition file.

None.

Attempt to determine the cause of the write error and correct it.

At system startup, the server finds that the specified database volume is in the offline state.

The volume is not accessed.

Determine the reason for the volume being offline; if possible, vary it online.

At system startup, the server finds that the recovery log volume shown is in the offline state.

The volume is not accessed.

Determine the reason for the volume being offline; if possible, vary it online.

At system startup, the server finds that the database volume shown is not synchronized.

A process is started to synchronize the volume.

None.

At system startup, the server finds that the recovery log volume shown is not synchronized.

A process is started to synchronize the volume.

None.

An attempt has been made to add a database volume that is smaller than the server minimum.

The volume is not added.

Increase the size of the volume or supply another larger volume.

An attempt has been made to add a recovery log volume that is smaller than the server minimum.

The volume is not added.

Increase the size of the volume or supply another larger volume.

A background process was started to synchronize the contents of the database volume shown with its copy volume. The background process was assigned the process ID shown.

The background process starts to synchronize the volume and server operation continues.

The administrator may query the status of the background process by using the QUERY PROCESS command, or cancel the process by using the CANCEL PROCESS command.

A background process was started to synchronize the contents of the recovery log volume shown with its copy volume(s). The background process was assigned the process ID shown.

The background process starts to synchronize the volume and server operation continues.

The administrator may query the status of the background process by using the QUERY PROCESS command, or cancel the process by using the CANCEL PROCESS command.

An error occurred creating or changing the disk definition file.

None.

Attempt to determine the cause of the write error and correct it.

The disk definition file cannot be written.

Installation ends.

Determine the cause of the write error and correct it.

The specified volume name was specified more than once in the server installation execution.

Installation ends.

Reinitialize the server install specifying a unique name for each database and recovery log volume.

The -S option cannot be specified on the command line if the database ID file (dsmserv.dbid) is intact. This option is to be used only if the ID file does not exist.

The server does not start.

Start the server without specifying the -S command-line option.

The server's database ID file (dsmserv.dbid) could not be found. This file is created when the database is formatted, is stored in the directory from which the format is performed, and is required for normal server operation.

The server does not start.

Ensure that you are starting the server from the correct instance directory, and that the dsmserv.dbid file exists and can be read. If no dsmserv.dbid file exists, restart the server with the -S option to create a new database ID file.

The ID of the database opened does not match the ID stored in the database ID file (dsmserv.dbid).

The server does not start.

Ensure that you are in the proper instance directory for the database being opened, and that the environment is set up correctly. The instance directory is generally the directory from which you formatted the database, or, if on UNIX, have specified with the -i command-line option.

When the ID of the database that is opened does not match the ID that is stored in the database ID file (dsmserv.dbid), the server will not start. Use the -S (skip DB ID check) parameter after deleting the dsmserv.dbid file. After the initial use of the -S parameter in a restore scenario, the server creates a new dsmserv.dbid file in the instance directory.

The server's database ID file (dsmserv.dbid) could not be opened. The errno indicates the reason for the failure.

The server does not start.

Ensure that you are starting the server from the correct instance directory, and that the dsmserv.dbid file has the correct ownership and permission. If the file is empty, erase the file, and restart the server with the -S command-line option to generate a new database ID file.

The process that monitors the default (console) output stream and maintains the activity log cannot update the activity log. The error is due to the inability of the server to access the server database.

The server does not update the activity log. The activity log will continue to run and attempt to recover from this situation.

Access to the server database is temporarily unavailable. The server database manager will attempt to recover from this situation and reestablish access to the server database. When access to the server database is reestablished, the activity log processing will continue. If the server database access fails to be reestablished, additional messages will be issued providing more information.

The process that was attempting to synchronize the database volume shown has failed.

The volume is in the stale state.

See accompanying messages for more information.

The process that was attempting to synchronize the recovery log volume shown has failed.

The volume is in the stale state.

See accompanying messages for more information.

The process that was attempting to synchronize the database volume shown has been canceled.

The volume is in the stale state.

If desired, issue a VARY ONLINE command to start another synchronize process.

The process that was attempting to synchronize the database volume shown has been canceled.

The volume is in the stale state.

If desired, issue a VARY ONLINE command to start another synchronize process.

The synchronization process for the database volume named has finished successfully.

The volume is varied online.

None.

The synchronization process for the recovery log volume named has finished successfully.

The volume is varied online.

None.

The TSM server encountered an I/O error while attempting to start the database manager.

The server process ends.

Review the filesystems assigned to the server for the database and recovery log.

An unexpected system error occurred.

Some common reasons for this error are:

• The system name where you ran the server has been changed
• The system date and time is set incorrectly

The server process ends.

Contact your service representative.

While attempting to activate the database an error occured because the database was busy performing a BACKUP, RESTORE or was in ROLLFORWARD pending state. Examine the sqlcode to determine the condition that is preventing the database from activating. The following sqlcodes are most likely to occur during the activate database step and will prevent the server from starting. SQLE_RC_BKP_PEND ( -1116 ) indicates a database BACKUP is pending and must complete prior to activating the database. Once the database BACKUP is complete,the database can be activated by starting the server. SQLE_RC_ROLLFWD_PEND ( -1117 ) indicates a database Roll Forward operation is pending and must complete before activating the database. After the Roll Forward recovery step is complete, the database can be activated by starting the server. SQLE_RC_BKP_INPROG ( -1118 ) occurs when an attempt to activate the database fails because a database BACKUP was in progress. Prior to activating the database, it is necessary to rerun database BACKUP. Once the database BACKUP completes successfully, the database can be activated by starting the server. SQLE_RC_RST_INPROG ( -1119 ) shows that a database RESTORE was in progress when the database failed to activate. The RESTORE database must be restarted and allowed to complete successfully before activating the database. Once the database RESTORE in complete, the database can be activated by starting the server. SQLE_RC_BR_INPROG ( -1120 ) means that either a database BACKUP or RESTORE must complete before activating the database. Ensure that either a BACKUP or RESTORE operation completes successfully before activating the database.

The server is not started because the database cannot be activated.

See message explanation for more information.

TSM Server attempted to connect using the database instance set by the DB2INSTANCE environment variable, but the attempt failed.

The server is not started because the database instance is not valid.

Verify that the database instance exists and that it is configured properly. You can list DB2 instances by issuing the db2ilist command from the instance directory, under the DB2 installation directory. Example: c:\Program Files\tivoli\tsm\db2\instance\db2ilist

The process that was attempting to delete the database volume shown has failed.

The volume is not deleted.

See accompanying messages for more information.

The process that was attempting to delete the recovery log volume shown has failed.

The volume is not deleted.

See accompanying messages for more information.

The process that was attempting to delete the database volume shown has been canceled.

The volume is not deleted.

None.

The process that was attempting to delete the recovery log volume shown has been canceled.

The volume is not deleted.

None.

The delete process for the database volume named has finished successfully.

The volume is deleted.

None.

The delete process for the recovery log volume named has finished successfully.

The volume is deleted.

None.

An error has been encountered when attempting to read a page from the specified database volume.

The failed I/O operation is retried on a mirrored volume, if available.

See accompanying messages for information about the volume in error. If the error persists and another mirrored copy of the volume is available, the failing volume should be taken offline by using the VARY OFF command, and repaired. Otherwise, halt the server and repair the volume. Then restart the server.

After a read error, the server is able to read the desired page from another synchronized mirrored volume.

Processing continues.

None.

After a read error, the server is unable to read the desired page from another mirrored volume because no other mirrored volume is in the synchronized state. This message is normally preceded by a message indicating which volume failed.

Processing is ended.

You can repair the failed volume by halting the server and correcting the volume errors.

An error has been encountered when attempting to read a page from the specified recovery log volume.

The failed I/O operation is retried on a mirrored volume, if available.

See accompanying messages for information about the volume in error. If the error persists and another mirrored copy of the volume is available, the failing volume should be taken offline, by using the VARY OFF command, and repaired.

After a read error, the server is able to read the desired page from another synchronized mirrored volume.

Processing continues.

None.

After a read error, the server is unable to read the desired page from another mirrored volume because no other mirrored volume was in the synchronized state. This message is normally preceded by a message indicating which volume failed.

Processing is ended.

You can repair the failed volume by halting the server and correcting the volume errors.

An error has been encountered when attempting to write a page to the specified database volume.

If a mirrored volume is available then the failing volume is forced into the offline state.

Repair the failing volume, and then use the VARY ON command to bring the volume back online.

After a write error, the server is unable to write the desired page to another mirrored volume because no other mirrored volume is in the synchronized state. This message is normally preceded by a message indicating which volume failed.

Processing is ended.

Repair the failed volume.

An error has been encountered when attempting to write a page to the specified recovery log volume.

If a mirrored volume is available, the failing volume is forced into the offline state.

Repair the failing volume, and then use the VARY ON command to bring the volume back online.

After a write error, the server is unable to write the desired page to another mirrored volume because no other mirrored volume is in the synchronized state. This message is normally preceded by a message indicating which volume failed.

Processing is ended.

You can repair the failed volume by halting the server and correcting the volume errors.

An error has been encountered when attempting to write a page to the specified database volume.

If a mirrored volume is available, the failing volume is forced into the offline state.

Repair the failing volume, and then use the VARY ON command to bring the volume back online.

An error has been encountered when attempting to write a page to the specified database volume.

If a mirrored volume is available, the failing volume is forced into the offline state.

Repair the failing volume, and then use the VARY ON command to bring the volume back online.

While writing restart/checkpoint information to disk, the server encounters an error writing to a database or recovery log volume for which no synchronized mirrored copy is available. This message is normally preceded by a message indicating which volume failed.

Processing is ended.

Repair the failing volume.

During server restart, the server is unable to read a complete set of restart/checkpoint information from any of the defined database or recovery log volumes.

Server restart is ended.

Ensure that all defined database and recovery log volumes are available for use by the server.

After detecting a partially-written database page, the server is able to rewrite the page by using a synchronized mirror copy.

Processing continues.

None.

After detecting a partially-written recovery log page, the server is able to rewrite the page by using a synchronized mirror copy.

Processing continues.

None.

The restart/recovery area of the server database and recovery log volumes were written in a format that is not compatible with the restart/recovery area written by other versions of the server.

The server starts normally. If the database and recovery log are writable (not Read Only), then the restart/recovery area will be converted to a compatible format. Message ANR0263I will be issued when the conversion has been completed.

None.

The server converted the restart/recovery areas of its database and recover log volumes to a format compatible with the restart/recovery area written by other versions of the server. This is a one time conversion, and will only be performed if the restart/recovery area was not already in the compatible format.

The restart/recovery area was successfully converted.

None.

While attempting to activate the database an IO error occured when processing a database file. The problem may have occurred in one of the following situations: The system cannot open, read from, or write to a database file. The system cannot create the database because an error occurred while the system was creating a database file or a directory for the database. The system cannot drop the database because an error occurred while the system was deleting a database file or a directory for the database. The system cannot create the database because an interrupt was received while the system was creating or deleting a database file or a directory for the database. The system cannot locate the database subdirectory or database configuration file during connect. Problem causes are ordered in terms of their frequency of occurrence: A log file cannot be found in the active log path directory. There may be a problem with the database directory the operation is being attempted on. There may be inadequate disk space to complete the operation. The database cannot be used.

The server is not started because the database cannot be activated.

Appropriate responses for the problem causes described above are: To verify if a log file is missing, check the db2diag.log for the presence of a logging error (return code contains SQLO_FNEX). If present, this error will contain the name of the missing log file. Ensure that the file is located in the active log path directory. If the file cannot be located, restore and roll-forward the database to an earlier point in time referenced in a log file preceding the missing log file (use a timestamp that is earlier than that of the missing file). There may be a problem with the database directory. Check the integrity of the directory. Examples of potential problems include: permissions issues, mount point problems, corruption. Increase filesystem size.

At server installation, the server is unable to process the server log disks due to insufficient memory.

Server installation stops.

Restart the server installation process with more memory available.

At server installation, the server is unable to process the server database disks due to insufficient memory.

Server installation stops.

Restart the server installation process with more memory available.

The specified volume cannot be found during installation.

Server installation stops.

Determine the reason the disk is unavailable, and correct the problem. Restart the server installation process.

The specified volume cannot be found during installation.

Server installation stops.

Determine the reason the disk is unavailable, and correct the problem. Restart the server.

During installation for the indicated volume, the server cannot start a thread to service I/O requests.

Server installation stops.

See the documentation for the operating system about how to increase memory for an application.

Restart the server installation process.

During installation for the indicated volume, the server cannot start a thread to service I/O requests.

Server installation stops.

See the documentation for the operating system about how to increase memory for an application.

Restart the server installation process.

More recovery log volumes have been specified than the server can manage.

Server installation stops.

Reduce the number of recovery log volumes specified. Restart the server installation process.

More database volumes have been specified than the server can manage.

Server installation stops.

Reduce the number of database volumes specified. Restart the server installation process.

The External Library is set offline. It will not be used for new transactions until it is set online again.

This server skips the initialization of the library. The server continues processing.

Refer to the UPDATE PATH command for details on changing the online option.

The External Library is set offline. It will not be used for new transactions until it is set online again.

This mount fails.

Refer to the UPDATE PATH command for details on changing the online option.

The schema for the table referenced does not match the server definition for this table. The schema difference for this table will be reconciled.

Server startup continues if the schema difference was successfully reconciled. Server startup will fail if the schema reconciliation failed.

The schema for this table will attempt to be reconciled. Specifically, the server will try to modify the table in the database to match the schema that was expected. A message will be issued indicating the success or failure of the schema reconciliation.

The schema differences for this table were successfully reconciled.

Server operation continues.

None

The server was unable to reconcile the schema differences for the indicated table.

Server operation terminates.

Contact your IBM service representative.

Server operation stops.

Stop other applications running on the system, especially those that use large amounts of shared memory.

The database manager license key is invalid or was removed.

The server operation stops.

You can issue the following command, which displays the information about the database and its license status. Report the output to your service representative: db2licm -l

The database page shadowing function was started. The file specified is used to store the shadowed database pages.

None.

None.

The database page shadowing function could not start. An error has been encountered accessing the page shadow file specified.

None.

Verify that there is enough space for the page shadow file. That page shadow file requires approximately 65 kilobytes of space, if this space is not available a new location for the file should be specified.

The database page shadowing function could not use the contents of the existing file. Restart recovery using this file is not possible.

The server attempts to start without having the database page shadow file available.

The database page shadow file contents are not valid. This can be caused by: a partial write to the page shadow file itself, the file being manipulated by a process outside of the server, the file being overlaid by a different file, or the file could have been erased.

One or more pages from the last batch of pages written to the server database has been detected to be corrupt. The server will attempt to use the contents of database page shadow file and replace the corrupted database page.

Server startup continues.

A corruption of a database page within the server database, is typically caused by a partial write. A partial write may occur when the server is brought down external to normal server processing. If the server terminated without a halt command being issued or if the machine the server is running on crashed unexpectedly, this may account for the partial write. Other possible causes of a partial write are a disk drive failure, improperly terminated SCSI bus, or a failure in a device controller. Please try to identify the cause of the partial write and take the appropriate action to prevent this from occurring in the future.

The damaged database pages were replaced using the corresponding pages from the page shadow file. The pages were successfully replaced.

The server continues to restart.

None.

The damaged database pages could not be replaced using the corresponding pages from the page shadow file.

The server continues to restart.

None.

The server encountered an error writing to the database page shadow file. The page shadowing for the server is currently disabled.

Database page shadowing for the server will remain disabled until the server is halted and restarted.

Check the file specified as the database page shadow file. It may be that there is not enough space for the file. If enough space is available, check the filesystem, drive, or disk that it resides on for an indication of the error. Once the error preventing the server from writing to the page shadow file has been resolved, restart the server.

The server attempted to use the page shadow file referenced but was unable to open the file. The file does not exist.

The server will continue to operate and will attempt to create this as a new database page shadow file.

None.

The server is performing an online reorganization for the table referenced.

The server will continue to operate.

Monitor the available log space in the active log and archive log storage paths. If the log space available to the filesystem begins to fill up, then perform a BACKUP DATABASE command with the TYPE=FULL parameter in order to initiate pruning of the archive log space.

The server online reorganization for the table referenced has ended.

The server will continue to operate.

Review the available log space in the active log and archive log storage paths. If the log space available to the filesystem has to filled up or is close to filling up, then perform a BACKUP DATABASE command with the TYPE=FULL parameter in order to initiate pruning of the archive log space.

When the active log space used exceeds the log utilization threshold, a database backup is needed.

None.

None.

When the space used in the log file system exceeds the threshold for log file system utilization, a full database backup is required.

None.

None.

When the log space used since the last database backup exceeds the maximum log file size, either a full database backup is required, or the maximum log file size must be increased.

None.

None.

If the server is starting, then the user ID under which the dsmserv process is running does not have sufficient authority to access the database. If the server is running and a server operation failed, then the user ID does not have sufficient authority to perform the operation.

If the server is starting, the dsmserv process ends. If the server is running, the server stops.

Ensure that the user ID under which the server is running is either the instance user ID, or is authorized to access the database.

Initial formatting of the server recovery log has started.

The log is formatted for use by the server.

None.

The amount of the server recovery log shown has been successfully formatted.

Formatting continues.

None.

Formatting of the recovery log has completed and took the number of milliseconds shown.

None.

None.

During formatting, the formatter processed the number of pages indicated each second.

None.

None.

During formatting, the formatter required the number of milliseconds indicated to process each page.

None.

None.

Formatting of the server recovery log completed successfully.

None.

None.

During restart, the server is mounting required recovery log volumes.

None.

None.

As a result of an EXTEND LOG command, the additional recovery log pages are being formatted.

Formatting continues.

None.

The process started as a result of an EXTEND LOG command and has been canceled.

The EXTEND command is ended.

None.

As a result of a REDUCE LOG command, the amount of data from the recovery log shown has been moved.

The REDUCE LOG command continues.

None.

The process started as a result of a REDUCE LOG command and has been canceled.

The REDUCE command is ended.

None.

This message is issued to notify the administrator that the server recovery log utilization exceeds 90% or more of its assigned capacity.

Server operation continues.

• If the server is operating in NORMAL log mode, depending upon the size of your recovery log, add recovery log volumes, or extend the recovery log, or both, before it fills completely. Refer to the DEFINE LOGVOL, and EXTEND LOG commands for more information on these operations.
• If the server is operating in ROLLFORWARD log mode:
  • backup the database, or
  • define a database backup trigger if one is not already defined, or
  • lower the database backup trigger if one is defined
  Refer to the DEFINE DBBACKUPTRIGGER or UPDATE DBBACKUPTRIGGER commands.

The server encountered corrupted information in the recovery log. Typically, the corruption is caused by a hardware or environmental failure external to TSM.

Server operation terminates.

If the server database and recovery log are mirrored, set the MIRRORREAD LOG VERIFY and MIRRORREAD DB VERIFY options in the server options file and restart the server. If database and recovery log mirrors are not available, or all mirrors are corrupted, restore the server database to the latest backup and restart the server.

The storage agent referenced is not able to perform LAN-Free data movement operations using this storage pool and device class. The storage agent is back-level and is not able to support LAN-Free operations using this device class.

LAN-Free data movement operations are not performed. The operations are either sent via the LAN or else proxied by the storage agent directly to the server.

In TSM version 5.3, a change was made to the way the FILE and device classes are supported. This change prevents back-level storage agents from being able to use these device classes. The storage agent should be upgraded to the same version and release as the server. Until the storage agent is upgraded, any LAN-Free data movement operations that are attempted will be done using the LAN.

The storage agent is at an earlier version than the server and is not able to use advanced functions that were requested by a client.

The operation is not allowed.

The storage agent must be upgraded to a version, release, and level that supports this operation. Typically, the problem is that the storage agent and server are not at the same version and release. For example, if the server is version 5.3.0.0 and the storage agent is version 5.2.3.0, the storage agent needs to be upgraded to version 5.3.0.0 to perform the requested function.

If this was a restore or retrieve operation and the client node DATAREADPATH setting was ANY or LANFREE, the server will override this to be LAN only. This will cause the operation to fail on the storage agent and message ANR0416W to be issued. Retry the operation after performing one of the following actions:

• Halt the storage agent, upgrade the storage agent program, and then restart the storage agent.
• Set the ENABLELANFREE client option to NO, and then restart the client

If this was a no-query restore operation, the data was not restored by the storage agent using LAN-Free data transfer. If the client node is allowed to read data over the LAN, the data was restored over the LAN. If the operation failed because the client node is not allowed to read data over the LAN, consider updating the DATAREADPATH setting for this node by using the UPDATE NODE command.

If this was an operation performed by an agent node with proxy node authority to a target node, the session failed with a protocol error. The operation was attempted by a version 5.3 or higher client and server, but the storage agent is not able to support this operation. To allow an agent node to perform operations for a target node, the storage agent must be upgraded to version 5.3.0 or later.

The volume contains one or more deduplicated objects and must be restored to the original storage pool.

The operation is not allowed.

To restore the volume to the original storage pool, reissue the RESTORE VOLUME command without the NEWSTGPOOL parameter.

The storage pool contains deduplicated objects and must be restored to the original storage pool.

The operation is not allowed.

To restore the storage pool to the original storage pool, reissue the RESTORE STGPOOL command without the NEWSTGPOOL parameter.

While attempting to restore the database, the Tivoli Storage Manager server detects a missing value for ARCHIVELOGDIR in the server option file.

Server database restore stops.

Before reissuing the command to restore the database, check the following items:

• Ensure that ARCHIVELOGDIR option has a valid value.
• Ensure that the command is using the correct options file for the server. If you are using the -o option with the command to specify a server options file, ensure that the name and location of the file is correct.

The server stops.

Remove or rename the specified file and restart the server.

A database restore to the most current state was requested but it is not possible to perform this action. The archive logs are not available. This might be because the archive log files have been moved or deleted, or the entire archive log directory has been moved, deleted, or renamed. The server performs the database restore to the most recent point-in-time possible.

Database restore processing continues using point-in-time mode.

Review the ARCHIVELOGDIR server option in the server options file and determine why this directory is no longer available to the server. If the archive log directory and its contents can be recovered and made available to the server RESTORE DB processing, retry the DSMSERV RESTORE DB command.

This message is issued to notify the administrator that the server has detected that the API is reporting an invalid drive condition during a REMOVE DB process.

Server REMOVE DB stops.

Interrogate the database, correct the problem then issue the command again.

During server initialization, the server database initialization failed because the version of the restart record is not recognized.

The Server is terminated.

Install the latest version of the Server or restore the database to a point in time prior to the previous upgrade.

The Express® server has been started with a database that has been upgraded from Express to base TSM. Once the database is upgraded from Express, it cannot be used by an Express server.

The Server is terminated.

Either restore the database from a version taken prior to the upgrade, or use a base TSM Server with the current database.

During server initialization, the process of bringing the server database back to a state of consistency has begun.

None.

None.

During server initialization, the process of bringing the server database back to a state of consistency has completed successfully.

None.

None.

During server initialization, the process of recovering any incomplete transactions has completed successfully.

None.

None.

During server initialization, the process of analyzing the server recovery log has begun.

None.

None.

During server initialization, the process of committing incomplete transactions has begun.

None.

None.

During server initialization, the process of rolling back incomplete transactions has begun.

None.

None.

The process of removing unneeded data from the server recovery log has begun.

None.

None.

The process of removing unneeded data from the server recovery log has completed.

None.

None.

During server initialization, the server database fails initialization because sufficient server memory is not available.

Initialization fails.

Make more memory available to the server.

During server initialization, the server database initialization fails because the required restart record cannot be read.

Initialization fails.

Contact your service representative.

During server initialization, the server database initialization fails because the size of the database does not match its prior size.

Initialization fails.

Contact your service representative.

During server initialization, the server database initialization fails because the page allocator cannot be started.

Initialization fails.

Contact your service representative.

This message is issued to notify the administrator that the server database utilization exceeds 80% or more of its assigned capacity.

Server operation continues.

Depending upon the size of your database, add database volumes, or extend the database, or both, before it fills completely. The server expiration process may also free up database space making it available to other server processes. Refer to the EXPIRE INVENTORY, DEFINE DBVOL, and EXTEND DB commands for more information on these operations.

This message is issued to notify the administrator that the server database was automatically upgraded to the current server program level. The upgrade is performed when the UPGRADEDB parameter is specified at server startup and the server is started over a database that was written by a down-level version of the server program.

Server operation continues.

None. The UPGRADEDB parameter does not need to be specified during future server start-ups.

This message is issued to notify the administrator that the server has detected a zero bit mismatch error during a RESTORE DB process. The recovery process is the database must be restored with a process that includes a DSMSERV FORMAT. Either the data base volumes must be formatted then a DSMSERV RESTORE DB performed from a data base backup that does not have this problem, or a DSMSERV UNLOADDB followed by the formatting, then a DSMSERV LOADDB. Do not use DSMSERV DUMPDB on the data base for this recovery.

Server RESTORE DB continues.

Perform one of the data base recovery actions after the RESTORE DB completes.

This message is issued to notify the administrator that the server has detected that the database is currently in use during a REMOVE DB process.

Server REMOVE DB stops.

Drop all database connections then issue the command again.

This message is issued to notify the administrator that the server has removed the server database successfully.

None.

The server database was removed. In order to run the TSM server, you need to format a new database using the 'DSMSERV FORMAT' command.

While attempting to format a database, the Tivoli Storage Manager server has found that this database name already exists.

Server format stops.

Before reissuing the command to format a new database, check the following items:

• Remove the old database using command 'DSMSERV REMOVEDB DB_NAME'.
• Ensure that the command is using the correct options file for the server. If you are using the -o option with the command to specify a server options file, ensure that the name and location of the file is correct.

The server is done creating its database

None.

Stopping the server's database manager.

None.

Space is not available for the server to write data to the directory.

The format operation stops.

Before reissuing the command to format a new database, check the following items:

• Check whether the format operation created a database but did not remove the database after the failure. If the database that was created was not removed, use the utility DSMSERV REMOVEDB db_name to remove it.
• Check that space is available to the directories that you specified for ACTIVELOGDIR,ARCHIVELOGDIR, and ARCHFAILOVERLOGDIR. Ensure that the amount of space meets requirements. For example, the directory for ACTIVELOGDIR must have at least 8 GB space available.
• Remove any files that are in the directories that you want to use for the recovery logs.

The server is unable to set the content of the environment variable on the operating system to the value specified in the message. The return code in the message is the last error code set in the operating system. The return code, or, last error code is a system error code as a result of the failed function call to set the environment variable.

The server operation stops.

Refer to the list of system error codes provided by the operating system to determine the cause of the problem. Resolve the problem and retry the server operation.

This message is issued to notify the administrator that the server has detected that the database is damaged during a REMOVE DB process.

Server REMOVE DB stops.

Interrogate the database, correct the problem then issue the command again.

This message is issued to notify the administrator that the server has detected that the database is reporting a File error during a REMOVE DB process.

Server REMOVE DB stops.

Interrogate the database, correct the problem then issue the command again.

This message is issued to notify the administrator that the server has detected that the API is reporting an Invalid DB error during a REMOVE DB process.

Server REMOVE DB stops.

Interrogate the database, correct the problem then issue the command again.

This message is issued to notify the administrator that the server has detected that the database is reporting an authorization error during a REMOVE DB process.

Server REMOVE DB stops.

Interrogate the database, correct the problem then issue the command again.

This message is issued to notify the administrator that the server has detected that the API is reporting the DB cannot be found during a REMOVE DB process.