Unable to determine operating system platform using command: command
Explanation: The server attempted to determine the platform of an operating system resource, but was not successful. The specified Tivoli Framework command was run by the server, but did not produce a valid value.
Message Inserts:
System Action: The operating system resource is placed under a default platform aggregate.
Operator Response: Run the specified Tivoli Framework command outside the context of the server and try to determine the reason for the failure. If you cannot resolve the problem, contact your system programmer.
System Programmer Response: Run the specified Tivoli Framework command outside the context of the server and try to determine the reason for the failure. If you cannot resolve the problem, contact your Tivoli Support Center.
A blank host name was encountered. No system resource is created.
Origin: origin
Suborigin: suborigin
Explanation: The server was trying to create a system resource from a heartbeat or system monitor event, but the host name passed in the event was blank. A system resource cannot be created from this event.
Message Inserts:
System Action: A system resource is not created for the heartbeat or system monitor event. For heartbeat events, the corresponding business resource will not reflect any status information for the operating system on which it is running.
Operator Response: No response is necessary if system information is not required for the resources in question.
If you want system information to be shown, then a host name must be provided with the events:
While writing to the databases, a string was truncated to the maximum length of maximum length. This may cause unexpected results if you continue to use the databases. Truncated string: string
Explanation: Strings associated with database resources, such as the display name, are limited to the specified number of characters when written to disk. The string committed to the database was longer than the specified number of characters characters and was truncated.
Message Inserts:
System Action: The topology server continues to operate normally, unless you were shutting down when the databases were being written. If you continue to use the databases without removing the corrupted resource, unexpected results may occur. Your results will depend on which string is truncated and how that string gets used by the topology server.
Operator Response: Do the following:
An invalid parameter was passed to the AMP open routine.
AMP Filename: AMPFilename
Replace the AMP file, and if the problem persists, contact the Tivoli Support Center.
Explanation: The topology server or ihsaunpk command line utility attempted to open an AMP file, but the open failed due to an invalid parameter. This is probably caused by an AMP file that is not valid.
Message Inserts:
System Action: The action being attempted on the AMP file was not completed successfully.
Operator Response: Ensure that the AMP file is valid and retry the operation. One test of validity is to run the ihsaunpk utility with the -v parameter in order to list its contents.
An attempt was made to open an AMP file whose format is not valid.
Filename: AMPFilename
Replace the AMP file and, if the problem persists, contact the provider of the AMP.
Explanation: The topology server or ihsaunpk command line utility attempted to open an AMP file whose format is not valid.
Message Inserts:
System Action: The action being attempted on the AMP file was not completed successfully.
Operator Response: Ensure that the AMP file is valid, replacing it if necessary, and retry the operation. One test of validity is to run the ihsaunpk utility with the -v parameter in order to list its contents.
An internal error occurred while processing an AMP file.
AMP Filename: AMPFilename
Explanation: The topology server or ihsaunpk command line utility encountered an internal error while processing an AMP file.
Message Inserts:
System Action: The action being attempted on the AMP file was not completed successfully.
Operator Response: Ensure that the AMP file is valid, replacing it if necessary, and retry the operation. One test of validity is to run the ihsaunpk utility with the -v parameter in order to list its contents.
A CRC error was detected while opening an AMP file.
AMP Filename: AMPFilename
Explanation: The topology server or ihsaunpk command line utility detected a CRC error indicating that the AMP file being processed is not valid.
Message Inserts:
System Action: The action being attempted on the AMP file was not completed successfully.
Operator Response: Ensure that the AMP file is valid, replacing it if necessary, and retry the operation. One test of validity is to run the ihsaunpk utility with the -v parameter in order to list its contents.
A syntax error was encountered in the AMP unpacking configuration file.
Filename: AMPUnpackingConfigFilename
Line number: lineNumber
Explanation: The topology server or ihsaunpk utility read a line from the AMP unpacking configuration file whose syntax was not valid.
Message Inserts:
System Action: The line with the syntax error and any lines that follow it in the AMP unpacking configuration file are not processed. The AMP files being processed may have been processed successfully, but not according to the rules specified in the AMP file unpacking configuration file.
Operator Response: Correct the syntax error in the AMP unpacking configuration file and retry the operation.
An error occurred opening the AMP unpacking configuration file.
Filename: AMPUnpackingConfigFilename
Explanation: The topology server or ihsaunpk utility could not open the AMP unpacking configuration file.
Message Inserts:
System Action: The action requested on the AMP file is performed using the default AMP file unpacking rules.
Operator Response: Check the file permissions on the AMP file unpacking configuration file and change them if necessary. Ensure that the file is not locked by some other application.
An error occurred opening an AMP file.
AMP Filename: AMPFilename
Explanation: The topology server or ihsaunpk utility was unable to open the specified AMP file.
Message Inserts:
System Action: The action requested on the specified AMP file was not performed.
Operator Response: Check the file permissions on the AMP file unpacking configuration file and change them if necessary. Ensure that the file is not locked by some other application. Ensure that the AMP file is valid, replacing it if necessary, and retry the operation. One test of validity is to run the ihsaunpk utility with the -v parameter in order to list its contents.
An error occurred while closing an AMP file.
AMP Filename: AMPFilename
Replace the AMP file and if the problem persists contact Tivoli Service.
Explanation: The topology server or ihsaunpk utility was unable to close the specified AMP file after processing it.
System Action: The action requested on the specified AMP file may or may not have been performed successfully.
Operator Response: Make sure that the file has not been locked by some other application. Terminate the program that generated this message and retry the operation.
An error occurred getting the global information from an AMP file.
AMP Filename: AMPFilename
Explanation: The topology server or ihsaunpk utility was unable to access the global information in the specified AMP file.
Message Inserts:
System Action: The action requested on the AMP file is not performed.
Operator Response: Ensure that the specified file is a valid AMP file and retry the operation. The most likely cause of this error is a corrupted AMP file or attempting an AMP file operation on a file that is not an AMP file.
An error occurred getting the information for an entry in an AMP file.
AMP Filename: AMPFilename
Explanation: The topology server or ihsaunpk utility was unable to access the information for an AMP file entry in the specified AMP file.
Message Inserts:
System Action: The requested action is not successfully performed on the specified AMP file.
Operator Response: Ensure that the specified file is a valid AMP file and retry the operation. The most likely cause of this error is a corrupted AMP file or attempting an AMP file operation on a file that is not an AMP file.
An error occurred seeking to an entry in an AMP file.
AMP Filename: AMPFilename
Previous entry name: PreviousEntryName
Explanation: The topology server or ihsaunpk utility was unable to access the information for an AMP file entry in the specified AMP file.
Message Inserts:
System Action: The requested action is not performed successfully on the specified AMP file.
Operator Response: Ensure that the specified file is a valid AMP file and retry the operation. The most likely cause of this error is a corrupted AMP file or attempting an AMP file operation on a file that is not an AMP file.
An error occurred while extracting an entry from an AMP file.
AMP Filename: AMPFilename
Entry name: AMPEntryName
Explanation: The topology server or ihsaunpk utility encountered an error while trying to extract the specified entry from the specified AMP file.
Message Inserts:
System Action: The specified entry is not extracted from the specified AMP file.
Operator Response: Ensure that the specified file is a valid AMP file and retry the operation. The most likely cause of this error is a corrupted AMP file or attempting an AMP file operation on a file that is not an AMP file.
An error occurred while closing an entry in an AMP file.
AMP Filename: AMPFilename
Entry name: AMPEntryName
Explanation: The topology server or ihsaunpk utility encountered an error while trying to close the specified entry in the specified AMP file.
Message Inserts:
System Action: The requested action may or may not have been performed on the specified AMP file.
Operator Response: Ensure that the specified file is a valid AMP file and retry the operation. The most likely cause of this error is a corrupted AMP file or attempting an AMP file operation on a file that is not an AMP file.
An error occurred during AMP file extraction while opening a target file.
Target Filename: targetFilename
Explanation: The topology server or ihsaunpk utility encountered an error opening the specified target file while trying to extract an entry from an AMP file.
Message Inserts:
System Action: The specified target file is not written and the corresponding AMP entry is not extracted.
Operator Response: Ensure that the specified target file is a valid filename and that the subdirectory in which it should reside actually exists. Also ensure that the file permission settings on the subdirectory and the target file itself will allow the file to be created or overwritten. If the target filename was acquired from the AMP unpacking configuration file and is not correct, make corrections to the AMP unpacking configuration file. Then retry the operation.
An error occurred during AMP file extraction while writing to a target file.
Target Filename: targetFilename
Explanation: The topology server or ihsaunpk utility encountered an error writing to the specified target file while trying to extract an entry from an AMP file.
Message Inserts:
System Action: The specified target file is not successfully written and the corresponding AMP entry is not completely extracted.
Operator Response: Ensure that the specified target file is a valid filename and that the subdirectory in which it should reside actually exists. Also ensure that the file permission settings on the subdirectory and the target file itself will allow the file to be created or overwritten. If the target filename was acquired from the AMP unpacking configuration file and is not correct, make corrections to the AMP unpacking configuration file. Ensure that the target disk is not full. Then retry the operation.
An error occurred during AMP file extraction while closing a target file.
Target Filename: targetFilename
Explanation: The topology server or ihsaunpk utility encountered an error closing the specified target file while trying to extract an entry from an AMP file.
Message Inserts:
System Action: The specified target file may not be successfully written and the corresponding AMP entry may not be not completely extracted.
Operator Response: Ensure that the specified target file is a valid filename and that the subdirectory in which it should reside actually exists. Also ensure that the file permission settings on the subdirectory and the target file itself will allow the file to be created or overwritten. If the target filename was acquired from the AMP unpacking configuration file and is not correct, make corrections to the AMP unpacking configuration file. Ensure that the target disk is not full. Then retry the operation.
A file was successfully created from an AMP file entry.
AMP Filename: AMP_filename
Entry name: AMPEntryName
File created: FileCreated
Explanation: The topology server or ihsaunpk utility successfully extracted the specified entry from the specified AMP file and created the specified file.
Message Inserts:
System Action: An entry is extracted from the AMP file and a new file is created.
A file was successfully overwritten by an AMP file entry.
AMP Filename: AMP_filename
Entry name: AMPEntryName
File overwritten: FileOverwritten
Explanation: The topology server or ihsaunpk utility successfully extracted the specified entry from the specified AMP file and overwrote the specified file.
Message Inserts:
System Action: An entry is extracted from the AMP file and an older file is overwritten.
AMP entry was not extracted.
AMP entry is not newer than the target file.
AMP Filename: AMP_filename
Entry name: AMPEntryName
Target Filename: targetFilename
Explanation: The topology server or ihsaunpk utility did not extract the specified entry from the specified AMP file because the AMP file entry has a timestamp that is not newer than the last modification timestamp of the specified target file.
Message Inserts:
System Action: The specified target file is not modified and the specified entry is not extracted.
Syntax is: ihsaunpk [-v|-k|-K] [-t testbedDirName] [-n] amp1spec [amp2spec ... [ampNspec]]
Explanation: The ihsaunpk utility was invoked with incorrect command line syntax.
Message Inserts:
System Action: This informational message is displayed.
Operator Response: Invoke ihsaunpk using the correct command line syntax.
No files meeting the file specification were found.
File specification: AMPFileSpecification
Explanation: The ihsaunpk utility found no files meeting the specified AMP file specification that was passed on the command line.
Message Inserts:
System Action: No AMP files are processed and the command line syntax message is displayed.
Operator Response: Re-start the utility using one or more valid AMP file specifications.
Unable to delete fileToDelete
Explanation: The topology server or ihsaunpk utility was unable to delete the specified file.
Message Inserts:
System Action: The specified file is not deleted.
Operator Response: Check the file permissions on the specified files and modify them if necessary. Ensure that no other applications have the file locked. Then retry the operation.
Deleted fileToDelete.
Explanation: The topology server or ihsaunpk utility deleted the specified file.
Message Inserts:
System Action: The specified file is deleted.
The AMP file being imported contains an entry with the same name as an existing instrumentation file.
AMP Filename: AMP_filename
Existing Instrumentation Filename: existingFilename
Explanation: A request was made to the topology server to dynamically load a new AMP file. The AMP file contains an entry with the same filename as an existing instrumentation that has previously been installed. This is not allowed. New in this context means not containing any files that collide with instrumentation files already installed on the topology server.
Message Inserts:
System Action: The AMP file is not loaded by the server.
Operator Response: Verify that the correct AMP filename has been specified. If so, notify your system programmer.
System Programmer Response: Contact the provider of the AMP file and ask that the entry in the AMP file be renamed to a name that does not collide with any previously installed files. This may or may not require that corresponding changes be made to other entries in the AMP file that reference the renamed entry. You may want to use the ihsaunpk utility on the topology server to try to manually install the AMP. You can then examine the AMP file unpacking log to determine if there are any additional conflicts.
The AMP file cannot be imported because an AMP file with this name has already been installed.
AMP Filename: AMP_filename
Explanation: A request was made to the topology server to dynamically load a new AMP file. An AMP file with the specified filename already exists on the topology server. This is not allowed.
Message Inserts:
System Action: The AMP file is not loaded by the server.
Operator Response: Verify that the correct AMP filename has been specified. If so, notify your system programmer.
System Programmer Response: If the AMP files are actually different sets of instrumentation, rename one of them and try again.
The AMP file import completed.
AMP Filename: AMP_filename
Explanation: The topology server successfully loaded the specified AMP file.
Message Inserts:
System Action: The AMP file is successfully loaded by the topology server.
The AMP file was not imported because an error occurred during extraction.
AMP Filename: AMP_filename
Explanation: A request was made to the topology server to dynamically load a new AMP file. An error occurred during the extraction of one or more entries. The AMP file was not loaded.
Message Inserts:
System Action: The AMP file is not loaded by the server.
Operator Response: Verify that the correct AMP filename has been specified.
System Programmer Response: Verify that the format of the AMP file is correct by using the tserver ihsaunpk utility on the server with the -v parameter to list its contents.
The instrumentation description files for the following business system
have been installed on the topology server.
Manufacturer: Manufacturer
Product: Product
Version: Version
Explanation: The AMP file for the specified business system was successfully loaded by the topology server.
Message Inserts:
System Action: The instrumentation description files for the specified business system were loaded by the topology server.
The AMP file cannot be imported because one of its entries contains a syntax error or is missing a required group.
AMP Filename: ampFilename
AMP Entry: ampEntryFilename
Explanation: A request was made to the topology server to dynamically load a new AMP file. One or more of the entries in the specified AMP file are description files that contain a syntax error or are missing a required group.
Message Inserts:
System Action: The AMP file is not loaded.
Operator Response: Verify that the correct AMP filename was specified.
System Programmer Response: Correct the syntax error or add the missing required group in the specified AMP file entry and try importing the AMP file again.
The AMP file cannot be imported because the internal identifiers of
one of its entries are the same as an existing file.
AMP Filename: ampFilename
AMP Entry: ampEntryFilename
Existing Filename: existingFilename
Explanation: A request was made to the topology server to dynamically load an AMP file. The specified AMP file contains one or more entries which are description files whose internal identifiers are the same as an existing description file that is already installed on the topology server. This is not allowed.
Message Inserts:
System Action: The AMP file is not imported.
Operator Response: Verify that the correct AMP file was specified. If so, notify your system programmer.
System Programmer Response: Modify the contents of the conflicting AMP file entry to eliminate the conflict and modify any other entries in the AMP that reference the entry being modified. The internal identifiers for a description file are the following:
The AMP file cannot be imported because it would overwrite an existing file.
AMP Filename: ampFilename
Existing Filename: existingFilename
Explanation: A request was made to the topology server to dynamically load an AMP file. The specified AMP file contains one or more entries whose filenames are the same as files already installed on the topology server, but whose contents are different than the files that they would overlay if the AMP file were loaded. This is not allowed.
Message Inserts:
System Action: The AMP file is not imported.
Operator Response: Verify that the correct AMP file was specified.
System Programmer Response: Change the file name of the conflicting AMP file entry to a filename that does not already exist on the topology server. Then change any entries in the AMP file that reference the renamed entry to the new name, and try reloading the AMP file.
The AMP file contained no entries to be extracted that were not
already installed on the server.
AMP Filename: ampFilename
Explanation: A request was made to the topology server to dynamically load an AMP file. All of the entries to be extracted from the specified AMP were already installed on the topology server and they are identical to the entries in the specified AMP file.
Message Inserts:
System Action: The AMP file is not imported.
Operator Response: Verify that the correct AMP file was specified.
xdfmaint command queue file not found.
Explanation: The server attempted to read the xdfmaint command queue file but was not successful.
System Action: No queued xdfmaint commands are processed.
Operator Response: Before you execute the run or runforce commands, queue the xdfmaint commands.
System Programmer Response: If the xdfmaint commands were queued prior to executing the run or runforce commands, and you cannot resolve the problem, contact your Tivoli Support Center.
Removing MIF object
ID: mpvTriplet
Abstraction Level: absLevel
Filename: xdfFilename
Explanation: The server is removing a MIF Object from its database.
Message Inserts:
System Action: The MIF object is removed from the server database.
Error deleting BDF file
Filename: bdfFilename
ID: mpvTriplet
Level: absLevel
Explanation: The server attempted to delete a BDF file from its database but was not successful.
Message Inserts:
System Action: The BDF file is not removed from the server database.
Operator Response: Ensure the BDF file is the correct one to be removed.
System Programmer Response: Ensure the BDF file is the correct one to be removed. If you cannot resolve the problem, contact your Tivoli Support Center.
Error deleting file
Filename: xdfFilename
Explanation: The server attempted to delete an BDF, CDF, or GDF file from its database but was not successful.
Message Inserts:
System Action: The file is not removed from the server database.
Operator Response: Ensure the file is the correct one to be removed.
System Programmer Response: Ensure the file is the correct one to be removed. If you cannot resolve the problem, contact your Tivoli Support Center.
Error deleting CDF file
Filename: cdfFilename
Explanation: The server attempted to delete a CDF file from its database but was not successful.
Message Inserts:
System Action: The CDF file is not removed from the server database.
Operator Response: Ensure the CDF file is the correct one to be removed.
System Programmer Response: Ensure the CDF file is the correct one to be removed. If you cannot resolve the problem, contact your Tivoli Support Center.
An error occured while deleting a resource type database entry
ID: mpvTriplet
Abstraction Level: absLevel
Filename: xdfFilename
Explanation: The server attempted to delete a resource type from its database but was not successful.
Message Inserts:
System Action: The resource type is not removed from the server database.
Operator Response: Ensure the resource type is the correct one to be removed.
System Programmer Response: Ensure the resource type is the correct one to be removed. If you cannot resolve the problem, contact your Tivoli Support Center.
The CDF cannot be removed because it is still referenced by a GDF.
CDF ID: cdfMpvTriplet
CDF Filename: cdfFilename
GDF ID: gdfMpvTriplet
GDF Filename: gdfFilename
Explanation: The server attempted to delete a CDF from its database but was not successful because the CDF was referenced by an existing GDF.
Message Inserts:
System Action: The CDF is not removed from the server database.
Operator Response: Ensure the CDF is the correct one to be removed.
System Programmer Response: Ensure the CDF is the correct one to be removed. If you cannot resolve the problem, contact your Tivoli Support Center.
Command added to queue
Explanation: The xdfmaint command has been successfully added to the server xdfmaint command queue file.
System Action: The xdfmaint command has been successfully queued. It will be processed when the run or runforce command is executed.
File not found.
Filename: filename
Explanation: The server could not find the required file.
Message Inserts:
System Action: Since the required file could not be found, no action was taken by the server.
Operator Response: Ensure that the specified file exists.
System Programmer Response: Ensure that the specified file exists. If you cannot resolve the problem, contact your Tivoli Support Center.
Clients remained logged on. Requests not processed.
Explanation: The server attempted to process the queued xdfmaint commands but was not successful because all of the clients did not log off within the required time period.
System Action: No action was taken by the server, because some clients remained logged on.
Operator Response: Do the following:
System Programmer Response: Do the following:
Unable to lock databases. Requests not processed.
Explanation: The server attempted to process the queued xdfmaint commands but was not succesful because it could not lock its databases.
System Action: No action was taken by the server, because the databases could not be locked.
Operator Response: Do the following:
System Programmer Response: Do the following:
An invalid xdfmaint command was found and ignored.
Command: command
Explanation: The server has found an invalid command queued in the xdfmaint command queue file.
Message Inserts:
System Action: The invalid command is ignored and the processing of the command queue continues.
Operator Response: Processing continues, so no intervention required.
System Programmer Response: Processing continues, so no intervention required.
A file being extracted from the AMP already exists with a different M;P;V triplet.
AMP filename: ampFile
Existing filename: existFile
Explanation: The server has found a file being extracted from the specified AMP already exists, and the existing file has a different M;P;V triplet. This cannot be resolved.
Message Inserts:
System Action: Since the M;P;V discrepency cannot be resolved, the load AMP/load changed AMP command is aborted.
Operator Response: Either remove the package that contains the conflicting M;P;V, or the new package cannot be added. Contact the vendor of the package to report the error in conflicting file names.
System Programmer Response: Either remove the package that contains the conflicting M;P;V, or the new package cannot be added. Contact the vendor of the package to report the error in conflicting file names.