Explanation: The server.properties file which contains customization parameters for NMC Topology Server could not be accessed.
System Action: The topology server will utilize predetermined default values for all of the customization parameters.
Operator Response: Issue the tserver utility -p command to obtain a summary of the current settings for all customization parameters.
System Programmer Response: Do the following:
Unknown keyword unknown_keyword
found in server properties file on line linenum.
Explanation: While reading the server.properties configuration file, an unknown keyword was found. The keyword and its value, if any, are disregarded.
Message Inserts:
System Action: The topology server disregards the unknown keyword and its value, if any.
System Programmer Response: Edit the server.properties file and remove or comment out the unknown keyword. This will keep this message from reappearing if the topology server is reinitialized.
No = delimiter found for keyword keyword on line linenum. Default will be used.
Explanation: While reading the server.properties configuration file no '=' delimiter was found for a valid keyword. In this case the default value for the keyword will be used.
Message Inserts:
System Action The NMC topology server uses the default value for the keyword.
System Programmer Response: Edit the server.properties file and add the '=' delimiter. Reinitialize the topology server.
Multiple entry found for keyword keyword
on line linenum. Last one read will be used.
Explanation: While reading the server.properties configuration file multiple entries were found for the same keyword. In this case the value for the last one read will be used.
Message Inserts:
System Action: The NMC topology server uses the value of the last entry found.
System Programmer Response: Edit the server.properties file and remove or comment out the unwanted entry. Reinitialize the topology server.
Invalid value found for keyword inv_keyword
on line linenum. Default will be used.
Explanation: While reading the server.properties configuration file an invalid value was found for a specific keyword. The default value for this keyword will be used.
Message Inserts:
System Action: The topology server uses the default value of the keyword.
System Programmer Response: Edit the server.properties file and correct the invalid value. Reinitialize the NMC topology server.
Invalid syntax found for keyword inv_keyword
on line linenum. Default will be used.
Explanation: While reading the server.properties configuration file invalid syntax was found for a specific keyword. The default value for this keyword will be used.
Message Inserts:
System Action: The topology server uses the default value of the keyword.
System Programmer Response: Edit the server.properties file and correct the invalid syntax. Reinitialize the topology server.
No entry found for keyword no_keyword.
Default will be used.
Explanation: While reading the server.properties configuration file no entry was found for one of the defined keywords. Default value for this keyword will be used.
Message Inserts:
System Action: The topology server uses the default value of the keyword.
System Programmer Response: Edit the server.properties file and add an entry for the missing keyword. Reinitialize the topology server.
No value found for BINDIR. Can not access Server Properties file.
Program Defaults will be used.
Explanation: While trying to read the server.properties file the topology server found no value for the BINDIR environment variable. As a result program defaults for all the customization parameters will be used.
System Action: The NMC topology server uses the program defaults for all values normally found in the server.properties file.
System Programmer Response: Ensure that the command to start the topology server component defined the BINDIR environment variable, which gives access to server.properties file. For example, the tserver command file or script sets up the environment for the component of the topology server to run under. Reinitialize the topology server.
Value for keyword max_keyword
on line linenum is greater than max_default.
Maximum value max_default will be used.
Explanation: Many of the configuration parameters used in the server.properties file have maximum limits. If the user enters a value which exceeds the maximum allowed, the topology server will adjust the value to the maximum allowed.
Message Inserts:
System Action: The topology server uses the maximum default value of the keyword.
System Programmer Response: Follow these steps:
Value for keyword min_keyword on line
linenum is less than min_default. Minimum
value min_default will be used.
Explanation: Many of the configuration parameters used in the server.properties file have minimum limits. If the user enters a value which is less than the minimum allowed, the topology server will adjust the value to the minimum allowed.
Message Inserts:
System Action: The topology server uses the minimum default value of the keyword.
System Programmer Response: Follow these steps:
Value for keyword time_keyword
has been adjusted to time_value+1, 1 greater than time_value.
Explanation: The keywords timeoutSmall, timeoutMedium, timeoutLarge, and timeoutHuge are dependent on one another:
Message Inserts:
System Action: The topology server adjusts the timeout values to conform to the keyword dependency.
System Programmer Response: Follow these steps:
Value for keyword max_keyword
on line linenum is greater than max_default.
Maximum value max_default will be used.
Explanation: Many of the configuration parameters used in the server.properties file have maximum limits. If the user enters a value which exceeds the maximum allowed, the topology server will adjust the value to the maximum allowed.
Message Inserts:
System Action: The topology server uses the maximum default value of the keyword.
System Programmer Response: Follow these steps:
Value for keyword min_keyword on line
linenum is less than min_default. Minimum
value min_default will be used.
Explanation: Many of the configuration parameters used in the server.properties file have minimum limits. If the user enters a value which is less than the minimum allowed, the topology server will adjust the value to the minimum allowed.
Message Inserts:
System Action: The topology server uses the minimum default value of the keyword.
System Programmer Response: Follow these steps:
String size string_size for keyword keyword on
line linenum is greater than allowed. String is truncated to
maximum length of max_length.
Explanation: The string value for this keyword in the server.properties file can not exceed the maximum length. If the user enters a value which is greater than the maximum length allowed, the topology server will truncate the value to the maximum length allowed.
Message Inserts:
System Action: The topology server truncates the value of the keyword to the maximum allowed length.
System Programmer Response: Follow these steps:
Unable to write to audit log. Error occurred in module1 on line line1. Audit entry originated in module2 line2 is not written to the audit log.
Explanation: An error occurred while attempting to write to the audit log.
Message Inserts:
System Action: The message is also written to the message log, ihsmessage.log. The audit log entry is not written to the audit log. Processing of the Topology Server continues.
System Programmer Response: Ensure that your operating system is able to access the audit log. The audit log, ihsaudit.xml, is located in one of the following directories:
More information about the audit log can be found in the Customizing the NetView Management Console Topology Server Chapter of the NetView Management Console User's Guide.
Though this is a suspected operating system file access error, rename the audit log so that a new ihsaudit.xml file will be created the next time an audit log entry is generated.
If the error persists, contact the IBM Service Center.
Return code rc from module module1 called from module module2 on line line_num indicates an error when accessing the audit log.
Explanation: An error occurred while attempting to access the audit log.
Message Inserts:
System Action: The message is also written to the message log, ihsmessage.log. The audit log entry is not written to the audit log. Processing of the Topology Server continues.
System Programmer Response: Ensure that your operating system is able to access the audit log. The audit log, ihsaudit.xml, is located in one of the following directories:
More information about the audit log can be found in the Customizing the NetView Management Console Topology Server Chapter of the NetView Management Console User's Guide.
Though this is a suspected operating system file access error, rename the audit log so that a new ihsaudit.xml file will be created the next time an audit log entry is generated.
If the error persists, contact the IBM Service Center.
An error occurred trying to determine the PID (process ID) for a process. Command processing terminates.
Explanation: A process ID (PID) was needed to execute a command, but the information was not available.
System Action: The command stops.
Operator Response: Re-issue the command. If the problem persists, contact your system programmer.
System Programmer Response: Check the error and message logs for information. If you cannot fix the problem, contact your Tivoli Support Center.
Error sending data to task task_name. Error code major_error_code - minor_error_code.
Explanation: The command was not able to send data to the process that would handle your request.
Message Inserts:
System Action: The command stops.
System Programmer Response: Re-issue the command.
If the problem persists, check the error and message logs for information. If you cannot fix the problem, contact your Tivoli Support Center.
Error sending data to task task_name. Error code major_error_code - minor_error_code. Ensure that the destination task is running.
Explanation: The command was not able to send data to the process that would handle your request, most likely because the task that would process your request is not running.
Message Inserts:
System Action: The command stops.
System Programmer Response: Ensure that the task is running. If the task is running, try the operation again.
If the problem persists, check the error and message logs for information. If you cannot fix the problem, contact your Tivoli Support Center.
Ihsccmd was invoked with only parameter_number parameters. At least three parameters are required.
Explanation: The script that invoked the ihsccmd executable did not include the correct number of parameters.
Message Inserts:
System Action: The command stops.
System Programmer Response: Contact your Tivoli Support Center.
Error registering task task_name. The task is already registered. Rerun the command. If the problem persists restart the system.
Explanation: The command being run is trying to register a task with the ACM communications subsystem. The registration is failing because the task is already registered and duplicate registrations are not allowed. The problem might result from a process that temporarily has the task registered.
Message Inserts:
System Action: The command stops.
System Programmer Response: Try the operation again. If the problem persists, follow these steps:
On Unix, after stopping these processes, run the tserver stop -f command).
If the problem persists, contact your Tivoli Support Center.
Error registering task task_name. Error code major_error_code - minor_error_code. Contact the system programmer.
Explanation: The command being run is trying to register a task with the ACM communications subsystem. The registration is failing.
Message Inserts:
System Action: The command stops.
System Programmer Response: Contact your Tivoli Support Center.
Error freeing ACM memory. Error code major_error_code - minor_error_code. Function completed, but future work may be impaired.
Explanation: The command attempted to free ACM memory, but the free operation failed. The command that was executing at the time completed successfully, but this error might indicate a more serious problem in the system.
Message Inserts:
System Action: The command completed successfully, but the ACM memory was not freed.
System Programmer Response: If these types of errors persist, stop and restart the server.
If the problem persists, contact the Tivoli Support Center.
Error allocating ACM memory. Error code major_error_code - minor_error_code.
Explanation: The command attempted to allocate memory from the ACM memory pool. The allocation failed and the command did not complete successfully.
Message Inserts:
System Action: The memory allocation failed and the command failed.
System Programmer Response: Try the command again. If the problem persists, reinitialize the server.
If the problem still persists, contact your Tivoli Support Center.
Error deregistering task task_name. Error code major_error_code - minor_error_code. If future errors occur, restart the system.
Explanation: A task registered to the ACM subsystem could not be deregistered. This may stop you from executing commands in the future.
Message Inserts:
System Action: The command completed.
System Programmer Response: If task registration errors occur for this task in the future, reinitialize the server.
If the problem continues, contact the Tivoli Support Center.
Unable to queue request for later processing. Error at location location, error code error code.
Explanation: The command could not be queued for later processing. The error code identifies a possible explanation as to the cause of this error.
Message Inserts:
System Action: The command is not queued.
System Programmer Response: Do one of the following:
Try the command again. If the problem persists, contact your Tivoli Support Center.