ANS9003E program-name: file system for path-name is not in the dsmmigfstab file.
Explanation: ADSM cannot find the file system in the dsmmigfstab file.
System Action: ADSM cannot complete the requested operation.
User Response: Ensure that the file system is both valid and local, and that it is an FSM file system.

ANS9004E program-name: cannot update file-system because it is not an FSM file system.
Explanation: The program cannot find the file system in the dsmmigfstab file. The update failed.
System Action: ADSM cannot complete the requested operation.
User Response: The file system cannot be updated because it is not an FSM file system. You must first add space management to the file system before you can update space management settings for the file system.

ANS9007E error-program: error occurred. Run 'dsmreconcile file-system'.
Explanation: An error occurred.
System Action: ADSM terminates the operation.
User Response: Run the operation specified.

ANS9008W program-name: cannot mix -a and named file systems.
Explanation: You have used the -a option (which tells ADSM to work on all of the local file systems), as well as one or more named file systems.
System Action: ADSM terminates the operation.
User Response: Enter the command again, using either the -a option, or the name of one or more file systems, but not both.

ANS9009W program-name: no file system specified.
Explanation: You did not include the name of a file system as part of the argument to this command.
System Action: ADSM terminates the operation.
User Response: Enter the command again, including the name of one or more file systems.

ANS9012E error-program: Command must be run by root user.
Explanation: ADSM requires that a root user perform this operation.
System Action: ADSM terminates the operation.
User Response: Change to root user, and then retry the operation.

ANS9016E Cannot get space management migration status for path.
Explanation: An error occurred while trying to get the space management migration status. Either the permissions for the status file are not set correctly, or the status file is damaged.
System Action: ADSM terminates the operation.
User Response: The root user should check the permissions of the status file, or contact the service representative.

ANS9017W error-program: Minimum number of recall daemons min-dsmrecalld cannot be greater than maximum number of recall daemons max-dsmrecalld; defaulting to minimum min-dsmrecalld and maximum max-dsmrecalld.
Explanation: A minimum number of recall daemons has been entered that is greater than the maximum number of recall daemons.
System Action: ADSM uses defaults instead of the values specified in the client system options file (dsm.sys).
User Response: Correct the MINRECALLDAEMONS and MAXRECALLDAEMONS options in the client system options file and retry the operation.

ANS9018W program-name: option option value value invalid, range min-value to max-value.
Explanation: An invalid value has been entered. Value should be in the range specified by the message.
System Action: ADSM uses defaults instead of the value specified by the user.
User Response: Correct the invalid input value.

ANS9019W program-name: unable to parse option value 'argument'.
Explanation: Input is incorrect or is not in correct format.
System Action: ADSM continues.
User Response: Retry operation with correct usage syntax.

ANS9020I program-name: dispatching a subsidiary recall daemon slave-ID ...
Explanation: The master recall daemon is starting a subsidiary recall daemon.
System Action: ADSM continues.
User Response: Continue.

ANS9021E error-program Unknown recall daemon (pid process-ID) terminated abnormally, status: status.
Explanation: A recall daemon is terminated abnormally.
System Action: ADSM terminates the operation.
User Response: Retry operation. If problem persists, contact your service representative.

ANS9022E error-program Recall daemon (pid process-ID) terminated abnormally, status: status.
Explanation: A recall daemon is terminated abnormally.
System Action: ADSM terminates the operation.
User Response: Retry operation. If problem persists, contact your service representative.

ANS9023I error-program: Subsidiary recall daemon process exiting.
Explanation: The process is interrupted and exiting. The user has terminated the process.
System Action: ADSM detected an interrupt. The recall daemon is terminated and exiting.
User Response: None.

ANS9025W program-name: cannot truncate inode inode-number on file system (file-system-ID, file-system-ID): error.
Explanation: ADSM cannot truncate the file to its correct stub file size. The file remains one full block in size.
System Action: ADSM continues.
User Response: Retry the operation. If error persists, reboot the system. If error still persists, contact your service representative.

ANS9026E program-name: no space for file (block-count) (free-blocks) in file system file-system.
Explanation: ADSM does not have enough space in the file system to perform recall.
System Action: ADSM cannot complete the requested operation.
User Response: Free some space in the file system and retry the operation.

ANS9028E program-name: cannot determine the file system name for fsid (file-system-ID, file-system-ID).
Explanation: ADSM is unable to determine the name of the file system with the specified file-system-id.
System Action: ADSM is unable to recall the requested file.
User Response: Determine if the file system which contains the file has an entry in /etc/adsm/SpaceMan/config/dsmmigfstab. Typically this problem should not occur unless the dsmmigfstab file was manually updated after the file system was mounted, and the entry was either removed or commented out. Once the entry is added back to dsmmigfstab, try the file recall again.

ANS9029E error-program: cannot store information into database, error: error.
Explanation: ADSM is unable to store the premigration information into its database.
System Action: ADSM continues.
User Response: None.

ANS9030W Cannot set conflicting attributes to file file-name.
Explanation: ADSM cannot set the file attributes because the requested attributes are in conflict with one another.
System Action: ADSM does not set the file attributes.
User Response: Retry this operation with attributes that do not conflict with each other.

ANS9031W File file-name is not a migrated file.
Explanation: ADSM can only set file attributes to a migrated file. This file has not been migrated.
System Action: ADSM does not set the file attributes.
User Response: Migrate this file, and then retry the operation.

ANS9032W File file-name is not in an FSM file system.
Explanation: ADSM detects that the file is not in an FSM file system, and therefore, it cannot perform the operation requested.
System Action: ADSM does not set the file attributes.
User Response: Add space management to the file system, migrate the file, and then retry the operation.

ANS9036W program-name: migrated file(s) are missing on server for number stub file(s).
Look in 'file-spec' for file names.
Explanation: ADSM cannot find the migrated file(s) on the server.
System Action: ADSM continues.
User Response: Look in the path mentioned in the message for the file name. Also ensure that you are working with the correct server for this file.

ANS9054E error-program: cannot set specified execution mode: error.
Explanation: ADSM cannot set the execution mode successfully.
System Action: ADSM cannot complete the requested operation.
User Response: Retry the operation. If the problem persists, contact your service representative.

ANS9057W error-program: cannot get space information for file-system: error.
Explanation: ADSM cannot get the space information for the file system.
System Action: ADSM continues.
User Response: Verify that space management has been added to the file system.

ANS9058E error-program: cannot close file-spec: error.
Explanation: ADSM cannot close the file.
System Action: ADSM terminates the current operation.
User Response: Retry the operation. If problem persists, contact your system administrator.

ANS9059E error-program: process cannot detach to become a daemon.
Explanation: ADSM process cannot detach itself to become a daemon.
System Action: ADSM cannot start the daemon as requested. ADSM stops.
User Response: Retry the operation.

ANS9060W error-program: cannot get and increase limit of open files.
Explanation: ADSM either cannot get the limit of the number of open files, or cannot increase the limit of the number of open files.
System Action: ADSM cannot increase the number of open files, and was not able to complete the operation.
User Response: Free some file space by ending some processes or removing some files, and retry the operation.

ANS9061E program-name: directory-spec: not a writable directory.
Explanation: A -t option has been entered for a directory that does not have a write permission.
System Action: ADSM cannot complete the requested operation.
User Response: Correct the argument or permissions, and retry the operation.

ANS9062E program-name: argument: not a valid directory argument for -t option.
Explanation: An invalid directory argument has been entered for the -t option.
System Action: ADSM cannot complete the requested operation.
User Response: Correct the argument, and retry the operation.

ANS9063E error-program: file system file-system is out of inodes.
Explanation: ADSM cannot get space for the file system because the file system is out of inodes.
System Action: ADSM cannot get space via migration.
User Response: Remove some files to make more inodes available and retry.

ANS9064E error-program: Cannot fork a new process: error.
Explanation: ADSM cannot fork a new process that is needed.
System Action: ADSM cannot complete the requested operation.
User Response: Free some file space by ending some processes or removing some files, and retry the operation.

ANS9067W error-program: error updating dsmmigfstab file for file-system.
Explanation: ADSM found an error in updating the dsmmigfstab file for this file system.
System Action: ADSM does not update the dsmmigfstab file.
User Response: See the preceding error message and correct the error if possible. Then, retry the operation. If problem persists, contact your system administrator.

ANS9068I program-name: dsmmigfstab file updated for file system file-system.
Explanation: ADSM successfully updated the dsmmigfstab file for the file system.
System Action: ADSM continues.
User Response: Continue with normal operation.

ANS9069I program-name: all file systems are reactivated to previous states.
Explanation: ADSM has reactivated all file systems managed by HSM to their previous states before the global deactivation.
System Action: ADSM continues.
User Response: Continue with normal operation.

ANS9070I program-name: space management is now deactivated for all FSM file systems.
Explanation: ADSM has deactivated space management for all file systems listed in the dsmmigfstab file.
System Action: ADSM continues.
User Response: Continue with normal operation.

ANS9071W program-name: error reactivating space management for all FSM file systems.
Explanation: ADSM found an error in trying to reactivate space management.
System Action: ADSM does not reactivate space management for FSM file systems.
User Response: Make sure space management is installed correctly and retry the operation.

ANS9072W error-program: error deactivating space management for all FSM file systems.
Explanation: ADSM found an error in trying to deactivate space management.
System Action: ADSM does not deactivate space management for FSM file systems.
User Response: Make sure space management is installed correctly and retry the operation.

ANS9073W program-name: error deactivating space management for file system file-system.
Explanation: ADSM found an error in trying to deactivate the file system.
System Action: ADSM does not deactivate space management for the file system.
User Response: Make sure space management is installed correctly and retry the operation.

ANS9074I program-name: FSM file system file-system is now deactivated.
Explanation: ADSM has deactivated space management for the file system.
System Action: ADSM continues.
User Response: Continue with normal operation.

ANS9075W program-name: error reactivating space management for file system file-system.
Explanation: ADSM found an error in trying to reactivate space management for the file system.
System Action: ADSM does not reactivate space management for the file system.
User Response: Correct the error if possible and retry the operation. If the problem persists, contact your service representative.

ANS9076I program-name: space management is now active for file system file-system.
Explanation: ADSM has reactivated space management for the file system.
System Action: ADSM continues.
User Response: Continue with normal operation.

ANS9077I program-name: removed space management from file system file-system.
Explanation: ADSM removed space management. The file system is now a native file system.
System Action: ADSM continues.
User Response: Continue with normal operation.

ANS9078W Space management is not removed from file system file-system.
Explanation: ADSM was not able to remove space management from this file system. Possible causes:

Kernel extension is downlevel.

Program is downlevel.

Insufficient disk space.

System Action: ADSM is unable to complete the requested operation.
User Response: Refer to the immediately preceding error message and retry the operation.

ANS9079W program-name: no migrated files matching search criteria found.
Explanation: ADSM did not find any migrated files matching the search criteria.
System Action: ADSM cannot complete the requested operation.
User Response: Retry the operation with a different search criteria.

ANS9080E program-name: not enough space to recall all migrated files.
Explanation: ADSM detects there is not enough space in the file system to hold all the migrated files if all are recalled.
System Action: ADSM does not attempt to recall all the migrated files.
User Response: Make room in the file system by increasing the file system size or removing some files. Retry the operation.

ANS9081W program-name: orphaned stub file(s) detected in file system file-system.
Explanation: ADSM detected one or more orphaned stub files. Either the migration server was changed in the client system options file after the file was migrated, or the migration server database is damaged.
System Action: ADSM does not attempt to remove space management from the file system.
User Response: Determine the cause of orphaned stub files. Switch to the correct migration server and recall the migrated files. Retry the operation.

ANS9082W program-name: error encountered while reconciling file system file-system.
Explanation: ADSM encountered an error performing reconciliation on the file system.
System Action: ADSM continues.
User Response: Refer to other messages displayed or messages in the log to correct the problem. Then retry the operation.

ANS9083W program-name: cannot deactivate space management on file system file-system.
Explanation: ADSM cannot deactivate space management on the file system.
System Action: ADSM continues.
User Response: Correct the error if possible and retry the operation.

ANS9085E program-name: space management has not been added to file system file-system.
Explanation: There is no entry for the file system in the dsmmigfstab file.
System Action: ADSM will not perform space management functions on this file system.
User Response: Add space management to the file system, if appropriate, and then retry the operation.

ANS9086E program-name: error adding FSM to file system file-system.
Explanation: ADSM encountered an error and cannot add FSM to the file system.
System Action: ADSM continues.
User Response: Refer to the preceding error message and retry the operation.

ANS9087I Space management is successfully added to file system file-system.
Explanation: ADSM has added space management to the file system, and will now monitor its space usage. You can also perform other space management operations on this file system.
System Action: ADSM continues.
User Response: Continue with normal operation.

ANS9088W program-name: an entry for file system file-system is already in the dsmmigfstab file.
Explanation: ADSM found that the file system is already listed in the dsmmigfstab file.
System Action: ADSM continues.
User Response: None.

ANS9090E program-name: file-system is not a valid file system name.
Explanation: ADSM received an invalid file system name. The file system is not mounted, or is not mounted correctly.
System Action: ADSM continues.
User Response: Correct the file system name, and retry the operation.

ANS9091I program-name: file file-spec is already premigrated.
Explanation: ADSM found that the file is already premigrated.
System Action: ADSM continues.
User Response: Continue with normal operation.

ANS9092W program-name: file file-spec is not eligible for migration.
Explanation: ADSM found that the file is not eligible for migration.
System Action: ADSM continues.
User Response: Continue with normal operation.

ANS9093W program-name: cannot update migration candidates list file-name.
Explanation: ADSM cannot update the migration candidates list because not enough memory is available to create a temporary file.
System Action: Processing stops.
User Response: Make some memory available by ending some processes, and then retry the operation.

ANS9094W program-name: no candidates found in file system file-system.
Explanation: ADSM found no files eligible for migration in the file system after running dsmreconcile.
System Action: ADSM continues.
User Response: Continue with normal operation.

ANS9096E User is not the owner of file filesystem-namedirectory-namefile-name so file is skipped.
Explanation: The user does not own this file and cannot perform this operation.
System Action: ADSM skips the file.
User Response: None, or if you have root-user authority, switch to root user and retry the operation.

ANS9098E program-name: space management does not support file system file-system.
Explanation: ADSM space management does not support this type of file system. Space management supports only true local file systems (e.g. JFS on AIX). Space management does not support other types of file systems (AFS, NFS, etc).
System Action: Processing of the file system stopped.
User Response: None.

ANS9099E program-name: space management is not active for file system file-system.
Explanation: ADSM found the file system did not have space management activated.
System Action: Processing of that file system stopped.
User Response: Reactivate space management for the file system.

ANS9100E Space management has not been added to file system file-system, or FSM is not mounted.
Explanation: ADSM found the file system was not in a migratable state. Either space management was not added to the file system, or the FSM is not mounted.
System Action: Processing of the file system stopped.
User Response: Either add space management to the file system, or mount the FSM if it is not mounted. Refer to the User's Guide for the correct syntax for mounting the FSM.

ANS9101I No migrated files matching 'file-name' were found.
Explanation: You entered a search pattern or file name that cannot be found in the server database as a migrated file.
System Action: Processing stopped.
User Response: Ensure that your search pattern is correct, or specify a new search string.

ANS9126E program-name: cannot get the state of space management for file-system: error.
Explanation: ADSM cannot determine whether space management is activated, deactivated, or globally deactivated on the file system.
System Action: ADSM stops the operation.
User Response: Retry the operation.

ANS9127I Process stopped, signal number=signal-number.
Explanation: The space management process stopped.
System Action: ADSM process temporarily stops.
User Response: Wait for process to restart.

ANS9128I program-name: exported space management file system file-system.
Explanation: ADSM has exported the indicated space managed file system. You must import this file system to gain access to the migrated files.
System Action: ADSM continues.
User Response: Continue with normal operation.

ANS9129I Space management normal termination, exit status = status.
Explanation: Space management is ending normally.
System Action: ADSM exits from space management processing.
User Response: None.

ANS9130W program-name: High threshold (value) less than low threshold (value).
Explanation: ADSM detects that the high threshold is lower than the low threshold. The high threshold must be higher than or equal to the low threshold.
System Action: ADSM logs the condition and continues processing other parameters.
User Response: Correct the invalid input value.

ANS9131W program-name: invalid size factor (value).
Explanation: An invalid value has been entered for the size factor.
System Action: ADSM logs the condition and continues processing other parameters.
User Response: Correct the invalid input value.

ANS9132W program-name: invalid stub file size (value).
Explanation: An invalid value has been entered for the stub file size setting.
System Action: ADSM logs the condition and continues processing other parameters.
User Response: Correct the invalid input value.

ANS9133W program-name: invalid quota factor (value).
Explanation: An invalid value has been entered for the quota setting for the file system.
System Action: ADSM logs the condition and continues.
User Response: Correct the invalid input value.

ANS9134W program-name: invalid age factor (value).
Explanation: An invalid value has been entered for the age factor setting.
System Action: ADSM logs the condition and continues.
User Response: Correct the invalid input value.

ANS9135W program-name: invalid premigration percentage (value).
Explanation: An invalid value has been entered for premigration percentage.
System Action: ADSM logs the condition and continues.
User Response: Correct the invalid input value.

ANS9136W program-name: invalid high threshold (value).
Explanation: An invalid value has been entered for high threshold.
System Action: ADSM logs the condition and continues.
User Response: Correct the invalid input value.

ANS9137W program-name: invalid low threshold (value).
Explanation: An invalid value has been entered for low threshold.
System Action: ADSM logs the condition and continues.
User Response: Correct the invalid input value.

ANS9138W program-name: invalid stub file size (value) for file-system, range value..value.
Explanation: An invalid value has been entered for the stub file size setting. The value should be in the range specified by the message.
System Action: ADSM does not change the value.
User Response: Correct the invalid input value.

ANS9139W program-name: invalid quota (value) for file-system, range value..value.
Explanation: An invalid value has been entered for the quota setting. Value should be in the range specified by the message.
System Action: ADSM does not change the value.
User Response: Correct the invalid input value.

ANS9140W program-name: invalid size factor (value) for file-system, range value..value.
Explanation: An invalid value has been entered for the size factor setting. Value should be in the range specified by the message.
System Action: ADSM does not change value.
User Response: Correct the invalid input value.

ANS9141W program-name: invalid age factor (value) for file-system, range value..value.
Explanation: An invalid value has been entered for the age factor setting. Value should be in the range specified by the message.
System Action: ADSM does not change the value.
User Response: Correct the invalid input value.

ANS9142W program-name: file-spec: high threshold (value) less than low threshold (value) for file-system.
Explanation: ADSM detects that high and low thresholds specified for the file system are invalid values. The high threshold must be greater than or equal to the low threshold.
System Action: ADSM logs the condition and stops.
User Response: Enter valid values for the high and low thresholds.

ANS9143W program-name: file-spec: invalid premigration percentage (value) for file-system, range 0..100.
Explanation: ADSM detects an invalid premigration percentage value for the file system.
System Action: ADSM logs condition and stops.
User Response: Enter a valid value for the premigration percentage.

ANS9144W program-name: file-spec: invalid high threshold (value) for file-system, range 0..100.
Explanation: ADSM detects an invalid high threshold value for the file system.
System Action: ADSM logs the condition and stops.
User Response: Enter a valid value for the high threshold.

ANS9145W program-name: file-spec: invalid low threshold (value) for file-system, range 0..100.
Explanation: ADSM detects an invalid low threshold value for the file system.
System Action: ADSM logs the condition and stops.
User Response: Enter a valid value for the low threshold.

ANS9146E program-name: file-spec: expecting value field(s) in line line-number, found value field(s).
Explanation: ADSM detects too many or too few fields in an entry in the dsmmigfstab file.
System Action: ADSM cannot complete the requested operation.
User Response: Edit the dsmmigfstab file manually, and then retry the operation.

Note: Do not manually edit the dsmmigfstab file unless specifically instructed by a message.

ANS9147E program-name: cannot read file-spec: error.
Explanation: ADSM cannot read this file.
System Action: ADSM cannot fully complete the requested operation.
User Response: Retry the operation. Try to determine why the read failed. If the problem continues, check with your system administrator.

ANS9148E program-name: cannot find mount point for file system file-system.
Explanation: ADSM cannot find file system mount point.
System Action: ADSM cannot complete the requested operation.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9149E program-name: cannot create transition stub file: error.
Explanation: ADSM cannot create transition stub file.
System Action: ADSM cannot complete the requested operation. Processing continues.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9150W Space management is not exported from file system file-system.
Explanation: ADSM was not able to export the space managed file system. Possible causes:

Kernel extension is downlevel.

Program is downlevel.

System Action: ADSM is unable to complete the requested operation.
User Response: Refer to the immediately preceding error message and retry the operation.

ANS9152E program-name: cannot deactivate space management for whole system: error.
Explanation: Cannot deactivate space management for this whole system (whole machine).
System Action: ADSM cannot deactivate space management support.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9153E program-name: cannot reactivate space management for whole system: error.
Explanation: Cannot reactivate space management for this whole system (whole machine).
System Action: ADSM cannot reactivate space management support.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9154E program-name: cannot deactivate space management for file system file-system: error.
Explanation: Cannot deactivate space management for this file system.
System Action: ADSM unable to deactivate space management support for the file system.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9155E program-name: cannot reactivate space management for file system file-system: error.
Explanation: Cannot reactivate space management for this file system.
System Action: ADSM cannot reactivate space management support to the file system.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9156I program-name: removing space management from file system file-system.
Explanation: Space management is being removed.
System Action: ADSM is removing space management from a file system.
User Response: Continue with operation.

ANS9157W program-name: cannot turn off ENOSPC checking in kernel: error.
Explanation: ADSM cannot turn off ENOSPC checking.
System Action: ADSM cannot turn off ENOSPC checking. Processing continues.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9158W program-name: cannot turn on ENOSPC checking in kernel: error.
Explanation: ADSM cannot turn on ENOSPC checking.
System Action: ADSM cannot turn on ENOSPC checking. Processing continues.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9159E program-name: unable to create temporary file.
Explanation: ADSM cannot create a temporary file.
System Action: ADSM cannot complete its operation.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9160E program-name: cannot write to temporary file file-spec: error.
Explanation: ADSM cannot complete writing to the temporary file.
System Action: ADSM cannot complete the requested operation.
User Response: Retry the operation. Determine why the write failed. If the problem continues, check with your system administrator.

ANS9161E program-name: file-system: error in migration initialization.
Explanation: ADSM cannot initialize for migration.
System Action: ADSM cannot complete the requested operation.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9162E program-name: file-spec invalid: not found in path/path.
Explanation: ADSM cannot find an entry for the file system in the dsmmigfstab file.
System Action: ADSM cannot complete the requested operation.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9163E program-name: cannot make symbolic link of file-spec to file-spec: error.
Explanation: ADSM cannot create the symbolic link.
System Action: ADSM cannot complete the requested operation.
User Response: Retry the operation. Ensure that there are not too many nested symbolic links or a recursive symbolic link. If the problem continues, check with your system administrator.

ANS9164E program-name: cannot obtain time of day: error.
Explanation: ADSM cannot obtain the timestamp from the operating system.
System Action: ADSM cannot complete the requested operation.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9165E program-name: cannot open directory directory-spec: error.
Explanation: ADSM cannot open the directory.
System Action: ADSM cannot complete the requested operation.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9166E Cannot set password in a background process.
Explanation: ADSM cannot get a valid password from the password file locally. Either the password is not stored locally, or the password has been changed at the server. The user cannot be prompted for a new password because the process is a background process, for example, a daemon.
System Action: ADSM cannot complete the requested operation.
User Response: The root user needs to provide a valid password. Enter the password at the prompt using the HSM client in the foreground; the password will then be stored locally. Retry the operation.

ANS9167E program-name: cannot find directory directory-spec.
Explanation: ADSM cannot find this directory.
System Action: ADSM cannot use this directory.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9168E program-name: cannot open database file-spec: error.
Explanation: ADSM cannot successfully open (lock/unlock) the database.
System Action: ADSM cannot complete the requested operation.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9169E program-name: cannot create directory directory-spec, reason.
Explanation: ADSM cannot create this directory.
System Action: ADSM does not create this directory.
User Response: Verify that this directory does not already exist, and that its parent directory has proper permissions.

ANS9170E program-name: file-system is not a mounted local file system.
Explanation: ADSM did not find that this file system is properly mounted.
System Action: ADSM ignores the file system.
User Response: Verify that this file system is local and mounted and activated properly.

ANS9171E Internal string is too long: error.
Explanation: ADSM internally has a long string that is beyond its capability.
System Action: ADSM cannot complete the requested operation and stops processing.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9178E program-name: cannot open file file-spec: error.
Explanation: ADSM cannot open the file.
System Action: ADSM cannot complete the requested operation.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9179E program-name: cannot get real pathname of file-spec: error.
Explanation: ADSM cannot get the real pathname.
System Action: ADSM cannot complete the requested operation.
User Response: Ensure that the pathname is valid for your system, and then retry the operation. If the problem continues, check with your system administrator.

ANS9181W program-name: file system path/path error: error (errno: error-number).
Explanation: ADSM cannot find needed information for the file system. The information is stored in a status file to which the symbolic link specified in the error message points.
System Action: ADSM cannot complete the requested operation, and cannot properly work with the status file.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9183E program-name: file system file-system is not in the dsmmigfstab file.
Explanation: ADSM cannot find the file system in the dsmmigfstab file.
System Action: ADSM cannot complete the requested operation.
User Response: Ensure that the file system is both valid and local. Retry the operation. If the problem continues, check with your system administrator.

ANS9184E program-name: cannot allocate memory, error: error.
Explanation: ADSM cannot allocate adequate storage for the user.
System Action: ADSM cannot complete the requested operation.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9186E program-name: cannot open mounted file system file-system: error.
Explanation: ADSM cannot open mounted file system.
System Action: ADSM ignores the file system.
User Response: Verify that this file system is mounted and activated properly.

ANS9188E Not enough memory for recall operation.
Explanation: ADSM cannot allocate storage for the requested recall operation.
System Action: ADSM cannot complete the requested operation.
User Response: Retry the recall operation. If the problem continues, check with your system administrator.

ANS9189I Recall stopped by user.
Explanation: You requested that ADSM stop the recall operation.
System Action: Recall stopped.
User Response: Continue with normal operations.

ANS9191E Error checking file system state.
Explanation: The system cannot open /dev/dsm or cannot open the file system.
System Action: Transaction stopped.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9192I Cannot disable file-system.
Explanation: ADSM cannot disable the file system.
System Action: ADSM ignores the request.
User Response: ADSM space management is not installed correctly. Read the space management documentation for installation instructions, or check with your system administrator.

ANS9193I Cannot open file-system.
Explanation: ADSM cannot open the file system.
System Action: ADSM ignores the request.
User Response: Verify whether this file system exists and whether space management has been added to it.

ANS9194W A selective migration is in progress. Wait
until it completes and retry the recall.
Explanation: You tried a recall operation while a selective migration is in progress.
System Action: ADSM ignores the request.
User Response: Wait until the selective migration is complete and retry the recall operation.

ANS9195W A selective recall is in progress. Wait
until it completes and retry the migration.
Explanation: You initiated a migration operation while a selective recall is in progress.
System Action: ADSM ignores the request.
User Response: Wait until the selective recall is complete and retry the migration operation.

ANS9196W The PASSWORDACCESS option in your dsm.sys file is not set to GENERATE.
Reset it to GENERATE and restart the HSM client.
Explanation: The PASSWORDACCESS option in your dsm.sys file is set to PROMPT. It must be set to GENERATE in order for automatic space management services to work.
System Action: ADSM terminates the client.
User Response: The root user must set the PASSWORDACCESS option to GENERATE in the dsm.sys file.

ANS9197E File: file-name has already been recalled.
Explanation: You tried to recall the a file that has already been recalled.
System Action: ADSM does not highlight the file.
User Response: None.

ANS9198E File: file-name is a resident file.
Explanation: You tried to recall a file that is resident.
System Action: ADSM will not highlight the file.
User Response: None.

ANS9199S Cannot open /dev/fsm.
Explanation: ADSM cannot open the space management device file, /dev/fsm.
System Action: ADSM cannot complete the operation.
User Response: Check to see whether ADSM is installed correctly and that the /dev/fsm file exists. Correct the problem and retry the operation.

ANS9230E Cannot unmount FSM from file system file-system.
Message from umount command:.
Explanation: Space management control files have been updated or deleted, or both, for the file system. However, FSM cannot be unmounted because the file system is being referenced by another process.
System Action: ADSM left FSM mounted on the file system.
User Response: Determine why unmounting the FSM failed.

If the reason is Device Busy, try unmounting the FSM by issuing the umount command for the file system.

If umount again fails, check to see if the current directory is in the file system, or if another process is referencing the file system, such as an NFS mount or an open file.

After the file system is clear of references, issue the umount command for the file system. No problems will result in continuing to run with the FSM mounted and a machine reboot will eliminate the FSM.

ANS9249E File 'file-namefile-namefile-name' accessed during migration. File skipped.
Explanation: The specified file-name was not migrated because the file was accessed by another process during the attempt to migrate it.
System Action: ADSM left the file resident.
User Response: If you want the file migrated, stop the process which is accessing the file and retry the migration.

ANS9250I File system 'file-system' reconciliation completed.
Explanation: ADSM has finished reconciling the file system.
System Action: ADSM continues.
User Response: Continue with normal operations.

ANS9251E ProgramName: Cannot parse command-line options correctly.
Explanation: An internal program error occurred trying to parse the command-line arguments.
System Action: The program is not able to process the request.
User Response: Use the -h or -help option to see what options are allowed on the command-line, and then retry the request. If this problem continues, contact your service representative.

ANS9254E Error encountered while adding implicit excludes to the include-exclude list.
Explanation: Error encountered when implicitly excluded files are being added to the include-exclude list.
System Action: ADSM cannot proceed.
User Response: Retry the operation. If the problem persists, contact your service representative.

ANS9255E program-name: invalid value found in the dsmmigfstab file
for file system file-spec.
Explanation: ADSM detects invalid values in the dsmmigfstab file. The entry that contains the invalid values is for file system file-spec
System Action: ADSM cannot perform migration until the error is corrected in the table.
User Response: Find the invalid values in the table entry and correct them using the dsmmigfs command or the HSM graphical user interface.

ANS9256E File 'file-namefile-namefile-name' is currently opened by another process. File skipped.
Explanation: The specified file-name was not migrated because the file was open by one or more other processes.
System Action: ADSM left the file resident.
User Response: If you want the file migrated, stop the processes which currently have the file open and retry the migration.

ANS9257E Server 'server-name' does not support space management.
Explanation: The specified server-name does not support space management. It is a downlevel server, or a platform that does not support space management.
System Action: ADSM failed the operation.
User Response: If you want to use the space management function, make sure you connect to a server that supports space management.

ANS9263W program-name: cannot reserve transition stub file for file system file-system: reason.
Explanation: ADSM cannot reserve transition stub file. ADSM tries to reserve some space for the transition stub file for emergency cases. At this point, there is either not enough space or inodes to allow the reservation. The attempt to reserve the transition stub file will be made again during reconciliation.
System Action: ADSM cannot reserve space for the transition stub files. Processing continues.
User Response: If possible, make more space or inodes available and run reconciliation.

ANS9264E program-name: ADSM space management does not support file systems with
mount points that are relative paths or contain symbolic links.
Explanation: ADSM does not support adding space management to file systems with mount points which are either relative path names or contain symbolic links.
System Action: ADSM does not add space management to the file system.
User Response: Change the file system mount point so that it is not a relative path or does not contain symbolic links, and then retry the operation.

ANS9267E program-name: File system file-system has exceeded its quota.
Explanation: ADSM detects that the file system has exceeded its quota. No more data can be migrated out of this file system.
System Action: ADSM 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.

ANS9280E program-name: cannot get space management kernel extension ID. Error : error.
Explanation: The program cannot determine the level of space management client kernel extension.
System Action: ADSM stops the operation.
User Response: Ensure that space management is installed correctly, and then retry the operation. If the problem continues, check with your system administrator.

ANS9281E Space management kernel extension is downlevel from the user program.
Explanation: The space management kernel extension on the system is downlevel from the user program that is currently running. Unexpected results may occur.
System Action: ADSM stops processing the kernel extension.
User Response: Upgrade the space management kernel extension to the correct level, and then retry the operation.

ANS9282E User program is downlevel from the space management kernel extension.
Explanation: The user program that is currently running is downlevel from the space management kernel extension on the system. Unexpected results may occur.
System Action: ADSM stops processing the extension.
User Response: Upgrade the user program to the correct level, and then retry the operation.

ANS9283K Attempting to access remote file.
Explanation: The space management kernel extension is attempting to access a file that is not stored locally. If the file is migrated, ADSM is attempting to access it from an ADSM space management server.
System Action: ADSM waits for the kernel to access the file.
User Response: None.

ANS9284K File access waiting for migration to complete.
Explanation: The file being accessed is currently being migrated. Access to this file must wait until the migration process is finished.
System Action: ADSM waits until the file migration is completed.
User Response: None.

ANS9285K Cannot complete remote file access.
Explanation: The space management kernel extension cannot complete the remote file access. The file may be migrated to an ADSM migration server. The file cannot be recalled to the local machine. The server could be temporarily disabled.
System Action: ADSM terminates the current operation.
User Response: Check to see whether the server has been disabled by the system administrator, then retry the operation.

ANS9286K File migration has been discontinued.
Explanation: Migration stops because the file is being migrated by another process.
System Action: ADSM terminates the current operation.
User Response: None.

ANS9287I Out of free space or inodes in file system file-system to migrate or recall.
Explanation: The file system is full. No more free space or free inodes can be allocated for the transaction file that is required for migration or recall.
System Action: ADSM terminates the current operation for this file system.
User Response: Remove some files from the file system, and then run reconciliation. Retry the operation.

ANS9288I File file-name of size file-size is too small to qualify for migration.
Explanation: The file is smaller than the minimum size required for migration. A file is considered for migration only if its size is greater than both the stub file size specified for the file system plus 1 byte and the block size defined for the file system.
System Action: ADSM does not migrate this file because it will not free additional space.
User Response: None.

ANS9289I Object 'dir-name' is a directory. It is skipped for migration.
Explanation: The object is a directory. It is not migrated. Space management does not migrate directories.
System Action: ADSM does not migrate this object because it is a directory.
User Response: None.

ANS9290I File file-name of type file-type is skipped for migration.
Explanation: The file either cannot be read, is not a regular file, or its type is unknown to space management. Space management only migrates regular files and does not migrate directories.
System Action: ADSM does not migrate this file.
User Response: None.

ANS9291E program-name: A conflicting space management program is already
running in the file-system file system.
Re-run this program later in this file system.
Explanation: ADSM detected another program running in the file system that cannot run at the same time as the program your tried to initiate. The following programs cannot run at the same time for a file system:

dsmreconcile

dsmautomig

dsmmigfs remove.

Also, dsmmigfs remove cannot run while a migration process is running in the file system.
System Action: ADSM will not run the program at this time.
User Response: Try running the program later.

ANS9292E program-name: Cannot access lock file lock-file/lock-filelock-file: error.
Explanation: ADSM cannot access a lock file due to an error. The lock file provides serialization of certain programs to prevent conflicting processes from running at the same time.
System Action: ADSM will not run the program at this time.
User Response: Check the permissions on the directories leading up to the lock file and also the permissions on the program executable.

ANS9293E ADSM space management cannot access ERRORPROG error-program:error.
Explanation: ADSM encountered an error trying to access the program specified with the ERRORPROG option in your client system options file (dsm.sys). This message will appear only the first time this error occurs.
System Action: ADSM cannot send a severe error message to the specified error message program.
User Response: Check to make sure the program exists and that it accepts standard input when run. It is usually best if ERRORPROG specifies the fully qualified file name of the program.

ANS9294I No files matching 'file-name' were found.
Explanation: You entered a search pattern or file name that cannot be found in the local file system.
System Action: Processing stopped.
User Response: Ensure that your search pattern is correct, or specify a new search string.

ANS9297I File file-name is skipped for migration: No backup copy found.
Explanation: A management class is assigned to the file with the attribute MIGREQUIRESBKUP set to YES. This requires a current backup copy of the file before migration. However, there is no backup copy found on the migration server. This file will not be migrated.

Note: ADSM checks only the migration server for a backup copy. If the migration server and backup server are different servers, ADSM does not find a backup copy of the file.
System Action: ADSM does not migrate this file.
User Response: Back up this file on the migration server, or assign a management class to this file that does not require a current backup copy. Retry the operation.

ANS9298I File file-name is skipped for migration: Backup copy found is not current.
Explanation: A management class is assigned to the file with the attribute MIGREQUIRESBKUP set to YES. This requires a current backup copy of the file before migration. However, the backup copy found on the migration server is an old version. This file will not be migrated.

Note: ADSM checks only the migration server for a backup copy. If the migration server and backup server are different servers, there must be a valid backup copy of the file on the migration server.
System Action: ADSM does not migrate this file.
User Response: Back up the current file on the migration server, or assign a management class to this file that does not require a current backup copy. Retry the operation.

ANS9299I Cannot get the number of migrated files for file system file-system.
Explanation: Failed to get the number of migrated files on the file system. The number is stored in the status file for the file system.
System Action: If you are removing space management from the file system, processing stops. Space management is not removed.
User Response: Run reconciliation to reconcile the file system. Retry operation.

ANS9300I Migrated files found in file system file-system.
Check for any error encountered during recall.
Explanation: Remove space management failed because there are migrated files in the file system. ADSM was unable to recall any files, or some of the migrated files may have failed during a recall operation.
System Action: ADSM remove processing stops.
User Response: Check for error messages that occurred during the recall process, correct any problems, and retry the remove process.

ANS9301I Cannot remove the entry for file-system from the dsmmigfstab file.
Explanation: The entry for the file system in the dsmmigfstab file cannot be removed. Possible reasons:

• Not enough memory to create temporary file name for temporary file system table.
• Not enough free space or inodes to create temporary file system table
• Cannot open the real and/or temporary file system table files.

System Action: ADSM does not remove the entry from the dsmmigfstab file.
User Response: Manually edit the dsmmigfstab file and delete the entry.

ANS9302E Mount FSM: ERROR - file-system is not in the dsmmigfstab file. Check the
/etc/adsm/SpaceMan/config/dsmmigfstab file,
or add space management to the file system.
Explanation: ADSM cannot mount the file system because it is not listed in the dsmmigfstab file.
System Action: ADSM does not mount the FSM to the file system.
User Response: If you previously added space management to the file system, check the /etc/adsm/SpaceMan/config/dsmmigfstab file to see whether the entry has been removed or commented out. If you want to add space management to the file system, use 'dsmmigfs add'.

ANS9303E Mount FSM: ERROR - file system type 'FSM' was not found.
ADSM space management is not installed correctly. Please read the
space management documentation for installation instructions.
Explanation: ADSM cannot mount the file system because the file 'FSM' entry is missing from /etc/vfs.
System Action: ADSM does not mount the FSM to the file system.
User Response: AIX only. ADSM space management is not installed correctly. Read the space management documentation for installation instructions.

ANS9304E Mount FSM: ERROR - invalid source (object) path 'source-path': error.
Explanation: ADSM cannot mount the file system due to an invalid path.
System Action: ADSM does not mount the FSM to the file system.
User Response: Correct the problem and retry the mount.

ANS9305E Mount FSM: ERROR - invalid mount (stub) path 'mount-path': error.
Explanation: ADSM cannot mount the file system due to an invalid path.
System Action: ADSM does not mount the FSM to the file system.
User Response: Correct the problem and retry the mount. Make sure the directory exists.

ANS9306E Mount FSM: ERROR - mount-path must be a directory.
Explanation: ADSM cannot mount the file system because the mount path is not a directory.
System Action: ADSM does not mount the FSM to the file system.
User Response: Correct the problem and retry the mount. Make sure the mount path is a directory.

ANS9307W Mount FSM: ADSM space management is already mounted on mount-path.
Explanation: ADSM cannot mount the file system because the file system is already mounted.
System Action: ADSM does not mount the FSM to the file system.
User Response: None.

ANS9308E Mount FSM: ERROR - mount-path is not a supported native file system.
Explanation: ADSM cannot mount the file system because it is not a supported native file system.
System Action: ADSM does not mount the FSM to the file system.
User Response: The file system must be one of the supported native file systems in order for the ADSM space management to mount it.

ANS9309I Mount FSM: ADSM space management mounted on mount-path.
Explanation: ADSM successfully mounted the FSM to the file system.
System Action: ADSM space management now manages the file system.
User Response: None.

ANS9310E Mount FSM: ERROR - cannot FSM mount source-path on mount-path: error.
Explanation: ADSM cannot mount the file system due to the specified error.
System Action: ADSM does not mount the FSM to the file system.
User Response: Correct the problem and retry the mount.

ANS9311E Mount FSM: ERROR - cannot unlock file system, internal error: error.
Explanation: ADSM cannot unlock the internal file system lock.
System Action: ADSM does not allow non-root user access to the file system.
User Response: Attempt to unmount the file system, and try the mount again. If the problem continues, contact your service representative.

ANS9312S program-name: Cannot change owner/group on file: file-name: error.
Explanation: ADSM cannot change the ownership or group, or both for the specified file. This change is necessary for space management to run properly.
System Action: ADSM cannot continue processing.
User Response: Ensure that directory permissions allow the file owner or group to be changed. Reissue the command.

ANS9313I One or more files will be retrieved from or stored to offline media.
Explanation: For the backup or archive operation, one or more files must be sent to offline storage media (generally tape), or a migrated file must be recalled from offline storage media. The waiting time depends on your site's offline storage management policies.
System Action: ADSM waits for offline storage media to become available and then continues.
User Response: None.

ANS9318W program-name: error encountered while undeleting file system file-system.
Explanation: ADSM encountered an error performing undelete on the file system.
System Action: ADSM continues.
User Response: Continue with normal operation.

ANS9500W program-name: cannot disposition the mount event. Reason: error.
Explanation: The system wide mount event could not be dispositioned. Mount events will not be received by this daemon.
System Action: ADSM continues.
User Response: Try to resolve the problem and restart the recall daemon. If the problem cannot be resolved immediately, kill and restart the recall daemon after an ADSM space management supported file system has been added using dsmmigfs or after a file system has been mounted using the mount command.

ANS9501W program-name: cannot set event disposition on session session for file system mountdir
token = token. Reason: error.
Explanation: Events could not be dispositioned on the file system. No events will be received for this filesystem. HSM is not enabled for this file system.
System Action: ADSM continues.
User Response: The file system must be one of the supported native file systems in order for the ADSM space management to support it. Verify that the mount options the file system are correct. Correct the problem and remount the file system.

ANS9502W program-name: cannot remove event disposition on session session for file system mountdir
token = token. Reason: error.
Explanation: Event dispositions could not be removed from the file system.
System Action: ADSM continues.
User Response: Correct the problem and retry the operation.

ANS9503I program-name: events have been set and dispositioned on session session for file system filesystem-name.
Explanation: Setting events and dispositioning these on a DM session enables the file system for ADSM space management support.
System Action: ADSM continues.
User Response: Continue with normal operation.

ANS9504W program-name: The file system filesystem-name is not mounted or is mounted with wrong options.
Explanation: Either the file system is not mounted or it has been mounted with incorrect options.
System Action: ADSM continues.
User Response: Mount the file system or remount it with corrected mount options.

ANS9505E program-name: cannot initialize DM services. Reason: error.
Explanation: ADSM space management cannot initialize the DM services.
System Action: ADSM cannot start space management support.
User Response: Correct error and retry operation. Make sure that DM services have been installed on the system (Hierarchical Storage Management Support).

ANS9506E program-name: cannot query the right on session session token = token. Reason: error.
Explanation: ADSM space management cannot query the right that is held on a file during the recall process.
System Action: Processing of the file is interrupted.
User Response: Continue with normal operation.

ANS9507E program-name: cannot request the right on session session for file handle filehandle
token = token. Reason: error.
Explanation: ADSM space management cannot request the required right on a file.
System Action: Processing of the file is interrupted.
User Response: Continue with normal operation.

ANS9508W program-name: cannot release the right on session session for file handle = filehandle
token = token. Reason: error.
Explanation: ADSM space management cannot release the right on a file.
System Action: Processing of the file is interrupted.
User Response: Continue with normal operation.

ANS9509W program-name: received an unexpected event of type event-type on session session.
Explanation: ADSM space management daemon received an unexpected event. This event has not been dispositioned.
System Action: ADSM ignores event and continues.
User Response: Continue with normal operation.

ANS9510E program-name: cannot get event messages from session session,
expected max message-length = msglen, returned message-length = return-length.
Reason: error.
Explanation: ADSM space management encountered an error while trying to receive a message on a DM session.
System Action: ADSM continues.
User Response: Continue with normal operation.

ANS9511E program-name: cannot read DM attributes on session session for
file handle = handle token = token. Reason: error.
Explanation: ADSM space management cannot read the DM attributes of a DM object, usually a file.
System Action: Processing of the file is interrupted.
User Response: Continue with normal operation.

ANS9512E program-name: cannot set DM attributes on session session for
file handle = filehandle token = token. Reason: error.
Explanation: ADSM space management cannot set DM attributes for a DM object, usually a file.
System Action: Processing of the file is interrupted.
User Response: Continue with normal operation.

ANS9513E program-name: cannot remove DM attributes on session session for
file handle = filehandle token = token. Reason: error.
Explanation: ADSM space management cannot remove DM attributes for a DM object, usually a file.
System Action: Processing of the file is interrupted.
User Response: Continue with normal operation.

ANS9514E program-name: cannot create a file handle from path. Reason: error.
Explanation: ADSM space management cannot create a file handle from the given file.
System Action: Processing of the file is interrupted.
User Response: Continue with normal operation.

ANS9515E program-name: cannot set the migration information. Reason: error.
Explanation: ADSM space management cannot set the migration information of a file, because space management cannot create a file handle from the file and/or from the file system.
System Action: Processing of the file is interrupted.
User Response: Continue with normal operation.

ANS9516E program-name: cannot create an user event message on session session. Reason: error.
Explanation: ADSM space management cannot create an user event message, needed to reference rights on a file to be processed.
System Action: Processing of the file is interrupted.
User Response: Continue with normal operation.

ANS9517E program-name: cannot clear all event messages from session session. Reason: error.
Explanation: ADSM space management is in the process of destroying a DM session. There are still - unexpected - event messages on this session that could not be responded to.
System Action: ADSM DM session is not destroyed.
User Response: See your system administrator.

ANS9518E program-name: cannot respond to an event message on session session using token token
Reason: error.
Explanation: An event message could not be responded to (returned to the system).
System Action: ADSM space management continues.
User Response: If a user process is unexpectely blocked and cannot be killed, see your system administrator.

ANS9519W program-name: cannot set eventlist for a file system on session session
token = token fs-handle = fs-handle. Reason: error.
Explanation: An eventlist could not be set on a file system. None of the events will be generated by the system on this file system.
System Action: ADSM space management continues.
User Response: Resolve the problem and retry the operation.

ANS9520E program-name: cannot set a managed region on session session
for file handle = filehandle token = token. Reason: error.
Explanation: A managed region could not be set on a file. No events will be generated for this file.
System Action: Processing of the file is interrupted.
User Response: If this error recurs, see your system administrator.

ANS9521E program-name: cannot get the file attributes on session session
for file handle = handle token = token. Reason: error.
Explanation: ADSM space management cannot read the attributes of a file.
System Action: Processing of the file is interrupted.
User Response: If this error recurs, see your system administrator.

ANS9522E program-name: file for migration has changed - migration skipped
for file handle = filehandle.
Explanation: The file in migration has been modified.
System Action: ADSM stopped migration of the file.
User Response: Retry operation.

ANS9523E program-name: cannot probe the hole for the file on session session
file handle = filehandle token = token. Reason: error.
Explanation: A correct stubsize could not be determined by the system.
System Action: ADSM stopped migration of the file.
User Response: Resolve the problem and retry the operation.

ANS9524W program-name: probe hole adjusted stubsize to an allowed value on session session
file handle = filehandle token = token
old stubsize = old-size new stubsize = new-size.
Explanation: The predefined stubsize for the file was not valid. The system corrected the stubsize.
System Action: ADSM space management continues.
User Response: Continue with normal operation.

ANS9525E program-name: cannot punch a hole in the file (create a stubfile) on session session
for file handle = handle token = token. Reason: error.
Explanation: An error occurred while creating a stub file.
System Action: Processing of the file is interrupted.
User Response: Continue with normal operation.

ANS9526E program-name: cannot open the state file filename for writing. Reason: error.
Explanation: The state file (global or file system state file) could not be opened.
System Action: ADSM stops processing.
User Response: Resolve the problem and retry the operation.

ANS9527E program-name: cannot write to the state file filename. Reason: error.
Explanation: ADSM space management could not write to the state file.
System Action: ADSM stops processing.
User Response: Resolve the problem and retry the operation.

ANS9528W program-name: cannot read from the state file filename. Reason: error.
Explanation: ADSM space management could not read from the state file.
System Action: ADSM stops processing.
User Response: Resolve the problem and retry the operation.

ANS9529W program-name: cannot obtain handle of file system state file.
Explanation: ADSM space management could not find the handle of a file system state file, that is stored in the global state file. This can be true if either space management is querying a file system that has no HSM support added, or the file system state file is corrupted, or the global state file is corrupted.
System Action: ADSM continues or stops processing, depending on the situation.
User Response: If processing has stopped, resolve the problem and retry the operation.

ANS9530W program-name: cannot remove an entry for file-system from the global state file.
Explanation: The entry for the file system in the dmiFSGlobalState file cannot be removed. Possible reasons:

• Not enough memory to create temporary file name for temporary file system table.
• Not enough free space or inodes to create temporary file system table
• Cannot open the real and/or temporary file system table files.

System Action: ADSM does not remove the entry from the global state file.
User Response: Resolve the problem and retry the operation.

ANS9531E program-name: cannot create a DM session: old session = oldsession
session info = session-info. Reason: error.
Explanation: ADSM space management could not create a DM session.
System Action: ADSM stops processing.
User Response: See your system administrator.

ANS9532W program-name: cannot destroy the session session. Reason: error.
Explanation: ADSM space management could not destroy a DM session.
System Action: ADSM continues.
User Response: See your system administrator.

ANS9533W program-name: failed getting all sessions. Reason: error.
Explanation: ADSM space management could not get all DM sessions on the system.
System Action: ADSM stops processing.
User Response: See your system administrator.

ANS9534W program-name: cannot query a session. Reason: error.
Explanation: ADSM space management could not query a DM session on the system.
System Action: ADSM continues.
User Response: Continue with normal operation.

ANS9535E program-name: a file handle could not be created from the file descriptor file-descriptor.
Reason: error.
Explanation: ADSM space management could not create a file handle.
System Action: Processing of the file is interrupted.
User Response: If this error recurs, see your system administrator.

ANS9536W program-name: the file system filesystem-name could not be umounted. Reason: error.
Explanation: The file system could not be unmounted to remove HSM support option from the mount command. HSM has been removed from the file system. All files on the file system are local. No migration will be possible.
System Action: ADSM continues.
User Response: Resolve the problem and remount the file system according to the entry in /etc/fstab.

ANS9537E program-name: the file system filesystem-name could not be mounted. Reason: error.
Explanation: The file system could not be mounted.
System Action: ADSM stops processing.
User Response: Resolve the problem and retry the operation.

ANS9538W program-name: request request for DM file attributes not recognized.
Explanation: An unknown request type has been encountered that cannot be handled.
System Action: ADSM continues.
User Response: Continue with normal operation.

ANS9539E program-name: cannot create a file system handle from the
file handle = filehandle. Reason: error.
Explanation: A file system handle could not be created from a file handle.
System Action: ADSM continues.
User Response: Continue with normal operation.

ANS9542E program-name: the file attributes could not be set on session session
for file handle = filehandle token = token flag = flag
Reason: error.
Explanation: ADSM space management could not update file attributes.
System Action: Processing of the file is interrupted.
User Response: If this error recurs, see your system administrator.

ANS9543W program-name: cannot reserve blocks for nospace condition on file system filesystem-name.
Reason: error.
Explanation: ADSM space management could not reserve blocks on the file system to be used in a nospace condition.
System Action: ADSM continues.
User Response: Resolve the problem, then restart the monitor daemon.

ANS9544W program-name: cannot obtain allocation info on session sessionL
file handle = filehandle token = tokenL offset=offsetL
number of extents = nextents (returned = nreturned)
Reason: error.
Explanation: ADSM space management could not get allocation information of a file.
System Action: Processing of the file is interrupted.
User Response: If this error recurs, see your system administrator.

ANS9545E program-name: cannot get lock for lockdirlockfile to continue processing.
Explanation: ADSM space management could not obtain a lock for a file.
System Action: Processing stopped.
User Response: Resolve the problem and retry the operation.

ANS9546I Attempting to access remote file.
Explanation: A process is attempting to access a file that is not stored locally.
System Action: waits for space management to recall the file.
User Response: Continue with normal operation.

ANS9547W File access denied because file is in migration.
Explanation: The file being accessed is currently being migrated. Access to this file is denied during the migration process.
System Action: Retry after migration has been completed.
User Response: Continue with normal operation.

ANS9548W Cannot complete remote file access.
Explanation: ADSM space management cannot complete the remote file access. The file may be migrated to an ADSM migration server. The file cannot be recalled to the local machine. The server could be temporarily disabled.
System Action: ADSM terminates the current operation.
User Response: Check to see whether the server has been disabled by the system administrator, then retry the operation.

ANS9549W File migration has been discontinued.
Explanation: Migration stops because the file is being migrated by another process or a system error occurred.
System Action: ADSM terminates the current operation.
User Response: Continue with normal operation.

ANS9550W File recall has been discontinued.
Explanation: Recall stops because the file being recalled would cause the file system to run out of space.
System Action: ADSM terminates the current operation.
User Response: Increase the file system space, or remove unneeded files, or wait until space management has migrated files off the file system by demand or threshold migration, or manually migrate files. Then retry the operation.

ANS9552E program-name: cannot add fsm to file-system; path includes non-local file system.
Explanation: An attempt was made to add space management to a file system whose path contains non-local elements.
System Action: Processing stopped.
User Response: File system must be entirely local.

ANS9553I Wrote temporary candidates list to file-name.
Explanation: Due to out of space condition, the candidates list was written to the named temporary file.
System Action: Temporary file created.
User Response: Temporary file can be copied to the appropriate .SpaceMan directory when space is made available.

ANS9555W program-name: This ADSM daemon requires cell_admin's password to refresh its DCE ticket.
Please enter your DCE password:.
Explanation: The DCE ticket expires after a certain time and the ADSM daemons require cell_admin's password to refresh their access privileges. This procedure can be automated by storing the password in /etc/security/adsm/dcepasswd.
System Action: The system waits for your password.
User Response: Enter your password.

ANS9556W program-name: Your account does not allow access to the DCE registry database! Aborting ...
Explanation: Certain programs require full cell administrator privileges. Otherwise, the start-up permission is not granted.
System Action: The program aborts the operation.
User Response: Contact your cell administrator.

ANS9557W program-name: It was not possible to renew the DCE ticket for an ADSM daemon! Please restart! Aborting ...
Explanation: There may be some situation where the ADSM daemons fail to renew their DCE ticket (for example, if the password for cell_admin is changed).
System Action: The program aborts the operation.
User Response: Restart dsmmonitord and dsmrecalld with proper privileges.

ANS9559W program-name: Cannot extract cell properties! Aborting ...
Explanation: There may be some situation where it is not possible to extract necessary cell information (for example, if the DCE daemons are not started properly).
System Action: The program aborts the operation.
User Response: Check your DCE environment.

ANS9560W program-name: You must be cell_admin to run this function! Aborting ...
Explanation: Certain programs require cell_admin privileges.
System Action: The program aborts the operation.
User Response: Contact your cell administrator.

ANS9561W program-name: Cannot extract your account information from the DCE registry! Aborting ...
Explanation: There may be some situation where it is not possible to extract necessary account information (for example, if the DCE daemons are not started properly).
System Action: The program aborts the operation.
User Response: Check your DCE environment.

ANS9562W program-name: Your account does not allow access to the DCE registry database! Aborting ...
Explanation: There may be some situation where it is not possible to extract DCE registry information (for example, if the DCE daemons are not started properly).
System Action: The program aborts the operation.
User Response: Check your DCE environment.

ANS9563W program-name: The default certificate lifetime must be longer than 1 hour! Aborting ...
Explanation: The default DCE ticket lifetime has to be longer than 1 hour to ensure that long operations have enough time to fullfill their tasks.
System Action: The program aborts the operation.
User Response: Set DCE ticket lifetime to a value greater than one hour.

ANS9564W program-name: Severe problem! Cannot access the dfstab and/or filesystem list!.
Explanation: ADSM requires access to the /opt/dcelocal/var/dfs/dfstab and the filesystem table.
System Action: None
User Response: Repeat operation. If the problem persists, contact your system and/or cell administrator.

ANS9565W program-name: Severe problem! Cannot access the dfstab!.
Explanation: ADSM requires access to the /opt/dcelocal/var/dfs/dfstab.
System Action: None
User Response: Repeat operation. If the problem persists, contact your system and/or cell administrator.

ANS9566W program-name: Failed to analyse path path!.
Explanation: The ADSM DFS HSM client works within HSM managed DCE environments only.
System Action: The program aborts the operation.
User Response: Contact your system and/or cell administrator.

ANS9567W program-name: The provided password failed for the cell_admin account!.
Explanation: Several ADSM commands require cell_admin privileges to perform security sensitive tasks. The password for the account can be supplied on the console, or it can be stored in /etc/security/adsm/dcepasswd.
System Action: The program aborts the operation.
User Response: Update /etc/security/adsm/dcepasswd, or enter the correct password.

ANS9568W program-name: Aggregate aggregate-name is going to be DETACHED from the cell !!!
You have 5 seconds to intervene via CTRL-C!.
Explanation: Activating HSM may require detaching aggregates from your cell to install DMApi support. All file operation within the aggregate will fail for this period.
System Action: The system waits 5 secs before the program continues.
User Response: Wait and grant the detachment or interrupt.

ANS9569W program-name: Please specify the name of the aggregate!.
Explanation: Some programs require the name of an aggregate as a parameter.
System Action: The program aborts the operation.
User Response: Restart the program with an aggregate name.

ANS9570W program-name: Aggregates without any fileset cannot be HSM managed!.
Explanation: An aggregate has to include at least one fileset to be HSM managed
System Action: The program aborts the operation.
User Response: Install at least one fileset in the aggregate.

ANS9571W program-name: Permission denied! Only cell_admin is allowed to run this command!.
Explanation: Some programs require cell administrator (cell_admin) privileges.
System Action: The program aborts the operation.
User Response: Contact your system and/or cell administrator.

ANS9572W program-name: All local aggregates are going to be DETACHED from the cell toactivate HSM management !!!
You have 5 seconds to intervene via CTRL-C!.
Explanation: Activating HSM may require detaching all local aggregates from your cell to install DMApi support. All file operation will fail for this period.
System Action: The system waits 5 secs before the program continues.
User Response: Wait and grant the detachment or interrupt.

ANS9574W program-name: The minimum ticket lifetime must be 10 minutes or longer! Aborting ...
Explanation: The minimum DCE ticket lifetime must be 10 minutes or longer to ensure that long ADSM operations have enough time to fullfill their tasks.
System Action: The program aborts the operation.
User Response: Set minimum DCE ticket lifetime to at least 10 minutes.

ANS9575W program-name: Your login context is not authorized to access necessary networkresources! Aborting ...
Explanation: This may happen if it was not possible to renew a DCE login context.
System Action: The program aborts the operation.
User Response: Contact your system and/or cell administrator. Restart daemons.

ANS9576W program-name: The password of cell administrator (cell_admin) has expired!Please update the ADSM password file and restart the daemons! Aborting ...
Explanation: Password expiration of the cell administrator's login context.
System Action: The program aborts the operation.
User Response: Update the DCE password file in /etc/security/adsm/dcepasswd and restart daemons.

ANS9577W program-name: The file or directory does not reside in an HSM managedaggregate: path!.
Explanation: Some of the ADSM DFS HSM commands works within HSM managed DCE environments only.
System Action: The program aborts the operation. The only exception is dsmls.
User Response: Make sure that the path resides in an HSM managed aggregate.

ANS9578W program-name: Cannot access the cell! You're either not logged into the cell or the cell is currently down! Aborting ...
Explanation: The program was not able to access the DFS filespace.
System Action: The program aborts the operation.
User Response: Make sure that you are correctly logged into the cell and/or renew your DCE ticket. Check whether your local DCE environment is running.

ANS9581W dsmmigfs: Severe Problem! Cannot mount a newly created fileset which is used for administrative HSM purposes. DFS may be inconsistent here! Aborting ...

Explanation: dsmmigfs was not able to create and mount a fileset within its administrative structure.
System Action: dsmmigfs aborts the operation.
User Response: The cell's behaviour is inconsistent here. Reinitialize DFS.

ANS9582W program-name: Severe Problem! Cannot access the DFS root directory!
Aborting ...
Explanation: The DFS root directory "/:/" or /.../cellname/fs was not accessible
System Action: The program aborts the operation.
User Response: The aggregate inhibiting the root fileset, or the root fileset itself has not been exported. Contact your cell administrator.

ANS9583W program-name: The size of this aggregate is too small.
Use aggregates larger than 100MB. The administrative HSM structure is relatively large for the specified size of only number MB.

Explanation: The size of this aggregate is too small. The administrative HSM structure is relatively large for the specified size of the aggregate.
System Action: The program aborts the operation.
User Response: Use aggregates larger than 100MB.

ANS9596W program-name: The selected aggregate is not yet enabled for Data Management!
Please perform the following steps prior to this command:
1. dfsexport -detach -aggregate aggregate name
2. Edit /opt/dcelocal/var/dfs/dfstab and change the filessystem type of aggregate aggregate name from lfs to dmlfs
3. /usr/lpp/dce/bin/dmaggr -aggregate aggregate name -on
4. dfsexport -aggregate aggregate name
Please be aware of the DCE usage restrictions on DM enabled aggregates!.
Explanation: HSM managed aggregates have to be DM enabled.
System Action: The program aborts the operation.
User Response: Perform the changes and restart the command. See manual for details.

ANS9597W program-name: The selected aggregate is still enabled for Data Management!
There are DCE usage restriction on DM enabled aggregates which can be disabled by performing the following steps:
1. dfsexport -detach -aggregate aggregate name
2. Edit /opt/dcelocal/var/dfs/dfstab and change the filessystem type of aggregate aggregate name from dmlfs to lfs
3. /usr/lpp/dce/bin/dmaggr -aggregate aggregate name -off
4. dfsexport -aggregate aggregate name.
Explanation: After removing HSM from an aggregate, the DM attribute should be set to its normal value.
System Action: None
User Response: Perform the changes. See manual for details.

ANS9641S Invalid option 'option' found in options file 'file-name'
at line number : number
Invalid entry : 'entry'.
Explanation: The specified optionin the ADSM options file (file-name) is in error.
System Action: Processing stopped.
User Response: Correct the options file entry.

ANS9732E No Backup Copy Group for Management Class: management-class.
Explanation: The management class for this file does not have a backup copy group specified.
System Action: Processing stopped.
User Response: See your system administrator.

ANS9733E File: File-name excluded by the Include/Exclude list.
Explanation: You tried to back up the named file-name that was specified to be excluded from backup.
System Action: ADSM did not back up the file.
User Response: Specify the file using the Include option and retry the operation.

ANS9734E There are number file(s) not selected. Click on file to find out reason.
Explanation: There are files that cannot be selected.
System Action: These files will not be selected for migrate or recall.
User Response: Click on the files to find out the reason these files are not selected, for example, inclexcl list.

ANS9735E Error doing realtime initialization.
Explanation: ADSM ran out of resource (either processes or shared storage) that prevents it from starting a migrate or recall operation. Your file selections remain intact.
System Action: ADSM cannot start the migrate or recall operation.
User Response: Retry the operation. If unsuccessful, see your system administrator.

ANS9736E Not enough memory for authorization list table.
Explanation: ADSM cannot allocate enough storage for the authorization list.
System Action: ADSM cannot complete the requested operation.
User Response: Retry the operation. If unsuccessful, see your system administrator.

ANS9737E Authentication failed -- Exit ADSM to retry.
Explanation: You typed an incorrect password four times in a row.
System Action: ADSM cannot connect to the server without a correct password.
User Response: Exit and restart ADSM if authorized; otherwise, see your system administrator.

ANS9738S Out of memory.
Explanation: ADSM found an error allocating storage at initialization.
System Action: ADSM cannot continue.
User Response: See your system administrator.

ANS9739E Cannot get shared memory.
Explanation: The system ran out of shared storage resources.
System Action: ADSM cannot continue without a shared storage segment.
User Response: Check the output of the "ipcs" program to see if there are many new shared storage segments. Use "ipcrm" to remove them. If this problem continues, configure UNIX to allow more shared storage segments.

ANS9740S This program is not installed correctly. Please place the application
defaults file (file-name) into the application default directory
(usually directory-name), or set the XAPPLRESDIR
environment variable to the directory containing the file-name
defaults file.
Explanation: ADSM cannot find its resource file (Sm) in the default directory (directory-name). A problem may have occurred during installation.
System Action: ADSM cannot start.
User Response: See your system administrator.

ANS9741E Not enough memory to hold directory structure.
Explanation: ADSM cannot allocate storage for the requested directory structure. This error can happen under migrate or recall operations.
System Action: ADSM cannot complete the requested operation.
User Response: Retry the operation. If unsuccessful, see your system administrator.

ANS9742E Error reading directory structure.
Explanation: ADSM cannot load the requested directory structure. This error is due to a corrupted file system or a storage shortage. This can happen under selective migrate or selective recall.
System Action: ADSM cannot complete the requested operation.
User Response: Retry the operation. If unsuccessful, see your system administrator.

ANS9743W No files selected in directory tree.
Explanation: You did not select any files to list for migrate or recall.
System Action: ADSM cannot complete the requested operation.
User Response: Select files and retry the operation.

ANS9744W Size exceeds limit.
Explanation: You tried to recall a file that has exceeded the maximum file size limitation on your system.
System Action: ADSM cannot recall the file.
User Response: Recall this file on a system that supports the file size. See your system administrator.

ANS9790I File is skipped for migration: No backup copy found.
Explanation: A management class is assigned to the file with the attribute MIGREQUIRESBKUP set to YES. This requires a current backup copy of the file before migration. However, there is no backup copy found on the migration server. This file will not be migrated.

Note: ADSM checks only the migration server for a backup copy. If the migration server and backup server are different servers, ADSM does not find a backup copy of the file.
System Action: ADSM does not migrate this file.
User Response: Back up this file on the migration server, or assign a management class to this file that does not require a current backup copy. Retry the operation.

ANS9791I File is skipped for migration: Backup copy found is not current.
Explanation: A management class is assigned to the file with the attribute MIGREQUIRESBKUP set to YES. This requires a current backup copy of the file before migration. However, the backup copy found on the migration server is an old version. This file will not be migrated.

Note: ADSM checks only the migration server for a backup copy. If the migration server and backup server are different servers, there must be a valid backup copy of the file on the migration server.
System Action: ADSM does not migrate this file.
User Response: Back up the current file on the migration server, or assign a management class to this file that does not require a current backup copy. Retry the operation.

ANS9792W A tree view of a file system is being built. Please
wait until it completes, and then retry the operation.
Explanation: You tried to choose Selective Migration or Selective Recall when a tree view of a file system is being built.
System Action: ADSM ignores the request.
User Response: Wait until the tree view build completes, and then retry the operation.

ANS9796E Cannot access lock file for file-system file system.
Explanation: ADSM cannot access a lock file due to an error. The lock file provides serialization of certain programs to prevent conflicting processes from running at the same time.
System Action: ADSM will not run the program at this time.
User Response: Check the permissions on the directories leading up to the lock file and also the permissions on the program executable.

ANS9797E A conflicting space management process is already
running in the file-system file system.
Rerun this process at a later time.
Explanation: ADSM detects that another process that conflicts with the process you are trying to run is running in the file system. The following processes cannot be run at the same time for a file system:

dsmreconcile

dsmautomig

dsmmigfs remove.

Also dsmmigfs remove cannot run while a migration process is running in the file system.
System Action: ADSM will not run the process at this time.
User Response: Try running the process again later.

ANS9799W Cannot open temp file for
mount command.
Explanation: ADSM cannot open a temporary file to process the mount command for this file system.
System Action: ADSM cannot add space management to the file system.
User Response: Check with the system administrator.

ANS9800W Cannot create temp file for
mount command.
Explanation: ADSM cannot create a temporary file to process the mount command for this file system.
System Action: ADSM cannot add space management to the file system.
User Response: Check with the system administrator.

ANS9801W Cannot create transaction file.
Explanation: Cannot create transaction file for this file system.
System Action: ADSM cannot add space management to the file system.
User Response: Check with the system administrator.

ANS9802W Cannot create status file.
Explanation: Cannot create status file for this file system.
System Action: ADSM cannot add space management to the file system.
User Response: Check with the system administrator.

ANS9803W Cannot create premigration database.
Explanation: Cannot create a premigration database for this file system.
System Action: ADSM cannot add space management to the file system.
User Response: Check with the system administrator.

ANS9804W Cannot create migration candidates list.
Explanation: Cannot create a migration candidates list for this file system.
System Action: ADSM cannot add space management to the file system.
User Response: Check with the system administrator.

ANS9805W Cannot create .SpaceMan directory.
Explanation: Cannot create .SpaceMan directory for this file system.
System Action: ADSM cannot add space management to the file system.
User Response: Check with the system administrator.

ANS9806W File system type is not supported.
Explanation: The file system is not a type supported by space management.
System Action: ADSM cannot add space management to the file system.
User Response: Check with the system administrator.

ANS9808W Invalid field in the dsmmigfstab file.
Explanation: There is an invalid field in the dsmmigfstab file entry for the file system.
System Action: ADSM cannot add space management to the file system.
User Response: Check with the system administrator.

ANS9809W Cannot open the dsmmigfstab file.
Explanation: ADSM cannot open the dsmmigfstab file.
System Action: ADSM cannot add space management to the file system.
User Response: Check with the system administrator.

ANS9811W Server did not respond. Check the server
connection. Select OK to exit.
Explanation: Server did not respond.
System Action: ADSM stops processing.
User Response: Exit dsmhsm. Check the server connection and try again later.

ANS9812I Files not found in current directory. Refresh file systems.
Explanation: Some files are not found in the local file system.
System Action: The transaction will show incorrect results.
User Response: Refresh the file systems to reflect local file systems.

ANS9813W Incorrect data shown. Run reconcile.
Explanation: Information in the space management status file is not synchronized with the file system.
System Action: ADSM continues processing.
User Response: To correct the information, run reconcile, and then refresh the current window.

ANS9814W Cannot create migration object ID.
Explanation: The file system is full. No more free space can be allocated for the migration object ID when a file is being migrated or recalled.
System Action: ADSM terminates the current operation for this file system.
User Response: Remove some files in the file system, and then run reconciliation. Retry the operation.

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

ANS9816W File system has exceeded its quota.
Explanation: ADSM detects that the file system has exceeded its quota. No more files can be migrated to ADSM storage for this file system.
System Action: ADSM will not migrate files from this file system.
User Response: Either recall some files to the local file system, or ask the system administrator to increase the quota for this file system.

ANS9817W file-system is globally deactivated. Please wait until the
file system is globally reactivated.
Explanation: The file system is in a global inactive state.
System Action: ADSM cannot continue the process.
User Response: Wait until the system administrator globally reactivates the file system.

ANS9818W A selective recall is in progress.
Stop the recall, and then close the window.
Explanation: You tried to close the Selective Recall Status window while a selective recall was in progress.
System Action: ADSM ignores the request.
User Response: Stop the selective recall process, and then close the window.

ANS9819W A selective migration is in progress.
Stop the process, and then close the
window.
Explanation: You tried to close the Selective Migration Status window while a selective migration was in progress.
System Action: ADSM ignores the request.
User Response: Stop the selective migration process, and then close the window.

ANS9820W A selective recall or a selective migration
is in progress. Wait until it completes,
and then retry the operation.
Explanation: You tried to perform one of the following while a selective recall or selective migration process was in progress:

Add space management

Deactivate or reactivate space management

Global deactivate or reactivate space management

Display policy information

Change password

System Action: ADSM ignores the request.
User Response: Wait until the selective recall or selective migration process is complete, and then retry the operation.

ANS9821W New password is not re-entered.
Explanation: You did not re-enter the new password.
System Action: The Change password dialog will display again.
User Response: Re-enter the new password.

ANS9822W New password is not entered.
Explanation: You did not enter the new password.
System Action: The Change password dialog will display again.
User Response: Enter the new password.

ANS9823W Current password is not entered.
Explanation: You did not enter the current password.
System Action: The Change password dialog will display again.
User Response: Enter the current password.

ANS9824W Cannot update space management
settings for file system.
Explanation: You tried to update space management settings for a file system, and the update failed.
System Action: ADSM continues with normal operation.
User Response: Check with the system administrator.

ANS9825W Total migrated space is greater than quota for file system.
Explanation: ADSM total migrated space is greater than quota.
System Action: ADSM continues.
User Response: You can remove this warning message by increasing the quota for the file system.

ANS9827W Error accessing the Recall daemon lock file: file name.
Explanation: There is a problem accessing the recall daemon lock file.
System Action: ADSM cannot determine whether the recall daemon is running. Because the recall daemon is needed to perform file recalls, the recall fails.
User Response: Check with the system administrator. The recall process needs read access to the /etc/adsm/SpaceMan/dsmrecalld.pid file.

ANS9828W Error processing the space monitor
daemon: reason.
Explanation: There is a problem accessing the space monitor daemon.
System Action: ADSM cannot perform automatic space management functions.
User Response: Check with the system administrator. The space monitor daemon is normally installed as /usr/lpp/adsm/bin/dsmmonitord.

ANS9829W Recall daemon is not running.
Explanation: An ADSM recall daemon is not running.
System Action: ADSM recall fails.
User Response: Ask the system administrator to start a recall daemon by issuing the dsmrecalld command.

ANS9830W Space monitor daemon is not running.
Explanation: The space monitor daemon is not running.
System Action: ADSM is unable to perform space management functions.
User Response: Ask the system administrator to start the space monitor daemon by issuing the dsmmonitord command.

ANS9840W Cannot open /dev/fsm.
Explanation: While attempting to add space management to a file system, ADSM was unable to open the /dev/fsm device, which is the space management (hsm) device driver.
System Action: ADSM terminates the requested process and returns to normal operation.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9841E Cannot get user name for the user ID.
Explanation: ADSM cannot get the user name for the user ID.
System Action: ADSM terminates the requested process and returns to normal operation.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9842E Cannot refresh local file space information.
Explanation: ADSM cannot refresh local file space information.
System Action: ADSM terminates the requested process and returns to normal operation.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9843E Cannot connect to migration server.
Explanation: ADSM cannot connect to the migration server specified in your client system options file.
System Action: ADSM terminates the requested process and returns to normal operation.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9844E Cannot close the premigrated files database.
Explanation: ADSM cannot close the premigrated files database for the file system. The premigrated files database resides in the .SpaceMan subdirectory of the file system's root directory.
System Action: ADSM terminates the requested process, and returns to normal operation.
User Response: Retry the operation. If the problem continues, check with your system administrator.

ANS9846W Cannot add space management to file system.
Explanation: ADSM cannot add space management to the file system.
System Action: ADSM continues with normal operation.
User Response: Check with the system administrator.

ANS9848W Cannot activate file system file system.
Explanation: ADSM cannot activate space management for the specified file system.
System Action: ADSM file system state is not changed.
User Response: Check with your system administrator.

ANS9849W A error occurred while refreshing the pie chart information for file system. Data is not updated.
Explanation: An error occurred while refreshing pie chart information.
System Action: ADSM pie chart information is not updated.
User Response: Check with your system administrator.

ANS9850E The view book program is already
running on your desktop.
Explanation: The view book program has already been launched and is still running.
System Action: ADSM continues with normal operation.
User Response: Check your desktop for the running view book program.

ANS9851E Cannot find the view book program.
Double check the BOOKS option in your
client user options file.
Explanation: The space management GUI client failed to execute the program you specified with the BOOKS option in your client user options file.
System Action: ADSM continues with normal operation.
User Response: Check to make sure the PATH environment variable contains the path to the program, or double check the BOOKS option to make sure the name is correct.

ANS9852E Cannot query the level of client and kernel.
Explanation: The space management GUI client fails to query the level of kernel and client code.
System Action: ADSM continues with normal operation.
User Response: Check with your system administrator.

ANS9853W The space management client program is downlevel.
Explanation: The space management client is downlevel compared to the kernel level.
System Action: ADSM continues with normal operation.
User Response: Check with your system administrator.

ANS9854W The space management kernel is downlevel.
Explanation: The space management kernel is downlevel compared to the client level.
System Action: ADSM continues with normal operation.
User Response: Check with your system administrator.

ANS9855W File is accessed during migration. File skipped.
Explanation: The specified file-name was not migrated because the file was accessed by another process during the attempt to migrate it.
System Action: ADSM left the file resident.
User Response: If you want the file migrated, stop the process which is accessing the file and retry the migration operation.

ANS9856E File is currently opened by another process. File skipped.
File has already been migrated or is currently being migrated
by another process.
Explanation: The specified file was not migrated because the file was opened by one or more other processes.
System Action: ADSM left the file resident.
User Response: If you want the file migrated, stop the processes which currently have the file open, and retry the migration operation.

ANS9857E View Books requires BOOKS option in the options file.
Explanation: The BOOKS option is not specified in your client user options file (dsm.opt).
System Action: ADSM continues with normal operation.
User Response: Add a BOOKS option specifying the executable name of the online book reader and the name of the ADSM Bookshelf. Then, retry the operation.

ANS9858E Bit file for image on push button cannot
be found. Please check to make sure the pixmap file
exists in your ADSM installed directory.
Explanation: ADSM failed to find the pixmap file defined for the push button.
System Action: ADSM continues with normal operation.
User Response: Check to see whether the pixmap file exists in the ADSM installation directory.

ANS9859E Cannot get information for filespace file space: reason.
Explanation: Error encountered when system reads common attributes about the file space.
System Action: ADSM cannot read file space attributes.
User Response: Check with your system administrator.

ANS9860W Some selected files are hidden. Change View option to see all.
Explanation: You have selected all files in a directory or in all subdirectories. Due to the current View option, only certain types of files are shown (either migrated, resident, or premigrated files).
System Action: ADSM proceeds normally.
User Response: If you want to see all selected files, change the View option from the View menu bar option.

ANS9862W Do you want to exit
ADSM space management?
Explanation: You have selected Exit from the File menu bar option.
System Action: ADSM waits for your response.
User Response: If you want to exit the program, select OK. Otherwise, select Cancel.

ANS9871W Specified column width is smaller than the largest attribute
value. Data will be truncated.
Explanation: You have entered a column width that is too small to display all digits of the largest attribute.
System Action: ADSM accepts your request.
User Response: To see all attributes in full length, increase the column width.

ANS9872W Remove is in progress. Requested operation is not allowed.
Explanation: A remove process is in progress. You have requested an operation that is not allowed when a remove process is in progress.
System Action: ADSM continues with normal operation.
User Response: Wait until the remove process completes, and then retry the operation.

ANS9875W Refresh time must be numeric value and within
0 - 14400 minutes or 0 - 240 hours (10 days).
Explanation: You have entered an invalid value for Refresh time. It must be a positive number between 0 and 14400.
System Action: ADSM continues with normal operation.
User Response: Enter a positive number between 0 and 14400.

ANS9876W Refresh time must be a positive number.
Explanation: You have entered an invalid value for Refresh time. It must be a positive number between 0 and 14400.
System Action: ADSM continues with normal operation.
User Response: Enter a positive number between 0 and 14400.

ANS9877W Size Factor must be a numeric value between 0 - 999999999.
Explanation: You have entered an invalid value for Size Factor. It must be a positive number between 0 and 999999999.
System Action: ADSM continues with normal operation.
User Response: Enter a positive number between 0 and 999999999.

ANS9878W Size Factor must be a positive number.
Explanation: You have entered an invalid value for Size Factor. It must be a positive number between 0 and 999999999.
System Action: ADSM continues with normal operation.
User Response: Enter a positive number between 0 and 999999999.

ANS9879W Age Factor must be a numeric value between 0 - 999999999.
Explanation: You have entered an invalid value for Age Factor. It must be a positive number between 0 and 999999999.
System Action: ADSM continues with normal operation.
User Response: Enter a positive number between 0 and 999999999.

ANS9880W Age Factor must be a positive number.
Explanation: You have entered an invalid value for Age Factor. It must be a positive number between 0 and 999999999.
System Action: ADSM continues with normal operation.
User Response: Enter a positive number between 0 and 999999999.

ANS9881W Premigration Percent must be a numeric value between 0 - 100.
Explanation: You have entered an invalid value for Premigration Percentage. It must be a positive number between 0 and 100.
System Action: ADSM continues with normal operation.
User Response: Enter a positive number between 0 and 100.

ANS9882W Premigration Percent must be a positive number.
Explanation: You have entered an invalid value for Premigration Percentage. It must be a positive number between 0 and 100.
System Action: ADSM continues with normal operation.
User Response: Enter a positive number between 0 and 100.

ANS9883W Quota must be a numeric value between 0 - 999999999.
Explanation: You have entered an invalid value for Quota. It must be a positive number between 0 and 999999999.
System Action: ADSM continues with normal operation.
User Response: Enter a positive number between 0 and 999999999.

ANS9884W Quota must be a positive number.
Explanation: You have entered an invalid value for Quota. It must be a positive number between 0 and 999999999.
System Action: ADSM continues with normal operation.
User Response: Enter a positive number between 0 and 999999999.

ANS9885I The premigration percentage will not be updated
until you select the Update push button on the Update
window or the Add push button on the Add window.
Explanation: While you have just selected 'OK' in the Advanced Feature dialog, the premigration percentage is not activated until you select 'Add' or 'Update' in the 'Add space management', or the 'Update space management' dialog.
System Action: ADSM waits until you select 'Add' or 'Update' to apply your premigration percentage to the system.
User Response: When you have changed the space management attribute, select 'Add' or 'Update', and then the system will apply your new premigration percentage.

ANS9886W Enter a positive number
for Column Width.
Explanation: You have entered an invalid value for Column Width. It must be a positive number between 0 and 18.
System Action: ADSM continues with normal operation.
User Response: Enter a positive number between 0 and 18.

ANS9887W Enter a positive number
for Space Between Column.
Explanation: You have entered an invalid value for Space Between Column. It must be a positive number between 0 and 18.
System Action: ADSM continues with normal operation.
User Response: Enter a positive number between 0 and 18.

ANS9889W Space management has not been added to file-system file system.
Do you want to build the directory tree anyway?
Explanation: You selected a file system that is not managed by HSM.
System Action: ADSM builds the directory tree if you select the OK button. Otherwise, it will not.
User Response: You can add space management to the file system by selecting the Space Manager push button in the ADSM main window, and then selecting Add under the Selected menu option.

ANS9891W Please mark either or both check boxes before proceeding.
Explanation: You have not marked either of the check boxes.
System Action: ADSM does not proceed with reconcile processing.
User Response: Mark either or both check boxes.

ANS9895W Space management in file system file system is not active.
Explanation: You tried to select a file in a file system for which space management is inactive.
System Action: ADSM continues with normal operation.
User Response: Reactivate space management for the file system, and then proceed with selecting files.

ANS9899E Cannot recall resident or premigrated file.
Explanation: The file is a resident or premigrated file.
System Action: The file is not selected.
User Response: Select only migrated files for recall.

ANS9900E FSM kernel extension not installed.
Explanation: The file system selected is not fully activated. The system received an error trying to open /dev/fsm.
System Action: ADSM operation stops.
User Response: Check to see whether /dev/fsm entry exists, and check space management installation.

ANS9901E Cannot migrate ADSM system internal file.
Explanation: You tried to select files that are used internally by the HSM client. You cannot migrate ADSM internal files.
System Action: ADSM ignores your request.
User Response: None.

ANS9903E Space management is deactivated for this file system.
Explanation: You tried to migrate a file in a file system for which space management is inactive.
System Action: ADSM continues to migrate files only in active file systems.
User Response: Reactivate space management for the file system, and retry the migration operation.

ANS9904E Transaction failed, migration aborted.
Explanation: The specified file-name was not migrated because the file was accessed by another process during the attempt to migrate it.
System Action: ADSM migration is aborted.
User Response: If you want the file migrated, stop the process that is accessing the file, and then retry the migration.

ANS9908E System Error.
Explanation: ADSM detects an error in reading the state of the file system.
System Action: ADSM proceeds with normal operation.
User Response: Report the error to your system administrator.

ANS9909I Error in accessing migration candidates list file.
Explanation: ADSM detects an error in reading the migration candidates list file. This file resides in the .SpaceMan directory of the file system.
System Action: ADSM proceeds with normal operation.
User Response: Report the error to your system administrator.

ANS9914I Space management settings have
been modified successfully on file-system file system.
Explanation: Space management settings have been updated successfully.
System Action: ADSM updated space management settings for the file system.
User Response: Continue with normal operation.

ANS9915I Space management has been added successfully
to file-system file system.
Explanation: Space management has been added successfully.
System Action: ADSM added and activated space management for the file system.
User Response: Continue with normal operation.

ANS9916I Space management successfully activated file-system file system.
Explanation: Space management has been activated successfully.
System Action: ADSM activated space management for the file system.
User Response: Continue with normal operation.

ANS9918E Cannot open migration candidates list for file-system.
Explanation: ADSM cannot access the migration candidates list for the specified file system.
System Action: ADSM continues normal operation.
User Response: Select OK to return.

ANS9919I Space management successfully removed from file-system file system.
Explanation: Space management is removed successfully.
System Action: ADSM removed space management from a file system.
User Response: Select OK to return.

ANS9928I Space management has been
deactivated successfully on file-system file system.
Explanation: Space management is deactivated successfully.
System Action: ADSM deactivated space management for the file system.
User Response: Select OK to return.

ANS9929I Space management has been
reactivated successfully on file-system file system.
Explanation: Space management is reactivated successfully.
System Action: ADSM reactivated space management for the file system.
User Response: Select OK to return.

ANS9933I Migration candidates list only exists in an 'Active'
file system. If you want to make file-system file system
'Active', select 'Add Space Management'.
Explanation: You tried to display the migration candidates list for a "Native" file system (a file system to which space management has not been added).
System Action: Processing stopped.
User Response: Select OK to return. Select "Add Space Management" if you want to add space management to the file system.

ANS9934I Reconcile only works on an 'Active' file
system. If you want to make file-system file system
'Active', select 'Add Space Management'.
Explanation: You tried to start reconciliation on a "Native" file system (a file system to which space management has not been added). You must add space management to a file system before starting reconcile.
System Action: Processing stopped.
User Response: Select OK to return. Select "Add" if you want to add space management to the file system.

ANS9935I Start Threshold Migration only works on an 'Active'
file system. If you want to make file-system file system 'Active',
select 'Add Space Management'.
Explanation: You tried to start Threshold Migration on a "Native" file system (a file system to which space management has not been added). You must add space management to the file system first.
System Action: Processing stopped.
User Response: Select OK to return. Select "Add" if you want to add space management to the file system.

ANS9936I Start Threshold Migration only works on an 'Active'
file system. If you want to make file-system file system 'Active',
select 'Reactivate'.
Explanation: You tried to start Threshold Migration on an "Inactive" file system (a file system for which space management has been deactivated). You must reactivate space management for your file system first.
System Action: Processing stopped.
User Response: Select OK to return. Select 'Reactivate' to reactivate space management for the file system.

ANS9938I Space management has not been added to file-system file
system. You do not need to deactivate space management.
Explanation: You tried to deactivate space management on a file system to which space management has not been added.
System Action: Processing stopped.
User Response: Select OK to return.

ANS9939I file-system file system has already been deactivated.
Explanation: You tried to deactivate space management for a file system that is already deactivated.
System Action: Processing stopped.
User Response: Select OK to return.

ANS9940I file-system file system has already been activated.
Explanation: You tried to activate space management for a file system that is already activated.
System Action: Processing stopped.
User Response: Select OK to return.

ANS9941I Space management has not been added to file-system.
If you want to add space management, select
'Add space management' option. The file system will
automatically be activated when you add space management.
Explanation: You tried to activate space management on a file system to which space management has not been added. You must first add space management. The file system will automatically be activated when the add process is complete.
System Action: Processing stopped.
User Response: Select OK to return. Select "Add" if you want to add space management to the file system.

ANS9942S Space management has not been added to file-system file system. Do you want to add space management now?
Explanation: You tried to update space management settings for a file system to which space management has not been added.
System Action: Processing stopped.
User Response: Select OK to add space management to the file system. Select Cancel to return.

ANS9943I Space management has already been added to file-system file system.
Explanation: You tried to add space management to a file system to which space management has already been added.
System Action: Processing stopped.
User Response: Select OK to return.

ANS9944I Space management has been deactivated on file-system file
system. You must reactivate space management before you can remove it.
Explanation: You tried to remove space management from a file system for which space management has been deactivated. You must reactivate space management for the file system before you can remove it.
System Action: Processing stopped.
User Response: Select OK to return. Select "Reactivate", and then select "Remove" to remove space management.

ANS9945I Space management has not been added to file-system file
system. You do not need to remove space management.
Explanation: You tried to remove space management from a file system to which space management has not been added.
System Action: Processing stopped.
User Response: Select OK to return.

ANS9947E File: file-spec is in a file system to which space
management has not been added.
Explanation: You tried to migrate a file that resides in a file system to which space management has not been added.
System Action: ADSM will not highlight/process the file.
User Response: Switch over to the Space Manager window, and add space management to the file system.

ANS9948E File: file-spec size is less than the minimum size required for migration.
Explanation: You tried to migrate a file that is smaller than the minimum size required for migration. To be eligible for migration, a file must be larger than both the stub file size specified for the file system plus one byte and the block size defined for the file system.
System Action: ADSM will not highlight the file.
User Response: None.

ANS9949E File: file-spec is not a regular file and therefore not qualified for migration.
Explanation: You tried to migrate a file that is not a regular file. It might be a FIFO file, a special file, a directory or a symbolic link.
System Action: ADSM will not highlight the file.
User Response: None.

ANS9950E File: file-spec is not qualified for migration because the Space Management Technique attribute is set to None.
Explanation: The Space Management Technique attribute in the management class is set to None, which does not allow a file to be migrated.
System Action: ADSM will not highlight the file.
User Response: Assign a management class to the file that specifies "Automatic" or "Selective" for the Space Management Technique attribute.

ANS9951E File: file-name file has already been migrated.
Explanation: You tried to migrate a file that is already migrated.
System Action: ADSM will not highlight the file.
User Response: None.

ANS9953E The management class assigned to this file does not allow migration.
Explanation: The management class assigned to this file does not allow migration.
System Action: ADSM does not migrate the file.
User Response: None.

ANS9954E This file has already been migrated.
Explanation: The file has been previously migrated.
System Action: File is skipped.
User Response: None.

ANS9956E File is not readable.
Explanation: You attempted to migrate a non-readable file.
System Action: ADSM skips this file and continues with the next file.
User Response: Continue with normal operation.

ANS9957E Unknown file type cannot be migrated.
Explanation: You attempted to migrate an unknown type of file.
System Action: ADSM skips this file and continues with the next file.
User Response: Continue with normal operation.

ANS9960W No files selected for migrate or recall.
Explanation: You requested a migrate or recall operation without selecting files from the presented directory tree.
System Action: ADSM cannot do the migration or recall without selected files.
User Response: Select the files that you want to migrate or recall, and retry the operation.

ANS9961E Server out of migrate data storage space.
Explanation: The server ran out of space in its migrate data storage.
System Action: ADSM cannot complete the migrate operation. Any files displayed in the Successful list of the Migrate Status window were successfully migrated.
User Response: Check with your system administrator.

ANS9962I Migration stopped by user.
Explanation: You requested that ADSM stop the migrate operation.
System Action: Migration stopped.
User Response: Continue with normal operations.

ANS9963I Selective Recall completed. Check failure
list for possible errors.
Explanation: The recall was completed.
System Action: ADSM recalled the files.
User Response: Continue with normal operations.

ANS9964I Selective Migration completed. Check failure
list for possible errors.
Explanation: The migration was completed.
System Action: ADSM migrated the files.
User Response: Continue with normal operations.

ANS9965S Please select a file system first.
Explanation: You did not select any file system for the Migrate window.
System Action: ADSM ignores this request and continues.
User Response: Select a file system, a directory, and all files you want to migrate, and then select the Migrate button to start the process.

ANS9966S No file system has been selected.
Explanation: You did not select a file system.
System Action: ADSM ignores the request and continues.
User Response: Select at least one file system and retry the operation

ANS9988S As part of the remove process, all migrated
files in file-system will be recalled from ADSM server.
Do you want to continue with the remove process now?
Explanation: When you remove space management from a file system, ADSM recalls all migrated files.
System Action: ADSM waits for your response before proceeding with the remove process.
User Response: Select Yes to remove space management from the selected file system, or select Cancel to skip the remove.

ANS9997W The selective migration, selective recall, or policy information
window is displayed. Stop any operations, close the window,
and then retry the operation.
Explanation: When a node is contacting more than one server for space management services, the selective migration, selective recall, and policy information windows may not be displayed at the same time.
System Action: ADSM ignores the request.
User Response: Close the selective migration, selective recall, or policy information window, and then retry the operation.

ANS9998E The migration server changed after the selective migration
or selective recall window was displayed. Close the window,
and then retry the operation.
Explanation: A migrate or recall operation will not be allowed to proceed if the user changed the migration server after the selective migration or selective recall window was displayed.
System Action: ADSM No files will be migrated or recalled.
User Response: Close the selective migration or selective recall window, and then retry the operation.