Topology Server Message Help

IHS2152I

Waiting up to number seconds for command_exit to terminate.

Message Inserts:

number
The number of seconds the topology server will wait before continuing termination.
command_exit
The name of the terminating command exit.

System Action: The topology server will eventually terminate.

IHS2164E

The topology server is ending due to an internal error. The resource type database has been corrupted. It appears that BDF or CDF files have been deleted or modified.

Explanation: The current set of description files is missing data that the server needs to initialize properly. The server cannot start.

System Action: The topology server ends.

Operator Response: Do one of the following:

IHS2165E

No missingCompType was found below lastDescFile in the description file hierarchy.
Component ID Group information:
Manufacturer: manufacturer
Product: product
Version: version
Component Type:lastCompType

Explanation: The topology server has found an incomplete branch in the tree. The information expected to be in the missing M;P;V triplet is displayed.

Message Inserts:

missingCompType
Component type that is missing
lastDescFile
Filename of the description file with missing component type
manufacturer
Manufacturer of missing component type
product
Product of missing component type
version
Version of missing component type
lastCompType
Component type of the description file with missing component type

Below are the possible combinations of lastDescFile type and missingCompType:

For Business systems only:
lastDescFile = business system description file
missingCompType = business subsystem component type

For Business systems only:
lastDescFile = business subsystem description file
missingCompType = business component component type

The first two are for business systems only because applications, databases and middleware do not have subsystems.

For applications, databases middleware systems only:
lastDescFile = business system description file
missingCompType = business component component type

The next pairs can apply to any of the types of software systems:
lastDescFile = business subsystem description file
missingCompType = business component component type

lastDescFile = business component description file
missingCompType = business mapping component type

lastDescFile = business mapping description file
missingCompType = software component component type

You will not see this combination because GDFs are optional:
lastDescFile = component description file
missingCompType = application component type

System Action: The topology server continues with missing information.

Operator Response: Do the following:

  1. Check the description files for a missing or incorrect file and correct the problem.
  2. Restart the server.
  3. If the server restarts with no errors and information is still missing, erase the server databases and restart the server. Erasing the databases will cause you to lose any customization you may have done. For that reason, you should create a backup prior to erasing the databases, so that you can restore them if the problem persists.

IHS2166W

Unable to find match for relationship in CDF file.
Relationship type: relationship type
Direction: relationship direction
Mapping file: BDF filename
Component file: CDF filename

Explanation: The topology server could not find the specified relationship (found in a mapping or business component file) in the CDF.

Message Inserts:

relationship type
The relationship type name specified in the BDF.
relationship direction
The relationship direction specified in the BDF.
BDF filename
Filename of the BDF that the relationship is referenced.
CDF filename
Filename of the CDF that is referenced by the specified BDF.

System Action: The topology server continues with missing information.

Operator Response: Do the following:

  1. Check the description files for a missing or incorrect group descriptions and correct the problem.
  2. Restart the server.
  3. If the server restarts with no errors and information is still missing, erase the server databases and restart the server. Erasing the databases will cause you to lose any customization you may have done. For that reason, you should create a backup prior to erasing the databases, so that you can restore them if the problem persists.

IHS2167W

Unable to find match for task task name in CDF file.
Mapping file: BDF filename
Component file: CDF filename

Explanation: The topology server could not find the specified task (found in a mapping or business component file) in the CDF.

Message Inserts:

task name
Name of task that was not found in CDF.
BDF filename
Filename of the BDF that specified or tried to map the specified task.
CDF filename
Filename of the CDF that is referenced by the specified BDF.

System Action: The topology server continues with missing information.

Operator Response: Do the following:

  1. Check the description files for a missing or incorrect task and correct the problem.
  2. Restart the server.
  3. If the server restarts with no errors and information is still missing, erase the server databases and restart the server. Erasing the databases will cause you to lose any customization you may have done. For that reason, you should create a backup prior to erasing the databases, so that you can restore them if the problem persists.

IHS2168W

Unable to find match for monitor name instance instance in component file.
Mapping file: BDF filename
Component file: CDF filename

Explanation: The topology server could not find the specified monitor (found in a Mapping or Business Component file) in the CDF.

Message Inserts:

name
Name of the monitor that was not found in CDF.
instance
Monitor instance value of the monitor that was not found. If this instance value if 0 it represents an Asynchronous Monitor, any other value indicates a Synchronous Monitor Instance.
BDF filename
Filename of the BDF that specified or tried to map the specified monitor.
CDF filename
Filename of the CDF that is referenced by the specified BDF.

System Action: The topology server continues with missing information.

Operator Response: Do the following:

  1. Check the description files for a missing or incorrect monitor and correct the problem.
  2. Restart the server.
  3. If the server restarts with no errors and information is still missing, erase the server databases and restart the server. Erasing the databases will cause you to lose any customization you may have done. For that reason, you should create a backup prior to erasing the databases, so that you can restore them if the problem persists.

IHS2169E

Internal error message in file filename.

Explanation:An internal error occurred during processing of the specified file. The error message will indicate the problem.

Message Inserts:

message
Message indicating problem.
filename
Filename of BDF or CDF being processed at the time of the error.

System Action: The topology server continues with missing information.

Operator Response: Do the following:

  1. Check for available system resources, memory, and disk space, and correct the problem.
  2. Restart the server.
  3. If the server restarts with no errors and information is still missing, erase the server databases and restart the server. Erasing the databases will cause you to lose any customization you may have done. For that reason, you should create a backup prior to erasing the databases, so that you can restore them if the problem persists.
  4. If the problem recurs, contact your Tivoli Support Center.

IHS2171I

No information found for group group in file filename.

Explanation: The topology server could not find a group description, or a table, for the specified group. The group is not a required group, so this does not necessarily indicate an error. Some groups that the topology server uses are optional. For example, groups like the Icon and Help groups provide additional information to make the product more usable. Specifying monitors or connections for a business system is also optional. If information appears to be missing on the topology console, a missing or improperly defined group may be the problem. If the desired group should be present, corrective action is needed.

Message Inserts:

group
Name of group in description file.
file name
File name of BDF or CDF with missing group information.

System Action: The topology server continues.

Operator Response: Do the following, if necessary:

  1. Check the description files for missing information and correct the problem, if desired.
  2. Restart the server.
  3. If the server restarts with no errors and information is still missing, erase the server databases and restart the server. Erasing the databases will cause you to lose any customization you may have done. For that reason, you should create a backup prior to erasing the databases, so that you can restore them if the problem persists.

IHS2172W

No synchronous monitor group information was found.
Insufficient data to create monitors.

Explanation: A synchronous monitor instance group was defined, but the topology server could not find a synchronous monitor group or table. The monitor instances could not be properly created. The next message will indicate the file in which the error was found. The topology server uses synchronous monitor instances as specified in the AMS (Application Management Specification). In order to create these instances it needs to correlate information from the synchronous monitor instance group, which specifies monitor instances, and the synchronous monitor group, which contains a base template of information. If a monitor name specified in a monitor instance is not included in the synchronous monitor group, the topology server does not have sufficient information available to use the monitor.

System Action: The topology server continues with missing information.

Operator Response: Do the following:

  1. Correct or replace the file in which the error was found.
  2. Restart the server.
  3. If the server restarts with no errors and information is still missing, erase the server databases and restart the server. Erasing the databases will cause you to lose any customization you may have done. For that reason, you should create a backup prior to erasing the databases, so that you can restore them if the problem persists.

IHS2173E

Internal error parsing group group in file filename.
RC = return code

Explanation: An error occurred while parsing the specified group.

Message Inserts:

group
Name of group where error occurred.
filename
Filename of BDF or CDF that contains the specified group.
return code
Return code from parser. Used for

System Action: The topology server continues with missing information.

Operator Response: Do the following:

  1. Check the syntax of the specified group and make any necessary corrections.
  2. Restart the server.
  3. If the server restarts with no errors and information is still missing, erase the server databases and restart the server. Erasing the databases will cause you to lose any customization you may have done. For that reason, you should create a backup prior to erasing the databases, so that you can restore them if the problem persists.

IHS2174W

No match was found in the synchronous monitor group for monitor instance name in file file?

Explanation: The topology server could not find a monitor with the specified name in the synchronous monitor group, so a monitor instance could not be created. The topology server uses synchronous monitor instances as specified in the AMS (Application Management Specification). In order to create these instances it needs to correlate information from the synchronous monitor instance group, which specifies monitor instances, and the synchronous monitor group, which contains a base template of information. If a monitor name specified in a monitor instance is not included in the synchronous monitor group, the topology server does not have sufficient information available to use the monitor.

Message Inserts:

name
Name of monitor being looked for.
file
Filename of CDF with error.

System Action: The topology server continues with missing information.

Operator Response: Do the following:

  1. Correct or replace the specified file.
  2. Restart the server.
  3. If the server restarts with no errors and information is still missing, erase the server databases and restart the server. Erasing the databases will cause you to lose any customization you may have done. For that reason, you should create a backup prior to erasing the databases, so that you can restore them if the problem persists.

IHS2175W

Error - duplicate path definition.

Explanation: A duplicate path description was specified in the CDF file. A previous message indicated the file in which the error was found.

System Action: The topology server continues.

Operator Response: Do the following:

  1. Correct or replace the specified file.
  2. Restart the server.
  3. If the server restarts with no errors and information is still missing, erase the server databases and restart the server. Erasing the databases will cause you to lose any customization you may have done. For that reason, you should create a backup prior to erasing the databases, so that you can restore them if the problem persists.

IHS2176E

Error opening file file.
Component information may be incomplete or unavailable.

Explanation: The topology server is unable to open the specified file.

Message Inserts:

file
Filename of BDF or CDF that could not be opened.

System Action: The topology server is unable to open the file, and continues with missing information.

Operator Response: Do the following:

  1. Check the file permissions, and availability of system resources.
  2. Restart the server.
  3. If the server restarts with no errors and information is still missing, erase the server databases and restart the server. Erasing the databases will cause you to lose any customization you may have done. For that reason, you should create a backup prior to erasing the databases, so that you can restore them if the problem persists.

IHS2177W

Error getting command indicator for resource.

Explanation:The topology server was unable to create a command indicator for the resource indicated. No commands will be available for this resource.

Message Inserts:

resource
The name of the resource that did not get a command indicator.

System Action: The topology server continues with missing information.

Operator Response:

IHS2178W

Error parsing group group. Group has no key or ID.

Explanation: The specified group does not have an ID or key specified. The AMS specification requires one of these. A previous message will indicate the file that is in error.

Message Inserts:

group
The name of the group with the missing key or ID.

System Action: The topology server continues with missing information.

Operator Response: Do the following:

  1. Correct or replace the appropriate file.
  2. Restart the server.
  3. If the server restarts with no errors and information is still missing, erase the server databases and restart the server. Erasing the databases will cause you to lose any customization you may have done. For that reason, you should create a backup prior to erasing the databases, so that you can restore them if the problem persists.

IHS2179W

Error with group group while creating object for file file.

Explanation: A previous error indicates the actual problem. This message is provided to help isolate the area in which the error occurred.

Message Inserts:

group
Name of group where error occurred.
file
Filename of BDF or CDF with incorrect group information.

System Action: The topology server continues with missing information.

Operator Response: Do the following:

  1. Correct or replace the appropriate file.
  2. Restart the server.
  3. If the server restarts with no errors and information is still missing, erase the server databases and restart the server. Erasing the databases will cause you to lose any customization you may have done. For that reason, you should create a backup prior to erasing the databases, so that you can restore them if the problem persists.