ANR0010W Unable to open message catalog for language language. The default language message catalog will be used.

Explanation

The message catalog for the specified language could not be found.

System action

The server continues to initialize with the default English message catalog.

User response

To resolve the issue, complete the following steps:
  • If you specified a LANGUAGE option in the server options file, verify that you specified a supported language.
  • If you specified environment variables for the system locale, ensure that you specified a supported locale and that the locale is installed on your system.
  • Ensure that the IBM Spectrum Protect language package for the specified language is installed on your system.
  • Restart the server.

ANR0011W Unable to set locale to first locale. Using locale second locale for message formatting.

Explanation

The first locale could not be set.

System action

The server continues to initialize using the second locale.

User response

To resolve the issue, complete the following steps:
  • If you specified a LANGUAGE option in the server options file, ensure that you specified a supported locale and that the locale is installed on your system.
  • If you specified environment variables for the system locale, ensure that you specified a supported locale and that the locale is installed on your system.
  • Restart the server.

ANR0098W This system does not meet the minimum memory requirements.

Explanation

The minimum memory required is 12 GB. 16 GB is required if you are using data deduplication. At least 32 GB is needed for heavily used servers. Using 32 GB or more of memory enhances performance of the IBM Spectrum Protect server database inventory.

If you plan to run multiple instances, each instance requires the memory listed for one server. Multiply the memory for one server by the number of instances planned for the system.

Node replication processing requires additional memory. Use a minimum of 32 GB of memory for node replication without data deduplication. Node replication with data deduplication requires a minimum of 64 GB of memory. You will require an active log at least 64 GB in size to run replication. If replication and deduplication are both being used, an active log at least 128 GB in size is required.

System action

Server operation continues.

User response

Increase the amount of memory on the system.

ANR0099W This operating system is not supported.

Explanation

The system has detected one of the following items:
  • a release of the operating system that is not supported
  • the required maintenance for the operating system is not installed

See the software requirements section in the information center for more details.

System action

Server operation continues.

User response

See the software requirements section in the information center and upgrade to a supported operating system.

ANR0100E Source file(line number): Error error code creating table "table name".

Explanation

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

System action

The activity that generated this error fails.

User response

Contact your service representative.

ANR0101E Source file(line number): Error error code opening table "table name".

Explanation

An internal error occurred when a server database table was being accessed. This error message always accompanies another error message which provides more details about the error.

System action

The activity that generated this error fails.

User response

If the server or storage agent stops in response to a HALT command, you can ignore this error message.

ANR0102E Source file(line number): Error error code inserting row in table "table name".

Explanation

An internal error occurred when data was added to a server database table. This error message always accompanies another error message which provides more details about the error.

System action

The activity that generated this error fails.

User response

An error occurred when a row was inserted into a server database table. Typically, this error causes an error code value of 1202 to be displayed. An error code value of 1202 indicates that the record being inserted already exists in the database. This type of error might be caused by a timing issue with the server or a synchronization issue involving server processes, client sessions, or other server actions. Review the activity log file to determine what operations were in progress and were affected by this error. Try the operation again and change the timing so that it does not run with the same processes or actions as when the error occurred.

ANR0103E Source file(line number): Error error code updating row in table "table name".

Explanation

An internal error occurred when data was updated in a server database table. This error message always accompanies another error message which provides more details about the error.

System action

The activity that generated this error fails.

User response

An error occurred when a row was inserted into a server database table. Typically, this error causes an error code value of 1114 to be displayed. An error code value of 1114 indicates that the record being updated does not exist in the database. This type of error might be caused by a timing issue with the server or a synchronization issue involving server processes, client sessions, or other server actions. Review the activity log file to determine what operations were in progress and were affected by this error. Try the operation again and change the timing so that it does not run with the same processes or actions as when the error occurred.

ANR0104E Source file(line number): Error error code deleting row from table "table name".

Explanation

An internal error occurred when data was being removed from a server database table. This error message always accompanies another error message which provides more details about the error.

System action

The activity that generated this error fails.

User response

An error occurred when a row was deleted from a server database table. Typically, this error causes an error code value of 1114 to be displayed. An error code value of 1114 indicates that the record being deleted does not exist in the database. This type of error might be caused by a timing issue with the server or a synchronization issue involving server processes, client sessions, or other server actions. Review the activity log file to determine what operations were in progress and were affected by this error. Try the operation again and change the timing so that it does not run with the same processes or actions as when the error occurred.

ANR0105E Source file(line number): Error setting search bounds for table "table name".

Explanation

An internal error occurred when data was being accessed from a server database table. This error message always accompanies another error message which provides more details about the error.

System action

The activity that generated this error fails.

User response

Review the activity log file to determine what operations were in progress and were affected by this error. Try the operation again and change the timing so that it does not run with the same processes or actions as when the error occurred.

ANR0106E Source file(line number): Unexpected error error code fetching row in table "table name".

Explanation

An internal error occurred when data was being accessed from a server database table. This error message always accompanies another error message which provides more details about the error.

System action

The activity that generated this error fails.

User response

Review the activity log to determine what operations were in progress and were affected by this error. Try the operation again and change the timing so that it does not run with the same processes or actions as when the error occurred.

ANR0107W Source file(line number): Transaction transaction ID was not committed due to an internal error.

Explanation

An internal error was detected during transaction commit. This message is typically preceded by another error message which provides more details about the error.

System action

The activity that generated this error fails.

User response

Review the activity log to determine what operations were in progress and were affected by this error. Try the operation again and change the timing so that it does not run with the same processes or actions as when the error occurred.

ANR0108E Source file(line number): could not start a new transaction.

Explanation

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

System action

The activity that generated this error fails.

User response

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

ANR0109E Attempt number att_num Unable to load cryptography module from 'icc location'.

Explanation

An error occurred while attempting to load the cryptography module.

System action

The application will not start.

User response

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

ANR0110E An unexpected system date has been detected; the server is disabled. Verify the system date and use the ACCEPT DATE command to establish the current date as valid.

Explanation

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

System action

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

User response

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

ANR0111E Command: The BEGINNODEID and ENDNODEID are both required to be specified.

Explanation

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

System action

The server fails the command.

User response

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

ANR0112E Command: The specified BEGINNODEID node id is greater than the ENDNODEID node id.

Explanation

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

System action

The server fails the command.

User response

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

ANR0113E Command: The storage pool list specified with the parameter parameter name includes storage pool storage pool name more than once.

Explanation

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

System action

The command fails.

User response

Reissue the command specifying unique storage pool names.

ANR0114E Command: The NUMBER parameter is required on this command. The current default value is 0.

Explanation

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

System action

The command is not executed.

User response

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

ANR0115W The server script script name attempted to start more parallel commands than are allowed for a single script. A single script is limited to parallel command limit parallel commands.

Explanation

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

System action

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

User response

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

ANR0116W The server script script name attempted to start more parallel commands than are allowed for the server. The server is limited to parallel command limit parallel commands.

Explanation

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

System action

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

User response

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

ANR0117E The server contains stored data. Archive data retention protection cannot be changed.

Explanation

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

System action

Processing continues.

User response

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

ANR0118W The client option client option is not valid and will not be sent to the client. Use the INCLEXCL option instead.

Explanation

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

System action

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

User response

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

ANR0119W The client option client option is not valid and will not be sent to the client. Delete it from client option sets.

Explanation

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

System action

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

User response

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

ANR0120I Archive data retention protection is set to state of archive data retention protection.

Explanation

The archive data retention protection state has been set.

System action

Processing continues.

User response

None.

ANR0121E command is not allowed when archive data retention is enabled.

Explanation

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

System action

Processing continues.

User response

None.

ANR0122E command: A node cannot be assigned to a new domain when archive data retention is enabled.

Explanation

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

System action

Processing continues.

User response

None.

ANR0123E command: A device type of SERVER is not allowed when archive data retention is enabled.

Explanation

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

System action

Processing continues.

User response

None.

ANR0124W Object object name (object id hi ) for node node name (node id), filespace filespace name (filespace id) is retention protected and can not be deleted.

Explanation

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

System action

Server operation continues.

User response

None.

ANR0125W DELETE FILESPACE filespace name for node node name contains retention protected data and cannot be deleted.

Explanation

The specified file space cannot be deleted because it contains one or more objects that must be retained for one of the following reasons:
  • Archive retention protection is enabled and the object's retention period has not elapsed.
  • The object is part of a deletion hold.

System action

The file space is not deleted.

User response

None.

ANR0126W DELETE VOLUME: Volume volume name contains retention protected data and can not be deleted.

Explanation

The specified volume cannot be deleted because it contains one or more objects that must be retained because of one of the following:
  • Archive retention protection is enabled and the object's retention period has not elapsed.
  • The object is part of a deletion hold.

System action

Processing continues.

User response

None.

ANR0127E command to another server is not allowed when data retention protection is enabled on the target server.

Explanation

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

System action

Processing continues.

User response

None.

ANR0128E Command: The list of storage pools specified with the parameter parameter name includes storage pool storage pool name, which is already in use by another storage pool.

Explanation

The specified storage pool name is already being used to protect another storage pool. You cannot protect multiple storage pools using the same container-copy storage pool.

System action

The command fails.

User response

Reissue the command specifying unique storage pool names.

ANR0129I Database upgrade completed successfully.

Explanation

The requested database upgrade operation completed successfully.

System action

Processing continues.

User response

None.

ANR0130E Diagnostic(ID): Server LOG space exhausted.

Explanation

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

System action

The activity that generated this error fails.

User response

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

ANR0131E Diagnostic(ID): Server DB space exhausted.

Explanation

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

System action

The activity that generated this error fails.

User response

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

ANR0132E Diagnostic(ID): Memory allocation failed: object object name, size size.

Explanation

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

System action

The activity that generated this error fails.

User response

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

ANR0133E Error loading module modname: error string

Explanation

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

System action

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

User response

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

ANR0134I Tiering process process ID for storage rule stgrule_name started from storage pool source_stgpool to tgt_stgpool_type storage pool target_stgpool.

Explanation

The server started the tiering process to move client data that meets the specified criteria for age and state. The data can include backup, archive, and space-managed files. The tiering process was started as process number process ID.

System action

Server operation continues. The tiering process can be canceled, if necessary.

User response

No action is required. However, you can query the process by using the QUERY PROCESS command. You can cancel the process by using the CANCEL PROCESS command.

ANR0135I Tiering process process ID from storage pool source_stgpool started searching for eligible file spaces.

Explanation

The tiering process began a search for file spaces with eligible data that must be moved to the target storage pool.

System action

Server operation continues.

User response

No action is required.

ANR0136I Table updating statistics performed successfully for processed tables of total tables.

Explanation

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

System action

Server operation continues.

User response

No user action required.

ANR0137E Source file(line number): Error error code allocating num rows database rows.

Explanation

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

System action

The activity that generated this error fails.

User response

Contact your service representative.

ANR0138E Value primary logs for number of primary logs is invalid.

Explanation

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

System action

Server installation stops.

User response

Reissue the command with a valid number of primary logs.

ANR0139I Tiering process process ID identified number of files files for node node name, file space filespace name to tier from storage pool source_stgpool to storage pool target_stgpool.

Explanation

The actual number of files to be tiered can vary, depending on the tiering action type and the method of data storage.

System action

Server operation continues as the files are moved.

User response

No action is required. However, to learn more about the tiering process, go to the product documentation and search for "tiering."

ANR0140I Command: success. Node node_id_1 is granted proxy authority to node node_id_2.

Explanation

The command was successful.

System action

The server performs the command.

User response

None.

ANR0141E Command: failed. Node node_id_1 was not granted proxynode authority to node node_id_2.

Explanation

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

System action

The server fails the command.

User response

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

ANR0142I Command: success. Proxynode authority for node node_id_1 has been revoked from node node_id_2.

Explanation

The command was successful.

System action

The server performs the command.

User response

None.

ANR0143E Command: failed. Proxynode authority for node node_id_1 has not been revoked to node node_id_2.

Explanation

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

System action

The server fails the command.

User response

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

ANR0144E Command: failed. Node node_id_1 was not granted proxynode authority to node node_id_2 because node node_id_missing has not been defined to the server.

Explanation

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

System action

The server fails the command.

User response

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

ANR0145E Command: failed. Node node_id_1 already has been granted proxynode authority to node node_id_2.

Explanation

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

System action

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

User response

None.

ANR0146E Command: failed. Node node_id_1 was not granted proxynode authority to itself.

Explanation

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

System action

The server fails the command.

User response

None.

ANR0147E Command: failed. Proxy node authority for node node_id_1 to node node_id_2 was not revoked because node node_id_missing has not been defined to the server.

Explanation

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

System action

The server fails the command.

User response

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

ANR0148I Command: No proxy relationships were found.

Explanation

No proxy relationships were found.

System action

None.

User response

None.

ANR0149E Filespace filespace for node node_name was deleted concurrently with the command.

Explanation

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

System action

The server will fail the command.

User response

Retry the command.

ANR0150E Failed to open object object_name. There was an error decrypting the password_type password.

Explanation

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

System action

The server will fail the related command or action.

User response

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

ANR0151W Database manager fails to start. For more information about the failure, issue the db2start command.

Explanation

The server was unable to start the database manager. The following are possible causes:
  • The database manager license key is invalid or missing.
  • The server instance password was changed.

System action

Server initialization stops.

User response

For more information about the failure, try to start the database manager by issuing the db2start command, as in this example: C:\Users\admin>db2start. You might receive messages similar to the following ones: SQL1397N The Db2 service failed to logon. SQL1032N No start database manager command was issued. SQLSTATE=57019. To determine the cause of the failure, evaluate recent changes to the server and review the system error logs. Information can be found in the Db2 diagnostic log file. If you are starting a Db2 server on a Windows platform, you can set the logon account for a Db2 service by using the Services dialog box from the Control Panel.

ANR0152I Database manager successfully started.

Explanation

The server was successfully able to start the database manager.

System action

The server operations continue.

User response

None.

ANR0153I Database manager already running.

Explanation

The server database manager is already running.

System action

The server continues startup.

User response

None.

ANR0154E Command: The active data pool list that you specified with the ACTIVEDESTINATION parameter includes active data pool active data pool name that is a duplicate. All names must be unique.

Explanation

You may enter up to 10 unique active data pool names specified with the ACTIVEDESTINATION parameter.

System action

The command fails.

User response

Reissue the command specifying unique active-data pool names.

ANR0155E Command: The number of active data pool names specified with the ACTIVEDESTINATION parameter cannot exceed 10.

Explanation

The maximum number of active data pool names that you can specify with the ACTIVEDESTINATION parameter is 10. You may enter up to 10 unique names, separated by commas.

System action

The command fails.

User response

Reissue the command specifying up to 10 unique active-data pool names separated only by commas.

ANR0156E Command: The pool active data pool name with pool ID pool ID is not an active pool.

Explanation

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

System action

The command fails.

User response

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

ANR0157W Database operation table operation for table table name failed with result code op code and tracking ID: id.

Explanation

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

System action

The activity that generated this error fails.

User response

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

ANR0158W Database operation table operation for table table name failed with operation code op code and tracking id tracking number. The data for column column number is: column data.

Explanation

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

System action

The activity that generated this error fails.

User response

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

ANR0159E Diagnostic(ID): Database deadlock detected on Db2 Statement Handle.

Explanation

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

System action

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

User response

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

ANR0160I Displaying segment segment number of total segments for client object object identifier with text: object name.

Explanation

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

System action

The fully qualified name for this object is displayed.

User response

None.

ANR0161I Displaying segment segment number for message insert insert identifier with text segment text.

Explanation

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

System action

The entire message insert segment is displayed.

User response

None.

ANR0162W Supplemental database diagnostic information: dbReturnCode:dbState:dbCode (dbErrorMessage).

Explanation

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

System action

The activity that generated this error fails.

User response

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

ANR0163E Diagnostic(ID): Database insufficient memory detected on Db2 Statement Handle.

Explanation

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

System action

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

User response

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

ANR0165I Inventory file expiration started processing for node nodename, filespace filespace name, copygroup copygroup and object type type.

Explanation

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

System action

Inventory file expiration continues.

User response

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

ANR0166I Inventory file expiration finished processing for node nodename, file space filespace name, copy group copygroup, and object type type with processing statistics: examined examined, retained retained, deleted deleted, retrying retrying, failed failed and skipped skipped files.

Explanation

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

System action

Inventory file expiration continues.

User response

No action is required. This message is informational and displayed only if the expiration processing is executed with the QUIET=NO parameter setting.

ANR0167I Inventory file expiration process process ID processed for minutes minutes.

Explanation

Server expiration processing ran for the indicated number of minutes.

System action

None.

User response

None.

ANR0168I Analyst authority for administrator admin name will be ignored. Analyst authority is not supported on this server.

Explanation

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

System action

The operation continues.

User response

None.

ANR0169E An unexpected error has occurred and the IBM Spectrum Protect server is stopping.

Explanation

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

System action

The server halts.

User response

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

ANR0170E Diagnostic(ID): Error detected on Db2 Statement Handle, database restart required.

Explanation

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

System action

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

User response

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

ANR0171I Diagnostic(ID): Error detected on Db2 Statement Handle, database in evaluation mode.

Explanation

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

System action

Server processing continues.

User response

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

ANR0172I Diagnostic(ID): Error encountered performing action action.

Explanation

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

System action

Server processing terminates, the requested action fails.

User response

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

ANR0173I The database failed action action because of insufficient system memory available.

Explanation

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

System action

Server processing terminates, the requested action fails.

User response

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

ANR0174E Diagnostic(ID): Maximum Db2 connections reached on DB2 Handle.

Explanation

There are no more available connections to the server database.

System action

The activity that generated this error fails.

User response

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

ANR0175E Diagnostic(ID): Space exhausted for one or more of the following: DB, LOG, or instance directory.

Explanation

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

System action

The server terminates.

User response

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

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

ANR0185E The data in primary storage pool name can not be copied to active data pool name. The active-data pool is not defined to a domain.

System action

The command fails.

User response

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

ANR0186E There is insufficient authority to start the database manager.

Explanation

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

System action

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

User response

Ensure that the user ID under which the server is running is authorized to start the database manager. Take the following actions:
  • Log in to the user ID for your IBM Spectrum Protect instance and start the server.
    • To run the server using the root user ID on a UNIX system, add the root user ID to the primary group of the IBM Spectrum Protect instance user ID.
    • Or, to run the server using the instance user ID on a UNIX system, when using the automatic start, specify the -u option when you start the server.

ANR0187E Database db name was not found.

Explanation

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

System action

The server process ends.

User response

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

ANR0188E Fail to start the database manager. Database manager license not found

Explanation

Could not find database manager license.

System action

The server process ends.

User response

Contact your service representative.

ANR0189E Fail to start the database manager. Database manager license has expired

Explanation

Database manager license has expired.

System action

The server process ends.

User response

Contact your service representative.

ANR0190I Inventory file expiration started processing node node name for backup sets.

Explanation

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

System action

Inventory file expiration continues.

User response

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

ANR0191I Inventory file expiration finished processing node node name for backup sets with processing statistics: examined examined, deleted deleted, retrying retrying, and failed failed.

Explanation

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

System action

Inventory file expiration continues.

User response

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

ANR0193E The REPAIR EXPIRATION TYPE=type command cannot be issued from the server console.

Explanation

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

System action

The server ignores the command and continues processing.

User response

Issue the command from an administrative client.

ANR0195W Attempting to remove extraneous database entries for volume volume name.

Explanation

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

System action

IBM Spectrum Protect will attempt to remove the extraneous database entries for this volume.

User response

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

ANR0196I Removal of extraneous database entries for volume volume name was successful.

Explanation

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

System action

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

User response

The server successfully repaired the specified volume.

ANR0197E Removal of extraneous database entries for volume volume name failed due to contention with other server processes or activities.

Explanation

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

System action

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

User response

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

ANR0198E Removal of extraneous database entries for volume volume name failed.

Explanation

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

System action

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

User response

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

ANR0199W Not possible to repair volume volume name due to other database references to this volume.

Explanation

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

System action

System operation continues.

User response

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

ANR0200E PROTECT STGPOOL process process ID failed due to insufficient space in destination storage pool.

Explanation

The destination stgpool had insufficient space.

System action

The indicated process ends.

User response

Make more space available in the storage pool and restart the operation.

ANR0201I The access mode for storage pool directory Directory Name in storage pool Pool Name was changed to Access Mode.

Explanation

The access mode is changed for the specified storage pool directory.

System action

Client nodes and server processes cannot access the storage pool.

User response

To change the access mode, issue the UPDATE STGPOOLDIR command.

ANR0202I The parameter name has been set but the changes will not be effective until the next start

Explanation

The Database configuration has been updated but has not taken effect. This setting will take effect on next server start.

System action

This server parameter does not take effect until next start. The server continues processing.

User response

None.

ANR0203E MOVE CONTAINER process process ID terminated for container name - insufficient space in directory directory name.

Explanation

During MOVE CONTAINER processing, the server could not allocate sufficient space in the storage pool directory for the container.

System action

Server processing continues.

User response

Make more space available in the storage pool, and re-issue the MOVE CONTAINER command.

ANR0204I The container state for container name is updated from previous state to current state.

Explanation

The server updates the container state.

System action

Server processing continues.

User response

Review the other messages issued to determine if further action is required.

ANR0205W Command name skipped data extent ID Chunk ID because it is marked damaged.

Explanation

During command processing, the server skipped a chunk that was marked damaged.

System action

Server processing continues.

User response

None.

ANR0206E Command name process process ID failed due to insufficient space in destination storage pool.

Explanation

The indicated process failed because the destination storage pool has insufficient space.

System action

The indicated process ends.

User response

Make more space available in the storage pool and reissue the command.

ANR0207W Command name skipped object ID Object ID because one or more extents are marked damaged.

Explanation

During command processing, the server skipped an object because a data extent (chunk) was marked damaged.

System action

Server processing continues.

User response

None.

ANR0208I Tiering process process ID identified a total of number of files files and number of bytes bytes to move from storage pool source_stgpool to storage pool target_stgpool.

Explanation

The tiering process finished searching for older files that must be moved to the target storage pool.

System action

Server operation continues as the files are moved.

User response

No action is required.

ANR0209W Tiering process process ID stopped - the target storage pool has insufficient space.

Explanation

The server cannot tier the data because either the target storage pool has insufficient space to store the data or the access for the storage pool is unavailable or read-only.

System action

The process of tiering the data from the local storage pool to a target storage pool is stopped.

User response

Make more space available in the target storage pool, or specify a storage pool with more space, and reissue the START STGRULE command.

ANR0210W DELETE FILESPACE filespace name for node node name contains objects belonging to a retention set and cannot be deleted.

Explanation

The specified file space cannot be deleted because it contains one or more objects that belong to a retention set.

System action

The file space is not deleted.

User response

None.

ANR0211W The shredding process was unable to shred a deleted file.

Explanation

The shredding process encountered an error that prevents a file from being shredded. See previous error messages for more details.

System action

The file is not shredded. The next time the shredding process runs, it will attempt to shred the file again.

User response

If there are files that can not be shredded due to integrity or corruption errors or unrecoverable I/O errors, run the following commands:
  1. Set for manual shredding, if not already done: SETOPT SHREDDING MANUAL
  2. Run manual shredding with IOERROR parameter: SHRED DATA IOERROR=SHREDSUCCESS
  3. Reset for automatic shredding, if desired: SETOPT SHREDDING AUTOMATIC
If an entire disk volume has failed and all files on it are no longer accessible, run the following commands:
  1. Set the volume access to destroyed: UPDATE VOLUME volname ACCESS=DESTROYED
  2. Delete the volume and the data: DELETE VOLUME volname DISCARDDATA=YES
  3. Set for manual shredding, if not already done: SETOPT SHREDDING MANUAL
  4. Run manual shredding with IOERROR parameter: SHRED DATA IOERROR=SHREDSUCCESS
  5. Reset for automatic shredding, if desired: SETOPT SHREDDING AUTOMATIC

ANR0212E Unable to read disk definition file file specification.

Explanation

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

System action

Server initialization fails.

User response

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

ANR0213E Command: No jobs found.

Explanation

A QUERY JOB command specified, and no matching jobs were found.

System action

The server continues.

User response

None.

ANR0214I Copying process process ID for storage rule stgrule name started from storage pool source stgpool to target stgpool type storage pool target stgpool.

Explanation

The server started processing to copy client backup, archive, and space-managed file copies. The copying process was started as process number process ID.

System action

Server operation continues. The copying process can be cancelled, if necessary.

User response

No action is required. However, you can query the process by using the QUERY PROCESS command. You can cancel the process by using the CANCEL PROCESS command.

ANR0215I Copying process process ID from storage pool source stgpool started searching for eligible file spaces.

Explanation

The copying process began a search for file spaces with eligible data that must be copied to the target storage pool.

System action

Server operation continues.

User response

No action is required.

ANR0216I Copying process process ID identified number of files files for node node name, file space filespace name to copy from storage pool source stgpool to storage pool target stgpool.

Explanation

The actual number of files to be copied can vary, depending on the copying action type and the method of data storage.

System action

Server operation continues as the files are copied.

User response

No action is required. However, to learn more about the copying process, go to the product documentation and search for "copying."

ANR0217I Copying process process ID identified a total of number of files files and number of bytes bytes to copy from storage pool source stgpool to storage pool target stgpool.

Explanation

The copying process finished searching for older files that must be copied to the target storage pool.

System action

Server operation continues as the files are copied.

User response

No action is required.

ANR0218W Copying process process ID stopped - the target storage pool has insufficient space.

Explanation

The server cannot copy the data because either the target storage pool has insufficient space to store the data or the access for the storage pool is unavailable or read-only.

System action

The process of copying the data from the local storage pool to a target storage pool is stopped.

User response

Make more space available in the target storage pool, or specify a storage pool with more space, and reissue the START STGRULE command.

ANR0219W Copying process process ID terminated for storage pool storage pool name - duration exceeded.

Explanation

During a storage pool copying action for the indicated storage pool, a process performing the copying has been terminated because the process duration has exceeded.

System action

The copying process is terminated.

User response

None.

ANR0220I Copying process process ID for storage pool storage pool name has completed.

Explanation

The process of copying data from primary storage pool to a copy storage pool has completed.

System action

None.

User response

None.

ANR0221I Tiering process process ID for storage rule stgrule_name, subrule subrule_name started from storage pool source_stgpool to tgt_stgpool_type storage pool target_stgpool.

Explanation

The server started the tiering process to move client data that meets the specified criteria for age and state. The data can include backup, archive, and space-managed files. The tiering process was started as process number process ID.

System action

Server operation continues. The tiering process can be canceled, if necessary.

User response

No action is required. However, you can query the process by using the QUERY PROCESS command. You can cancel the process by using the CANCEL PROCESS command.

ANR0222E Error action disk definition file file specification.

Explanation

An error occurred creating or changing the disk definition file.

System action

None.

User response

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

ANR0225S Invalid use of the -S command-line option.

Explanation

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

System action

The server does not start.

User response

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

ANR0226S The database ID file could not be found for server startup.

Explanation

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

System action

The server does not start.

User response

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

ANR0227S Incorrect database opened. Server cannot start.

Explanation

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

System action

The server does not start.

User response

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

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

ANR0228S Error errno opening the database ID file for server startup.

Explanation

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

System action

The server does not start.

User response

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

ANR0229W Server is unable to add entries to the Activity Log. Console messages will not be logged until database access is available.

Explanation

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

System action

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

User response

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

ANR0230I The copying process (process number process ID) for storage rule stgrule name is completed. Data was copied from storage pool source stgpool to target stgpool type storage pool target stgpool. Copied Files: copied files, Copied Bytes: copied bytes, Skipped Files: skipped files, Skipped Bytes: skipped bytes, Total Bytes Transferred: transferred bytes, Elapsed time: elapsed time.

ANR0231I The copying process (process number process ID) for storage rule stgrule name, subrule subrule name, is completed. Data was copied from storage pool source stgpool to target stgpool type storage pool target stgpool. Copied Files: copied files, Copied Bytes: copied bytes, Skipped Files: skipped files, Skipped Bytes: skipped bytes, Total Bytes Transferred: transferred bytes, Elapsed time: elapsed time.

ANR0232I The copying retention set process (process number process ID) for storage rule stgrule name is completed. Data was copied from retention set retention set Id to target stgpool type storage pool target stgpool. Copied Files: copied files, Copied Bytes: copied bytes, Skipped Files: skipped files, Skipped Bytes: skipped bytes, Total Bytes Transferred: transferred bytes, Elapsed time: elapsed time.

ANR0236E Fail to start the database manager due to an I/0 error. Check for filesystem full conditions, file permissions, and operating system errors.

Explanation

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

System action

The server process ends.

User response

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

ANR0237E Fail to start the database manager. An unexpected system error occurred.

Explanation

An unexpected system error occurred.

Some common reasons for this error are:
  • The system name where you ran the server has been changed
  • The system date and time is set incorrectly

System action

The server process ends.

User response

Contact your service representative.

ANR0238E A database recovery task is prohibiting activation of db name with sqlcode dbCode.

Explanation

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

System action

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

User response

See message explanation for more information.

ANR0239E The Db2 instance name instance name may not be valid or is not configured properly. The return code was sqlcode

Explanation

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

System action

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

User response

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

ANR0264E A database file IO error is prohibiting activation of db name with sqlcode dbCode.

Explanation

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

System action

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

User response

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

ANR0273W Not initializing library library name because the library is set offline .

Explanation

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

System action

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

User response

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

ANR0274E Attempt to access library library name failed, because the library is set offline.

Explanation

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

System action

This mount fails.

User response

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

ANR0275I Detected schema change for table table, attempting to reconcile.

Explanation

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

System action

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

User response

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

ANR0276I Schema reconciliation for table table succeeded.

Explanation

The schema differences for this table were successfully reconciled.

System action

Server operation continues.

User response

None

ANR0277E Schema reconciliation for table table failed.

Explanation

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

System action

Server operation terminates.

User response

Contact your IBM service representative.

ANR0278S The database manager cannot create the database because of a virtual memory shortage.

System action

Server operation stops.

User response

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

ANR0279S Database manager failed to start due to incorrect service logon credentials.

Explanation

The server was unable to start the database manager because the database manager service credentials (userid and/or password) are incorrect.

System action

Server initialization stops.

User response

Correct the logon properties for the database manager service by using the Services dialog box from the Control Panel.

ANR0280W Servermon failed to start during initialization.

Explanation

The server was unable to start the servermon monitoring process. This will prevent the automated collection of system health information.

System action

Will disable server monitoring.

User response

User should correct reason for servermon initialization failure and restart server to enable servermon.

ANR0281I Servermon successfully started during initialization, using process process id.

Explanation

The server was able to start the servermon monitoring process, or find that an existing servermon process was running for this instance. This will allow for the automated collection of system health information.

System action

Will collect server monitoring information.

User response

None.

ANR0282W Error return code accessing or creating directory directory name: this will prevent the execution of servermon

Explanation

The directory path for servermon can not be accessed or created. This will prevent servermon from collecting monitoring information.

System action

Will not start servermon.

User response

Ensure that you have the proper authorization to access or create the directory for use by servermon.

ANR0283W Error return code copying source file to target file. This will prevent the execution of servermon.

Explanation

The file copy for servermon cannot be fulfilled. This file is required for proper execution of servermon.

System action

Will not start servermon.

User response

Ensure that you have the proper authorization to copy the specified file for use by servermon.

ANR0293I Reorganization for table table name started.

Explanation

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

System action

The server will continue to operate.

User response

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

ANR0294I Reorganization for table table name ended.

Explanation

The server online reorganization for the table referenced has ended.

System action

The server will continue to operate.

User response

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

ANR0297I A full database backup might be required. The last log number used is last log used and the first log number used is first log used. The log file size is log file size megabytes. The maximum log file size is maximum log file size megabytes.

Explanation

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

System action

None.

User response

None.

ANR0298S Authority is insufficient to access the database.

Explanation

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

System action

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

User response

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

ANR0299I A full database backup will be started. The archive log space used is archive log% and the archive log space used threshold is arch log threshold%.

Explanation

When the archive log space used exceeds the threshold, a full database backup will be started.

System action

None.

User response

None.

ANR0300W Instance directory instance directory has free space GB available space of capacity GB total capacity.

Explanation

The server instance directory exceeds the threshold of its assigned capacity specified by the INSTDIRTHRESHOLD server option.

System action

Server operation continues, but a continued decrease in the amount of free space in the instance directory might cause the server to halt.

User response

Remove unnecessary files or extend the instance directory file system.

ANR0314W Recovery log usage exceeds utilization percentage % of its assigned capacity.

Explanation

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

System action

Server operation continues.

User response

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

ANR0316W A full backup for database DB Name cannot be started. This backup is required.

Explanation

An automatic full backup was attempted for this database. However, the device class for database backups has not been specified.

System action

The database backup operation is not started.

User response

Issue the SET DBRECOVERY command to specify the default device class for automatic database backups. Then, issue the BACKUP DB command and specify TYPE=FULL to back up the database.

ANR0317I Reorganization of indices for table table name started.

Explanation

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

System action

The server will continue to operate.

User response

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

ANR0318I Reorganization of indices for table table name ended with sqlCode dbCode.

Explanation

The server online reorganization for the indices for the table referenced has ended.

System action

The server will continue to operate.

User response

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

ANR0319W The file system for the database archive log has insufficient free space.

Explanation

The usage of the file system for the database archive log has exceeded the ARCHLOGUSEDTHRESHOLD. Space is used by files that are not database archive log files, and the BACKUP DB command cannot free space in the filesystem..

System action

The server will continue to operate.

User response

Create sufficient free space on the file system so that usage does not exceed the ARCHLOGUSEDTHRESHOLD.

ANR0320W Storage agent storage agent is not able to use device class device class for storage pool storagepool for LAN-Free data movement operations.

Explanation

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

System action

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

User response

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

ANR0321W Storage agent storage agent name at version storage agent VRMF does not support operation operationName, although the server server name at version server VRMF can support it.

Explanation

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

System action

The operation is not allowed.

User response

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

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

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

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

ANR0322E The NEWSTGPOOL parameter is not valid for deduplicated volume volume name.

Explanation

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

System action

The operation is not allowed.

User response

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

ANR0323E The NEWSTGPOOL parameter is not valid for deduplicated storage pool pool name.

Explanation

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

System action

The operation is not allowed.

User response

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

ANR0324E command: Replication parameters cannot be used with the TYPE=SERVER parameter.

System action

The command failed.

User response

Reissue the command without replication parameters. Replication parameters include REPLSTATE, REPLMODE, BKREPLRULEDEFAULT, ARREPLRULEDEFAULT and SPREPLRULEDEFAULT.

ANR0325E command: Operation is not allowed because node nodename is a replica.

Explanation

The specified node is a replica of a node on another server, created using the REPLICATE NODE command.

You can restore or retrieve data from this node, but you cannot store new data or alter existing data in any way.

System action

Client sessions that attempt to store new data or change existing data will be terminated with a protocol error. IMPORT operations will skip the node.

User response

Perform the operation on the server on which the original node resides.

ANR0326E command: The ROLEOVERRIDE parameter cannot be used with either the TYPE=SERVER or TYPE=NAS parameter.

System action

The command failed.

User response

Reissue the command without the ROLEOVERRIDE parameter.

ANR0327I Replication of node node list completed. Files current: files current. Files replicated: files replicated of files to replicate. Files updated: files updated of files to update. Files deleted: files deleted of files to delete. Amount replicated: amount replicated of amount to replicate. Amount transferred: amount transferred. Elapsed time: elapsed time.

Explanation

The replication process has completed. The meanings of the numbers are:
  • Files current indicates the number of files that do not need to be replicated.
  • Files replicated indicates the number of files successfully replicated out of the number of files that we attempted to replicate.
  • Files updated indicates the number of files which had meta-data updated on the target server out of the number of files that needed an update.
  • Files deleted indicates the number of files deleted from the target server out of the number that needed to be deleted.
  • Amount replicated indictaes the size of the files that were replicated out of the size of the files that needed to be replicated
  • Amount transferred indicates the number of bytes transferred for the files that were replicated. For compressed files, the number of bytes transferred is the compressed size in bytes. The total number of bytes transferred can be less than the amount replicated if data deduplication or compression is used to reduce the amount of data transferred.
  • Elapsed time indicate how long the process ran

System action

None.

User response

None.

ANR0328I Replication preview of node(s) node list completed. Files current: files current. Files to be replicated: files to replicate. Files to be updated: files to update. Files to be deleted: files to delete. Amount to replicated: amount to replicate. Estimated run time: estimated runtime.

Explanation

The replication process has completed in preview mode. The meanings of the numbers are:
  • Files current indicates the number of files that do not need to be replicated.
  • Files to be replicated indicates the number of files requiring replication.
  • Files to be updated indicates the number of files requiring a meta-data update.
  • Files to be deleted indicates the number of files to be deleted from the target server.
  • Amount to be replicated indicates the size of the files that require replication.
  • Estimated run time is an estimate of how long the process will run.

System action

None.

User response

None.

ANR0329I Starting replication of data type data for node node name, filespace ID filespace id.

Explanation

The replication process has started processing data for the specified node and file space ID.

System action

None.

User response

None.

ANR0330W Session session number for node node name (client platform) refused - invalid authentication protocol requested.

Explanation

The server refuses a request to start a session because an invalid authentication protocol was requested during sign-on processing. This might be due to a down-level client, server, or storage agent that is accessing a server or storage agent that is configured to disallow such attempts.

System action

Server operation continues.

User response

Upgrade the accessing client, server, or storage agent to version 6.3 or later, or re-configure the server to allow access from down-level clients, servers, or storage agents.

ANR0331W Replication session for server server name refused - server is down-level.

Explanation

The server specified for replication cannot be used because it is not at the current level.

System action

Server operation continues.

User response

Upgrade the server to version 6.3 or later, or specify a different server for replication.

ANR0332E Replication mode source repl mode of node node name is incompatible with mode target repl mode on server server name.

Explanation

The replication mode of the indicated node is incompatible. If the source mode is SEND, the target mode must be RECV. If the source mode is SYNCSEND, the target mode must be SYNCRECV. The source mode cannot be anything other than SEND or SYNCSEND.

System action

The replication of the node's data fails. Server operation continues.

User response

Use the UPDATE NODE command to put the node in the proper state on both the source and target servers.

ANR0333E Server server name is disabled for outbound sessions. The session request is rejected.

Explanation

The DISABLED SESSION SERVER command disabled outbound sessions for the indicated server. Sessions to this server are not permitted.

System action

The session request fails. Server operation continues.

User response

Issue the QUERY STATUS command to view the servers that are disabled for inbound and outbound sessions. Issue the ENABLE SESSIONS SERVER command to make the server available for outbound sessions.

ANR0334E Server server name is disabled for inbound sessions. The session request is rejected.

Explanation

The DISABLED SESSION SERVER command disabled inbound sessions for the indicated server. The indicated server is not permitted to initiate sessions to this server.

System action

The session request fails. Server operation continues.

User response

Issue the QUERY STATUS command to view the servers that are disabled for inbound and outbound sessions. Issue the ENABLE SESSIONS SERVER command to make the server available for inbound sessions.

ANR0335I Schema reconciliation for table table in progress; pct% completed.

Explanation

The schema for this table is reconciling.

System action

Schema reconciliation will continue for this table.

User response

None

ANR0336I Runstats for table table name started.

Explanation

The server is performing an online runstats on the referenced table.

System action

Server operation continues.

User response

None.

ANR0337I Runstats for table table name ended with sqlCode dbCode.

Explanation

The server online runstats for the table referenced has completed.

System action

Server operation continues.

User response

For a non-zero sqlCode, consult the Db2 Information Center for details.

ANR0338E Database create terminated.

Explanation

Db2 detected a problem during the create database operation. The source of the problem might be a Db2 limitation. When "No File System Caching" is used to create a table space with Database Managed Storage containers, Db2 only supports storage devices with a sector size of 512 Bytes on AIX, Solaris, Linux, Windows, and a sector size of 1024 Bytes on HP-UX.

System action

The create database operation is terminated.

User response

See the db2diag.log file for additional information to confirm the Db2 limitation. Change the sector size to 512 Bytes on AIX, Solaris, Linux, Windows, and to 1024 Bytes on HP-UX.

ANR0339E command: Outbound replication is disabled.

Explanation

Replication operations originating from this server are disabled.

System action

Processing ends.

User response

Use the ENABLE REPLICATION command to re-enable the use of replication.

ANR0340E command: Outbound replication operations are disabled because the database was restored.

Explanation

The database for this server was restored. Data that was on this server but that is not referenced by the restored database is no longer accessible. To prevent this server from deleting copies of data that might exist on the target replication servers, replication operations originating from this server are disabled.

System action

Processing ends.

User response

Disabling replication after a database restore is a precautionary step to alert the user of the potential that a restored database might contain node inventory that could result in the loss of filespace data on a target replication server that is using node replication. If replication was not used on this server before the database restore, issue the ENABLE REPLICATION command to resume replication operations.

To preserve the data that exists on target replication servers, determine whether copies of data that are on the target replication server are needed. If they are, you must replicate data that is on the target replication server to the source replication server. After the replication is complete, issue the ENABLE REPLICATION command to resume replication operations.

For example, suppose that PRODSRV is the source replication server. The data belonging to client node NODE1 was replicated from PRODSRV to DRSRV, the target replication server. The database on PRODSRV was restored.

To resume replication, complete the following steps:
  1. On PRODSRV and DRSRV, remove NODE1 from replication by issuing the following command: REMOVE REPLNODE NODE1.
  2. Update NODE1 definitions. When replication occurs, DRSRV will send the data to PRODSRV that was lost because of the database restore.
    1. On DRSRV, issue the following command: UPDATE NODE NODE1 REPLSTATE=ENABLED REPLMODE=SYNCSEND.
    2. On PRODSRV, issue the following command: UPDATE NODE NODE1 REPLSTATE=ENABLED REPLMODE=SYNCRECEIVE.
  3. On DRSRV, set the replication rules to match those on PRODSRV. For example, if only archive data was being replicated from PRODSRV to DRSRV, set the rules on DRSRV to replicate only archive data from DRSRV to PRODSRV. Backup and space-managed data will not be replicated to PRODSRV.
  4. On DRSRV, set the target replication server by issuing the following command: SET REPLSERVER PRODSRV.
  5. On DRSRV, replicate data belonging to NODE1 by issuing the following command: REPLICATE NODE NODE1. Replication processing changes the replication mode of NODE1 to SEND on DRSRV and to RECEIVE on PRODSRV.
  6. On PRODSRV and DRSRV, remove NODE1 from replication by issuing the following command: REMOVE REPLNODE NODE1.
  7. Update NODE1 definitions:
    1. On PRODSRV, issue the following command: UPDATE NODE NODE1 REPLSTATE=ENABLED REPLMODE=SYNCSEND.
    2. On DRSRV, issue the following command: UPDATE NODE NODE1 REPLSTATE=ENABLED REPLMODE=SYNCRECEIVE.
  8. On PRODSRV, enable replication by issuing the following command: ENABLE REPLICATION.
  9. On PRODSRV, replicate data belonging to NODE1 by issuing the following command: REPLICATE NODE NODE1. Replication processing changes the replication mode of NODE1 to SEND on PRODSRV and to RECEIVE on DRSRV.

The original replication configuration is restored. PRODSRV has all the data that was lost because of the database restore.

REMEMBER: To replicate data that was on DRSRV, you set the target replication server to PRODSRV. In your original configuration, if you were replicating data from DRSRV to another server, for example, BKUPDRSRV, you must reset the target replication server. To reset the target replication server, issue the following command on DRSRV: SET REPLSERVER BKUPDRSRV.

ANR0341E command with keyword keyword is not allowed when archive data retention protection is enabled.

Explanation

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

System action

Processing continues.

User response

None.

ANR0343W File space filespace name could not be created by node $$_TSMDBMGR_$$. $$_TSMDBMGR_$$ node name is reserved for IBM Spectrum Protect database backup and restore.

System action

Server processing continues.

User response

Node $$_TSMDBMGR_$$ is only used for IBM Spectrum Protect database backup or restore. The server does not create a file space with this special node since there is no running database backup or restore session.

User response

Use another node name to create this filespace.

ANR0344E The server failed to restore the database. Missing ARCHIVELOGDIR value in the server option file.

Explanation

While attempting to restore the database, the IBM Spectrum Protect server detects a missing value for ARCHIVELOGDIR in the server option file.

System action

Server database restore stops.

User response

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

ANR0345E The database manager cannot start while file file name exists.

System action

The server stops.

User response

Remove or rename the specified file and restart the server.

ANR0347E Database database name is reporting a drive is invalid and the database can not be removed.

Explanation

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

System action

Server REMOVE DB stops.

User response

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

ANR0358E Database initialization failed: sufficient memory is not available.

Explanation

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

System action

Initialization fails.

User response

Make more memory available to the server.

ANR0361I Recovery is in progress following a database failure.

Explanation

During server initialization, the database manager indicated that the database requires failure recovery. A database failure can occur in the event of a power outage or other abnormal termination of the database manager. Failure recovery can take extensive time, depending on how many transactions in the log require examination.

System action

The server initialization is delayed while the database is recovered.

User response

No action is required.

ANR0365E Database database name is currently in use and can not be removed.

Explanation

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

System action

Server REMOVE DB stops.

User response

Drop all database connections then issue the command again.

ANR0366I Database database name was removed successfully.

Explanation

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

System action

None.

User response

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

ANR0367W The server failed to format the database database name. This database name already exists.

Explanation

While attempting to format a database, the IBM Spectrum Protect server has found that this database name already exists.

System action

Server format stops.

User response

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

ANR0369I Stopping the database manager because of a server shutdown.

System action

Stopping the server's database manager.

User response

None.

ANR0370E Diagnostic(ID) During the format operation, the server cannot create files in one or more directories that you specified for log type. Ensure that the file system where the directory is located has sufficient space.

Explanation

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

System action

The format operation stops.

User response

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

ANR0371E Error setting environment variable environment variable name with value value - return code return code value.

Explanation

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

System action

The server operation stops.

User response

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

ANR0372E Database database name is currently damaged and can not be removed.

Explanation

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

System action

Server REMOVE DB stops.

User response

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

ANR0373E Database database name is reporting a File error and can not be removed.

Explanation

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

System action

Server REMOVE DB stops.

User response

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

ANR0374E Database database name is invalid and can not be removed.

Explanation

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

System action

Server REMOVE DB stops.

User response

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

ANR0375E Database database name is reporting an authorization error and can not be removed.

Explanation

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

System action

Server REMOVE DB stops.

User response

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

ANR0376E Database database name is not found and can not be removed.

Explanation

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

System action

Server REMOVE DB stops.

User response

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

ANR0377E Database database name is reporting a drive is not found and can not be removed.

Explanation

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

System action

Server REMOVE DB stops.

User response

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

ANR0378W Database database name is reporting a drive is not found and can not be removed.

Explanation

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

System action

Server REMOVE DB completed successfully.

User response

The drop database command has completed successfully, however, there are some nodes where the database alias or database name was not found. It is possible that DROP DATABASE AT NODE was already performed on these nodes.

ANR0379W A server database deadlock situation has been encountered; the lock request for the lock name lock, key name will be denied to resolve the deadlock.

Explanation

The server detected a deadlock situation between a number of processes attempting to access database information. A lock request for one of the processes will be denied to resolve the database deadlock. When the server processes encounter a database deadlock, they usually try to run the function that was in progress when the deadlock was encountered again. Not all process can explicitly try an operation again. For example, migration and reclamation will eventually try again. However, something like a delete volume run in a macro will only be tried again if the delete command is reissued either in the macro or the command line.

System action

A lock request fails for one of the deadlocked processes. Server operation continues.

User response

If a process can be retried (like migration), monitor the retry effort to see if it succeeds. If the process or command cannot be retried, reissue the command or macro that caused the action.

Consider what other processes are running at the time the deadlock is reported. For example, if a process is started manually, as opposed to running as part of your regularly scheduled server maintenance tasks, that process may have caused the deadlock. You might have to adjust the scheduling of your server maintenance tasks to avoid the problem.

ANR0387I Evaluating node node name using storage agent storage agent for LAN-free data movement.

Explanation

The server is evaluating whether the node and storage agent can use storage pools capable of LAN-free data movement.

System action

The server evaluates the storage pool destinations available to this node and reports which storage pools can and cannot be used for LAN-free data movement.

User response

Review the results of this processing to determine if the appropriate LAN-free environment is configured.

ANR0388I Node node name using storage agent storage agent has capable count storage pools capable of LAN-free data movement and not capable count storage pools not capable of LAN-free data movement.

Explanation

The server has completed evaluation of the LAN-free and non-LAN-free storage pool destinations for this node using this storage agent. The server determined that there are capable count storage pools that are capable of LAN-free data movement. It also determined that there are not capable count storage pools that cannot be used for LAN-free data movement.

System action

None.

User response

Review the other messages issued to determine which storage pools are capable of LAN-free data movement and those which are not capable of LAN-free data movement for this node using this storage agent.

ANR0389W Node node name has data path restrictions.

Explanation

The node name has data path restrictions. The registered node has data write path, data read path, or both, configured to not allow LAN-free operations.

System action

None.

User response

Issue the command QUERY NODE node name F=D and evaluate the data read path and data write path settings. To store data or read data using LAN-free data movement, set the data write path to ANY or LANFREE.

ANR0390W A server database deadlock situation has been encountered; the lock request for transaction transaction ID will be denied.

Explanation

The server detected a deadlock situation between a number of processes that were attempting to access database information. A lock request for one of the processes is denied, to resolve the database deadlock. When server processes encounter a database deadlock, they usually reattempt the function that was in progress when the deadlock was encountered. Not all process can explicitly try an operation again. For example, migration and reclamation will eventually be tried again. However, something such as a delete volume run in a macro will only be tried again if the delete command is reissued either in the macro or the command line.

System action

A lock request fails for one of the deadlocked processes. Server operation continues.

User response

If a process can try again (like migration), then monitor the subsequent attempt to see if it succeeds or not. If it fails, contact a service representative. If the process or command is not able to automatically try again, then reissue the command or macro that caused the action to occur. If it fails again, contact a service representative for further assistance to better isolate the deadlock condition.

ANR0397I Session session number for node agent_node has begun a proxy session for node target_node.

Explanation

A client session has begun proxy operations.

System action

The server granted a proxy session to a client node.

User response

None.

ANR0398W Session session number for node agent_node has failed to begin a proxy session for node target_node.

Explanation

A client session attempted to begin a proxy operation. The server failed the client request. This can occur if the agent node does not have a proxy association with the target node.

System action

The server blocks the proxy authorization attempt.

User response

None.

ANR0399I Session session number for node agent_node has ended a proxy session for node target_node.

Explanation

A proxy session has been ended. The server terminates a session if there is an error in the protocol. On the other hand, the client can also terminate the session.

System action

The server, or the client, has ended a proxy session for a client node.

User response

None.

ANR0400I Session session number started for node node name (client platform) (communication method).

Explanation

A new client session has been initiated by the specified node. The session number, client platform type and communication method used by this session are included in the message.

System action

The server begins a communications session to service the client node.

User response

None.

ANR0401W Session session number for administrator admin name (client platform) refused - server version is down-level with this client.

Explanation

The server refuses an administrative client session because the client program version level is newer than that supported by the server program.

System action

Server operation continues.

User response

Apply service to the server program to make it compatible with the newer client program, or use an older client program to contact the server.

ANR0402I Session session number started for administrator administrator ID (administrator's platform) (communication method).

Explanation

A new administrator client session has been initiated by the specified administrator. The session number, administrator's platform type and communication method used by this session are included in the message.

System action

The server begins a communications session to service the administrator client.

User response

None.

ANR0403I Session session number ended for node node name (client platform).

Explanation

A client session has completed normally.

System action

Server operation continues.

User response

None.

ANR0404W Session session number for administrator admin name (client platform) refused - client is down-level with this server version.

Explanation

The server refuses the administrative client session because the client program version level is older than that supported by the server program. For certain problems (such as the compression fix), once an administrative client connects to the server using the newer client, the server records this fact and will not let this administrative client back off this client version to a version that does not include the fix.

System action

Server operation continues.

User response

Apply service to the client program to make it compatible with the newer server program.

ANR0405I Session session number ended for administrator administrator ID (client platform).

Explanation

An administrative client session has completed normally.

System action

Server operation continues.

User response

None.

ANR0406I Session session number started for node node name (client platform) (communication method communication address).

Explanation

A new client session has been initiated by the specified node. The session number, client platform type, communication method and address used by this session are included in the message.

System action

The server begins a communications session to service the client node.

User response

None.

ANR0407I Session session number started for administrator administrator ID (administrator's platform) (communication method communication address).

Explanation

A new administrator client session has been initiated by the specified administrator. The session number, administrator's platform type, communication method and address used by this session are included in the message.

System action

The server begins a communications session to service the administrator client.

User response

None.

ANR0408I Session session number started for server server name (server's platform) (communication method) for purpose.

Explanation

A new server session has been initiated by the specified server for the specified purpose. The session number, server's platform type and communication method used by this session are included in the message.

System action

The server begins a communications session to service the administrator client.

User response

None.

ANR0409I Session session number ended for server server name (client platform).

Explanation

A server has completed normally.

System action

Server operation continues.

User response

None.

ANR0410E EXPORT operation to server server name rejected - administrator administrator is not authorized to perform the import operation on the target server.

Explanation

An export operation to the named server was rejected, because the administrator issuing the export command is not defined on the target server or does not have sufficient authority to perform the import operation on the target server.

System action

Server operation continues.

User response

None.

ANR0411I Session session number for administrator administrator name logged in as node node name restored or retrieved object type object: node node name, filespace filespace name, object object name.

Explanation

This message logs information about an object that was restored or retrieved by an administrator logged in for a node.

System action

Server operation continues.

User response

None.

ANR0412I Session session number for node node name(Userid=user id), restored or retrieved object type object: node node name, filespace filespace name, object object name.

Explanation

This message logs information to the activity log about an object that was restored or retrieved by a user logged in for a node. A user ID with no value indicates that an administrative or root user on the platform initiated the restore.

System action

Server operation continues.

User response

None.

ANR0413I Session session number for administrator administrator name logged in as node node name is restoring backup set: node node name, set filespace name.

Explanation

This message logs information about a backup set restored by an administrator logged in for a node.

System action

Server operation continues.

User response

None.

ANR0414I Session session number for node node name is restoring backup set: node node name, set filespace name.

Explanation

This message logs information about a backup set restored by a node.

System action

Server operation continues.

User response

None.

ANR0415I Session session number proxied by storage agent name started for node node name.

Explanation

This session is started for the indicated node and the storage agent acts as the proxy for the node. Client node sessions are used to perform LAN-free operations between the client and server.

System action

Server operation continues.

User response

None.

ANR0416W Session session number for node node name not allowed to operation using path data transfer path.

Explanation

This session attempted this operation using the specified data transfer path. This operation is not permitted for this client.

System action

Server operation continues.

User response

Issue QUERY NODE FORMAT=DETAILED for this node to see the current DATA WRITE PATH or DATA READ PATH settings. These settings determine if a given operation is permitted using a specific data transfer path. If this client node should be permitted to perform this operation using this data transfer path, the UPDATE NODE command should be used to correct this.

ANR0417W Session session number for node node name terminated - data transfer path not allowed.

Explanation

This session attempted an operation that needed a data transfer path that this node is not allowed to use.

System action

This client session terminates.

User response

Refer to the ANR0416W message that was issued for this client session to determine which operation and data transfer path was attempted.

ANR0418W Session session number for administrator administrator name (client platform) is refused because an incorrect password was submitted.

Explanation

The server refuses a request to start a client session because an invalid password has been submitted by the client during sign-on processing.

System action

The server will continue to deny access attempts by this client until a valid password is submitted.

User response

Enter the proper password. If you have forgotten the password, contact an authorized administrator, who can assign a new password using the UPDATE ADMIN command.

ANR0419W Administrative client userid administrative ID cannot be used when authentication is on.

Explanation

The server refuses a request for a client (administrative) session because the user ID specified cannot be used when authentication of IDs is in effect. SERVER_CONSOLE is an administrative ID that has this restriction.

System action

Server operation continues.

User response

Use an administrative ID that was registered for this server and that has a password.

ANR0420W Session session number for node node name (client platform) refused - server disabled for user access.

Explanation

The server refuses a request for a client (backup-archive) session because the server is currently disabled for client access.

System action

Server operation continues. Administrative clients are permitted access to the server.

User response

An authorized administrator must issue the ENABLE SESSION command before client nodes are permitted access to the server.

ANR0421W Session session number for node node name (client platform) refused - sign-on protocol violation.

Explanation

The server refuses a request for a client session because sign-on protocol has been violated.

System action

Server operation continues.

User response

This error is usually the result of a client programming error in which the sign-on verb has been incorrectly formatted and delivered to the server. This error can also result when the server is contacted by an application that is not a part of this product.

ANR0422W Session session number for node node name (client platform) refused - node name not registered.

Explanation

The server refuses a request to start a client session because the client node name is not registered in the server database. On newer servers operating with newer clients, the client platform field contains the communication method and address.

System action

Server operation continues.

User response

Register the node name with the server before establishing a session. If the server is running with OPEN registration, no action is required; the client prompts the user for a password and registers the client with the server. If CLOSED registration is in effect on the server, an authorized administrator must use the REGISTER NODE command to register the client node name with the server.

ANR0423W Session session number for administrator administrator ID (client platform) refused - administrator name not registered.

Explanation

The server refuses a request to start an administrative session because the administrator name is not registered in the server database.

System action

Server operation continues.

User response

Register the administrator name with the server before establishing a session. An authorized administrator must use the REGISTER ADMIN command to register the administrator with the server.

ANR0424W Session session number for node node name (client platform) refused - invalid password submitted.

Explanation

The server refuses a request to start a client session because an invalid password has been submitted by the client during sign-on processing. The server will continue to deny access attempts by this client until a valid password is submitted. On newer servers operating with newer clients, the client platform field contains the communication method and address.

System action

Server operation continues.

User response

Enter the proper password. If the password has been forgotten by the user, an authorized administrator can assign a new password by using the UPDATE NODE command.

ANR0425W Session session number for node node name (client platform) refused - node password has expired.

Explanation

The server refuses the specified session because the client node's password has expired.

System action

Server operation continues.

User response

Upon receipt of this error condition, the client program immediately reconnects to the server specifying a password update session and prompts the user for a new password. After the user enters a new password, the client reconnects to the server for normal operations. Alternatively, an authorized administrator can update the client password using the UPDATE NODE command.

ANR0426W Session session number for node node name (client platform) refused - open registration not permitted.

Explanation

The server refuses a client session because an open registration action has been attempted and the server is running with CLOSED registration.

System action

Server operation continues.

User response

Ask an authorized administrator to submit the request using the REGISTER NODE or REGISTER ADMIN command.

ANR0427W Session session number for node node name (client platform) refused - server version is down-level with this client.

Explanation

The server refuses a client session because the client program version level is newer than that supported by the server program.

System action

Server operation continues.

User response

Apply service to the server program to make it compatible with the newer client program, or use an older client program to contact the server.

ANR0428W Session session number for node node name (client platform) refused - client is down-level with this server version.

Explanation

The server refuses the client session because the client program version level is older than that supported by the server program. For certain problems (such as the compression fix), once a node connects to the server using the newer client, the server records this fact and will not let this node back off this client version to a version that does not include the fix.

System action

Server operation continues.

User response

Apply service to the client program to make it compatible with the newer server program.

ANR0429W Session session number for node node name (client platform) refused - maximum server sessions (max sessions allowed) exceeded.

Explanation

The server refuses the specified client or administrative session because the maximum number of concurrent client sessions has been exceeded.

System action

Server operation continues.

User response

If necessary, increase the maximum number of permitted sessions. To do this, update the value for the MAXSESSIONS parameter in the server options file and restart the server with the updated options file. Note that increasing the MAXSESSIONS value requires additional memory resource by the server. You may want to retry the connection at a later time.

ANR0430W Session session number for node node name (client platform) refused - node name is locked.

Explanation

The server refuses the specified client session because the node is locked from server access (with the LOCK NODE command or by the LDAP directory server).

System action

Server operations continue.

User response

Before the client node is permitted to access the server, a properly authorized administrator must unlock the node. Nodes using LOCAL authentication can be unlocked with the UNLOCK NODE command. Nodes using LDAP authentication can be unlocked from within the LDAP directory server.

ANR0431W Session session number refused - administrator administrator ID (client platform) is locked.

Explanation

The server refuses the specified administrative session because the administrator is locked from server access (with the LOCK ADMIN command or by the LDAP directory server).

System action

Server operations continue.

User response

Before the administrator is permitted to access the server, a properly authorized administrator must unlock the administrator. Administrators using LOCAL authentication can be unlocked with the UNLOCK ADMIN command. Administrators using LDAP authentication can be unlocked from within the LDAP directory server.

ANR0432W Session session number for node node name (client platform) refused - insufficient memory.

Explanation

The server ends the specified session because sufficient memory (virtual memory) is not available.

System action

The server ends the session and continues operation.

User response

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

ANR0433W Session session number for node or administrator ID (client platform) was refused because of insufficient recovery log space.

Explanation

If a log runs out of space, the current transaction is rolled back. The server issues an error message and halts. You cannot restart the server until the recovery log size is increased.

System action

The server halts.

User response

Monitor archive logs and active logs. If the recovery log space is insufficient, monitor the archive log space first. If the archive log space is full or nearly full, run a full database backup to remove archive logs and consider adding more disk space to the archive log directory. If the archive log space is not full and the active log space is full or nearly full, update the value of the ACTIVELOGSIZE option in the dsmserv.opt file. Set the value of the ACTIVELOGSIZE option to the new maximum size of the active log.

ANR0434W Session session number for node or administrator ID (client platform) was refused because of insufficient database space.

Explanation

The server ends the specified client or administrative session because of insufficient database space.

System action

The server ends the session, but continues operation.

User response

To increase the amount of database space that is available to the server, issue the EXTEND DBSPACE command. Add one or more directories to the database.

ANR0435W Session session number for node node name (client platform) refused - internal error detected.

Explanation

The server ends the specified session because an internal logic error is detected.

System action

The server ends the session and continues operation.

User response

To determine the source of the error, the administrator can examine server messages issued prior to this message. The QUERY ACTLOG command can be used to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0437W Session session number for node client node name (client platform) encountered an internal server error while checking license compliance.

Explanation

The server encountered an internal error in determining if the server is in compliance with license terms.

System action

The client session is ended.

User response

Use the QUERY LICENSE and QUERY STATUS commands to determine if the server is in compliance with license terms. Start an AUDIT LICENSES process to readjust server license information. When this process completes you may restart the session. If the problem persists, contact your service representative.

ANR0438W Session session number archive operation for client client node name (client platform) has been denied - Server is not in compliance with license terms.

Explanation

The server refuses a client archive operation because the current server configuration is not in compliance with license terms.

System action

Server operation continues. Clients may perform any action except backup or archive.

User response

Use the QUERY LICENSE command to determine the license terms that are no longer in compliance.

ANR0439W Session session number backup operation for client client node name (client platform) has been denied - Server is not in compliance with license terms.

Explanation

The server refuses a client backup operation because the current server configuration is not in compliance with license terms.

System action

Server operation continues. Clients may perform any action except backup or archive.

User response

Use the QUERY LICENSE command to determine the license terms that are no longer in compliance.

ANR0440W Protocol error on session session number for node client node name (client platform) - invalid verb header received.

Explanation

The server detects a protocol error on the specified session because an invalid verb header has been received from the client. Verb headers always precede communication sent to the server from the client or from the server to the client.

System action

The server ends the client session.

User response

Correct the programming error in the client program if it has been written by your installation using WDSF verbs. Otherwise, contact your service representative.

ANR0441W Protocol error on session session number for node client node name (client platform) - invalid data length received.

Explanation

The server detects a protocol error on the specified session because an invalid verb length has been received from the client.

System action

The server ends the client session.

User response

Correct the programming error in the client program if it has been written by your installation using WDSF verbs. Otherwise, contact your service representative.

ANR0442W Protocol error on session session number for node client node name (client platform) - invalid stream mode switch.

Explanation

The server detects a protocol error on the specified session because the client has attempted an illegal stream operation.

System action

The server ends the client session.

User response

Correct the programming error in the client program if it has been written by your installation. Otherwise, contact your service representative.

ANR0443W Protocol error on session session number for node client node name (client platform) - invalid "field name" field found in "verb name" verb (offset offset position).

Explanation

The server detects a protocol error on the specified session because an invalid field has been found in a verb sent from the client node.

System action

The server ends the client session.

User response

Correct the programming error in the client program if it has been written by your installation using WDSF verbs. Otherwise, contact your service representative.

ANR0444W Protocol error on session session number for node client node name (client platform) - out-of-sequence verb (type verb name) received.

Explanation

The server detects a protocol error on the specified session because a verb has been received that does not adhere to the client-server exchange sequence.

System action

The server ends the client session.

User response

If the client generating the error is not an API client, contact your service representative. If the client generating the error is an API client, contact the owner of the API client. If the client generating the error is a client that you have created using WDSF verbs, correct the programming error in your client program.

ANR0445W Protocol error on session session number for node client node name (client platform) - maximum group transaction size exceeded.

Explanation

The server detects a protocol error on the specified session because the client has attempted to group more than the maximum database update operations in a single database transaction.

System action

The server ends the client session.

User response

Correct the programming error in the client program if it has been written by your installation using WDSF verbs. Otherwise, contact your service representative.

ANR0446W Session session number client client node name compression method unsupported - Compression forced OFF. Please obtain the latest level of the client code.

Explanation

The client is using a compression method that is no longer supported by the Server.

System action

Server operation continues. The client's backup operation continues, without compressing the data.

User response

The compression method used by the client is no longer supported. In order to use compression, the client needs to be upgraded to a client service level that supports the newer compression method.

ANR0447W Session session number space management migration operation for client client node name (client platform) has been denied - Server is not in compliance with license terms.

Explanation

The server refuses a client space management migration operation because the current server configuration is not in compliance with license terms.

System action

Server operation continues. Clients may perform any action except backup, archive, or space-managed file migration.

User response

Use the QUERY LICENSE command to determine the license terms that are no longer in compliance.

ANR0448W Session session number space management migration operation for client client node name (client platform) has been denied - server is not licensed for space management support.

Explanation

The server refuses a client space management migration operation because the server is not licensed to support space-managed clients.

System action

Server operation continues.

User response

Licenses to support space-managed clients can be obtained from your service provider or re-seller. The REGISTER LICENSE command can be used with these licenses to enable space management support.

ANR0449W Session session number space management migration operation for client client node name (client platform) is in violation of server license terms - server is not licensed for space management support.

Explanation

The server warns about a client space management migration operation because the server is not licensed to support space-managed clients.

System action

Server operation continues.

User response

Licenses to support space-managed clients can be obtained from your service provider or re-seller. The REGISTER LICENSE command can be used with these licenses to enable space management support.

ANR0450W Session session number for server server name (client platform) refused - server name not defined for server to server communications.

Explanation

The server refuses a request to start a server session because the requesting server name is not defined in the server database, or the requesting server definition does not have a SERVERPASSWORD, or a password or node name is not setup for virtual volume use on the source server.

System action

Server operation continues.

User response

Register the requesting server name with the server before establishing a session, or update the existing requesting server definition and set a SERVERPASSWORD. An authorized administrator must use the DEFINE SERVER or UPDATE SERVER command to register the requesting server and set the password. For a virtual volume environment, the source server must have a definition for the target server which includes a node name and password.

ANR0451W Session session number for server server name (server platform) refused - invalid password submitted.

Explanation

The server refuses a request to start a server session because an invalid password has been submitted during sign-on processing. The server will continue to deny access attempts by that server until valid passwords are submitted.

System action

Server operation continues.

User response

Set the proper passwords. If the password has been changed on either server, an authorized administrator can set new passwords by using the UPDATE SERVER command with the SERVERPASSWORD parameter.

ANR0452W Session for server source server name refused. Server source server name is not defined for server-to-server communications on server target server name.

Explanation

The server refuses a request to start a server-to-server session because a server name is not defined in the server database, or the server definition does not have a SERVERPASSWORD. Server-to-server communications that use the SERVERPASSWORD require that each server has a server definition for the other server.

System action

Server operation continues.

User response

Register the server names on both servers before establishing a session, or update the server's existing server definition and set a SERVERPASSWORD. An authorized administrator must use the DEFINE SERVER or UPDATE SERVER command to register the servers and set the passwords.

ANR0453W Server to server session refused - no password defined.

Explanation

The server to server session cannot be initiated because no server password has been defined for this server.

System action

Server operation continues.

User response

Define a server password with the SET SERVERPASSWORD command and retry the command.

ANR0454E Session rejected by server target server name, reason: rejection reason.

Explanation

The server tried to open a session with the named server. The session was rejected for the indicated reason.

System action

The operation fails.

User response

Check both the servers for any additional messages that might further describe the reason the session was rejected. The rejection reason will be in the form of "diagnostic code - reason". The diagnostic code is only intended for use by your service representative. The following responses apply to the specified rejection reasons.
  • No Resource: Ensure that the receiving server is enabled and has sufficient database, log, and memory resource to support the server session.
  • Verifier expired: Ensure that the administrator's password is current on both servers.
  • Admin not registered: Ensure that the administrator is registered on the target server.
  • Inbound sessions disabled: Ensure that the target server has not disabled this server with the DISABLE SESSIONS SERVER command.
  • Down Level: Ensure that this server's level is current with respect to the target server's level.
  • Admin in use: Ensure that the administrator is not being updated on the target server.
  • Language not available: Ensure that required languages are installed on the target server.
  • Admin locked: Ensure that the administrator is not locked on either server.
  • License Failure: Ensure that appropriate licenses are registered.
  • Admin on client port: Use the UPDATE SERVER command to set the admin port for the target server.
  • SSL Required: Ensure that SSL is properly configured.
  • Authentication Failure: Ensure that all passwords have been set correctly on both servers. The password for the server (set by SET SERVERPASSWORD on server X) and the password in the server definition (set by DEFINE or UPDATE SERVER X SERVERPASSWORD=) are the same password.
  • Verification Failure: Use the QUERY SERVER command to determine that the HLADDRESS and LLADDRESS of the target server are correct. If they are not, correct them with the UPDATE SERVER command. If they are correct, resynchronize with the target server by issuing the UPDATE SERVER FORCESYNC=YES command.
  • Communication Failure: Ensure that the target server is available and that TCPIP is available on both servers. Use the QUERY SERVER command to determine that the HLADDRESS and LLADDRESS of the target server are correct. If they are not, correct them with the UPDATE SERVER command.
  • Node Type: Either the TYPE of the registered node on the target server is not SERVER or the NODENAME parameter of the server definition on the source server is incorrect.
  • Internal error: Use the messages on the target server to determine the problem.

ANR0455W Invalid Command command name for SNMP session.

Explanation

An SNMP administrative session attempted to run a command which is not an macro invocation. SNMP administrative sessions are only allowed to issue macro commands.

System action

The server ends the client session.

User response

Enter commands through the SNMP administrative interface which are macros defined on the server.

ANR0456W Session rejected for server server name - the server name at High level address, Low level address does not match.

Explanation

The server name at the address specified does not match the name in the server definition. The connection is not established.

System action

The server continues.

User response

Ensure the HLADDRESS and LLADDRESS in the define server command are correct, and that the servername on the server being contacted matches the name used in the DEFINE SERVER command.

ANR0457W Session for server server name refused - crossdefine is not allowed on this server.

Explanation

The server refuses a request to start a server to server session for crossdefine because it is not allowed on this server. The server will deny any sessions for crossdefine until crossdefine is allowed on this server. Storage Agents can also request server to server sessions when setting up to access libraries through library client servers or library servers.

System action

Server operation continues.

User response

An authorized administrator must use the SET CROSSDEFINE ON command to allow cross registration of servers.

ANR0458S Server server name does not support access by the Storage Agent.

Explanation

The storage agent attempted to contact a Database Server, but the server contacted was not at the correct level.

System action

The Storage Agent terminates.

User response

Specify a correct Database Server in the devconfig file for the Storage Agent.

ANR0459W Authentication Protocol error on session session number for node client node name (client platform) - out-of-sequence verb (type verb name) received.

Explanation

The server detects a protocol error on the specified session because a verb has been received that does not adhere to the client-server authentication exchange sequence.

System action

The server ends the client session.

User response

If the client generating the error is not an API client, contact your service representative. If the client generating the error is an API client, contact the owner of the API client. If the client generating the error is an IBM-provided client, please ensure that it is at the current software level.

ANR0460W Open registration failed for session session number - node name node name (client platform) already exists.

Explanation

The server refuses a client session during open registration because the client has specified a node name that is already registered on the server.

System action

Server operation continues.

User response

The client program user must specify a different node name for the client in the client options file.

ANR0461W Open registration failed for session session number for node node name (client platform) - policy domain STANDARD does not exist.

Explanation

The server refuses a client session during open registration because the STANDARD policy domain does not exist. All nodes added to the server database under open registration are automatically assigned to the STANDARD policy domain. This policy domain must be defined and have an active policy set to support open registration.

System action

Server operation continues.

User response

If you want to support open registration, define a policy domain using the DEFINE DOMAIN command with the name STANDARD and activate a valid policy set in the domain. You can issue the UPDATE NODE command to move nodes to different policy domains after the nodes have registered themselves through open registration.

ANR0462W Open registration failed for session session number for node node name (client platform) - invalid node name.

Explanation

The server refuses a client session during open registration because the node name specified by the client is not valid.

System action

Server operation continues.

User response

Specify a node name in the options file of the client program that contains valid characters and does not exceed the maximum length in size.

ANR0463W Open registration failed for session session number for node node name (client platform) - invalid password.

Explanation

The server refuses a client session during open registration because the password name specified by the user is not valid.

System action

Server operation continues.

User response

Specify a password that uses valid characters and is less than the maximum length in size.

ANR0464W Open registration failed for session session number for node node name (client platform) - exceeded number of nodes available under license terms.

Explanation

The server detected an attempt to register more nodes than allowed by the terms of the current license.

System action

Server operation continues, but the REGISTER NODE command fails, and the node is not registered.

User response

Use the QUERY LICENSE command to determine the license terms that are no longer in compliance.

ANR0465W Open registration failed for session session number for node node name (client platform) - policy domain STANDARD does not have an ACTIVE policy set.

Explanation

The server refuses a client session during open registration because the STANDARD policy domain does not have an active policy set. All nodes added to the server database under open registration are automatically assigned to the STANDARD policy domain. This policy domain must be defined and have an active policy set to support open registration.

System action

Server operation continues.

User response

If you want to support open registration, define a policy domain using the DEFINE DOMAIN command with the name STANDARD and activate a valid policy set in the domain. You can issue the UPDATE NODE command to move nodes to different policy domains after the nodes have registered themselves through open registration.

ANR0466E The SETSTORAGESERVER command did not complete successfully.

Explanation

The SETSTORAGESERVER command encountered an error and did not complete successfully.

System action

Storage agent operation terminates.

User response

Please review prior error messages and take the necessary corrective actions.

ANR0467I The SETSTORAGESERVER command completed successfully.

Explanation

The SETSTORAGESERVER command has completed successfully, and the appropriate device configuration files have been updated.

System action

Storage agent operation terminates.

User response

None

ANR0468E Server-to-server export and import not allowed with server server name. Export server is at version export version; import server is at version import version.

Explanation

An attempt was made to export to an outdated server. The server on which the import is performed must be at the same or later level than the server from which the data was exported.

System action

The export operation ends and server operation continues.

User response

Export to a server that is at the same or later level.

ANR0469W Session session number for node node name (client platform) refused - client is not configured for archive retention protection.

Explanation

The server refuses a client session because the client is not configured for archive retention protection.

System action

Server operation continues.

User response

Either disable archive retention protection on the server or configure the client for archive retention protection.

ANR0470W Session session number for administrator administrator name refused - administrator password has expired.

Explanation

The server refuses the specified session because the administrator's password has expired.

System action

Server operation continues.

User response

Upon receipt of this error condition, the client program immediately reconnects to the server specifying a password update session and prompts the user for a new password. After the user enters a new password, the client reconnects to the server for normal operations. Alternatively, an authorized administrator can update the client password using the UPDATE ADMIN command.

ANR0472E The database manager did not start. A tablespace container is inaccessible.

Explanation

The server was unable to start the database manager.

System action

The server halts.

User response

Before restarting the server, check the following items:
  • Reboot the system.
  • Check that the directories for dbdir, log, or devices exists and that the file system is mounted (if it is on a separate file system).
  • Make sure that the hardware and network connection are working properly.
  • Fix any errors in the system log or db2diag.log.

ANR0473W Session session number for administrator administrator ID (client platform) refused - administrator name does not have the correct level of authority over client node.

Explanation

The server refuses a request to start an administrative session because the administrator name does not have appropriate authority over the node.

System action

Server operation continues.

User response

Use command GRANT AUTHORITY to grant appropriate authority to the current administrator ID.

ANR0474W Session session number for administrator administrator ID (administrator platform) was refused because administrators are not allowed to initiate sessions on the client port.

Explanation

The server did not start the specified administrative session because the administrator connected to the server on the server port that is used for client sessions, and the option ADMINONCLIENTPORT is set to NO. When different port numbers are used for administrative and client sessions (controlled by the TCPPORT and TCPADMINPORT options), and option ADMINONCLIENTPORT is set to NO, administrative sessions can be started only on the port used for administrative sessions (as specified by the TCPADMINPORT option).

System action

Server operation continues.

User response

Update the client options file to specify the port to be used for administrative sessions. This is typically specified by the TCPADMINPORT option in both client and server option files.

ANR0475W Session session number for node node name (client platform) refused - node is not allowed to initiate sessions on administrative port.

Explanation

The server had refused to start a session with the specified client node because the node connected to the server on the server's administrative port. When different port numbers are used for administrative and client sessions, client sessions may be started only on the port used for client sessions.

System action

Server operation continues.

User response

The client option file should be updated to specify the port to be used for client sessions. This is typically specified by TCPPORT option in both client and server option files. The MVS server also uses the ICSPORT option.

ANR0476W Session session number for node node name (client platform) refused - node is not allowed to initiate sessions.

Explanation

The server had refused to start a session with the specified client node because the node is not allowed to initiate session. Only server initiated sessions are allowed with this client. The SESSIONINIT parameter of the REGISTER NODE and UPDATE NODE commands control the ability of a client to initiate sessions.

System action

Server operation continues.

User response

An administrator can use the UPDATE NODE command with the SESSIONINIT parameter to specify that the client may initiate sessions. Alternatively, sessions can be scheduled with the client that are stared by the server through server-prompted scheduling commands ( DEFINE SCHEDULE, DEFINE ASSOCIATION ).

ANR0477W Session session number refused - The client client node name cannot access the server with a platform type of client platform.

Explanation

A client with a invalid combination of node type and platform type has requested a session with the server. For example, a node id of type NAS can only sign on with a platform type of "TSMNAS", all other node types cannot use this platform type.

System action

The session request is refused. The server operation continues.

User response

Verify that the Id used by a client to sign on has the proper platform type.

ANR0478W Session request refused. Server is running in standalone mode.

Explanation

A client has requested a session with the server. The server is running in a mode in which it cannot start client sessions.

System action

The session request is refused. The server operation continues.

User response

No response is required. To reduce or disable the display of this message, you can update the server options before running in standalone mode with the COMMMETHOD NONE option. This will allow the server to run without enabling client connections.

ANR0479W Session session number for server server name (server platform) terminated - connection with server severed.

Explanation

If server A has opened a connection with server B, server B's session is ended because the communications link has been closed by a network error or by server A's program.

System action

Server A continues operation.

User response

If server B halts operation or in some way stops communicating with server A, this message will be displayed on server A indicating that the connection was closed suddenly by server B. A network failure can also cause this message to be displayed. If a large number of these messages occur simultaneously, check the network for failure and correct any problems.

ANR0480W Session session number for node node name (client platform) terminated - connection with client severed.

Explanation

The specified client session is ended because the communications link has been closed by a network error or by the client program.

System action

Server operation continues.

User response

If a user breaks out of a client program, this message will be displayed on the server as the connection is suddenly closed by the client. A network failure can also cause this message to be displayed. If a large number of these messages occur simultaneously, check the network for failure and correct any problems.

ANR0481W Session session number for node node name (client platform) was terminated. The client did not respond within commtimeout seconds seconds.

Explanation

The server ends a client session because the client was holding database locks during a transaction. The client did not respond within the number of seconds specified by the COMMTIMEOUT server option.

System action

The server rolls back the transaction that was in progress and the session is ended. Server operation continues.

User response

If this message appears frequently, consider incrementing the value specified for the COMMTIMEOUT option. Use the SETOPT command to change the value of the COMMTIMEOUT option without stopping or restarting the server. This update changes the amount of time that the server waits for an expected client message during an operation that causes a database update.

ANR0482W Session session number for node node name (client platform) terminated - idle for more than idletimeout minutes minutes.

Explanation

The server ends a client session because it has been idle for more minutes than specified in the IDLETIMEOUT parameter in the server options file. The client program will automatically attempt to reconnect to the server when necessary.

System action

Server operation continues.

User response

If the problems persists, increase the value specified for the IDLETIMEOUT parameter in the server options file and restart the server. Many times, the client program is idle while waiting for the user to choose an action to perform (for example, backup, archive, restore, or retrieve files). If a user starts the client program and does not choose an action to perform, the session will eventually time out. The client program automatically reconnects to the server when the user chooses an action that requires server participation. Note that a large number of idle sessions can inadvertently prevent other users from connecting to the server, so care should be used when increasing the IDLETIMEOUT parameter.

ANR0483W Session session number for node node name (client platform) terminated - forced by administrator.

Explanation

The server ends a client session in response to a CANCEL SESSION command issued by an authorized administrator.

System action

The server rolls back any transactions in progress for the terminated client session.

User response

None.

ANR0484W Session session number for node node name (client platform) terminated - protocol violation detected.

Explanation

The server ends the specified session because a communications protocol error by the client has been detected.

System action

The server ends the client session.

User response

Examine the client message to determine the problem. Correct the programming error in the client program. If the error cannot be isolated and resolved, contact your service representative.

If this session is a proxied LAN-Free session for a storage agent, this error may be the result of a mount point or volume preemption on the storage agent. Review the messages logged by the storage agent to determine if a storage agent action caused this to occur.

ANR0485W Session session number for node node name (client platform) terminated - sufficient memory is not available.

Explanation

The server ends the specified session because sufficient memory (virtual memory) is not available.

System action

The server ends the session and continues operation.

User response

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

ANR0486W Session session number for node node name (client platform) terminated - internal error detected.

Explanation

The specified client session is ended by the server because an internal processing error has been detected on the server. A programming error may have occurred in the server program.

System action

The session is ended and server operation continues.

User response

If this session is a proxied LAN-Free session for a storage agent, this error may be the result of a mount point or volume preemption on the storage agent. Review the messages logged by the storage agent to determine if a storage agent action caused this to occur.

If the cause of the error can not be determined after reviewing the activity log, contact your service representative.

ANR0487W Session session number for node node name (client platform) terminated - preempted by another operation.

Explanation

The server ends a client session in response to a cancel request issued by a higher priority operation that needed the mount point that the client was using.

System action

The server rolls back any transactions in progress for the terminated client session.

User response

Reissue the operation. If this message appears frequently, consider increasing the mountlimit value for the affected device class.

ANR0488W Session session number for node node name (client platform) terminated - transfer rate is less than (transfer rate) and more than (elapsed time since first data transfer) minutes have elapsed since first data transfer.

Explanation

The server is canceling client session number session number. Depending on the state of the session, it may take a while for the session to be canceled. The server ends a client session because it has been active for more minutes than specified in the THROUGHPUTTIMETHRESHOLD parameter in the server options file and the data transfer rate is less than the amount specified with the THROUGHPUTDATATHRESHOLD parameter in the server options file. The client is transferring data to the server at an abnormally slow rate and may have become a bottleneck for handling data from other clients. If the client has caused log records to be written, it is possible that this client will prevent log space reclamation.

System action

The session is canceled and server operation continues.

User response

If a low data transfer rate is not a problem, the THROUGHPUTTIMETHRESHOLD or THROUGHPUTDATATHRESHOLD parameters in the server options file can be set to zero - this will disable the throughput check. The change can be made without taking down the server and restarting it by using the SETOPT THROUGHPUTTIMETHRESHOLD or the SETOPT THROUGHPUTDATATHRESHOLD commands. If a low data transfer rate is not expected, external causes should be investigated. This would include network problems and problems in accessing data on the client node. The client program may automatically reconnect to the server, so this message may appear on subsequent sessions until the data transfer problem is resolved. The default server operation is not to perform a throughput check.

ANR0489W Session session number refused for client node name - NAS type nodes are not supported by a storage agent.

Explanation

The specified client tried to connect to a storage agent. The storage agent does not support a node that is defined as TYPE=NAS.

System action

The session request is refused. The server operation continues.

User response

The client should be re-configured to not try LAN-free operations. This may be done by setting UPDATE NODE ENABLELANFREE=NO for the client.

ANR0490I Canceling session session number for node node name (client platform) .

Explanation

The server is canceling client session number session number. This message is displayed in response to the CANCEL SESSION command. Depending on the state of the session, it may take a while for the session to be canceled.

System action

The session is canceled and server operation continues.

User response

None.

ANR0491I No matching session(s) found to cancel.

Explanation

The server cannot find any sessions to cancel matching the specifications entered in the CANCEL SESSION command.

System action

Server operation continues.

User response

Use the QUERY SESSION command to ensure that the session you wish to cancel is connected. Reissue the command using the appropriate session number to cancel the client session.

ANR0492I All drives in use. Session session number for node node name (client platform) being preempted by higher priority operation.

Explanation

When a high priority operation attempted to find an available drive, all the drives were being used. To free up a drive for this operation, the client session identified is being cancelled by the system.

System action

The lower priority client session is cancelled to free up a mount point (drive).

User response

When a drive again becomes available, restart the session that was cancelled. This session was most likely a backup/archive session and you may just want to let it restart automatically during its next scheduled backup window. If this message appears frequently, you may want to increase the number of drives available. See the MOUNTLIMIT parameter on the UPDATE DEVCLASS command.

ANR0493I Restore session session number canceled.

Explanation

The specified session was canceled with the CANCEL RESTORE command.

System action

The restore session is canceled and server operation continues.

User response

None.

ANR0494I Volume volume name in use. Session session number for node node name (client platform) being preempted by higher priority operation.

Explanation

When a high priority operation attempted to acquire a specific volume, it was being used. To free the volume for this operation, the client session identified is being cancelled by the system.

System action

The lower priority client session is cancelled to free up the volume.

User response

Restart the session that was cancelled, it will wait until the higher priority operation if finished with the volume. This cancelled session was most likely a backup/archive session and you may just want to let it restart automatically during its next scheduled backup window.

ANR0495I Cannot cancel the specified EXPORT/IMPORT session.

Explanation

The server cannot cancel the session specified in the CANCEL SESSION command.

System action

Server operation continues.

User response

Export/Import sessions cannot be canceled using CANCEL SESSION. The user should use the CANCEL PROCESS command to terminate the EXPORT/IMPORT operation.

ANR0496E Session session number operation for client client node name (client platform) has been denied because verb (type verb name) is not allowed when archive retention is active.

Explanation

The server refuses the specified client operation because archive retention protection is active.

System action

Server operation continues.

User response

Do not send the specified operation to the server when archive retention protection is active.

ANR0497W Session request refused from non-Express client.

Explanation

A non-Express client has requested a session with the Express server. Only connections from an Express client will be accepted by an Express server.

System action

The session request is refused. The server operation continues.

User response

None.

ANR0498W Session session number refused for client node name because restore DB is in progress.

Explanation

Restore DB is in progress, only connection from Client related to restore DB are allowed.

System action

The session request is refused. The server Restore DB operation continues.

User response

None.

ANR0500W Transaction failed for session session number for node node name (client platform) - invalid password submitted.

Explanation

The server ends a password update transaction because the user has not correctly specified the current password.

System action

Server operation continues.

User response

Update your password by correctly specifying the current password. If the current password has been misplaced, the administrator can reassign a password for the client by using the UPDATE NODE or UPDATE ADMIN command.

ANR0501W Transaction failed for session session number for node node name (client platform) - invalid policy binding specified.

Explanation

The server ends a database update transaction for the specified session because an invalid management class has been specified for a file or directory object.

System action

The specified session is ended and server operation continues.

User response

Correct the programming error in the client program if it has been written by your installation using WDSF verbs. Otherwise, contact your service representative.

ANR0502E Transaction failed for session session number for node node name (client platform) - A storage pool for the target destination is associated with a device class that has a Centera device type.

Explanation

The server ends a database update transaction for the specified session because an invalid management class has been specified. Centera device types may be used only for archive objects.

System action

The specified session is ended and server operation continues.

User response

Ensure that Centera device types are associated with device classes that are used only for archive operations. The UPDATE COPYGRP command can be used to update copy groups associated with space management and/or backup storage pools so that they point to valid destinations.

ANR0503I Session session number for administrator administrator name logged in as node node name restored or retrieved object type object: node node name, filespace filespace name, object object name, version version of total version.

Explanation

This message logs information about an object that was restored or retrieved by an administrator logged in for a node.

System action

Server operation continues.

User response

None.

ANR0504I Session session number for node node name(Userid=user id), restored or retrieved object type object: node node name filespace filespace name, object object name, version version of total version.

Explanation

This message logs information to the activity log about an object that was restored or retrieved by a user logged in for a node. A user ID with no value indicates that an administrative or root user on the platform initiated the restore.

System action

Server operation continues.

User response

None.

ANR0505E The database manager encountered a null value for column name during the data fetching.

Explanation

The server received an unexpected data value.

System action

The server cannot process the command.

User response

Before reissuing the command, try the following actions:
  • Reboot the system.
  • Check that the directories for dbdir, log, or devices exists and that the file system is mounted (if it is on a separate file system).
  • Make sure that the hardware and network connection are working properly.
  • Fix any errors in the system log or db2diag.log.

ANR0506I A full backup has been started for database DB Alias. This backup is required.

Explanation

This level of the IBM Spectrum Protect server uses a new version of the database manager that has a new format for log files. Database backups created prior to this level of the server cannot be used to restore the database. A new database backup image is needed to ensure that the database is protected.

System action

A full database backup is started.

User response

None.

ANR0507E Protocol error on session session number for node client node name (client platform) because an owner was not properly provided for the indicated node.

Explanation

The session does not adhere to the client-server exchange sequence, therefore the server detected a protocol error on the specified session.

System action

The server ends the client session.

User response

If the client runs in a non-standard environment, the server detects that the owner field is not being sent properly. It is not recommended to run the client in a non-standard environment.

ANR0508E An automatic full database backup for database DB Alias has failed.

Explanation

A full database backup failed. This message always accompanies one or more other message that provides more details about the error.

System action

The server operation continues.

User response

Examine the server messages that were issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages.

ANR0509E The database restore failed on DB Alias due to the log format differences between database manager versions.

Explanation

The database restore failed because the backup image was produced by a previous version of the database manager.

System action

The database restore terminates.

User response

If you need to restore the database immediately, uninstall the upgraded server, re-install the previous version of the server, then run the restore command. Otherwise, start the upgraded server. The upgraded server creates a new backup image automatically. After the database backup completes, run the server restore utility again.

ANR0510I Session session number opened input volume volume name.

Explanation

The indicated session has opened the specified volume for input processing.

System action

Processing continues.

User response

None.

ANR0511I Session session number opened output volume volume name.

Explanation

The indicated session has opened the specified volume for output processing.

System action

Processing continues.

User response

None.

ANR0512I Process process number opened input volume volume name.

Explanation

The indicated process has opened the specified volume for input processing. You may or may not see an associated ANR0515I message for this process/volume combination, since some volumes are shared between multiple processes.

System action

Processing continues.

User response

None.

ANR0513I Process process number opened output volume volume name.

Explanation

The indicated process has opened the specified volume for output processing. You may not see an associated ANR0515I message for this process/volume combination, since some volumes are shared between multiple processes.

System action

Processing continues.

User response

None.

ANR0514I Session session number closed volume volume name.

Explanation

The indicated session has finished using the specified volume.

System action

Processing continues.

User response

None.

ANR0515I Process process number closed volume volume name.

Explanation

The indicated process has finished using the specified volume. It is possible that the process indicated was not the process that opened the volume.

System action

Processing continues.

User response

None.

ANR0516E SQL processing for statement statement failed.

Explanation

The indicated select statement failed. The failure was caused by a syntax error with the statement itself.

System action

The select statement failed.

User response

Review the server activity log for message ANR0162W for an explanation of the error that caused this statement to fail.

ANR0517E command: The DEDUPLICATION parameter cannot be used with either the TYPE=SERVER or TYPE=NAS parameter.

System action

The command failed.

User response

Reissue the command without the DEDUPLICATION parameter.

ANR0518W NDMP restore failed for session session number for node node name (client platform), file space filespace.

Explanation

The server ends a restore operation for the specified NAS node because an error has been encountered on the server. Some common reasons for the error are:
  • The input volume is unavailable
  • The storage pool is unavailable
  • Data is corrupted on the input volume
  • Hardware or media failure has occurred
  • The server database is corrupted

System action

The server ends the restore operation.

User response

Examine any prior error messages to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages if needed. Correct any problem and try the restore again. If the data is also backed up in a copy storage pool, the retry operation will attempt to read the file from the alternate location. If retry of the restore operation continues to fail contact your service representative.

ANR0519E A retrieve or restore operation failed for session session number for node node name (client platform). An invalid partial object request was received.

Explanation

The server ended a file retrieve or restore operation for the specified session because an invalid value for the offset, length, or both was received from the client application for the object being retrieved or restored.

System action

The server ends the specified operation and server operation continues.

User response

Specify an offset, length, or both within the bounds of the object to be retrieved or restored, and rerun the application.

ANR0520W Transaction failed for session session number for node node name (client platform) - storage pool pool name is not defined.

Explanation

The server rolls back a database update transaction for the specified session because the destination specified for a management class copy group specifies the named storage pool, but that storage pool does not exist.

System action

Server operation continues.

User response

An administrator with policy authority over the client policy domain must correct management class definitions so that copy group destinations refer to defined storage pools, or the specified storage pool must be created by an authorized administrator.

ANR0521W Transaction failed for session session number for node node name (client platform) - object excluded by size in storage pool pool name and all successor pools.

Explanation

The server ends a database update transaction for the specified session because the size of a file sent from the client node is larger than that allowed in the storage pool specified in the client's management class copy group. No successor storage pools to the one specified on the copy group can accept the large file.

System action

The specified session is ended and server operation continues.

User response

If the client is not using compression to send files to the host, turn compression on for the client (using the UPDATE NODE command) to try and resolve the problem. Otherwise, the maximum file size for one or more of the storage pools in the storage hierarchy can be increased to accommodate the file. An authorized administrator can increase the MAXSIZE parameter by issuing the UPDATE STGPOOL command.

ANR0522W Transaction failed for session session number for node node name (client platform) - no space available in storage pool pool name and all successor pools.

Explanation

The server ends a database update transaction for the specified session because the storage pool specified in the client's management class copy group does not contain enough free space to hold the files sent from the client. Successor storage pools to the one specified on the copy group do not contain enough free space.

System action

The specified session is ended and server operation continues.

User response

An authorized administrator can add storage to one or more storage pools in the storage hierarchy. Ensure that you size the file system based on the amount of data that you manage. Add storage space by using operating system tools. On the UPDATE STGPOOL command, specify the ACCESS parameter as READWRITE to ensure that client nodes and server processes can read and write to the storage pool.

ANR0523W Transaction failed for session session number for node node name (client platform) - error on output storage device.

Explanation

The server ends a database update transaction for the specified client because an I/O error has been encountered by the server in writing to a device.

System action

The specified session is ended and server operation continues.

User response

Query the activity log to find messages preceding this one that specify the failing device. Storage pool volumes can be varied offline (by using the VARY command), or the server may need to be halted to correct the hardware problem. After the problem is corrected, the client should retry the operation.

ANR0524W Transaction failed for session session number for node node name (client platform) - data transfer interrupted.

Explanation

The database transaction associated with session session number was aborted because data transfer to or from data storage was interrupted by an external event.

System action

The session is canceled and server operation continues.

User response

Examine the messages issued prior to this message to determine why the data transfer was interrupted. Attempt the client operation again if the problem can be resolved.

ANR0525W Transaction failed for session session number for node node name (client platform) - storage media inaccessible.

Explanation

The server ends a transaction for the specified session because storage volumes are not available in the storage pools in which the client's files are to be stored.

System action

The server ends the specified session and server operation continues.

User response

An authorized administrator can issue the DEFINE VOLUME command to add storage to one or more storage pools in the storage hierarchy. The VARY ONLINE command can be used to vary offline storage volumes online in the storage hierarchy to make them available to client nodes for file storage.

ANR0526W A transaction failed for session session number for node node name (client platform) because of insufficient recovery log space.

Explanation

If a log runs out of space, the current transaction is rolled back. The server issues an error message and halts. You cannot restart the server until the recovery log size is increased.

System action

The server halts.

User response

Monitor archive logs and active logs. If the recovery log space is insufficient, monitor the archive log space first. If the archive log space is full or nearly full, run a full database backup to remove archive logs and consider adding more disk space to the archive log directory. If the archive log space is not full and the active log space is full or nearly full, update the value of the ACTIVELOGSIZE option in the dsmserv.opt file. Set the value of the ACTIVELOGSIZE option to the new maximum size of the active log.

ANR0527W A transaction failed for session session number for node node name (client platform) because of insufficient database space.

Explanation

The server ends a database update transaction for the specified session because the server has insufficient database space.

System action

The server ends the specified session, but server operation continues.

User response

To increase the amount of database space that is available to the server, issue the EXTEND DBSPACE command. Add one or more directories to the database.

ANR0528W Transaction failed for session session number for node node name (client platform) - thread resource not available.

Explanation

The server ends a database update transaction for the specified session because sufficient memory is not available for starting additional processes on the server.

System action

The server ends the specified session and server operation continues.

User response

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

ANR0529W Transaction failed for session session number for node node name (client platform) - insufficient memory.

Explanation

The server ends a database update transaction for the specified session because sufficient memory is not available on the server.

System action

The server ends the specified session and server operation continues.

User response

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

ANR0530W Transaction failed for session session number for node node name (client platform) - internal server error detected.

Explanation

The server ends a database update transaction for the specified session because an internal logic error is detected.

System action

The server ends the specified session and server operation continues.

User response

Examine the server messages that were issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages that indicate the source of the error.

ANR0531W Transaction failed for session session number for node node name (client platform) - invalid file space identifier specified by client.

Explanation

The server ends a database update transaction for the specified session because the file space identified by the client for the transaction does not exist.

System action

This action usually occurs when a client is operating on a file space that is currently being deleted as a result of an administrative command or client action. The server ends the specified session and server operation continues.

User response

Use the QUERY PROCESS command to monitor and wait for any file space deletion processes to complete, or cancel the process if you do not want to delete the file space. Try the client action again after this action has been taken.

ANR0532W Diagnostic(ID): Transaction transaction ID was aborted for session session number for node node name (client platform).

Explanation

An error has been detected during a transaction commit for the specified session. This message should be preceded by other messages that give additional information about the failed transaction.

System action

The activity that generated this error fails.

User response

Check for additional messages and eliminate the condition that caused the failed transaction. If the error cannot be isolated and resolved, contact your service representative.

ANR0533W Transaction failed for session session number - compression method used by client not supported. Please obtain the latest level of the client code.

Explanation

The server ends the transaction for the specified session because the compression method that is used by the client is no longer supported by the server.

System action

The server ends the specified session and server operation continues.

User response

The client must either backup the data with compression turned off, or upgrade to a client that supports the newer compression method. If the client is a WDSF client, upgrade to a non-WDSF client in order to use the compression performed by the client.

ANR0534W Transaction failed for session session number for node node name (client platform) - size estimate exceeded and server is unable to obtain additional space in storage pool pool name. Size estimate was size estimate.

Explanation

The server ends a database update transaction for the specified session because the size estimate provided by the client is too small. The server has attempted to obtain additional space in the indicated storage pool, but was unable to do so.

System action

The specified session is ended and server operation continues.

If pool name is a random access storage pool with caching enabled, it is also possible that additional space can be made available in this storage pool by eliminating cached files. When the server allocates space based on the size estimate provided by the client, it frees space occupied by cached files if this space is needed to obtain the estimated space. However, if the server later determines that the file size estimate was too low, it attempts to obtain additional space that is not utilized, but does not delete cached files to do so.

If the client sending the data has the option COMPRESSALWAYS YES set, it is possible that a file grew during the compression operation and when the client sent it to the server it exceeded the space available in storage pool pool name.

User response

This message may indicate that there is no additional space in pool name. The following are possible circumventions:

An authorized administrator can issue the DEFINE VOLUME command to add storage to this pool.

If the suspected cause of the failure is that pool name is a DISK storage pool and that space in use by cached files was not freed, turn off caching for the storage pool and issue the MOVE DATA command for the volumes in pool pool name.

If the suspected cause of the failure is that a file grew in size during compression on the client, another possible circumvention is to set the COMPRESSALWAYS option in the client options file to NO and retry the operation. This may allow the client to accurately report the file size and possibly avoid the out of space condition in the storage pool.

ANR0535W Transaction failed for session session number for node node name (client platform) - insufficient mount points available to satisfy the request.

Explanation

The server was unable to allocate sufficient mount points to process the transaction.

System action

The operation is ended and server operation continues.

User response

If necessary, make more mount points available or validate your device class and library configuration.

ANR0536W Transaction failed for session session number for node node name (client platform) - down-level client does not support format of stored files.

Explanation

A client attempts to perform an operation involving files that are stored in a format that is not supported by that client level.

System action

The operation is ended and server operation continues.

User response

Upgrade the client to a later level.

ANR0537E Transaction failed for session session number for node node name (client platform) - filespace name cannot be renamed from or to a Unicode name.

Explanation

The server ends a database update transaction for the specified session because a file space was attempted to be renamed to or from unicode.

System action

The server ends the specified transaction and server operation continues.

User response

Do not attempt to rename a unicode file space to a non-unicode name or a non-unicode file space to a unicode name.

ANR0538I A resource waiter has been aborted.

Explanation

The server aborts a resource wait because of waiting too long for a resource to become available. This could cause a process or session to fail. If this causes a process or a session to fail then there will be other messages at this time indicating which process or session has failed. Resources are internal server resources such as locks and synchronization objects.

System action

The server terminates the resource with request and server operation continues.

User response

Either a server deadlock situation has occurred or the resource timeout value is set too low. Check the setting for the RESOURCETimeout server option and increase the value. If the problem persists with a higher timeout then contact your service representative.

ANR0539W Transaction failed for session session number for node node name. This node has exceeded its maximum number of mount points.

Explanation

The server ends the transaction because the node requires mount points to store data, and either the node is not allowed to acquire any mount points, or the node is already using the maximum number of mount points allowed for the node. The maximum number of mount points a node is allowed to use on the server is controlled by the setting of the MAXNUMMP parameter on the REGISTER NODE or UPDATE NODE command.

System action

The server ends the specified session and server operation continues.

User response

If the number of mount points that the node is allowed to use on the server are already acquired, reduce the number of client sessions for the specified node that are running concurrently. For example, decrease the value of the client option RESOURCEUTILIZATION. If sufficient mount points (for example, drives) are available to satisfy the data store operations, issue the UPDATE NODE command to increase the value of the MAXNUMMP parameter.

If the node is not allowed to acquire any mount points (the node's MAXNUMMP option is set to zero), issue the UPDATE NODE command to change the value of the MAXNUMMP parameter.

ANR0540W Retrieve or restore failed for session session number for node node name (client platform) - data integrity error detected.

Explanation

The server ends a file retrieval operation for the specified session because an internal database integrity error has been encountered on the server.

System action

The server ends the specified session and continues operation.

User response

Contact your service representative.

ANR0541W Retrieve or restore failed for session session number for node node name (client platform) - error on input storage device.

Explanation

The server ends a client retrieval or restore operation for the specified session because an I/O error has been encountered by the server in reading from a device.

System action

The server ends the specified session and server operation continues.

User response

Query the activity log to find messages preceding this one that specify the device that is failing. Storage pool volumes can be varied offline (by using the VARY OFFLINE command), or the server may need to be shut down by using the HALT command to correct the hardware problem. After the problem is corrected, the client may try the operation again.

ANR0542W Retrieve or restore failed for session session number for node node name (client platform) - storage media inaccessible.

Explanation

The server ends a client retrieval or restore operation for the specified session because a needed storage pool volume has been varied offline or the storage pool is unavailable.

System action

The server ends the specified session and server operation continues.

User response

Use the VARY ONLINE command to vary offline storage volumes online in the storage hierarchy and make them available to client nodes for file storage. If all volumes are online, check the ACCESS parameter of the storage pool. If the access mode is UNAVAILABLE, use the UPDATE STGPOOL command to update it to READONLY or READWRITE.

ANR0543W Retrieve or restore failed for session session number for node node name (client platform) - data transfer interrupted.

Explanation

The database transaction associated with session session number was aborted because data transfer to or from data storage was interrupted by an external event.

System action

The session is canceled and server operation continues.

User response

Examine the messages issued prior to this message to determine why the data transfer was interrupted. Attempt the client operation again, if the problem can be resolved.

ANR0544W Retrieve or restore failed for session session number for node node name (client platform) - thread resource not available.

Explanation

The server ends a file retrieval or restore operation for the specified session because sufficient memory is not available for starting additional processes on the server.

System action

The server ends the specified session and server operation continues.

User response

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

ANR0545W Retrieve or restore failed for session session number for node node name (client platform) - insufficient memory.

Explanation

The server ends a file retrieval or restore operation for the specified session because sufficient memory is not available on the server.

System action

The server ends the specified session and server operation continues.

User response

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

ANR0546W Retrieve or restore failed for session session number for node node name (client platform) - internal server error detected.

Explanation

The server ends a file retrieval or restore operation for the specified session because an internal logic error is detected in the server program.

System action

The server ends the specified session and continues operation.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0547E Invalid data was encountered in the command processor output stream: output formatting terminated for the last command entered.

Explanation

The server console session encounters an error in formatting output from a command.

System action

The command output is discarded and server operation continues.

User response

Use the server QUERY command to determine if the command you entered had the desired affect in the server. Use the QUERY ACTLOG command to see if a server error condition (like out of memory) occurred prior to the command. Resolve the error if it is found. Contact your service representative if you cannot resolve the error, or if an error is not found.

ANR0548W Retrieve or restore failed for session session number for node node name (client platform) processing file space filespace (fsId filespace id) for file file name stored as storage repository - error detected.

Explanation

The server ends a file retrieval operation for the specified session because an error has been encountered on the server. Some common reasons for the error are:
  • The input volume is unavailable
  • The storage pool is unavailable
  • Data is corrupted on the input volume
  • Hardware or media failure has occurred
  • Database corruption

System action

The server ends the specified session and continues operation.

User response

Try the restore or retrieve operation again, and if the file is also backed up in a copy storage pool, the operation will attempt to read the file from the alternate location. If retry of the restore or retrieve operation continues to fail examine any prior error messages to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages if needed. Correct the problem and try the restore or retrieve again.

ANR0549W Transaction failed for session session number for node node name (client platform) - no existing restore session found.

Explanation

A client attempted to start an additional no query restore session to increase restore throughput, but the original restore session was not found.

System action

The operation is ended and server operation continues.

User response

Check the status of the original restore. It may have already completed or been cancelled. The QUERY SESSION command and the QUERY RESTORE commands can provide information about existing sessions and restore sessions which are restartable.

ANR0550E The client operation failed for session session number for node node name (client platform) - see previous error messages.

Explanation

The indicated operation has failed. This message is always preceded by one or more other error messages which provide more detail about why the command failed.

System action

The operation is ended and server operation continues.

User response

Examine the previous error messages to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages if needed. Correct the problem and try the command again.

ANR0551E The client operation failed for session session number for node node name on the (client platform) operating system because of a lock conflict.

Explanation

An operation that requires the server to lock a system resource has been initiated. The operation cannot be completed because the resource is in use by another command or process.

System action

Server operations continue, but the server does not process the command.

User response

To resolve the issue, take one of the following actions: - If the failed command was run in a local area network (LAN) environment, run the command again later. - If the failed command was run in a LAN-free environment, run the VALIDATE LANFREE command and review the output: If the LAN-Free capable column displays a value of YES, retry the failed command. If the LAN-Free capable column displays a value of NO, correct the configuration to support LAN-free data movement for the storage agent and retry the failed command. Alternatively, retry the failed command in a LAN environment.

ANR0552E Client operation failed for session session number for node node name (client platform) - destination storage pool storage pool was skipped.

Explanation

The indicated client operation failed because the destination storage pool was skipped. A storage pool may be skipped because it does not have enough available space, or because it has a MAXSIZE value that is less than the size of the object to be inserted.

System action

The operation fails.

User response

Ensure that the destination storage pool is available, has an adequate MAXSIZE setting, and has adequate space. The MAXSIZE setting may be changed using the UPDATE STGPOOL command. Space may be added to the storage pool by checking in scratch volumes or defining new volumes in the storage pool. If volumes in the destination storage pool are offline, use the VARY ONLINE command to vary them online and make them available for use. Correct the problem and try the command again.

ANR0553E Client operation failed for session session number - administrator administrator name does not have adequate authority over node node name.

Explanation

The specified administrator does not have the proper authority necessary to perform this operation on the specified node.

System action

The server does not perform the query.

User response

Issue the command from a properly authorized administrator ID, or contact the system administrator to have additional authority granted to the current administrator ID.

ANR0554E command name: The parameter name parameter is only valid if the TOSERVER parameter is specified.

Explanation

The command failed because the TOSERVER parameter was not specified.

System action

The command fails and server operation continues.

User response

Reissue the command and specify the TOSERVER parameter.

ANR0555E command name: The parameter name parameter cannot be specified when the TOSERVER parameter is specified.

Explanation

The command failed because the TOSERVER parameter was not specified.

System action

The command fails and server operation continues.

User response

Reissue the command and omit the TOSERVER parameter.

ANR0556E command name: DATES=RELATIVE parameter value cannot be specified when merging imported files using the MERGE=YES parameter value.

Explanation

When importing files and merging them into existing file spaces, the DATES=RELATIVE parameter value cannot be specified.

System action

The command fails and server operation continues.

User response

Reissue the command and omit the DATES=RELATIVE parameter.

ANR0557I Import command: An invalid export record (version version, copy type copy type, object type object type) was found.

Explanation

An invalid import record was found for the specified version, copy type and object type. The object will be skipped, and import processing will continue.

System action

Server operation continues.

User response

Issue QUERY ACTLOG to determine the source of the error.

ANR0558W Import processing did not create a proxynode association for nodes node_id_target and node_id_agent.

Explanation

Import processing did not create a proxynode association between the two nodes. The association fails if either of the nodes does not exist on the server, or if import processing was not allowed to complete.

System action

The server does not create the specified proxynode association.

User response

Verify that both nodes were imported properly and issue the import command again. Or, use the GRANT PROXYNODE command to manually create the proxynode association.

ANR0559E Too many domains are specified on the EXPORT NODE command.

Explanation

The maximum length of the domain list cannot exceed approximately 1400 characters.

System action

The EXPORT command is ended.

User response

If you specified DOMAIN=* on the command, issue the command again without specifying the domain to let it default to all domains. If you specified a domain list, then split up the EXPORT into multiple export commands to reduce the number of domains specified on the command.

ANR0560E Import command: Unable to decrypt encrypted password or key.

Explanation

The server is not able to decrypt the password associated with a node or administrator, or the client encryption key associated with an object being imported. The password or key was encrypted with the AES encryption standard, but the server does not support AES.

System action

The object is not imported.

User response

Rerun the export command, specifying the ENCryptionstrength=DES option. Or, rerun the import on a server that supports AES.

ANR0561E Export command: Process aborted - sign on to server, target server name, failed.

Explanation

The server export process encountered an error in establishing a communication session with the target server.

System action

The export process ends and server operation continues.

User response

Check the activity log and server console for messages that indicate a failure or problem on the server issuing this command and on the target server. Next, check the server definition, administrator name, and password on both the server issuing the command and the server specified. Also, check the communication connection between the two servers. And finally, verify that the target server specified is running. If the problem is not resolved, contact your service representative.

ANR0562I Export command: Data transfer complete, deleting temporary data.

Explanation

The server export process has completed writing data to the target media or server. Temporary data used during the operation is now being deleted from the database.

System action

The export process continues until all temporary data is removed.

User response

None.

ANR0563W NDMP restore failed for node node name, file space filespace.

Explanation

The server ends a restore operation for the specified NAS node because an error has been encountered on the server. Some common reasons for the error are:
  • The input volume is unavailable
  • The storage pool is unavailable
  • Data is corrupted on the input volume
  • Hardware or media failure has occurred
  • The server database is corrupted

System action

The server ends the restore operation.

User response

Examine any prior error messages to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages if needed. Correct any problem and try the restore again. If the data is also backed up in a copy storage pool, the retry operation will attempt to read the file from the alternate location. If retry of the restore operation continues to fail contact your service representative.

ANR0564E Restartable restore request failed for session session number, restartable restore session restore session number - sessions are active from the original restore.

Explanation

A client attempted to restart a restartable no query restore session; However, sessions from the original no query restore invocation are still active. Both the current and restartable restore session numbers are shown.

System action

The restartable restore request is ended and server operation continues. The restore's restartability status does not change.

User response

Check the status of the original restore. The QUERY RESTORE command can be used to show the status of restartable restores. The restartable restore session number is the one for which sessions were found to be running. Sessions may be active on either the server or a storage agent. Restartable restores may be cancelled by issuing the CANCEL RESTORE command, after which the restore may be retried. Once CANCEL RESTORE is issued for a restore session, it is not eligible to be restarted.

ANR0565W Retrieve or restore failed for session session number for node node name (client platform). The storage volume volume name is inaccessible.

Explanation

The server ends a client retrieval or restore operation for the specified session because a needed storage pool volume has been varied offline.

System action

The server ends the specified session and server operation continues.

User response

Use the VARY ONLINE command to vary offline storage volumes online, and make them available to client nodes for file storage.

ANR0566W Retrieve or restore failed for session session number for node node name (client platform) - file was deleted from data storage during retrieval.

Explanation

The server ends a file retrieval operation for the specified session because the file has been deleted from data storage by another process before retrieval is complete.

System action

The server ends the specified session and continues operation.

User response

Contact your administrator to find out if DELETE FILESPACE, DELETE VOLUME, or inventory expiration processes are running; these processes can delete data storage files during retrieval. Reissue the restore or retrieve operation and specify a different file version.

ANR0567W Retrieve or restored failed for session session number for node node name (client platform) - insufficient mount points available to satisfy the request.

Explanation

The server was unable to allocate sufficient mount points to process the retrieve or restore operation.

System action

The operation is ended and server operation continues.

User response

If necessary, make more mount points available.

ANR0568W Session session number for admin admin name (client platform) terminated - connection with client severed.

Explanation

The specified admin session is ended because the communications link has been closed by a network error or by the client program.

System action

Server operation continues.

User response

If a user breaks out of a client program, this message will be displayed on the server as the connection is suddenly closed by the client. A network failure can also cause this message to be displayed. If a large number of these messages occur simultaneously, check the network for failure and correct any problems.

ANR0569I Object not processed for node name: type=type, file space=filespace name, object=object name.

Explanation

An error occurred. The object for node name, identified by type, file space and object name was not processed.

System action

Server action is defined by the error that occurred.

User response

Issue QUERY ACTLOG to determine the source of the error.

ANR0570E Export command: Invalid value for DURUNITS parameter detected while exporting administrative schedule schedule name - default or existing value is used during import.

Explanation

During processing of command export command, an invalid value is encountered for the DURUNITS parameter for administrative schedule schedule name.

System action

Export processing continues, but the exported data contains an unknown DURUNITS value for this schedule. If this data is imported, the server uses the default or existing DURUNITS value.

User response

Update the DURUNITS value for this schedule and restart the export command. Alternatively, the export data with the unknown value can be used, and the DURUNITS value can be checked and updated after import processing has been performed.

ANR0571E Export command: Invalid value for PERUNITS parameter detected while exporting administrative schedule schedule name - default or existing value is used during import.

Explanation

During processing of command export command, an invalid value is encountered for the PERUNITS parameter for administrative schedule schedule name.

System action

Export processing continues, but the exported data will contain an unknown PERUNITS value for this schedule. If this data is imported, the server uses the default or existing PERUNITS value.

User response

Update the PERUNITS value for this schedule and restart the export command. Alternatively, use the export data with the unknown value, and check and update the PERUNITS value after import processing has been performed.

ANR0572E Export command: Invalid value for DAYOFWEEK parameter detected while exporting administrative schedule schedule name - default or existing value is used during import.

Explanation

During processing of command export command, an invalid value is encountered for the DAYOFWEEK parameter for administrative schedule schedule name.

System action

Export processing continues, but the exported data contains an unknown DAYOFWEEK value for this schedule. If this data is imported, the server uses the default or existing DAYOFWEEK value.

User response

Update the DAYOFWEEK value for this schedule and restart the export command. Alternatively, use the export data with the unknown value, and check and update the DAYOFWEEK value after import processing has been performed.

ANR0573I Export/import command: Processing administrative schedule schedule name.

Explanation

The background export or import process to service the command export/import command is currently processing the schedule definition information for administrative schedule schedule name.

System action

Export or import processing for the command continues.

User response

None.

ANR0574E Import command: Invalid value for DURUNITS or PERUNITS parameter in exported data for administrative schedule schedule name.

Explanation

During preview processing of command import command, an invalid value is encountered for the DURUNITS or PERUNITS parameter for administrative schedule schedule name.

System action

Processing of the command continues. If a later command is issued that causes the data to be imported, the default or existing values are used for DURATION, DURUNITS, PERIOD, and PERUNITS.

User response

If the data is imported with a later command, verify that the correct values for DURATION, DURUNITS, PERIOD, and PERUNITS are used for this schedule.

ANR0575E Import command: Invalid value for DAYOFWEEK parameter in exported data for administrative schedule schedule name.

Explanation

During preview processing of command import command, an invalid value is encountered for the DAYOFWEEK parameter for administrative schedule schedule name.

System action

Processing of the command continues. If a later command is issued that causes the data to be imported, the default or existing DAYOFWEEK value is used.

User response

If the data is imported with a later command, verify that the correct DAYOFWEEK value is used for this schedule.

ANR0576E Import command: Invalid value for DURUNITS or PERUNITS parameter in exported data - administrative schedule schedule name defined with default values for DURATION, DURUNITS, PERIOD, and PERUNITS.

Explanation

During processing of command import command, an invalid value is encountered for the DURUNITS or PERUNITS parameter for administrative schedule schedule name.

System action

Processing of the command continues, by using the default values for DURATION, DURUNITS, PERIOD, and PERUNITS.

User response

Verify that the correct values have been used for DURATION, DURUNITS, PERIOD, and PERUNITS. Update these values, if necessary.

ANR0577E Import command: Invalid value for DAYOFWEEK parameter in exported data - administrative schedule schedule name defined with default DAYOFWEEK value.

Explanation

During processing of command import command, an invalid value is encountered for the DAYOFWEEK parameter for administrative schedule schedule name.

System action

Processing of the command continues, by using the default DAYOFWEEK value for this schedule.

User response

Verify that the correct DAYOFWEEK value has been used for this schedule. Update this value, if necessary.

ANR0578E Import command: Invalid value for DURUNITS or PERUNITS parameter in exported data - existing values for DURATION, DURUNITS PERIOD, and PERUNITS for administrative schedule schedule name were not updated.

Explanation

During processing of command import command, an invalid value is encountered for the DURUNITS or PERUNITS parameter for administrative schedule schedule name.

System action

Processing of the command continues, by using the existing values for DURATION, DURUNITS, PERIOD, and PERUNITS.

User response

Verify that the correct values have been used for DURATION, DURUNITS, PERIOD, and PERUNITS. Update these values, if necessary.

ANR0579E Import command: Invalid value for DAYOFWEEK parameter in exported data - existing DAYOFWEEK value for administrative schedule schedule name was not updated.

Explanation

During processing of command import command, an invalid value is encountered for the DAYOFWEEK parameter for administrative schedule schedule name.

System action

Processing of the command continues, by using the existing DAYOFWEEK value for this schedule.

User response

Verify that the correct DAYOFWEEK value has been used for this schedule. Update this value, if necessary.

ANR0580E Export command: Invalid value for SPACEMGTECHNIQUE parameter detected while exporting management class management class name in domain domain name, set policy set name - default or existing value is used during import.

Explanation

During processing of command export command, an invalid value is encountered for the SPACEMGTECHNIQUE parameter for management class management class name in domain domain name, policy set policy set name.

System action

Export processing continues, but the exported data contains an unknown SPACEMGTECHNIQUE value for this management class. If this data is imported, the default or existing SPACEMGTECHNIQUE value is used.

User response

Update the SPACEMGTECHNIQUE value for this copy group and restart the export. Alternatively, use the export data with the unknown value, and check and update the SPACEMGTECHNIQUE value after import processing has been performed.

ANR0581E Export command: Invalid value for MIGREQUIRESBKUP parameter detected while exporting management class management class name in domain domain name, set policy set name - default or existing value is used during import.

Explanation

During processing of command export command, an invalid value is encountered for the MIGREQUIRESBKUP parameter for management class management class name in domain domain name, policy set policy set name.

System action

Export processing continues, but the exported data contains an unknown value for this management class. If this data is imported, the default or existing MIGREQUIRESBKUP value is used.

User response

Update the MIGREQUIRESBKUP value for this copy group and restart the export. Alternatively, use the export data with the unknown value, and check and update the MIGREQUIRESBKUP value after import processing has been performed.

ANR0582E Import command: Invalid value for SPACEMGTECHNIQUE parameter in exported data for management class management class name in domain domain name, set policy set name.

Explanation

During preview processing of command import command, an invalid value is encountered for the SPACEMGTECHNIQUE parameter for management class management class name, in policy domain domain name, policy set policy set name.

System action

Processing of the command continues. If a later command is issued that causes the data to be imported, the default or existing SPACEMGTECHNIQUE value is used.

User response

None. If the data is imported with a later command, verify that the correct SPACEMGTECHNIQUE value is used for this management class.

ANR0583E Import command: Invalid value for SPACEMGTECHNIQUE parameter in exported data - management class management class name in domain domain name, set policy set name defined with default SPACEMGTECHNIQUE value.

Explanation

During processing of command import command, an invalid value is encountered for the SPACEMGTECHNIQUE parameter for management class management class name, in policy domain domain name, policy set policy set name.

System action

Processing of the command continues, by using the default SPACEMGTECHNIQUE value for this management class.

User response

Verify that the correct SPACEMGTECHNIQUE value has been used for this management class. Update this value, if necessary.

ANR0584E Import command: Invalid value for SPACEMGTECHNIQUE parameter in exported data - SPACEMGTECHNIQUE value for management class management class name in domain domain name, set policy set name was not updated.

Explanation

During processing of command import command, an invalid value is encountered for the SPACEMGTECHNIQUE parameter for management class management class name, in policy domain domain name, policy set policy set name.

System action

Processing of the command continues, by using the existing SPACEMGTECHNIQUE value for this management class.

User response

Verify that the correct SPACEMGTECHNIQUE value has been used for this management class. Update this value, if necessary.

ANR0585E Import command: Invalid value for MIGREQUIRESBKUP parameter in exported data for management class management class name in domain domain name, set policy set name.

Explanation

During preview processing of command import command, an invalid value is encountered for the MIGREQUIRESBKUP parameter for management class management class name, in policy domain domain name, policy set policy set name.

System action

Processing of the command continues. If a later command causes the data to be imported, the default or existing MIGREQUIRESBKUP value is used.

User response

None. If the data is imported with a later command, verify that the correct MIGREQUIRESBKUP value is used for this management class.

ANR0586E Import command: Invalid value for MIGREQUIRESBKUP parameter in exported data - management class management class name in domain domain name, set policy set name defined with default MIGREQUIRESBKUP value.

Explanation

During processing of command import command, an invalid value is encountered for the MIGREQUIRESBKUP parameter for management class management class name, in policy domain domain name, policy set policy set name.

System action

Processing of the command continues, by using the default MIGREQUIRESBKUP value for this management class.

User response

Verify that the correct MIGREQUIRESBKUP value has been used for this management class. Update this value, if necessary.

ANR0587E Import command: Invalid value for MIGREQUIRESBKUP parameter in exported data - MIGREQUIRESBKUP value for management class management class name in domain domain name, set policy set name was not updated.

Explanation

During processing of command import command, an invalid value is encountered for the MIGREQUIRESBKUP parameter.

System action

Processing of the command continues, by using the existing MIGREQUIRESBKUP value for this management class.

User response

Verify that the correct MIGREQUIRESBKUP parameter has been used for this management class. Update this value, if necessary.

ANR0588E Import command: Server is down-level compared to export data version version number.

Explanation

An attempt is made to import data to a down-level server. The server on which the import is performed must be at the same or later level than the server from which the data was exported.

System action

The import process ends and server operation continues.

User response

Import to a server that is at the same or later level than the server from which the export was performed.

ANR0589E Import command: Preview processing terminated abnormally - server is down-level.

Explanation

Processing for the command import command in preview mode ends when it is determined that the server is down-level compared to the export data.

System action

Import processing ends and server operation continues.

User response

Import to a server that is at the same or later level than the server from which the export was performed.

ANR0590E Import command: Processing terminated abnormally - server is down-level.

Explanation

Processing for the command import command ends when it is determined that the server is down-level compared to the export data.

System action

Import processing ends and server operation continues.

User response

Import to a server that is at the same or later level than the server from which the export was performed.

ANR0592E Export/import command: Invalid value for table of contents parameter - parameter value.

Explanation

The value (parameter value) specified for the table of contents (TOC) parameter in command export/import command is not a valid value for this parameter.

System action

The command fails and server operation continues.

User response

Reissue the command and specify a valid TOC parameter.

ANR0593E Export/import command: Invalid value for NOSPAN parameter - parameter value.

Explanation

The value (parameter value) specified for the NOSPAN parameter in command export/import command is not a valid value for this parameter.

System action

The command fails and server operation continues.

User response

Reissue the command and specify a valid NOSPAN parameter.

ANR0594E device class: NOSPAN parameter can only be used with a 3590 device class.

Explanation

The device class specified must be a 3590 device class when NOSPAN is set to True.

System action

The command fails and server operation continues.

User response

Reissue the command and specify a valid NOSPAN/Device Class parameter.

ANR0595W The server deleted object count objects that were part of incomplete groups.

Explanation

After importing data that was exported from another server, the server deletes any objects that are part of incomplete groups. Incomplete groups may be a result of importing from media written by an export operation that failed. Incomplete groups may also be a result of a failed import operation.

System action

Server operation continues.

User response

Ensure that the export and import operations run to completion. If any errors are observed, correct them and run again the export or import or both, as needed.

ANR0596W Space-managed object object name for client node node name, filespace filespace name already exists on the server - it will be skipped.

Explanation

While attempting to import a spaced-managed object, the server discovers that the object already exists. The space-managed object is skipped.

System action

Server operation continues.

User response

None.

ANR0597W IMPORT: Space management attributes in management class management class name for domain domain name is not defined - default management class will be used.

Explanation

During import processing, the server finds that the space management attributes for a space-managed file being imported does not exist in the active policy set for the domain to which the node is assigned.

System action

The default management class for the node's policy domain is bound to the space-managed file and import processing continues.

User response

If you want to define the missing management class, an authorized administrator may cancel the import operation, define the missing space management attributes or management class for the domain, and process the import operation again.

ANR0598W IMPORT: Space management attributes not found for default management class in domain domain name - space managed files bound to management class management class name in this domain cannot be imported.

Explanation

During import processing, the server finds that a management class bound to a space-managed file being imported does not exist in the active policy set for the domain to which the node is assigned. When trying to rebind the space-managed file to the default management class for the domain, the server finds that the space-managed attributes are not defined for the default management class.

System action

The file is not imported; import processing continues.

User response

If you want to define the missing copy group, an authorized administrator may cancel the import operation, define the missing space management attributes or management class for the domain, and process the import operation again.

ANR0599E Export/import command: Invalid volume name volume name specified for device class device class name.

Explanation

One of the volume names specified in the VOLUMENAMES parameter for an import or export command is not a valid volume name for the device class specified in the DEVCLASS parameter.

System action

The export or import command fails.

User response

Specify volume names in the VOLUMENAMES parameter that are valid for the device class specified in the DEVCLASS parameter.

ANR0600I Export command: No matching policy domains found for exporting.

Explanation

The background export process does not find any policy domains that match the specification entered in the export command.

System action

The export process continues and no policy domains are exported from the server.

User response

None.

ANR0601I Export command: No policy sets found in policy domain domain name for exporting.

Explanation

The background export process does not find any policy sets defined in domains matching domain name.

System action

The export process continues and no policy sets are exported from the domain.

User response

None.

ANR0602I Export command: No management classes were found in policy domain domain name for exporting.

Explanation

The background export process does not find any management classes defined in policy domains matching domain name.

System action

The export process continues and no management classes are exported from the domain.

User response

None.

ANR0603I Export command: No copy groups were found in policy domain domain name for exporting.

Explanation

The background export process does not find any copy groups defined in policy domains matching domain name.

System action

The export process continues and no copy groups are exported from the domain.

User response

None.

ANR0604I Export command: No schedules were found in policy domain domain name for exporting.

Explanation

The background export process does not find any schedules defined for policy domains matching domain name.

System action

The export process continues and no schedules are exported for the domain.

User response

None.

ANR0605I Export command: No schedule associations were found in policy domain domain name for exporting.

Explanation

The background export process does not find any schedule node associations defined for policy domains matching domain name.

System action

The export process continues and no schedule associations are exported for the domain.

User response

None.

ANR0606I Export command: No node definitions were found for exporting.

Explanation

The background export process does not find any node definitions to export as specified in the command export command.

System action

The export process continues.

User response

None.

ANR0607I Export command: No administrator definitions were found for exporting.

Explanation

The background export process does not find any administrator definitions to export as specified in the command export command.

System action

The export process continues.

User response

None.

ANR0608E Command: Command failed - see previous error messages or view the activity log.

Explanation

The indicated import command has failed. This message is always preceded by one or more other error messages which provide more detail about why the command failed.

System action

The operation fails.

User response

Examine the previous error messages to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages if needed. Correct the problem and try the command again.

ANR0609I Command started as process process ID.

Explanation

A background process has been started to service the command command. The background process is defined as process process ID.

System action

Server operation continues.

User response

To query the progress of the background process, use the QUERY PROCESS command. To cancel the background process, use the CANCEL PROCESS command. Use the process ID number to specify this specific process.

ANR0610I Command started by administrator name as process process ID.

Explanation

A background process has started to service the command command entered by administrator administrator name. The background process is defined as process process ID.

System action

Server operation continues.

User response

To query the progress of the background process, use the QUERY PROCESS command. To cancel the background process, use the CANCEL PROCESS command. Use the process ID number to specify this specific process.

ANR0611I Command started by administrator name as process process ID has ended.

Explanation

The background process to service the command command by administrator administrator name has completed processing.

System action

The specified process ends, and server operation continues.

User response

None.

ANR0612I Import command: Reading EXPORT SERVER data from server server name exported export date export time.

Explanation

The background import process to service the command import command is importing information exported from server server name with the EXPORT SERVER command on export date at export time.

System action

Import processing continues.

User response

None.

ANR0613I Import command: Reading EXPORT POLICY data from server server name exported export date export time.

Explanation

The background import process to service the command import command is importing information exported from server server name with the EXPORT POLICY command on export date at export time.

System action

Import processing continues.

User response

None.

ANR0614I Import command: Reading EXPORT ADMIN data from server server name exported export date export time.

Explanation

The background import process to service the command import command is importing information exported from server server name with the EXPORT ADMIN command on export date at export time.

System action

Import processing continues.

User response

None.

ANR0615I Import command: Reading EXPORT NODE data from server server name exported export date export time.

Explanation

The background import process to service the command import command is importing information exported from server server name with the EXPORT NODE command on export date at export time.

System action

Import processing continues.

User response

None.

ANR0616I Export/import command: Preview processing completed successfully.

Explanation

The background export or import process to service the command export/import command in preview (Preview=Yes) mode has completed successfully.

System action

Export or import processing for the command completes. Statistics on the projected number and type of objects moved, together with the projected total number of bytes copied, are displayed on the server console following this message.

User response

None.

ANR0617I Export/import command: Processing completed with status status.

Explanation

The background export or import process to service the command export/import command has completed with status status. If the status is INCOMPLETE, some files have been skipped due to errors reading or writing the file.

System action

Export or import processing for the command completes. Statistics on the number and type of objects moved, together with the total number of bytes copied, are displayed on the server console following this message. A summary of the number of files that were skipped is also displayed.

User response

None.

ANR0618I Export/import command: Preview processing canceled before completion.

Explanation

The background export or import process to service the command export/import command in preview (Preview=Yes) mode has been canceled with the CANCEL PROCESS command.

System action

Export or import processing for the command ends. Statistics on the projected number and type of objects moved, together with the projected total number of bytes copied, are displayed on the server console following this message.

User response

None.

ANR0619I Command: Processing canceled before completion.

Explanation

The background process to service the command command has been canceled with the CANCEL PROCESS command.

System action

Processing for the command command ends. Statistics on the number and type of objects moved, together with the total number of bytes copied, are displayed on the server console following this message.

User response

None.

ANR0620I Export/import command: Copied number domain(s).

Explanation

The background export or import process to service the command export/import command copies number policy domain definitions from the server database to export media or from export media into the server database. Data is not actually moved if Preview=Yes is specified in the command export/import command.

System action

Export or import processing for the command completes. Server operation continues.

User response

None.

ANR0621I Export/import command: Copied number policy sets.

Explanation

The background export or import process to service the command export/import command copies number policy set definitions from the server database to export media or from export media into the server database. Data is not actually moved if Preview=Yes is specified in the command export/import command.

System action

Export or import processing for the command completes. Server operation continues.

User response

None.

ANR0622I Export/import command: Copied number management classes.

Explanation

The background export or import process to service the command export/import command copies number management class definitions from the server database to export media or from export media into the server database. Data is not moved if Preview=Yes is specified in the command export/import command.

System action

Export or import processing for the command completes. Server operation continues.

User response

None.

ANR0623I Export/import command: Copied number copy groups.

Explanation

The background export or import process to service the command export/import command copies number copy group definitions from either the server database to export media or from export media into the server database. Data is not moved if Preview=Yes is specified in the command export/import command.

System action

Export or import processing for the command completes. Server operation continues.

User response

None.

ANR0624I Export/import command: Copied number schedules.

Explanation

The background export or import process to service the command export/import command copies number schedule definitions from either the server database to export media or from export media into the server database. Data is not moved if Preview=Yes is specified in the command export/import command.

System action

Export or import processing for the command completes. Server operation continues.

User response

None.

ANR0625I Export/import command: Copied number administrators.

Explanation

The background export or import process to service the command export/import command copies number administrator definitions from either the server database to export media or from export media into the server database. Data is not moved if Preview=Yes is specified in the command export/import command.

System action

Export or import processing for the command completes. Server operation continues.

User response

None.

ANR0626I Export/import command: Copied number node definitions.

Explanation

The background export or import process to service the command export/import command copies number client node definitions from the server database to export media or from export media into the server database. Data is not moved if Preview=Yes is specified in the command export/import command.

System action

Export or import processing for the command completes. Server operation continues.

User response

None.

ANR0627I Export/import command: Copied filespace number file spaces archive number archive files, backup number backup files, and spacemg number space managed files.

Explanation

The background export or import process to service the command export/import command copies filespace number client file space definitions, archive number archive file copies, backup number backup file copies, and spacemg number space-managed files from either the server database to export media or from import media into the server database. Data is not actually moved if Preview=Yes is specified in the command export/import command.

System action

Export or import processing for the command completes. Server operation continues.

User response

None.

ANR0629I Export/import command: Copied number bytes of data.

Explanation

The background export or import process to service the command export/import command copies number bytes of data from the server database and data storage to the export media or from the export media to the server database and data storage. Data is not moved if Preview=Yes is specified in the command export/import command. This figure can be used during export preview processing to estimate the number of removable media volumes needed to hold the exported information from the server.

System action

Export or import processing for the command completes. Server operation continues.

User response

None.

ANR0630I Export/import command: Copied number kilobytes of data.

Explanation

The background export or import process to service the command export/import command copies number kilobytes of data from the server database and data storage to the export media or from the export media to the server database and data storage. This figure can be used during export preview processing to estimate the number of removable media volumes needed to hold the exported information from the server.

System action

Export or import processing for the command completes. Server operation continues.

User response

None.

ANR0631I Export/import command: Copied number megabytes of data.

Explanation

The background export or import process to service the command export/import command copies number megabytes of data from the server database and data storage to the export media or from the export media to the server database and data storage. This figure can be used during export preview processing to estimate the number of removable media volumes needed to hold the exported information from the server.

System action

Export or import processing for the command completes. Server operation continues.

User response

None.

ANR0632I Export/import command: Copied number gigabytes of data.

Explanation

The background export or import process to service the command export/import command copies number gigabytes of data from the server database and data storage to the export media or from the export media to the server database and data storage. This figure can be used during export preview processing to estimate the number of removable media volumes needed to hold the exported information from the server.

System action

Export or import processing for the command completes. Server operation continues.

User response

None.

ANR0633I Export/import command: Copied number terabytes of data.

Explanation

The background export or import process to service the command export/import command copies number terabytes of data from the server database and data storage to the export media or from the export media to the server database and data storage. This figure can be used during export preview processing to estimate the number of removable media volumes needed to hold the exported information from the server.

System action

Export or import processing for the command completes. Server operation continues.

User response

None.

ANR0634I Export/import command: Detected number errors.

Explanation

The background export or import process to service the command export/import command detects number errors while copying information from the server database and data storage to the export media or from the export media to the server database and data storage.

System action

Export or import processing for the command completes. Server operation continues.

User response

Examine the server messages issued prior to this message to view the error. Use the QUERY ACTLOG command to view the activity log and search for messages.

ANR0635I Export/import command: Processing node node name in domain domain name.

Explanation

The background export or import process to service the command export/import command is currently processing the client node definition information for node node name. The node will be imported to domain domain name.

System action

Export or import processing for the command continues.

User response

None.

ANR0636I Import command: Processing file space filespace name for node node name as file space new filespace name.

Explanation

The background import process to service the command import command is currently processing the client file space definition information for file space filespace name belonging to client node node name. The file space is imported under the name new filespace name. During import processing, file spaces defined for clients are not replaced, and file copy information in the file spaces are imported to new file space names so that client file copies are not mixed with existing definitions. Import processing can then create file spaces with names generated by the import processor for client nodes that existed prior to the import operation.

System action

Import processing for the command continues.

User response

None; however, clients may want to examine the contents of the file space with the name new filespace name so that they know where certain file copies are kept.

ANR0637I Export/import command: Processing file space filespace name for node node name fsId filespace id.

Explanation

The background export or import process to service the command export/import command is currently processing client node file space information for file space filespace name belonging to client node node name.

System action

Export or import processing for the command continues.

User response

None.

ANR0638I Export/import command: Processing administrator administrator name.

Explanation

The background export or import process to service the command export/import command is currently processing the administrator definition information for administrator administrator name.

System action

Export or import processing for the command continues.

User response

None.

ANR0639I Export/import command: Processing domain domain name.

Explanation

The background export or import process to service the command export/import command is currently processing the policy domain definition information for domain domain name.

System action

Export or import processing for the command continues.

User response

None.

ANR0640I Export/import command: Processing policy set set name in policy domain domain name.

Explanation

The background export or import process to service the command export/import command is currently processing the policy set definition information for policy set set name belonging to policy domain domain name.

System action

Export or import processing for the command continues.

User response

None.

ANR0641I Export/import command: Processing management class class name in domain domain name, set set name.

Explanation

The background export or import process to service the command export/import command is currently processing the management class definition information for management class class name belonging to policy set set name in policy domain domain name.

System action

Export or import processing for the command continues.

User response

None.

ANR0642I Export/import command: Processing backup copy group in domain domain name, set set name, management class class name.

Explanation

The background export or import process to service the command export/import command is currently processing the backup copy group definition information for management class class name belonging to policy set set name in policy domain domain name.

System action

Export or import processing for the command continues.

User response

None.

ANR0643I Export/import command: Processing archive copy group in domain domain name, set set name, management class class name.

Explanation

The background export process to service the command export/import command is currently processing the archive copy group definition information for management class class name belonging to policy set set name in policy domain domain name.

System action

Export processing for the command continues.

User response

None.

ANR0644I Export command: Processing copy group of unknown type in domain domain name, set set name, management class class name.

Explanation

The background export or import process to service the command export command is currently processing copy group definition information for management class class name belonging to policy set set name in policy domain domain name. The type of copy group being processed is unknown.

System action

Export or import processing for the command continues. The import or export process assumes that the copy group is a backup copy group.

User response

After policy definitions are imported, use the QUERY MGMTCLASS and QUERY COPYGROUP commands to query the server definitions for management class class name to ensure that the copy groups defined have the desired attributes and types. Alternatively, the copy group can be deleted and defined with the correct type, and then the export command can be issued again.

ANR0645I Export/import command: Processing schedule schedule name in domain domain name.

Explanation

The background export or import process to service the command export/import command is currently processing the schedule definition information for schedule schedule name belonging to policy domain domain name.

System action

Export or import processing for the command continues.

User response

None.

ANR0646I Export/import command: message

Explanation

The background export or import process to service the command export/import command has received the message message from the server.

System action

Export or import processing for the command continues, but errors may have been encountered.

User response

Examine the documentation for the message message and resolve the problem reported.

ANR0647I Cancel in progress

Explanation

The export or import operation has been canceled and will end when resources have been freed for the background process. This message may be displayed in response to a QUERY PROCESS command for an export or import operation.

System action

Server operation continues.

User response

None.

ANR0648I Have copied the following:

Explanation

The export or import operation has copied the number and types of objects displayed. This message may be displayed in response to a QUERY PROCESS command for an export or import operation.

System action

Server operation continues.

User response

None.

ANR0649I Import command: Domain domain name does not exist - the system will attempt to import node node name to domain STANDARD.

Explanation

The background import process to service the command import command is currently processing client node node name. This node was assigned to domain domain name at the time of export. However, domain domain name does not exist on the server to which the import is being performed.

System action

Import processing continues, but node node name will be assigned to domain STANDARD during import unless one of the following conditions exist:
  • Preview=Yes
  • Node node name is already registered and Replacedefs=No
  • Domain STANDARD does not exist

User response

If Preview=Yes, consider defining domain domain name before nodes are actually imported. Otherwise, domain domain name can be created after the node is imported and the UPDATE NODE command can be used to assign the node to domain domain name.

ANR0650W IMPORT: Archive copygroup copy group name in management class management class name for domain domain name is not defined, default management class will be used.

Explanation

During import processing, the server finds that a management class or copy group bound to an archive file being imported does not exist in the active policy set for the domain to which the node is assigned.

System action

The default management class for the node's policy domain is bound to the archive file and import processing continues.

User response

If you want to define the missing management class, an authorized administrator may cancel the import operation, define the missing management class or copy group for the domain, and process the import operation again.

ANR0651W IMPORT: Backup copygroup copy group name in management class management class name for domain domain name is not defined, default management class will be used.

Explanation

During import processing, the server finds that a management class or copy group bound to a backup file being imported does not exist in the active policy set for the domain to which the node is assigned.

System action

The default management class for the node's policy domain is bound to the backup file copy and import processing continues.

User response

If you want to define the missing management class, an authorized administrator may cancel the import operation, define the missing management class or copy group for the domain, and process the import operation again.

ANR0652W IMPORT: Archive copygroup not found for default management class in domain domain name - archive files bound to management class management class name in this domain cannot be imported.

Explanation

During import processing, the server finds that a management class or copy group bound to an archive file being imported does not exist in the active policy set for the domain to which the node is assigned. When trying to rebind the archive file to the default management class for the domain, the server finds that an archive copy group is not defined for the default management class.

System action

The file is not imported; import processing continues.

User response

If you want to define the missing copy group, an authorized administrator may cancel the import operation, define the missing management class or copy group for the domain, and process the import operation again.

ANR0653W IMPORT: Backup copygroup not found for default management class in domain domain name - backup files bound to management class management class name in this domain cannot be imported.

Explanation

During import processing, the server finds that a management class or copy group bound to a backup file being imported does not exist in the active policy set for the domain to which the node is assigned. When trying to rebind the backup file to the default management class for the domain, the server finds that a backup copy group is not defined for the default management class.

System action

The file is not imported; import processing continues.

User response

If you want to define the missing copy group, an authorized administrator may cancel the import operation, define the missing management class or copy group for the domain, and process the import operation again.

ANR0654I Restartable export command with export identifier exportID started as process process ID.

Explanation

A background process was started to service the command command. The background process is defined as process process ID.

System action

Server operation continues.

User response

To query the progress of the background server-to-server export process, issue the QUERY PROCESS or QUERY EXPORT command. To suspend the process, issue the SUSPEND EXPORT command. To cancel the background process, issue the CANCEL PROCESS command. Use the process ID number to specify this specific process.

ANR0655W Command: Retrieve or restore failed - file was deleted from data storage during retrieval.

Explanation

The server ends a file retrieval operation for the specified command because the file has been deleted from data storage by another process before retrieval is complete.

System action

The server ends the command and continues operation.

User response

Contact your administrator to find out if DELETE FILESPACE, DELETE VOLUME, or inventory expiration processes are running; these processes can delete data storage files during retrieval. Reissue the command after these processes have been completed or canceled.

ANR0656W Export/import command: Skipped archive number archive files, backup number backup files, and spacemg number space managed files.

Explanation

The background export or import process to service the command export/import command skipped archive number archive file copies, backup number backup file copies, and spacemg number space-managed files from either the server database to export media or from import media into the server database. Data is not actually moved if Preview=Yes is specified in the command export/import command.

System action

Export or import processing for the command completes. Server operation continues.

User response

Check previous messages for the names of the files that were not exported or imported, and problem determination information.

ANR0657W Export command: Invalid authorization rule type rule type encountered for file space filespace name fsId filespace id in node node name - both backup and archive will be assumed during import.

Explanation

During import processing, the server encounters an invalid file space authorization rule type for the indicated file space and node.

System action

Server operation continues.

User response

After import processing is completed, ask the user of node node name to query the access rules and ensure that they are specified as desired. The user should correct any rules that grant access to objects that the user does not want others to access.

ANR0658W Export command: The password for administrator administrator name could not be obtained. The value 'password value' will be assumed: The system administrator may wish to change this password after importing administrator administrator name.

Explanation

During processing of command export command, the export processor cannot obtain the password for administrator administrator name. The value password value is assigned as the password for the administrator on the export media.

System action

Processing of the command continues.

User response

After the administrative definition has been imported to another server, an authorized administrator should use the UPDATE ADMIN command to set a password for the administrator administrator name.

ANR0659W Export command: The password for node node name could not be obtained. The value 'password value' will be assumed: The system administrator may wish to change this password after importing node node name.

Explanation

During processing of command export command, the export processor cannot obtain the password for client node node name. The value password value is assigned as the password for the client node on the export media.

System action

Processing of the command continues.

User response

After the client node definition has been imported to another server, an authorized administrator should use the UPDATE NODE command to set a password for the node node name.

ANR0660E Command: Insufficient memory available in accessing data storage.

Explanation

The server encounters a memory shortage in accessing data storage during command command operation.

System action

The command command operation ends and server operation continues.

User response

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

ANR0661E Command: Internal error encountered in accessing data storage.

Explanation

The server encounters an internal error in accessing data storage while processing command command operation.

System action

The command command operation is ended and server operation continues.

User response

Use the QUERY ACTLOG command to examine messages prior to this error to determine the cause of the data storage failure. If the failure can be found and resolved, reissue the command command operation. If the failure cannot be found, contact your service representative for assistance in resolving the problem.

ANR0662E Command: Output error encountered in accessing data storage.

Explanation

The command command operation ends because an error has been encountered by the server in writing to a device. Possible reasons include:
  • I/O error writing to a device
  • No storage space.
  • Incompatible storage pool data format.

System action

The command command operation ends and server operation continues.

User response

Query the activity log to find messages preceding this one to determine the cause of the error. After the problem is corrected, the command can be retried.

ANR0663E Command: Data transfer was interrupted in accessing data storage.

Explanation

The database transaction associated with command command operation failed because data transfer to or from data storage was interrupted by an external event.

System action

The command command operation is ended and server operation continues.

User response

Examine the messages issued prior to this message to determine why the data transfer was interrupted. Reissue the command command after the problem is resolved.

ANR0664E Export/import command: Media not accessible in accessing data storage.

Explanation

The server ends a transaction for an export or import operation because storage volumes are not available in the storage pools in which the client files are to be stored.

System action

The server ends the export or import operation and server operation continues.

User response

An authorized administrator can issue the DEFINE VOLUME command to add storage to one or more storage pools in the storage hierarchy. The VARY ONLINE command can be used to vary offline storage volumes online in the storage hierarchy to make them available for file storage.

ANR0665W Import command: Transaction failed - storage pool pool name is not defined.

Explanation

The server rolls back a database update transaction for an import operation because the destination specified for a management class copy group specifies the named storage pool, but that storage pool does not exist.

System action

The import operation is ended and server operation continues.

User response

An administrator with policy authority over the client policy domain must correct management class definitions so that copy group destinations refer to defined storage pools, or the specified storage pool must be created by an authorized administrator.

ANR0666W Import command: Transaction failed - object excluded by size in storage pool pool name and all successor pools.

Explanation

The server ends a database update transaction for an import operation because the size of an imported file is larger than that allowed in the storage pool specified in the bound management class copy group for the file. No successor storage pools to the one specified on the copy group can accept the large file.

System action

The import operation is ended and server operation continues.

User response

The maximum file size for one or more of the storage pools in the storage hierarchy can be increased to accommodate the file. An authorized administrator can increase the MAXSIZE parameter by issuing the UPDATE STGPOOL command. Alternatively, the appropriate copygroup definition can be updated so that a different destination storage pool is specified.

ANR0667W Import command: Transaction failed - no space available in storage pool pool name and all successor pools.

Explanation

The server ends an import operation because the storage pool specified in a management class copy group does not contain enough free space to hold the files being imported. Successor storage pools to the one specified on the copy group do not contain enough free space.

System action

The import operation is ended and server operation continues.

User response

An authorized administrator can issue the DEFINE VOLUME command to add storage to one or more storage pools in the storage hierarchy.

ANR0668W Export/import command: Transaction failed - error on output storage device.

Explanation

The server ends an export or import operation for the specified session because an I/O error has been encountered by the server in writing to a device.

System action

The server ends the export or import operation and server operation continues.

User response

Query the activity log to find messages preceding this one that specify the device that is failing. Storage pool volumes can be varied offline (by using the VARY OFFLINE command), or the server may need to be shut down by using the HALT command to correct the hardware problem. After the problem is corrected, the client may be able to try the operation again.

ANR0669W Export/import command: Transaction failed - data transfer interrupted.

Explanation

The database transaction associated with an export or import operation failed because data transfer to or from data storage was interrupted by an external event.

System action

The export or import operation is ended and server operation continues.

User response

Examine the messages issued prior to this message to determine why the data transfer was interrupted. Attempt the export/import operation again after problem is resolved.

ANR0670W Export/import command: Transaction failed - storage media inaccessible.

Explanation

The server ends a transaction for an export or import operation because storage volumes are not available in the storage pools in which the client files are to be stored.

System action

The server ends the export or import operation and server operation continues.

User response

An authorized administrator can issue the DEFINE VOLUME command to add storage to one or more storage pools in the storage hierarchy. The VARY ONLINE command can be used to vary offline storage volumes online in the storage hierarchy to make them available for file storage.

ANR0671W Export/import command: Transaction failed - sufficient recovery log space is not available.

Explanation

The server ends a database update transaction for an export or import operation because sufficient log space is not available on the server.

System action

The server ends the export or import operation and server operation continues.

User response

To increase the amount of log space that is available to the server, evaluate the directories and file systems that are assigned to the ACTIVELOGDIRECTORY, ARCHIVELOGDIRECTORY, and ARCHFAILOVERLOGDIRECTORY options in the dsmserv.opt file. An out of log space condition might occur because the ACTIVELOGDIRECTORY location is full.

Alternatively, an out of log space condition might occur if there are log files in the ACTIVELOGDIRECTORY location that are no longer active and cannot be archived to the ARCHIVELOGDIRECTORY and ARCHFAILOVERLOGDIRECTORY locations. If necessary, specify a larger directory for the ARCHIVELOGDIRECTORY or ARCHFAILOVERLOGDIRECTORY options in the dsmserv.opt file and then restart the server.

ANR0672W Export/import command: Transaction failed - sufficient database space is not available.

Explanation

The server ends a database update transaction for an export or import operation because sufficient database space is not available on the server.

System action

The server ends the export or import operation and server operation continues.

User response

To increase the amount of database space that is available to the server, issue the EXTEND DBSPACE command to add one or more directories to the database.

ANR0673W Export/import command: Data storage retrieve or restore failed - error detected.

Explanation

The server ends an export or import operation because an error has been encountered on the server. Some common reasons for the error are:
  • The input volume is unavailable
  • The storage pool is unavailable
  • Data is corrupted on the input volume
  • Hardware or media failure has occurred
  • Database corruption

System action

The server ends the export or import operation and continues operation.

User response

Examine any prior error messages to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages if needed. Correct the problem and try the restore or retrieve again.

ANR0674W Export command: Retrieve failed - error on input storage device.

Explanation

The server ends an export operation for the specified session because an I/O error has been encountered by the server in reading from a device. The object for which the I/O was issued is reported in a later message.

System action

Export processing skips this file, and continues operation.

User response

Query the activity log to find messages preceding this one that specify the device that is failing. Storage pool volumes can be varied offline (by using the VARY OFFLINE command), or the server may need to be shut down with the HALT command to correct the hardware problem.

ANR0675E EXPORT/IMPORT: Error starting the Export/Import Session.

Explanation

The server export/import process is not able to start the session to export information from the server or import information into the server.

System action

The export or import process ends and server operation continues.

User response

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

ANR0678E EXPORT/IMPORT: Communications Failure in Sending "verb type" verb.

Explanation

The server export/import process encounters a communications error in using the verb type verb to transfer information to or from the server.

System action

The export or import process ends and server operation continues.

User response

Contact your service representative.

ANR0679E EXPORT/IMPORT: Communications Failure in Receiving "verb type" verb.

Explanation

The server export/import process encounters a communications error in using the verb type verb to transfer information to or from the server.

System action

The export or import process ends and server operation continues.

User response

Contact your service representative.

ANR0681E EXPORT/IMPORT: Authentication Failure.

Explanation

The server export/import process encounters an authentication error in transferring information to or from the server.

System action

The export or import process ends and server operation continues.

User response

Contact your service representative.

ANR0682E EXPORT/IMPORT: Communications Failure in Sending "verb type" verb (command).

Explanation

The server export/import process encounters a communications error in using the verb type verb to issue command command.

System action

The export or import process ends and server operation continues.

User response

Contact your service representative.

ANR0683E EXPORT/IMPORT: Receive Buffer overflow.

Explanation

The server export/import process encounters an overflow error in transferring information to or from the server.

System action

The export or import process ends and server operation continues.

User response

Contact your service representative.

ANR0684E EXPORT/IMPORT: Communications failure: bad verb received (verb type).

Explanation

The server encounters an invalid communications verb during export or import processing and is not able to continue processing.

System action

The export or import process ends and server operation continues.

User response

Contact your service representative.

ANR0685E EXPORT/IMPORT: Internal error: Invalid table output handle detected.

Explanation

The server export/import process encounters an internal error in transferring information to or from the server.

System action

The export or import process ends and server operation continues.

User response

Contact your service representative.

ANR0686E Export/import command: Transaction failure - could not start database transaction.

Explanation

During processing of command export/import command, a database transaction cannot be started in the server database.

System action

Processing of the command terminates.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0687E Export/import command: Transaction failure - could not commit database transaction.

Explanation

During processing of command export/import command, a database transaction cannot be committed to the server database.

System action

Processing of the command ends.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0688E Export/import command: Transaction failure - commit called when no transaction started.

Explanation

During processing of command export/import command, a database transaction cannot be started in the server database.

System action

Processing of the command ends.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0690E Export/import command: Transaction failure - server aborted the transaction (abort code).

Explanation

During processing of command export/import command, a database transaction cannot be committed in the server database. The reason code abort code is returned.

System action

Processing of the command ends.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0692E Command: Out of space on sequential media, scratch media could not be mounted.

Explanation

During command command processing, the process encounters an out-of-space condition writing to the sequential media. Command command ends when there is no more space on the sequential media for storing data and SCRATCH=NO has been specified on command command.

System action

Command command processing ends. Server processing continues.

User response

Reissue the command and specify SCRATCH=YES or specify additional volume names on the command.

ANR0694E Import command: Invalid record format (format code) detected on import.

Explanation

During processing of command import command, an invalid record type is detected when reading the exported information from the export media.

System action

Processing of the command ends.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0695E Export command: Unexpected error error code encountered in receiving table output data.

Explanation

During processing of command export command, an unexpected error is detected.

System action

Processing of the command ends.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0696E Export command: Output table error encountered - 0 columns reported in the table.

Explanation

During processing of command export command, an unexpected error is detected.

System action

Processing of the command ends.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0697E Export command: Output table error encountered - not positioned to the first column in the table.

Explanation

During processing of command export command, an unexpected error is detected.

System action

Processing of the command ends.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0698E Export/import command: Invalid value for FILEDATA parameter - parameter value.

Explanation

The value (parameter value) specified for the FILEDATA parameter in command export/import command is not a valid value for this parameter.

System action

The command fails and server operation continues.

User response

Reissue the command and specify a valid FILEDATA parameter.

ANR0699E Export/import command: Device class DISK cannot be specified for this command.

Explanation

The DEVCLASS value DISK cannot be specified for the command export/import command.

System action

The command fails and server operation continues.

User response

Reissue the command and specify a valid device class. Issue the QUERY DEVCLASS command for a list of valid device classes for the server.

ANR0700E Export/import command: Invalid value for PREVIEW parameter - parameter value.

Explanation

The value (parameter value) specified for the PREVIEW parameter in command export/import command is not a valid value for this parameter.

System action

The command fails and server operation continues.

User response

Reissue the command and specify a valid PREVIEW parameter.

ANR0701E Export/import command: Invalid value for SCRATCH parameter - parameter value.

Explanation

The value (parameter value) specified for the SCRATCH parameter in command export/import command is not a valid value for this parameter.

System action

The command fails and server operation continues.

User response

Reissue the command and specify a valid SCRATCH parameter.

ANR0705E Export command: The VOLUMENAMES parameter must be specified when SCRATCH=NO is specified.

Explanation

The SCRATCH parameter is specified as NO for the command export command but the VOLUMENAMES parameter is not specified. When scratch volumes are not allowed, the VOLUMENAMES parameter must be specified to indicate the volumes that can be used for the command.

System action

The command fails and server operation continues.

User response

Reissue the command and specify a valid VOLUMENAMES parameter.

ANR0706E Export command: A device class must be specified unless PREVIEW=YES is specified.

Explanation

The DEVCLASS parameter is not specified in the command export command. Unless PREVIEW=YES is specified, a DEVCLASS value must be specified.

System action

The command fails and server operation continues.

User response

Reissue the command and specify a valid device class. Issue the QUERY DEVCLASS command for a list of valid device classes for the server.

ANR0707E Export command: The FILESPACE parameter cannot be specified.

Explanation

The FILESPACE parameter is specified for the command export command, but the FILEDATA parameter is specified as NONE, or is not specified and defaults to NONE. File spaces are only copied if the FILEDATA parameter is specified with a value other than NONE.

System action

The command fails and server operation continues.

User response

Reissue the command and specify a valid FILEDATA parameter.

ANR0708E Import command: The FILESPACE parameter cannot be specified unless the FILEDATA parameter specifies that files should be imported.

Explanation

The FILESPACE parameter is specified for the command import command, but the FILEDATA parameter is specified as NONE, or is not specified and defaults to NONE. File spaces are only copied if the FILEDATA parameter is specified with a value other than NONE.

System action

The command fails and server operation continues.

User response

Reissue the command and specify a valid FILEDATA parameter.

ANR0709E Command: No matching nodes registered in the specified domains.

Explanation

The DOMAIN parameter has been specified for this command, but no nodes matching the node name specification are found in the domains specified.

System action

The command fails and server operation continues.

User response

Reissue the command and specify a valid combination of node and domain names. Use the QUERY NODE command to view the names of nodes in the domains that you are interested in exporting.

ANR0710E Command: Unable to start background process.

Explanation

The server command processor is not able to start a background process to perform the command command.

System action

The command process ends and server operation continues.

User response

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

ANR0712E Import command: Invalid value for DATES parameter - parameter value.

Explanation

The value (parameter value) specified for the DATES parameter in command import command is not a valid value for this parameter.

System action

The command fails and server operation continues.

User response

Reissue the command and specify a valid DATES parameter.

ANR0713E Import command: Invalid value for REPLACEDEFS parameter - parameter value.

Explanation

The value (parameter value) specified for the REPLACEDEFS parameter in command import command is not a valid value for this parameter.

System action

The command fails and server operation continues.

User response

Reissue the command and specify a valid REPLACEDEFS parameter.

ANR0715E Import command: A device class must be specified.

Explanation

The command import command has been specified, but does not include specification of the DEVCLASS parameter. The DEVCLASS parameter must be specified for this command.

System action

The command fails and server operation continues.

User response

Reissue the command and specify a valid device class. For a list of valid device classes for the server, issue the QUERY DEVCLASS command.

ANR0716E Import command: Invalid export data detected.

Explanation

The command import command encounters invalid data on the export media while trying to import server information.

System action

The command fails and server operation continues.

User response

Ensure that the mounted export tapes are in the correct order (mounted in the same order as they were mounted during export). Reissue the command, and mount the tapes in the correct order. If the VOLUMENAMES parameter has been specified, make sure that the volume names in the command are specified in the correct order.

ANR0717E Export/import command: Preview processing terminated abnormally - communications send or receive failed.

Explanation

Processing for the command export/import command in preview mode has been terminated when an internal communications error is encountered in the server.

System action

Export/import processing is ended and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0718E Export/import command: Processing terminated abnormally - communications send or receive failed.

Explanation

Processing for the command export/import command ends when an internal communications error is encountered in the server.

System action

Export/import processing is ended and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0719E Export/import command: Preview processing terminated abnormally - insufficient memory.

Explanation

Processing for the command export/import command in preview mode is ended because sufficient memory is not available on the server.

System action

Export/import processing is ended and server operation continues.

User response

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

ANR0720E command: Processing terminated abnormally - insufficient memory.

Explanation

Processing for the command ends because sufficient memory is not available on the server.

System action

Command processing is ended and server operation continues.

User response

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

ANR0721E Export/import command: Preview processing terminated abnormally - unexpected verb received from server.

Explanation

Processing for the command export/import command in preview mode ends when an internal communications error is encountered in the server.

System action

Export/import processing ends and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0722E Export/import command: Processing terminated abnormally - unexpected verb received from server.

Explanation

Processing for the command export/import command ends when an internal communications error is encountered in the server.

System action

Export/import processing ends and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0723E Export/import command: Preview processing terminated abnormally - transaction failure.

Explanation

Processing for the command export/import command in preview mode ends when a database transaction error is encountered in the server.

System action

Export/import processing ends and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0724E Export/import command: Processing terminated abnormally - transaction failure.

Explanation

Processing for the command export/import command ends when a database transaction error is encountered in the server.

System action

Export/import processing ends and server operation continues.

User response

Examine the source and target server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0725E Export/import command: Preview processing terminated abnormally - authentication failure.

Explanation

Processing for the command export/import command in preview mode ends when an authentication error is encountered in the server.

System action

Export/import processing ends and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0726E Export/import command: Processing terminated abnormally - authentication failure.

Explanation

Processing for the command export/import command ends when an authentication error is encountered in the server.

System action

Export/import processing ends and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0727E Export/import command: Preview processing terminated abnormally - internal error.

Explanation

Processing for the command export/import command in preview mode ends when an internal error is encountered in the server.

System action

Export/import processing ends and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0728E Export/import command: Processing terminated abnormally - internal error.

Explanation

Processing for the command export/import command ends when an internal error is encountered in the server.

System action

Export/import processing ends and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0729E Import command: Syntax error from command 'server command'.

Explanation

During processing of the command import command, an internal syntax error is encountered in the server.

System action

Import processing continues, but the indicated command will have no effect.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. After import processing is complete, it may be necessary to issue additional commands manually to obtain the necessary definitions.

ANR0730E Import command: Internal error from command 'server command'.

Explanation

Processing for the command import command ends when an internal command error is encountered in the server.

System action

Import processing ends and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0731E Import command: Invalid value for COMPRESSION parameter in exported data for node node name.

Explanation

During preview processing of command import command, an invalid value is encountered for the COMPRESSION parameter for node node name.

System action

Processing of the command continues. If a later command causes the data to be imported, the default or existing COMPRESSION value is used.

User response

None. If the data is imported with a later command, verify that the correct COMPRESSION value is used for this node.

ANR0732E Import command: Invalid value for ARCHDELETE parameter in exported data for node node name.

Explanation

During preview processing of command import command, an invalid value is encountered for the ARCHDELETE parameter for node node name.

System action

Processing of the command continues. If a later command causes the data to be imported, the default or existing ARCHDELETE value is used.

User response

None. If the data is imported with a later command, verify that the correct ARCHDELETE value is used for this node.

ANR0733E Import command: Invalid value for BACKDELETE parameter in exported data for node node name.

Explanation

During preview processing of command import command, an invalid value is encountered for the BACKDELETE parameter for node node name.

System action

Processing of the command continues. If a later command causes the data to be imported, the default or existing BACKDELETE value is used.

User response

None. If the data is imported with a later command, verify that the correct BACKDELETE value is used for this node.

ANR0734E Import command: Invalid value for COMPRESSION parameter in exported data - node node name registered with default COMPRESSION value.

Explanation

During processing of command import command, an invalid value is encountered for the COMPRESSION parameter for node node name.

System action

Processing of the command continues, by using the default COMPRESSION value for this node.

User response

Verify that the correct COMPRESSION value has been used for this node. Update this value, if necessary.

ANR0735E Import command: Invalid value for ARCHDELETE parameter in exported data - node node name registered with default ARCHDELETE value.

Explanation

During processing of command import command, an invalid value is encountered for the ARCHDELETE parameter for node node name.

System action

Processing of the command continues, by using the default ARCHDELETE value for this node.

User response

Verify that the correct ARCHDELETE value has been used for this node. Update this value, if necessary.

ANR0736E Import command: Invalid value for BACKDELETE parameter in exported data - node node name registered with default BACKDELETE value.

Explanation

During processing of command import command, an invalid value is encountered for the BACKDELETE parameter for node node name.

System action

Processing of the command continues, by using the default BACKDELETE value for this node.

User response

Verify that the correct BACKDELETE value has been used for this node. Update this value, if necessary.

ANR0737E Import command: Invalid value for COMPRESSION parameter in exported data - existing COMPRESSION value for node node name was not updated.

Explanation

During processing of command import command, an invalid value is encountered for the COMPRESSION parameter for node node name.

System action

Processing of the command continues, by using the existing COMPRESSION value for this node.

User response

Verify that the correct COMPRESSION value has been used for this node. Update this value, if necessary.

ANR0738E Import command: Invalid value for ARCHDELETE parameter in exported data - existing ARCHDELETE value for node node name was not updated.

Explanation

During processing of command import command, an invalid value is encountered for the ARCHDELETE parameter for node node name.

System action

Processing of the command continues, by using the existing ARCHDELETE value for this node.

User response

Verify that the correct ARCHDELETE value has been used for this node. Update this value, if necessary.

ANR0739E Import command: Invalid value for BACKDELETE parameter in exported data - existing BACKDELETE value for node node name was not updated.

Explanation

During processing of command import command, an invalid value is encountered for the BACKDELETE parameter for node node name.

System action

Processing of the command continues, by using the existing BACKDELETE value for this node.

User response

Verify that the correct BACKDELETE value has been used for this node. Update this value, if necessary.

ANR0740E Import command: Invalid value for TYPE parameter in exported data for copy group copy group name in domain domain name, set policy set name, management class management class name - backup is assumed.

Explanation

During processing of command import command, an invalid value is encountered for the TYPE parameter for copy group copy group, in policy domain domain name, policy set policy set name, management class management class name.

System action

Processing of the command continues. Based upon other copy group parameters, a copy group type of backup is assigned.

User response

Verify that the assigned TYPE value of backup for this copy group is correct.

ANR0741E Import command: Invalid value for TYPE parameter in exported data for copy group copy group name in domain domain name, set policy set name, management class management class name - archive is assumed.

Explanation

During processing of command import command, an invalid value is encountered for the TYPE parameter for copy group copy group, in policy domain domain name, policy set policy set name, management class management class name.

System action

Processing of the command continues. Based upon other copy group parameters, a copy group type of archive is assigned.

User response

Verify that the assigned TYPE value of archive for this copy group is correct.

ANR0742E Import command: Invalid value for TYPE parameter in exported data for copy group copy group name in domain domain name, set policy set name, management class management class name - this copy group will not be imported.

Explanation

During processing of command import command, an invalid value is encountered for the TYPE parameter for copy group copy group, in policy domain domain name, policy set policy set name, management class management class name.

System action

Processing of the command continues. However, this copy group is not imported because a TYPE value cannot be assigned.

User response

Manually define this copy group, if necessary.

ANR0743E Import command: Invalid value for MODE parameter in exported data for archive copy group copy group name in domain domain name, set policy set name, management class management class name.

Explanation

During preview processing of command import command, an invalid value is encountered for the MODE parameter for archive copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System action

Processing of the command continues. If a later command causes the data to be imported, the default or existing MODE value is used.

User response

None. If the data is imported with a later command, verify that the correct MODE value is used for this archive copy group.

ANR0744E Import command: Invalid value for MODE parameter in exported data for backup copy group copy group name in domain domain name, set policy set name, management class management class name.

Explanation

During preview processing of command import command, an invalid value is encountered for the MODE parameter for backup copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System action

Processing of the command continues. If a later command causes the data to be imported, the default or existing MODE value is used.

User response

None. If the data is imported with a later command, verify that the correct MODE value is used for this backup copy group.

ANR0745E Import command: Invalid value for SERIALIZATION parameter in exported data for archive copy group copy group name in domain domain name, set policy set name, management class management class name.

Explanation

During preview processing of command import command, an invalid value is encountered for the SERIALIZATION parameter for archive copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System action

Processing of the command continues. If a later command causes the data to be imported, the default or existing SERIALIZATION value is used.

User response

None. If the data is imported with a later command, verify that the correct SERIALIZATION value is used for this archive copy group.

ANR0746E Import command: Invalid value for SERIALIZATION parameter in exported data for backup copy group copy group name in domain domain name, set policy set name, management class management class name.

Explanation

During preview processing of command import command, an invalid value is encountered for the SERIALIZATION parameter for backup copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System action

Processing of the command continues. If a later command causes the data to be imported, the default or existing SERIALIZATION value is used.

User response

None. If the data is imported with a later command, verify that the correct SERIALIZATION value is used for this backup copy group.

ANR0747E Import command: Invalid value for MODE parameter in exported data - archive copy group copy group name in domain domain name, set policy set name, management class management class name defined with default MODE value.

Explanation

During processing of command import command, an invalid value is encountered for the MODE parameter for archive copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System action

Processing of the command continues, by using the default MODE value for this archive copy group.

User response

Verify that the correct MODE value has been used for this copy group. Update this value, if necessary.

ANR0748E Import command: Invalid value for MODE parameter in exported data - backup copy group copy group name in domain domain name, set policy set name, management class management class name defined with default MODE value.

Explanation

During processing of command import command, an invalid value is encountered for the MODE parameter for backup copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System action

Processing of the command continues, by using the default MODE value for this backup copy group.

User response

Verify that the correct MODE value has been used for this copy group. Update this value, if necessary.

ANR0749E Import command: Invalid value for SERIALIZATION parameter in exported data - archive copy group copy group name in domain domain name, set policy set name, management class management class name defined with default SERIALIZATION value.

Explanation

During processing of command import command, an invalid value is encountered for the SERIALIZATION parameter for archive copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System action

Processing of the command continues, by using the default SERIALIZATION value for this archive copy group.

User response

Verify that the correct SERIALIZATION value has been used for this copy group. Update this value, if necessary.

ANR0750E Import command: Invalid value for SERIALIZATION parameter in exported data - backup copy group copy group name in domain domain name, set policy set name, management class management class name defined with default SERIALIZATION value.

Explanation

During processing of command import command, an invalid value is encountered for the SERIALIZATION parameter for backup copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System action

Processing of the command continues, by using the default SERIALIZATION value for this backup copy group.

User response

Verify that the correct SERIALIZATION value has been used for this copy group. Update this value, if necessary.

ANR0751E Import command: Invalid value for MODE parameter in exported data - existing MODE value for archive copy group copy group name in domain domain name, set policy set name, management class management class name was not updated.

Explanation

During processing of command import command, an invalid value is encountered for the MODE parameter for archive copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System action

Processing of the command continues, by using the existing MODE value for this archive copy group.

User response

Verify that the correct MODE value has been used for this copy group. Update this value, if necessary.

ANR0752E Import command: Invalid value for MODE parameter in exported data - existing MODE value for backup copy group copy group name in domain domain name, set policy set name, management class management class name was not updated.

Explanation

During processing of command import command, an invalid value is encountered for the MODE parameter for backup copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System action

Processing of the command continues, by using the existing MODE value for this backup copy group.

User response

Verify that the correct MODE value has been used for this copy group. Update this value, if necessary.

ANR0753E Import command: Invalid value for SERIALIZATION parameter in exported data - existing SERIALIZATION value for archive copy group copy group name in domain domain name, set policy set name, management class management class name was not updated.

Explanation

During processing of command import command, an invalid value is encountered for the SERIALIZATION parameter for archive copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System action

Processing of the command continues, by using the existing SERIALIZATION value for this archive copy group.

User response

Verify that the correct SERIALIZATION value has been used for this copy group. Update this value, if necessary.

ANR0754E Import command: Invalid value for SERIALIZATION parameter in exported data - existing SERIALIZATION value for backup copy group copy group name in domain domain name, set policy set name, management class management class name was not updated.

Explanation

During processing of command import command, an invalid value is encountered for the SERIALIZATION parameter for backup copy group copy group name, in policy domain domain name, policy set policy set name, management class management class name.

System action

Processing of the command continues, by using the existing SERIALIZATION value for this backup copy group.

User response

Verify that the correct SERIALIZATION value has been used for this copy group. Update this value, if necessary.

ANR0755E Import command: Invalid value for ACTION parameter in exported data for schedule schedule name in domain domain name.

Explanation

During preview processing of command import command, an invalid value is encountered for the ACTION parameter for schedule schedule name in policy domain domain name.

System action

Processing of the command continues. If a later command causes the data to be imported, the default or existing ACTION value is used.

User response

If the data is imported with a later command, verify that the correct ACTION value is used for this schedule.

ANR0756E Import command: Invalid value for DURUNITS or PERUNITS parameter in exported data for schedule schedule name in domain domain name.

Explanation

During preview processing of command import command, an invalid value is encountered for the DURUNITS or PERUNITS parameter for schedule schedule name in policy domain domain name.

System action

Processing of the command continues. If a later command causes the data to be imported, the default or existing values are used for DURATION, DURUNITS, PERIOD, and PERUNITS.

User response

If the data is imported with a later command, verify that the correct values for DURATION, DURUNITS, PERIOD, and PERUNITS are used for this schedule.

ANR0757E Import command: Invalid value for DAYOFWEEK parameter in exported data for schedule schedule name in domain domain name.

Explanation

During preview processing of command import command, an invalid value is encountered for the DAYOFWEEK parameter for schedule schedule name in policy domain domain name.

System action

Processing of the command continues. If a later command causes the data to be imported, the default or existing DAYOFWEEK value is used.

User response

If the data is imported with a later command, verify that the correct DAYOFWEEK value is used for this schedule.

ANR0758E Import command: Invalid value for ACTION parameter in exported data - schedule schedule name in domain domain name defined with default ACTION value.

Explanation

During processing of command import command, an invalid value is encountered for the ACTION parameter for schedule schedule name in policy domain domain name.

System action

Processing of the command continues, by using the default ACTION value for this schedule.

User response

Verify that the correct ACTION value has been used for this schedule. Update this value, if necessary.

ANR0759E Import command: Invalid value for DURUNITS or PERUNITS parameter in exported data - schedule schedule name in domain domain name defined with default values for DURATION, DURUNITS, PERIOD, and PERUNITS.

Explanation

During processing of command import command, an invalid value is encountered for the DURUNITS or PERUNITS parameter for schedule schedule name in policy domain domain name.

System action

Processing of the command continues, by using the default values for DURATION, DURUNITS, PERIOD, and PERUNITS.

User response

Verify that the correct values have been used for DURATION, DURUNITS, PERIOD, and PERUNITS. Update these values, if necessary.

ANR0760E Import command: Invalid value for DAYOFWEEK parameter in exported data - schedule schedule name in domain domain name defined with default DAYOFWEEK value.

Explanation

During processing of command import command, an invalid value is encountered for the DAYOFWEEK parameter for schedule schedule name in policy domain domain name.

System action

Processing of the command continues, by using the default DAYOFWEEK value for this schedule.

User response

Verify that the correct DAYOFWEEK value has been used for this schedule. Update this value, if necessary.

ANR0761E Import command: Invalid value for ACTION parameter in exported data - existing ACTION value for schedule schedule name in domain domain name was not updated.

Explanation

During processing of command import command, an invalid value is encountered for the ACTION parameter for schedule schedule name in policy domain domain name.

System action

Processing of the command continues, by using the existing ACTION value for this schedule.

User response

Verify that the correct ACTION value has been used for this schedule. Update this value, if necessary.

ANR0762E Import command: Invalid value for DURUNITS or PERUNITS parameter in exported data - existing values for DURATION, DURUNITS PERIOD, and PERUNITS for schedule schedule name in domain domain name were not updated.

Explanation

During processing of command import command, an invalid value is encountered for the DURUNITS or PERUNITS parameter for schedule schedule name in policy domain domain name.

System action

Processing of the command continues, by using the existing values for DURATION, DURUNITS, PERIOD, and PERUNITS.

User response

Verify that the correct values have been used for DURATION, DURUNITS, PERIOD, and PERUNITS. Update these values, if necessary.

ANR0763E Import command: Invalid value for DAYOFWEEK parameter in exported data - existing DAYOFWEEK value for schedule schedule name in domain domain name was not updated.

Explanation

During processing of command import command, an invalid value is encountered for the DAYOFWEEK parameter for schedule schedule name in policy domain domain name.

System action

Processing of the command continues, by using the existing DAYOFWEEK value for this schedule.

User response

Verify that the correct DAYOFWEEK value has been used for this schedule. Update this value, if necessary.

ANR0764E Import command: Invalid lock status detected while importing node node name - this node will not be locked.

Explanation

During processing of command import command, an invalid value is encountered for the lock status for node node name.

System action

Processing of the command continues, but the node is not locked.

User response

An administrator with the proper authorization must issue the LOCK NODE command, if necessary.

ANR0765E Import command: Invalid lock status detected while importing administrator administrator name - this administrator will not be locked.

Explanation

During processing of command import command, an invalid value is encountered for the lock status for administrator administrator name.

System action

Processing of the command continues, but the administrator is not locked.

User response

An administrator with the proper authorization must issue the LOCK ADMIN command, if necessary.

ANR0766E Export command: Invalid value for TYPE parameter detected while exporting copy group copy group name in domain domain name, set policy set name, management class management class name - system will attempt to assign value during import.

Explanation

During processing of command export command, an invalid value is encountered for the TYPE parameter for copy group copy group name, in domain domain name, policy set policy set name, management class management class name.

System action

Export processing continues, but the exported data contains an unknown TYPE value for this copy group. If this data is imported, the system attempts to assign a TYPE value based upon values for other copy group parameters.

User response

Delete and define this copy group to eliminate the invalid data, and then restart the export command. Alternatively, use the export data with the unknown value, and the system will attempt to assign a TYPE during import processing.

ANR0767E Export command: Invalid value for MODE parameter detected while exporting copy group copy group name in domain domain name, set policy set name, management class management class name - default or existing value is used during import.

Explanation

During processing of command export command, an invalid value is encountered for the MODE parameter for copy group copy group name in domain domain name, policy set policy set name, management class management class name.

System action

Export processing continues, but the exported data contains an unknown MODE value for this copy group. If this data is imported, the default or existing MODE value is used.

User response

Update the MODE value for this copy group and restart the export command. Alternatively, use the export data with the unknown value, and check and update the MODE value after import processing has been performed.

ANR0768E Export command: Invalid value for SERIALIZATION parameter detected while exporting copy group copy group name in domain domain name, set policy set name, management class management class name - default or existing value is used during import.

Explanation

During processing of command export command, an invalid value is encountered for the SERIALIZATION parameter for copy group copy group name, in domain domain name, policy set policy set name, management class management class name.

System action

Export processing continues, but the exported data contains an unknown SERIALIZATION value for this copy group. If this data is imported, the default or existing SERIALIZATION value is used.

User response

Update the SERIALIZATION value for this copy group and restart the export command. Alternatively, use the export data with the unknown value, and check and update the SERIALIZATION value after import processing has been performed.

ANR0769E Export command: Invalid value for ACTION parameter detected while exporting schedule schedule name in domain domain name - default or existing value is used during import.

Explanation

During processing of command export command, an invalid value is encountered for the ACTION parameter for schedule schedule name in domain domain name.

System action

Export processing continues, but the exported data will contain an unknown ACTION value for this schedule. If this data is imported, the default or existing ACTION value is used.

User response

Update the ACTION value for this schedule and restart the export command. Alternatively, use the export data with the unknown value, and check and update the ACTION value after import processing has been performed.

ANR0770E Export command: Invalid value for DURUNITS parameter detected while exporting schedule schedule name in domain domain name - default or existing value is used during import.

Explanation

During processing of command export command, an invalid value is encountered for the DURUNITS parameter for schedule schedule name in domain domain name.

System action

Export processing continues, but the exported data contains an unknown DURUNITS value for this schedule. If this data is imported, the default or existing DURUNITS value is used.

User response

Update the DURUNITS value for this schedule and restart the export command. Alternatively, use the export data with the unknown value, and check and update the DURUNITS value after import processing has been performed.

ANR0771E Export command: Invalid value for PERUNITS parameter detected while exporting schedule schedule name in domain domain name - default or existing value is used during import.

Explanation

During processing of command export command, an invalid value is encountered for the PERUNITS parameter for schedule schedule name in domain domain name.

System action

Export processing continues, but the exported data will contain an unknown PERUNITS value for this schedule. If this data is imported, the default or existing PERUNITS value is used.

User response

Update the PERUNITS value for this schedule and restart the export command. Alternatively, use the export data with the unknown value, and check and update the PERUNITS value after import processing has been performed.

ANR0772E Export command: Invalid value for DAYOFWEEK parameter detected while exporting schedule schedule name in domain domain name - default or existing value is used during import.

Explanation

During processing of command export command, an invalid value is encountered for the DAYOFWEEK parameter for schedule schedule name in domain domain name.

System action

Export processing continues, but the exported data contains an unknown DAYOFWEEK value for this schedule. If this data is imported, the default or existing DAYOFWEEK value is used.

User response

Update the DAYOFWEEK value for this schedule and restart the export command. Alternatively, use the export data with the unknown value, and check and update the DAYOFWEEK value after import processing has been performed.

ANR0773E Export command: Invalid lock status detected while exporting administrator administrator name - this administrator will not be locked during import.

Explanation

During processing of command export command, an invalid value is encountered for the lock status for administrator administrator name.

System action

Export processing continues, but the exported data contains an unknown lock status for this administrator. If this data is imported, the administrator will not be locked.

User response

An administrator with the proper authorization must issue the LOCK NODE or UNLOCK NODE command to achieve the desired lock status, and then restart the export command. Alternatively, use the export data with the unknown status, and issue a LOCK ADMIN or UNLOCK ADMIN command after import processing has been performed.

ANR0774E Export command: Invalid value for COMPRESSION parameter detected while exporting node node name - default or existing value is used during import.

Explanation

During processing of command export command, an invalid value is encountered for the COMPRESSION parameter for node node name.

System action

Export processing continues, but the exported data contains an unknown COMPRESSION value for this node. If this data is imported, the default or existing COMPRESSION value is used.

User response

Update the COMPRESSION parameter for this node and restart the export command. Alternatively, use the export data with the unknown value, and check and update the COMPRESSION value after import processing has been performed.

ANR0775E Export command: Invalid lock status detected while exporting node node name - this node will not be locked during import.

Explanation

During processing of command export command, an invalid value is encountered for the lock status for node node name.

System action

Export processing continues, but the exported data contains an unknown lock status for this node. If this data is imported, the node will not be locked.

User response

Lock or unlock the node to achieve the desired lock status, and then restart the export command. Alternatively, use the export data with the unknown status, and lock or unlock the node after import processing has been performed.

ANR0776E Export command: Invalid value for ARCHDELETE parameter detected while exporting node node name - default or existing value is used during import.

Explanation

During processing of command export command, an invalid value is encountered for the ARCHDELETE parameter for node node name.

System action

Export processing continues, but the exported data contains an unknown ARCHDELETE value for this node. If this data is imported, the default or existing ARCHDELETE value is used.

User response

Update the ARCHDELETE parameter for this node and restart the export command. Alternatively, use the export data with the unknown value, and check and update the ARCHDELETE value after import processing has been performed.

ANR0777E Export command: Invalid value for BACKDELETE parameter detected while exporting node node - default or existing value is used during import.

Explanation

During processing of command export command, an invalid value is encountered for the BACKDELETE parameter for node node name.

System action

Export processing continues, but the exported data contains an unknown BACKDELETE value for this node. If this data is imported, the default or existing BACKDELETE value is used.

User response

Update the BACKDELETE parameter for this node and restart the export command. Alternatively, use the export data with the unknown value, and check and update the BACKDELETE value after import processing has been performed.

ANR0778E Command: Error encountered in accessing data storage - device class device class name is not defined.

Explanation

During command command processing, an error occurred because the specified device class is not defined.

System action

The command command is ended and server operation continues.

User response

Make sure the specified device class is defined.

ANR0779E Command: Error encountered in accessing data storage - disk volume specified.

Explanation

During command command processing, an error occurred because a specified volume is a disk volume rather than a tape volume.

System action

The command command is ended and server operation continues.

User response

Make sure that all volumes specified for the command command are tape volumes.

ANR0780E Export/import command: Process aborted - a server communications session could not be established.

Explanation

The server export/import process encounters an internal error in establishing an intermemory communications session with other server components.

System action

The export or import process ends and server operation continues.

User response

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

If the error is not resolved, contact your service representative.

ANR0781E Export/import command: Process aborted - server sign on failed.

Explanation

The server export/import process encounters an internal error in establishing an intermemory communications session with other server components.

System action

The export or import process ends and server operation continues.

User response

Contact your service representative.

ANR0784E Export/import command: Process aborted - internal error detected with the Export/Import level: level number.

Explanation

The server export/import process encounters an internal error in evaluating the export/import level (SERVER, NODE, ADMIN, POLICY).

System action

The export or import process ends and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0785E Import command: Invalid record type xrecord type read from export data.

Explanation

The server export/import process encounters an internal error in reading data from the export media. An invalid record type of record type is encountered during the read operation.

System action

The export or import process ends and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0786E Import command: Invalid export version version number in exported data.

Explanation

The server import process encounters an internal error in reading data from the export media. An invalid export version number (version number) is encountered during the read operation.

System action

The export or import process ends and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0787E Import command: Import of file space filespace name in node node name aborted by server (abort reason).

Explanation

The server import process encounters an internal error in importing file space filespace name for client node node name. The reason code abort reason is encountered.

System action

The export or import process ends and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0789E Import command: Failure in normalizing transaction identifier for sending to the server.

Explanation

The server import process encounters an internal database transaction error in importing information into the server database.

System action

The export or import process ends and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0790E Import command: Error in absorbing data records.

Explanation

The server import process encounters an internal error in importing information into the server database.

System action

The export or import process ends and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Use the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0792E Import command: Invalid copy type encountered in an imported file space authorization rule for node node name, file space filespace name - a type of BACKUP will be assumed.

Explanation

During import processing for command import command, an invalid copy type is encountered for an authorization rule that grants access for file space filespace name on node node name. Authorization rules typically specify copy types of backup or archive, depending on whether backup file access or archive file access is granted by the file space owner to other users. Because the imported information for the rule is ambiguous, the server assumes that the rule is for backup data.

System action

The import process continues.

User response

The user for node node name should query the access rules for the specified node name after the import process has completed, and correct or delete any access rules that are in error or not needed.

ANR0793E Export/import command: Preview processing terminated abnormally - error accessing data storage.

Explanation

The server encountered an internal error in accessing data storage while executing an import or export preview operation.

System action

The export or import operation is ended and server operation continues.

User response

Use the QUERY ACTLOG command to examine messages prior to this error to determine the cause of the data storage failure. If you find and resolve the error, retry the export or import operation. If you cannot find the error, contact your service representative for assistance in resolving the problem.

ANR0794E Export/import command: Processing terminated abnormally - error accessing data storage.

Explanation

The server encountered an internal error in accessing data storage while executing an import or export operation.

System action

The export or import operation is ended and server operation continues.

User response

Use the QUERY ACTLOG command to examine messages prior to this error to determine the cause of the data storage failure. If the import or export operation involves a session with another server, run the QUERY ACTLOG command to examine messages on the other server as well. Messages on the other server can help you troubleshoot the error on the local server. If you find and resolve the error, retry the export or import operation. If you cannot find the error, contact your service representative for assistance in resolving the problem.

ANR0795E Command: Error encountered in accessing data storage - invalid volume name specified.

Explanation

The server encounters an error in accessing data storage while processing command command. The error occurred because an attempt has been made to access a volume with an invalid name.

System action

The command command operation is ended and server operation continues.

User response

Issue the command with a valid volume name.

ANR0796E Command: Error encountered in accessing data storage - insufficient number of mount points available for removable media.

Explanation

During command command processing, the server cannot allocate sufficient mount points.

System action

The command command operation is ended and server operation continues.

User response

If necessary, make more mount points available.

ANR0797E Command: Error encountered in accessing data storage - required volume was not mounted.

Explanation

During command command processing, a required volume cannot be mounted. The mount request may have been canceled.

System action

The command command operation is ended and server operation continues.

User response

Issue the command again and make sure the necessary volumes are accessible.

ANR0798E Import command: Error encountered in accessing data storage - volume cannot be used.

Explanation

During import processing, a volume has been mounted but cannot be used.

System action

The import operation is ended and server operation continues.

User response

Query the activity log for messages preceding this one that give additional information. Make sure a usable volume is specified and mounted.

ANR0799E Command: Error encountered in accessing data storage - volume already in use.

Explanation

During command command processing, a volume cannot be used because it is already defined in a storage pool, or has been previously used by an export, database dump, or database backup operation (as recorded in the volume history) or is in use by another process.

System action

The command command operation is ended and server operation continues.

User response

Specify a volume that is not in use or defined in a storage pool, and that has not been previously used for an export, database dump, or database backup operation as recorded in the server volume history information. Use the QUERY VOLUME command to display the names of volumes that are defined to server storage pools. Use the QUERY VOLHISTORY command to display the names of volumes that have been used for export, database dump, or database backup operations.

ANR0800I Command command for node node name started as process process ID.

Explanation

A file space deletion process has started to delete one or more file spaces for the specified node. The process is assigned the ID specified in the message.

System action

The server starts a background process to perform the operation in response to the DELETE FILESPACE command entered by an administrator.

User response

To obtain status on the file space deletion process, issue the QUERY PROCESS command. The process may be canceled with the CANCEL PROCESS command.

ANR0801I DELETE FILESPACE filespace name for node node name started as process process ID.

Explanation

The specified client node has started a file space deletion process (on the server) to delete one or more file spaces. The process has been assigned the ID specified in the message.

System action

The server starts a background process to perform the operation in response to a request from the client node.

User response

To obtain status on the file space deletion process, issue the QUERY PROCESS command. The process may be canceled by an authorized administrator using the CANCEL PROCESS command.

ANR0802I DELETE FILESPACE filespace name (backup/archive data) for node node name started.

Explanation

A background server process has started (on the server) to delete the specified file space belonging to the node indicated. If a file space name is not included in the message, all file spaces belonging to the node are deleted.

System action

The background process deletes backup and archive objects for the specified file space while server operation continues.

User response

To obtain status on the file space deletion process, issue the QUERY PROCESS command. The process may be canceled by an authorized administrator using the CANCEL PROCESS command.

ANR0803I DELETE FILESPACE filespace name (backup data) for node node name started.

Explanation

A background server process has started (on the server) to delete backup objects in the specified file space belonging to the node indicated. If a file space name is not included in the message, then the backup objects for all file spaces that belong to the node are deleted.

System action

The background process deletes backup objects for the specified file space while server operation continues.

User response

To obtain status on the file space deletion process, issue the QUERY PROCESS command. The process may be canceled by an authorized administrator using the CANCEL PROCESS command.

ANR0804I DELETE FILESPACE filespace name (archive data) for node node name started.

Explanation

A background server process has started (on the server) to delete archive objects in the specified file space belonging to the node indicated. If a file space name is not included in the message, then the archive objects for all file spaces that belong to the node are deleted.

System action

The background process deletes archive objects for the specified file space while server operation continues.

User response

To obtain status on the file space deletion process, issue the QUERY PROCESS command. The process may be canceled by an authorized administrator using the CANCEL PROCESS command.

ANR0805I The deletion for filespace name was canceled for node node name: number of objects objects were deleted, number of objects objects were retained, and number of objects objects were skipped.

Explanation

A background server process that was deleting file space data for the specified node was canceled by the CANCEL PROCESS command. The numbers of objects deleted, retained and skipped before the cancel ended the operation are reported in the message.

System action

Server operation continues, but the server process is ended.

User response

No action is required. An authorized administrator can issue the DELETE FILESPACE command to delete remaining objects from the file space.

ANR0806I File space filespace name was deleted for node node name: number of objects objects were deleted,number of objects objects were retained, and number of objects objects were skipped.

Explanation

A server process deleted file space data for the specified node. The numbers of deleted, retained, and skipped objects are reported in the message.

System action

The deletion process is complete, but server operations continue.

User response

No action is required.

ANR0811I Inventory client file expiration started as process process ID.

Explanation

The server has started roll-off processing to remove expired client backup and archive file copies, based on the management class policy that is bound to the files. The copy group retention and version parameters for each file's copy group are used by the server to determine if copies are to be deleted from the server. The expiration process was started as process number process ID, and may be queried or canceled with the QUERY PROCESS or CANCEL PROCESS commands, respectively.

System action

The expiration process is now cancellable. Server operation continues.

User response

None.

ANR0812I Inventory file expiration process process ID is completed: processed number of nodes nodes, examined number of objects objects, retained number of objects objects, deleted number of backup objects backup objects, number of archive objects archive objects, number of DB backup volumes database backup volumes, and number of recovery plan files recovery plan files. retry count objects were retried error count errors were detected, and skipped count objects were skipped.

Explanation

Server expiration processing is complete. The numbers of client objects examined, deleted and retained, based on management class policy, are displayed in the message. A total error count is also displayed. A count of objects skipped due to replication being required is also included. The number of database(DB) backup volumes that are deleted is based on the value specified by the SET DRMDBBACKUPEXPIREDAYS command. The number of recovery plan files that are deleted is based on the value specified by the SET DRMRPFEXPIREDAYS command. Server expiration processing deletes the DB backup volumes and recovery plan files only if the disaster recovery manager (DRM) function is licensed on the server and the volumes or plan files are created on the server to server virtual volumes.

System action

Server operation continues, but the roll-off process is ended.

User response

If the error count is not equal to 0, examine messages that might have been issued in the activity log to determine the cause of the errors.

ANR0813I Inventory file expiration process process ID was canceled prior to completion: processed number of nodes nodes, examined number of objects objects, retained number of objects objects, deleted number of backup objects backup objects, number of archive objects archive objects, number of DB backup volumes database backup volumes, and number of recovery plan files recovery plan files. retry count objects were retried error count errors were detected and skipped count objects were skipped.

Explanation

The inventory file expiration process was canceled by an administrator. The number of objects examined, deleted and retained prior to the cancellation are reported. The total error count and number of skipped objects are also displayed.

System action

The server ends the file expiration process.

User response

No action is required.

ANR0814I The deletion process for file space filespace name for node node name is complete, but not all objects were deleted. number of objects objects were deleted, number of objects objects were retained, and number of objects objects were skipped.

Explanation

A DELETE FILESPACE command has deleted file space data for the specified node, but did not delete every object belonging to the file space. The numbers of objects that were deleted, retained, and skipped are reported in the message.

System action

The deletion process is complete, but server operations continue.

User response

To determine why objects could not be deleted, review other messages issued by the process. If necessary, correct the problems and run the command again.

ANR0819I Cancel in progress

Explanation

This message is displayed in response to a QUERY PROCESS command, and indicates that an inventory expiration process has been canceled. The process will end shortly.

System action

The expiration process terminates and server operation continues.

User response

None.

ANR0820I Sorting information for number objects has been deleted.

Explanation

A background server process has deleted sorting information for number files from the server database. This process is started during initialization to remove any sorting information which is left over from previous export operations.

System action

The actual backup or archive objects were not deleted, but only information used to sort these objects during the previous export operation.

User response

None.

ANR0821E Filespace identifier fsId is not valid.

Explanation

The identifier assigned for a filespace is out of range.

System action

The file space is not added.

User response

Contact your service representative.

ANR0822I command: Filespace filespace name (fsId=filespace id) successfully renamed to new filespace name for node node name.

Explanation

The file space specified was renamed to the new name specified for the node. This message is displayed in response to successful completion of the RENAME FILESPACE command.

System action

The system renames the file space for the node as indicated

User response

None.

ANR0823E command: Filespace filespace name cannot be renamed to new filespace name, a filespace with this name already exists for node node name.

Explanation

The file space name specified as a target name for the command was found to already exist for the node specified. The command fails.

System action

Server operation continues, the command fails.

User response

Reissue the command with a different target filespace name

ANR0824I Delete Filespace filespace name (space-managed data) for node node name started.

Explanation

A background server process has started (on the server) to delete space-managed objects in the specified file space belonging to the node indicated. If a file space name is not included in the message, then the space-managed objects for all file spaces that belong to the node are deleted.

System action

The background process deletes space-managed objects for the specified file space while server operation continues.

User response

To obtain status on the file space deletion process, issue the QUERY PROCESS command. The process may be canceled by an authorized administrator using the CANCEL PROCESS command.

ANR0826I DELETE FILESPACE filespace name for node node name encountered a transaction failure.

Explanation

A background server process that has been deleting file space data for the indicated node encountered a transaction failure.

System action

The server process is retried if the maximum number of retry attempts have not been exceeded.

User response

Transaction failure usually indicates that a database deadlock was detected during file space deletion. These deadlock conditions are sometimes encountered when multiple file space deletion processes are running at the same time. No action is required unless the DELETE FILESPACE terminates without completing the deletion process (see message ANR0828).

ANR0827I DELETE FILESPACE filespace name will be retried for node node name.

Explanation

A file space deletion process for the node indicated is being retried because an error was encountered.

System action

The server process is retried.

User response

None.

ANR0828W The deletion of filespace name for node node name ended before completion due to transaction failure: number of objects objects were deleted, number of objects objects were retained, and number of objects objects were skipped.

Explanation

A background server process that was deleting file space data for the specified node is ended prematurely because of a transaction failure. A transaction failure usually indicates a database deadlock was detected during file space deletion. These deadlock conditions can occur when multiple file space deletion processes run at the same time. The numbers of objects deleted, retained, and skipped before the DELETE FILESPACE operation ended are reported in the message.

System action

Server operation continues, but the server process is ended.

User response

To resolve the problem, take one or both of the following actions:
  • -Restart the command when fewer file space deletion processes are active.
  • -Issue the DELETE FILESPACE command to delete remaining files in the file space or file spaces.

ANR0829E Command: Invalid combination of TYPE and DATA parameters.

Explanation

The specified command has been issued with an invalid combination of the TYPE and DATA parameters. DATA=IMAGES can only be specified if TYPE=ANY or TYPE=BACKUP.

System action

Server operation continues, but the command is not processed.

User response

Issue the command and specify a valid combination of parameters.

ANR0830W Management class class name in domain domain name used by node node name in file space filespace name is no longer active, or no longer has a BACKUP copy group: DEFAULT management class attributes will be used for expiration.

Explanation

During policy roll-off processing, the server has found a client file copy whose management class or backup copy group no longer exists.

System action

The server obtains the DEFAULT management class for the specified domain and uses its backup copy group version and retention parameters to determine if file copies need to be expired.

User response

No action is required. A policy administrator with authority over the specified domain may use the DEFINE COPYGROUP, DEFINE MGMTCLASS, and ACTIVATE POLICY commands to define and activate a policy set that contains definitions for the missing management class or copy group.

ANR0831W The DEFAULT management class class name in domain domain name does not have a BACKUP copy group: GRACE PERIOD will be used for expiration.

Explanation

During policy roll-off processing, the server found a client file copy whose management class or backup copy group no longer exists. The DEFAULT management class for the indicated policy domain does not contain a backup copy group; therefore, the server uses the GRACE PERIOD retention value defined for the specified policy domain to determine if client file copies need to be expired and removed from the server database.

System action

The server obtains the GRACE PERIOD retention values for the specified domain and then determines if backup file copies need to be expired.

User response

No action is required. A policy administrator with authority over the specified domain may use the DEFINE COPYGROUP, DEFINE MGMTCLASS, and ACTIVATE POLICY commands to define and activate a policy set that contains definitions for the missing management class or backup copy group.

ANR0832W Management class class name in domain domain name used by node node name in filespace filespace name is no longer active, or no longer has an ARCHIVE copy group: DEFAULT management class attributes will be used for expiration.

Explanation

During policy roll-off processing, the server found a client file copy whose management class or archive copy group no longer exists.

System action

The server obtains the DEFAULT management class for the specified domain and uses its archive copy group retention parameter to determine if file copies need to be expired.

User response

No action is required. A policy administrator with authority over the specified domain may use the DEFINE COPYGROUP, DEFINE MGMTCLASS, and ACTIVATE POLICY commands to define and activate a policy set that contains definitions for the missing management class or copy group.

ANR0833W The DEFAULT management class class name in domain domain name does not have an ARCHIVE copy group: GRACE PERIOD will be used for expiration.

Explanation

During policy roll-off processing, the server found a client file copy whose management class or archive copy group no longer exists. The DEFAULT management class for the indicated policy domain does not contain an archive copy group; therefore, the server uses the GRACE PERIOD retention value defined for the specified policy domain to determine if client file copies need to be expired and removed from the server database.

System action

The server obtains the GRACE PERIOD retention values for the specified domain and then determines if archive file copies need to be expired.

User response

No action is required. A policy administrator with authority over the specified domain may use the DEFINE COPYGROUP, DEFINE MGMTCLASS, and ACTIVATE POLICYSET commands to define and activate a policy set that contains definitions for the missing management class or backup copy group.

ANR0834W Inventory client file expiration cannot start because of insufficient memory - will retry in number of seconds seconds.

Explanation

The server inventory expiration process is pausing to retry an operation that failed because sufficient memory is not available on the server.

System action

Server operation continues; the expiration process will be retried after the stated delay.

User response

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

ANR0835W Management class class name in domain domain name is no longer active, or no longer has a BACKUP copy group, or no longer has an ARCHIVE copy group. DEFAULT management class used to delete number of backup files backup files and number of archive files archive files. Retention grace period used to delete number of backup files backup files and number of archive files archive files.

Explanation

During policy roll-off processing, the server found a management class or backup copy group or archive copy group that no longer exists. When a management class or backup copy group no longer exists, the number of backup client file copies that have been deleted using the default management class or the retention grace period is displayed in the message. When a management class or archive copy group no longer exists, the number of archive client files that have been deleted using the default management class or the retention grace period is displayed in the message.

System action

The server obtains the DEFAULT management class for the specified domain and uses its backup copy group or archive copy group version and retention parameters to determine if file copies need to be expired. If, however, the needed backup copy group or archive copy group does not exist in the DEFAULT management class, the server will use the retention grace period for the domain.

User response

No action is required. This message is only issued when expiration processing has been started with the QUIET option to suppress detailed messages. Expiration processing can be started without the QUIET option to see the detailed messages which will indicate specific node and filespaces and will further distinguish between backup and archive copy groups. A policy administrator with authority over the specified domain may use the DEFINE COPYGROUP, DEFINE MGMTCLASS, and ACTIVATE POLICY commands to define and activate a policy set that contains definitions for the missing management class or copy group.

ANR0836W No query restore processing session session id for node node name and filespace name failed to retrieve file high-level file namelow-level file name - file being skipped.

Explanation

The no query restore processing for the session listed relating to the specified node name and filespace failed to retrieve the specified file. An error occurred while retrieving this file so it will be skipped.

System action

The no query restore operation continues.

User response

Determine the cause of the file retrieve failure and correct it. After this situation is correct, the client can do a restore of the specific file that was skipped.

ANR0837I Inventory file expiration process process ID was terminated after exceeding the duration limit of duration minutes: processed number of nodes nodes, examined number of objects objects, retained number of objects objects, deleted number of backup objects backup objects, number of archive objects archive objects, number of DB backup volumes database backup volumes, and number of recovery plan files recovery plan files. retry count objects were retried, error count errors were encountered and skipped count objects were skipped.

Explanation

An administrator or schedule issued the EXPIRE INVENTORY command and specified the DURATION parameter. The value specified for the DURATION parameter is the number of minutes allotted to the expire inventory process. When the specified number of minutes is reached, the expire inventory process ends.

System action

The expire inventory process ends.

User response

No action is required.

ANR0844E Command: node name is not a backup-archive node.

Explanation

The specified node name is not a backup-archive node.

System action

Processing fails for the command. Server operation continues.

User response

Reissue the command with a valid node name.

ANR0848W Expiration failed to delete file type file file name for node node name and filespace filespace name - file will be skipped.

Explanation

The expiration process was unable to delete the indicated file. The file will be skipped by expiration.

System action

The expiration process continues.

User response

Try expiration again to determine if the cause of the deletion failure was an intermittent problem or if it is a permanent problem. If after a subsequent expiration attempt the file still is not deleted, contact your service representative.

ANR0849E Command: Not permitted for node Node Name - node of type SERVER.

Explanation

The indicated DELETE FILESPACE process is not started because the node specified is of NODETYPE=SERVER. A DELETE FILESPACE may only be processed for nodes of this type with the TYPE=SERVER parameter specified.

System action

The DELETE FILESPACE command is ended and server processing continues.

User response

If this filespace must be deleted, Reissue the command with the TYPE parameter set to TYPE=SERVER. Please use caution when using the TYPE=SERVER parameter as this can impact the availability of data for the server that owns these files.

ANR0850E Command: Cannot Start process name Process.

Explanation

The indicated DELETE FILESPACE process cannot be started on the server.

System action

The DELETE FILESPACE command is ended and server processing continues.

User response

This usually indicates that sufficient server memory is not available on the server.

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

ANR0851E Cannot start delete file space thread for node node name.

Explanation

The indicated DELETE FILESPACE process cannot be started on the server. Sufficient memory on the server may not be available.

System action

The DELETE FILESPACE command is ended and server processing continues.

User response

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

ANR0852E Command: No matching file spaces found for node node name.

Explanation

The server did not find any file spaces for the node indicated matching the names specified in the command.

System action

The server ends the command.

User response

Enter the command with file space names that refer to defined file spaces for the specified node. Note that file space names are case sensitive. Enter them by using exactly the same uppercase and lowercase characters that match the file space name defined on the server. Use the QUERY FILESPACE command to determine which file spaces are defined for a node on the server.

ANR0853E Transaction failed in file space deletion, DELETE FILESPACE process aborted.

Explanation

A database transaction fails while the server is deleting file space data.

System action

The server ends the file space deletion process.

User response

Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0854E Inventory file space query failure, DELETE FILESPACE process aborted.

Explanation

The server encounters an error in querying the inventory database during a file space deletion process.

System action

The server ends the file space deletion process.

User response

Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0855E Server LOG space exhausted, DELETE FILESPACE process aborted.

Explanation

Insufficient server log space has been encountered during file space deletion processing.

System action

The server ends the file space deletion process.

User response

To increase the amount of log space that is available to the server, evaluate the directories and file systems that are assigned to the ACTIVELOGDIRECTORY, ARCHIVELOGDIRECTORY, and ARCHFAILOVERLOGDIRECTORY options in the dsmserv.opt file. An out of log space condition might occur because the ACTIVELOGDIRECTORY location is full.

Alternatively, an out of log space condition might occur if there are log files in the ACTIVELOGDIRECTORY location that are no longer active and cannot be archived to the ARCHIVELOGDIRECTORY and ARCHFAILOVERLOGDIRECTORY locations. If necessary, specify a larger directory for the ARCHIVELOGDIRECTORY or ARCHFAILOVERLOGDIRECTORY options in the dsmserv.opt file and then restart the server.

ANR0856E Server database space exhausted, DELETE FILESPACE process aborted.

Explanation

Insufficient server database space has been encountered during file space deletion processing.

System action

The server ends the file space deletion process.

User response

To increase the amount of database space that is available to the server, issue the EXTEND DBSPACE command to add one or more directories to the database.

ANR0859E Data storage object erasure failure, DELETE FILESPACE process aborted.

Explanation

The server encounters an error in removing file copies from data storage during file space deletion processing.

System action

The server ends the file space deletion process.

User response

Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0860E Expiration process process ID ended due to an internal error: examined number of objects objects, retained number of objects objects, deleted number of backup objects backup objects, number of archive objects archive objects, number of DB backup volumes database backup volumes, and number of recovery plan files recovery plan files. retry count objects were retried and error count errors were detected.

Explanation

The server detected an internal error during file expiration processing. The numbers of files that were examined and deleted prior to the error are reported. A total error count is also displayed.

System action

The server ends the expiration process.

User response

Examine the server messages that are issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If you cannot resolve the error, contact IBM Software Support.

ANR0861E Transaction failed in expiration, inventory expiration aborted.

Explanation

The server encounters a database transaction failure during policy roll-off processing.

System action

The server ends roll-off processing.

User response

Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0865E Expiration processing failed - internal server error.

Explanation

Server retry processing during policy roll-off fails.

System action

The server ends policy roll-off processing.

User response

Issue the QUERY ACTLOG command to view the activity log and search for messages. Examine the server messages issued prior to this message to determine the source of the error.

The following issues can cause this message to occur:
  • The server is out of database space. To increase the amount of database space that is available to the server, issue the EXTEND DBSPACE command to add one or more directories to the database.
  • The server is out of log space. To increase the amount of log space that is available to the server, evaluate the directories and file systems that are assigned to the ACTIVELOGDIRECTORY, ARCHIVELOGDIRECTORY, and ARCHFAILOVERLOGDIRECTORY options in the dsmserv.opt file. An out of log space condition might occur because the ACTIVELOGDIRECTORY location is full. Alternatively, an out of log space condition might occur if there are log files in the ACTIVELOGDIRECTORY location that are no longer active and cannot be archived to the ARCHIVELOGDIRECTORY and ARCHFAILOVERLOGDIRECTORY locations. If necessary, specify a larger directory for the ARCHIVELOGDIRECTORY or ARCHFAILOVERLOGDIRECTORY options in the dsmserv.opt file and then restart the server.
  • The server is low on memory. To increase the amount of memory that is available to the server, see the operating system documentation that describes how to increase memory for an application.

If the error cannot be isolated and resolved, contact your service representative.

ANR0866E Expiration processing retries failed - no success after maximum retries retries.

Explanation

Server policy roll-off processing ends because retry processing has not been successful in expiring client file copies from the server database.

System action

The server ends policy roll-off processing and server operation continues.

User response

Issue the QUERY ACTLOG command to view the activity log and search for messages. Examine the server messages issued prior to this message to determine the source of the error.

The following issues can cause this message to occur:
  • The server is out of database space. To increase the amount of database space that is available to the server, issue the EXTEND DBSPACE command to add one or more directories to the database.
  • The server is out of log space. To increase the amount of log space that is available to the server, evaluate the directories and file systems that are assigned to the ACTIVELOGDIRECTORY, ARCHIVELOGDIRECTORY, and ARCHFAILOVERLOGDIRECTORY options in the dsmserv.opt file. An out of log space condition might occur because the ACTIVELOGDIRECTORY location is full. Alternatively, an out of log space condition might occur if there are log files in the ACTIVELOGDIRECTORY location that are no longer active and cannot be archived to the ARCHIVELOGDIRECTORY and ARCHFAILOVERLOGDIRECTORY locations. If necessary, specify a larger directory for the ARCHIVELOGDIRECTORY or ARCHFAILOVERLOGDIRECTORY options in the dsmserv.opt file and then restart the server.
  • The server is low on memory. To increase the amount of memory that is available to the server, see the operating system documentation that describes how to increase memory for an application.

If the error cannot be isolated and resolved, contact your service representative.

ANR0867E Unable to open policy domain for node node name during server operation.

Explanation

Policy roll-off processing on the server encounters an error while obtaining policy information related to the specified node.

System action

The server ends roll-off processing and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0868E Cannot find management class name for ID management class ID.

Explanation

Policy roll-off processing on the server encounters an error while obtaining policy information.

System action

The server ends roll-off processing and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0869E Cannot find policy domain for node node ID.

Explanation

Policy roll-off processing on the server encounters an error while obtaining policy information related to the specified node.

System action

The server ends roll-off processing and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0870E Cannot find node name for node node ID.

Explanation

Policy roll-off processing on the server encounters a database error in obtaining information for a client node.

System action

The server ends roll-off processing and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0871E Cannot find file space name for node node ID, file space file space ID.

Explanation

Policy roll-off processing on the server encounters a database error in obtaining information for a client node.

System action

The server ends roll-off processing and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0872E Grace Period retention for domain domain name could not be obtained.

Explanation

Policy roll-off processing on the server encounters a database error in obtaining GRACE PERIOD values for the specified policy domain.

System action

The server ends roll-off processing and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0873E Invalid copy type encountered in expiring files: copytype ID

Explanation

Policy roll-off processing on the server encounters a database error in obtaining copy group information.

System action

The server ends roll-off processing and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0874E Backup object object not found during inventory processing.

Explanation

Inventory processing on the server encounters a database error in obtaining backup information in data storage.

System action

The server ends roll-off processing, or client session(s) and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0875E Archive object object.ID not found during expiration processing.

Explanation

Policy roll-off processing on the server encounters a database error in obtaining archive information in data storage.

System action

The server ends roll-off processing and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0879E Error opening inventory file space query.

Explanation

Policy roll-off processing on the server encounters a database error in accessing inventory information.

System action

The server ends roll-off processing and server operation continues.

User response

Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. If the error cannot be isolated and resolved, contact your service representative.

ANR0880E Filespace command: No matching file spaces.

Explanation

The server did not find any file space names matching the specifications entered in the filespace command.

System action

Server operation continues.

User response

Use the QUERY FILESPACE command to determine which file spaces are defined on the server. Note, that file space names are case sensitive. Reissue the file space command and specify the proper file space name (in proper case).

ANR0881E Policy Error : the GRACE PERIOD archive retention value could not be obtained for domain domain ID during client inventory processing.

Explanation

The server encounters an internal error in accessing policy information.

System action

The operation is ended and server operation continues.

User response

Contact your service representative.

ANR0882E Policy Error: Unable to open policy domain for node node name during client inventory query processing.

Explanation

The server encounters an internal error in accessing policy information.

System action

The client operation is ended and server operation continues.

User response

Contact your service representative.

ANR0883E Cannot obtain node name for node node ID.

Explanation

The server encounters an internal error in accessing client node information.

System action

The operation is ended and server operation continues.

User response

Contact your service representative.

ANR0884E Error code during deletion of sorting information for number objects.

Explanation

A background server process encountered an internal error after deleting sorting information for number files from the server database. This process is started during initialization to remove any sorting information which is left over from previous export operations.

System action

The backup or archive objects were not deleted. Only the information used to sort these objects during the previous export operation was deleted. The background process was terminated before all sorting information had been deleted. The system will not perform further export processing of file data until this problem has been resolved.

User response

Examine the server messages issued prior to this message to determine the source of the error. Issue the QUERY ACTLOG command to view the activity log and search for messages. Then restart the server. If the error cannot be isolated and resolved, contact your service representative.

ANR0885I Import command: Processing management class management class name for domain domain name and policy set policy set name as management class new management class name.

Explanation

The background import process to service the command import command is currently processing the policy information for management class management class name in domain domain name and policy set policy set name. The management class is imported under the name new management class name. During import processing, management classes defined as either DEFAULT or GRACE_PERIOD must be renamed so that the management class does not conflict with existing server policy conventions. Import processing is then able to import file data by using the renamed management class.

System action

Import processing for the command continues.

User response

None. However, an administrator may want to examine the policy definitions for new management class name so they are aware of the management classes that may be used if the policy set containing this management class is activated.

ANR0886E Management class class name in domain domain name used by node node name in file space filespace name has no BACKUP copy group with id copy group id; Expiration will not be performed for files from this node and filespace that are bound to this management class and copy group id.

Explanation

During policy roll-off processing, the server finds a client file copy with a management class or a backup copy group that no longer exists.

System action

The server skips the files in error.

User response

For programming support, contact your service representative.

ANR0887E Management class class name in domain domain name used by node node name in file space filespace name has no archive copy group with id copy group id. Server operation will not be performed for files from this node and filespace that are bound to this management class and copy group id.

Explanation

During policy roll-off processing, the server finds a client file copy with a management class or an archive copy group that no longer exists.

System action

The server skips the specified files.

User response

For programming support, contact your service representative.

ANR0888E SQL commands cannot be issued from the server console.

Explanation

An SQL command was issued from the server console. SQL commands cannot be issued from the server console because they may require a long time complete and the server console should be available to control other server functions.

System action

The server ignores the command and continues processing.

User response

Issue the SQL command from an administrative client.

ANR0889I Deleted count statistics reports about data deduplication for node node name.

Explanation

The server processed DELETE DEDUPSTATS for the specified node, with the total number of deleted statistics reports about data deduplication specified in this message.

System action

The deletion of data deduplication statistics is complete for the node, and server operations continue.

User response

None.

ANR0890I Export/import command: Processing optionset optionset name.

Explanation

The background export or import process to service the command export/import command is currently processing optionset definition information.

System action

Export or import processing for the command continues.

User response

None.

ANR0891I Export/import command: Copied number optionset definitions.

Explanation

The background export or import process to service the command export/import command copies number client optionset definitions from the server database to export media or from export media into the server database. Data is not moved if Preview=Yes is specified in the command export/import command.

System action

Export or import processing for the command completes. Server operation continues.

User response

None.

ANR0892I Export command: No matching optionsets found for exporting.

Explanation

The background export process does not find any client optionsets for export command.

System action

The export process continues and no option sets from the server.

User response

None.

ANR0893I Are you sure that you want to accept the current system date as valid ?

Explanation

This message is displayed when the ACCEPT DATE command has been issued to confirm that you want to accept the date on the system as valid. Accepting an invalid date can cause any of the following problems:
Premature deletion of data
Excessive retention of data
Scheduling problems
Event record problems
Password expiration problems.

System action

The command waits for you to confirm the action.

User response

Specify Yes if you want to accept the system date as valid, or No if you do not want to execute the command.

ANR0894I Current system has been accepted as valid.

Explanation

This message is displayed when the ACCEPT DATE command has been issued and the date has been accepted as valid by the server.

System action

The current system date is accepted as valid by the server. The server will begin processing using the current system date.

User response

Issue the ENABLE SESSIONS ALL command to allow client, server and administrative sessions to start.

ANR0895E Command: Cannot Start process name Process.

Explanation

The indicated process cannot be started on the server.

System action

The specified command is ended and server processing continues.

User response

This usually indicates that sufficient server memory is not available on the server.

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

ANR0896I Generated count statistics reports about data deduplication for node node name in pool pool name.

Explanation

The server processed GENERATE DEDUPSTATS for the specified node and pool, with the total number of generated statistics reports about data deduplication specified in this message.

System action

The generation of data deduplication statistics is complete for the node and pool specified in the command, and server operations continue.

User response

None.

ANR0900I Processing options file filespec.

Explanation

At server initialization, the server is reading the server options file whose name is shown in the message.

System action

The server reads and processes the options in this file.

User response

None.

ANR0901W Invalid option statement found in file filespec.

Explanation

While processing the server options file named, the server has encountered an invalid statement. The invalid statement type is shown in the message. The lines following this message provide more information.

System action

The server ignores the statement in error. Server initialization continues. The default value is used for any missing or ignored options.

User response

Ignore the error, or use a text editor to correct the error and restart the server.

ANR0902W Unsupported keyword or invalid value found in file filespec.

Explanation

While processing the server options file named, the server has encountered an invalid keyword or an invalid value on an option statement. The lines following this message provide more information.

System action

The server ignores the option statement in error. Server initialization continues. The default value is used for any missing or ignored options.

User response

Ignore the error, or use a text editor to correct the error and restart the server.

ANR0905W Options file filespec not found.

Explanation

At server initialization, the server is unable to locate the server options file named.

System action

The server uses the default values for all options. Server initialization continues.

User response

If the default values are acceptable, ignore the error. Otherwise, move a valid server options file to the proper location, rename a valid options file to the proper name, or use a text editor to build the proper server options file, and then restart the server.

ANR0914E Diagnostic(ID): a request failed because object (object name), size (size), exceeds the maximum size of maximum size.

Explanation

The size of the specified object exceeds the maximum size defined for that object. The server cannot handle the new object.

System action

The activity that generated this error fails.

User response

Determine why the new object's length exceeds the maximum specified for the object. Reduce the length of the object.

ANR0915E Unable to open language language name for message formatting.

Explanation

The server is unable to open the specified message repository.

System action

Server initialization continues with the default message repository.

User response

Ensure that a valid language is specified in the LANGUAGE option of the server options file. If a change is made to the options file, restart the server to activate changes.

ANR0916I Product Name distributed by Company is now ready for use.

Explanation

The server has completed startup processing and is now ready for use.

System action

None.

User response

None.

ANR0917W Session session number for node node name (client platform) - in domain domain name failed because of policy length.

Explanation

The client cannot handle very long policies.

System action

The client operation is ended and server operation continues.

User response

Upgrade the client to the latest level, or activate a policy set with fewer management classes.

ANR0918E Inventory operation for node node name terminated - lock conflict.

Explanation

During the indicated operation, the server needs to obtain a lock that is not available.

System action

The indicated operation ends.

User response

Restart the operation.

ANR0919E Filespace name fsName with length length was encountered for nodes node list.

Explanation

The specified filespace name was found for the nodes in the list. The name is not allowed. The error may occur while processing an administrative command or client request.

System action

Server processing continues.

User response

If the error occurs during processing for an administrative command such as EXPORT NODE or RENAME FILESPACE, rename the filespace for the nodes in the list using a valid name. If found while processing a client request, contact your service representative.

ANR0920I Tracing is now active to standard output.

Explanation

In response to a TRACE START command, server trace records are being written to the standard output destination (usually the server console).

System action

None.

User response

None.

ANR0921I Tracing is now active to file file spec.

Explanation

In response to a TRACE START command, server trace records are being written to the file named.

System action

None.

User response

None.

ANR0922I Trace ended.

Explanation

In response to a TRACE END command, server trace records are no longer being written.

System action

None.

User response

None.

ANR0923E Tracing is inactive.

Explanation

A TRACE END command has been entered, but tracing is not active.

System action

The command is ignored.

User response

If tracing is desired, use the TRACE ENABLE and TRACE START commands to activate server tracing.

ANR0924E Tracing is already active to file file spec.

Explanation

A TRACE BEGIN command has been entered, but tracing is already active to the file named.

System action

The command is ignored.

User response

If the current trace output file is acceptable, no action is required. Otherwise use the TRACE END command to stop tracing and then reissue the TRACE BEGIN command as desired.

ANR0925E Tracing is already active to standard output.

Explanation

A TRACE BEGIN command has been entered, but tracing is already active to the standard output destination (usually the server console).

System action

The command is ignored.

User response

If the current trace output destination is acceptable, no action is required. Otherwise use the TRACE END command to stop tracing and then reissue the TRACE BEGIN command as desired.

ANR0926E command name: The MERGEFILESPACES=YES parameter value cannot be specified for file spaces that have data in retention sets.

Explanation

During an IMPORT NODE or the IMPORT SERVER operation, the server detected a file space that has retention set data associated with it. When you issue the IMPORT NODE or IMPORT SERVER command, the MERGEFILESPACES=YES parameter value cannot be specified for file spaces that have data that is included in retention sets.

System action

Server operation continues, but the import command fails.

User response

To resolve the issue, complete the following steps:
  1. To determine which file spaces have data in retention sets, issue the QUERY RETSET command.
  2. To import data from file spaces that have data in retention sets, issue the IMPORT NODE command for those file spaces and specify the MERGEFILESPACES=NO parameter value.

ANR0927E Unknown trace class keyword - class.

Explanation

A TRACE ENABLE command has been entered which specifies an unknown trace class.

System action

The command is ignored.

User response

Reissue the TRACE command with the correct class.

ANR0928E Unable to open trace file file spec for appending.

Explanation

A TRACE BEGIN command specifies an output file, but the server cannot write to that file.

System action

The command is ignored.

User response

Check the file for proper access permissions, or reissue the TRACE command specifying a different output file.

ANR0929E Insufficient memory to activate tracing.

Explanation

A TRACE BEGIN command has been entered, but the server has insufficient memory available to activate tracing.

System action

The command is ignored.

User response

If tracing is required, make more memory available to the server then restart the server.

ANR0936E Session session ID for session name failed sending verb verb name because client not able to handle extended qualifier attribute.

Explanation

A server was going to send the reported verb for the indicated session but was not able to send it. The verb could not be sent to the client because it contains extended information about the low-level qualifier. The extended low-level qualifier is used to store names up to 512 bytes in length. The client that this verb was supposed to be sent to does not support the extented low-level qualifier information.

System action

The send of the verb to the reported session fails and this server operation will fail and report a communication error.

User response

The client session reported needs to have the installed client upgraded to IBM Spectrum Protect version 5.1.5 or higher in order to support the extended low-level qualifier.

ANR0937I Expiration process process ID is ending.

Explanation

The expiration process referenced is ending either because it has been cancelled or because it has completed the necessary actions. This message is only issued in the case where expiration was processing a long-running operation, such as deleting a group of related files (for example, a backup group). This message indicates the time when the long-running operation ended.

System action

None.

User response

None.