Messages


Chapter 10. Client Event Logging (4000-4999)



ANS4000EError processing 'filespace-name': file space does not exist

Explanation: The specified file space (domain) is incorrect or does not exist on the workstation. If the message results from the BACKUP IMAGE command with the -MODE=INCREMENTAL option, it may mean that you have entered the name of a raw logical volume. The MODE=INCREMENTAL option is not valid for raw logical volumes.
System Action: Processing stopped.
User Response: Retry the operation specifying an existing domain (drive letter or file system name). If the message resulted from improper use of the MODE=INCREMENTAL option, retry the command, omitting that option.



ANS4001EError processing 'filespace-name': file space not known to server

Explanation: The number defining the correspondence between drive letter or file (domain name) and volume label is not known to the server.
System Action: Processing stopped.
User Response: Report the program error to your service representative.



ANS4002EError processing 'filespace-name': volume label does not exist

Explanation: The selected drive does not have a label.
System Action: TSM is unable to do the requested operation without a drive or label entered.
User Response: 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.



ANS4003EError processing 'filespace-name': duplicate volume label encountered

Explanation: The selected drive has a duplicate volume label. Because TSM 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.
System Action: TSM cannot select the drive.
User Response: If the volume needs to be available to the system, exit TSM, and assign a volume label to the drive. Restart TSM and retry the operation.



ANS4004EError processing 'filespace namepath-namefile-name': destination file or directory is write locked

Explanation: 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.
System Action: File skipped.
User Response: Either determine which operation has the file write locked, or restore the file to another name or location.



ANS4005EError processing 'filespace namepath-namefile-name': file not found

Explanation: 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 TSM.
System Action: File skipped.
User Response: None.



ANS4006EError processing 'filespace namepath-namefile-name': directory path not found

Explanation: You have specified a directory that does not exist as shown on your workstation.
System Action: Processing stopped.
User Response: Recheck all spelling and punctuation, particularly the placement of directory delimiters (for example, "\"). Correct the syntax, then retry the operation.



ANS4007EError processing 'filespace namepath-namefile-name': access to the object is denied

Explanation: 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.
System Action: Processing stopped.
User Response: Ensure that you specified the correct file or directory name, correct the permissions, or specify a new location.



ANS4008EError processing 'filespace namepath-namefile-name': file is temporarily unavailable

Explanation: File is temporarily unavailable.
System Action: File skipped.
User Response: Check and see if file is locked by other process. If not, retry the command.



ANS4009EError processing 'filespace namepath-namefile-name': disk full condition

Explanation: No more files can be restored or retrieved because the destination disk is full.
System Action: Processing stopped.
User Response: Free up disk space, or restore or retrieve the file to another disk.



ANS4010EError processing 'filespace namepath-namefile-name': stale NFS handle

Explanation: An NFS file system becomes stale.
System Action: File system skipped.
User Response: Check the NFS mounted filesystem.



ANS4011EError processing 'filespace namepath-namefile-name': no file handles available

Explanation: All file handles for your system are currently in use. No more are available.
System Action: Processing stopped.
User Response: 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.



ANS4012EError processing 'filespace namepath-namefile-name': file already exists

Explanation: The file being restored or retrieved exists.
System Action: File is replaced or skipped depending on client options.
User Response: None.



ANS4013EError processing 'filespace namepath-namefile-name': invalid file handle

Explanation: An internal system error occurred. A file operation failed because an invalid file handle was passed.
System Action: Processing stopped.
User Response: Report the problem to your system administrator, and then retry the operation.



ANS4014EError processing 'filespace namepath-namefile-name': unknown system error (error-code) encountered. Program ending.

Explanation: An unknown and unexpected error-code occurred within the client program. This is a programming failure and the client program ends.
System Action: Processing stopped.
User Response: Retry the operation. If the problem continues, see your administrator.



ANS4015EError processing 'filespace namepath-namefile-name': unexpected error (error-code) encountered

Explanation: An unexpected error occurred. This might be a low-level system or communication error that TSM cannot handle or recover from.
System Action: Processing stopped.
User Response: Retry the operation. If the problem continues, determine where the problem exists. See your system administrator for further help.



ANS4016EError processing 'filespace namepath-namefile-name': file is being executed; write permission denied

Explanation: The current file cannot be opened to write to because it is currently being run by another operation.
System Action: File skipped.
User Response: Stop the operation that is running the file and retry the operation, or restore or retrieve the file to a different name or directory.



ANS4017EError processing 'filespace namepath-namefile-name': too many symbolic links were detected while resolving name

Explanation: While trying to resolve the file name, too many symbolic links were found.
System Action: File skipped.
User Response: Ensure that you do not have a looping symbolic link for the file.



ANS4018EError processing 'filespace namepath-namefile-name': file name too long

Explanation: The file name specified is too long to be handled by TSM.
System Action: File is skipped.
User Response: See the appropriate Using the Backup-Archive Client book for the particular operating system, for the file names that are handled by TSM.



ANS4019EError processing 'filespace namepath-namefile-name': file system is locked by system

Explanation: File system cannot be accessed because it is locked by the system.
System Action: TSM cannot complete the operation.
User Response: See your system administrator.



ANS4020EError processing 'filespace namepath-namefile-name': format unknown

Explanation: TSM tried to restore or retrieve a file, but it had an unknown format.
System Action: File skipped.
User Response: See your system administrator.



ANS4021EError processing 'filespace namepath-namefile-name': file system not ready

Explanation: The file system/drive was not ready for access.
System Action: Processing stopped.
User Response: Ensure that the drive is available to TSM, and then retry the operation.



ANS4022EError processing 'filespace namepath-namefile-name': file system is invalid

Explanation: The drive was not available for access. A directory exists that does not have either a '.' or '..' entry.
System Action: Processing stopped.
User Response: Ensure that the drive is operational, and then retry the operation. If unsuccessful, have your service representative check the error log.



ANS4023EError processing 'filespace namepath-namefile-name': file input/output error

Explanation: An error was found while reading from or writing to the file.
System Action: File skipped.
User Response: 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.



ANS4024EError processing 'filespace namepath-namefile-name': file write error

Explanation: An error was found while writing to the file.
System Action: File skipped.
User Response: Check your system to ensure that it is operating properly.



ANS4025EError processing 'filespace namepath-namefile-name': file exceeds user or system file limit

Explanation: A file being restored or retrieved exceeds system set limits for this user.
System Action: File skipped.
User Response: Ensure that the system limits are set properly.



ANS4026WError processing 'filespace namepath-namefile-name': size of 'file-size' exceeded the maximum file size limit on your system

Explanation: You tried to restore or retrieve a file that has exceeded the maximum file size limitation on your system.
System Action: TSM cannot restore or retrieve the file.
User Response: Restore or retrieve this file on a system that supports the file size. See your system administrator.



ANS4027SError processing 'filespace namepath-namefile-name': internal program message 'value' encountered

Explanation: An unexpected catastrophic program failure occurred, indicated by value.
System Action: Processing stopped.
User Response: Retry the operation. If the problem continues, see your system administrator or service representative.



ANS4028EError processing 'filespace namepath-namefile-name': cannot create file/directory entry

Explanation: The directory path for files being restored or retrieved cannot be created.
System Action: File skipped.
User Response: Ensure that you have the proper authorization to create the directory for file being restored or retrieved.



ANS4029EError processing 'filespace namepath-namefile-name': unable to build a directory path; a file exists with the same name as a directory

Explanation: TSM tried to create a directory path, but is unable to because a file exists that has the same name as a directory.
System Action: Processing stopped.
User Response: 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.



ANS4030EError processing 'filespace namepath-namefile-name': disk space limit for this process reached

Explanation: The disk space allocated for the client owner is full.
System Action: Processing stopped.
User Response: Free up disk space and retry the restore or retrieve operation.



ANS4031EError processing 'filespace namepath-namefile-name': destination directory path length exceeds system maximum

Explanation: The path name specified plus the path name in the restored file name combine to create a name whose length exceeds the system maximum.
System Action: Processing stopped.
User Response: Specify a destination path that, when combined, is less than the system maximum.



ANS4032EError processing 'filespace namepath-namefile-name': file is not compressed.

Explanation: A file that was flagged as compressed was not compressed, and the system failed.
System Action: Processing stopped.
User Response: See your system administrator to report this problem. This error is a system failure.



ANS4033EError processing 'filespace namepath-namefile-name': file compressed on a different client machine that has more memory

Explanation: 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.
System Action: TSM canceled the operation.
User Response: Obtain a machine with more memory and retry the operation.



ANS4034EError processing 'filespace namepath-namefile-name': unknown system error

Explanation: An unknown error occurred. This might be a low-level system or communication error that TSM cannot handle or recover from.
System Action: Processing stopped.
User Response: Retry the operation. If the problem continues, determine where the problem exists. See your system administrator for further help.



ANS4035WFile 'filespace namepath-namefile-name' currently unavailable on server.

Explanation: You tried to restore or retrieve a file that is currently not available from the TSM server.
System Action: TSM Cannot restore or retrieve the file.
User Response: Try to restore or retrieve after the file was made available on the server. See your system administrator.



ANS4036EAn error occurred saving the registry key.

Explanation: The active registry key cannot be saved.
System Action: Registry backup operation terminates.
User Response: See your system administrator.



ANS4037EFile 'file-namefile-namefile-name' changed during processing. File skipped.

Explanation: The specified file-name was skipped during backup, archive, or migrate because it was changing during the attempt to process it.
System Action: TSM skipped the file.
User Response: 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.



ANS4040EError processing 'filespace namepath-namefile-name': file system filespace name has exceeded its space management quota.

Explanation: TSM detects that the file system has exceeded its quota. No more data can be migrated out of this file system.
System Action: TSM will not migrate files from this file system.
User Response: Recall some files, or ask the system administrator to increase the quota for this file system.



ANS4041WError processing 'filespace namepath-namefile-name': Out of free space or inodes in file system to migrate or recall.

Explanation: 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.
System Action: TSM terminates the current operation for this file system.
User Response: Remove some files in the file system, and then run reconciliation. Retry the operation.



ANS4042EObject name 'filespace namepath-namefile-name' contains one or more unrecognised characters and is not valid.

Explanation: The filename, directory name, or volume label syntax is incorrect.
System Action: File skipped.
User Response: You need to check the disk for errors.



ANS4900WSchedule 'schedule name' has opened a new session with the server.

Explanation: A scheduled event ended due to a connection failure. The scheduled event had to be restarted outside it's normal start-up window to continue the operation.
System Action: Be advised that there are multiple sessions associated with the scheduled event.
User Response: none.



ANS4987EError processing 'filespace namepath-name file-name': the object is in use by another process

Explanation: 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.
System Action: Processing stopped.
User Response: Ensure that you specified the correct file or directory name, correct the permissions, or specify a new location.



ANS4988WFile 'filespace namepath-namefile-name' is currently unavailable on server and has been skipped.

Explanation: You tried to restore or retrieve a file that is currently not available from the TSM server.
System Action: TSM cannot restore or retrieve the file.
User Response: Try to restore or retrieve after the file was made available on the server. See your system administrator.



ANS4999E Unable to log message 'message number' to server: message too long.

Explanation: The message text and inserts were too large to send to the server in the available internal buffer.
System Action: Refer to the local client error log for more information
User Response: None.


[ Top of Page | Previous Page | Next Page | Table of Contents ]