Waiting up to number seconds for command_exit to terminate.
Message Inserts:
System Action: The topology server will eventually terminate.
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:
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:
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:
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:
System Action: The topology server continues with missing information.
Operator Response: Do the following:
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:
System Action: The topology server continues with missing information.
Operator Response: Do the following:
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:
System Action: The topology server continues with missing information.
Operator Response: Do the following:
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:
System Action: The topology server continues with missing information.
Operator Response: Do the following:
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:
System Action: The topology server continues.
Operator Response: Do the following, if necessary:
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:
Internal error parsing group group in file filename.
RC = return code
Explanation: An error occurred while parsing the specified group.
Message Inserts:
System Action: The topology server continues with missing information.
Operator Response: Do the following:
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:
System Action: The topology server continues with missing information.
Operator Response: Do the following:
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:
Error opening file file.
Component information may be incomplete or unavailable.
Explanation: The topology server is unable to open the specified file.
Message Inserts:
System Action: The topology server is unable to open the file, and continues with missing information.
Operator Response: Do the following:
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:
System Action: The topology server continues with missing information.
Operator Response:
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:
System Action: The topology server continues with missing information.
Operator Response: Do the following:
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:
System Action: The topology server continues with missing information.
Operator Response: Do the following: