Topology Server Message Help

IHS0400E

The path specified for the error log file does not exist. Create the directory.

Explanation: The directory specified for the error log does not exist.

System Action: The log entry was not written to the error log.

Operator Response: Either change the log file directory with the IHSZSET tool, or create the specified directory.

IHS0401E

The error log could not be opened because too many files are already open. Stop other applications in the system.

Explanation: The error log could not be opened because too many files are already open.

System Action: The log entry was not written to the error log.

Operator Response: Stop other applications that are running in the system, until the error is corrected.

IHS0402E

The error log file was not opened because the disk is full.

Explanation: The error log file was not opened because the disk is full.

System Action: The log entry was not written to the error log.

Operator Response: Free some space on the disk or change the trace log path to a different disk.

IHS0403E

The error log file name is not valid.

Explanation: The file name specified for the error log is not valid.

System Action: The log entry was not written to the error log.

Operator Response: Change the error log file name with the IHSZSET tool.

IHS0404E

An error log entry failed because storage could not be allocated.

Explanation: The error logging facility was unable to obtain system memory.

System Action: The log entry was not written to the error log.

Operator Response: Free some storage by stopping other applications or by adding storage to the system. Also, confirm that swapping is enabled.

IHS0405E

An attempt was made to log a trace entry that was larger than the trace buffer.

System Action: The system continues, but trace data is discarded.

Operator Response: Contact your system programmer.

System Programmer Response: If the problem persists, recycle the topology server. If this does not correct the problem, contact your Tivoli Support Center.

IHS0406E

Message message in file file was not found

Explanation: A message was to be issued, but could not be found in the message file.

Message Inserts:

message
Message ID to be issued.
message variable
File where the message was expected to be found.

Operator Response: Contact your system programmer.

System Programmer Response: Contact your Tivoli Support Center.

IHS0411E

A time out occurred while waiting for all tasks to complete.

Explanation: This condition occurs when a task ends abnormally while logging a trace entry.

System Action: The trace buffer has been cleaned up and logged to the disk.

Operator Response: Contact your system programmer.

System Programmer Response: Contact your Tivoli Support Center.

IHS0412E

The path specified for the trace log file does not exist. Create the directory.

Explanation: The directory specified for the trace log does not exist.

System Action: The log entry was not written to the trace log.

Operator Response: Either change the log file directory with the IHSZSET tool, or create the specified directory.

IHS0413E

The trace log could not be opened because too many files are already open. Stop other applications in the system.

Explanation: The trace log could not be opened because too many files are already open.

System Action: The log entry was not written to the trace log.

Operator Response: Stop other applications that are running in the system until the error is corrected.

IHS0414E

The trace log file was not opened because the disk is full.

System Action: The log entry was not written to the trace log.

Operator Response: Free some space on the disk or change the trace log path to a different disk.

IHS0415E

The trace log file name is not valid.

System Action: The log entry was not written to the trace log.

Operator Response: Change the trace log file name with the IHSZSET tool.

IHS0416E

An internal error occurred in module at line number line

Message Inserts:

module
Module where error occurred.
line
Line number within the module where error occurred.

System Action: The action being performed is aborted.

Operator Response: Contact your system programmer.

System Programmer Response: Contact your Tivoli Support Center.

IHS0419E

An operating system error occurred in module at line number line. The operating system error code is error code.

Explanation: During internal processing, an operating system function call has returned an error code that was unexpected for the requested function.

Message Inserts:

module
Module where error occurred.
line
Line number within the module where error occurred.
error code
Error code returned by the operating system.

System Action: The action being performed is aborted.

Operator Response: Contact your system programmer.

System Programmer Response: Contact your Tivoli Support Center.

IHS0420E

The path specified for the message log file does not exist. Create the directory.

Explanation: The directory specified for the message log does not exist.

System Action: The log entry was not written to the message log.

Operator Response: Either change the log file directory with the IHSZSET tool, or create the specified directory.

IHS0421E

The message log could not be opened because too many files are already open. Stop other applications in the system.

System Action: The log entry was not written to the message log.

Operator Response: Stop other applications that are running in the system until the error is corrected.

IHS0422E

The message log file was not opened because the disk is full.

System Action: The log entry was not written to the message log.

Operator Response: Free some space on the disk or change the message log path to a different disk.

IHS0423E

The message log file name is not valid.

System Action: The log entry was not written to the message log.

Operator Response: Change the message log file name with the IHSZSET tool.

IHS0525E

The command exit facility is ending due to a missing dll file.

Explanation: The command exit facility could not find either the IHSX.DLL file or the IHSUR.DLL file. Verify that the $BINDIR/TDS/Server/bin directory is in the PATH.

System Action: The command exit facility ends without completing the command.

Operator Response: Contact your system programmer.

System Programmer Response: Verify that both IHSX.DLL and IHSUR.DLL exist in the path specified by PATH.

IHS0526E

The command exit facility is ending due to an internal error.

Explanation: An internal error occurred in the command exit facility. The cause of this error is normally related to constraints on system resources, such as storage or disk space. Detailed error information has been logged to the topology server error log.

System Action: The command exit facility ends without completing the command.

Operator Response: When an out-of-storage condition exists, you can free some storage by stopping other applications or by adding storage to the system. Also confirm that swapping is enabled. If you cannot resolve the error, contact the system programmer.

System Programmer Response: Check for an out-of-storage condition. If the condition does not exist, contact the Tivoli Support Center.

IHS0527E

An error occurred while loading the string table from the dynamic load library dllname.

Explanation: An error occurred while loading the string table from the specified dynamic load library.

Message Inserts:

dllname
The name of the DLL that could not be found.

Operator Response: Notify your system programmer. table-driven command exit.

System Programmer Response: Ensure that the correct version of the dynamic load library file is the first file of that name encountered in the PATH statement. If this does not resolve the problem, refer to "Documenting and Reporting a Problem" in Tivoli NetView for z/OS Problem Determination and Diagnosis and contact the Tivoli Support Center.

IHS0528E

An error occurred during semaphore initialization. Press enter to terminate the command exit facility.

Explanation: An internal error occurred during semaphore initialization in the table driven command exit.

Operator Response: Press Enter to end the table-driven command exit. Retry the command.

System Programmer Response: Contact the Tivoli Support Center.

IHS2000E

The topology server is ending due to an internal error. The databases will not be saved, therefore they may not reflect the latest changes.

Explanation: The topology server is ending due to an internal error. The databases will not be saved, therefore they will not reflect the latest changes.

System Action: The topology server terminates.

Operator Response: Contact your system programmer.

System Programmer Response: Collect the logs in $BINDIR/TDS/Server/log. Restart the topology server processes. If the problem persists, contact the Tivoli Support Center.

IHS2001W

Views from RODM are not supported. The level of Tivoli NetView for z/OS is incompatible with the server.

Explanation: A NETCONV command was issued from an incompatible version of the Tivoli NetView for z/OS program and specified this workstation as the destination.

System Action: The NETCONV session is still established, commands to Tivoli NetView for z/OS are still allowed, and business views (instrumentation) can still be supported. However, views that are retrieved by GMFHS (Graphic Monitor Facility Host Subsystem) out of RODM (Resource Object Model) are not supported.

Operator Response: Contact your system programmer.

System Programmer Response: If you need to display the views out of RODM, then install the correct version of the Tivoli NetView for z/OS program. See the Tivoli NetView for z/OS Installation: Migration Guide for information on migration.

IHS2002E

The topology server is ending due to a missing DLL file.

Explanation: The topology server is ending due to a missing library.

Operator Response: Check that the $BINDIR/TDS/Server/bin directory is included in the PATH environment variable. Check this directory to ensure that the DLL is in this directory.

System Programmer Response: If the problem persists, Contact the Tivoli Support Center.

IHS2003E

The topology server is already active. Only one instance of the server is allowed. This instance of the topology server will end.

Explanation: You can only start one instance of the topology server at a time.

System Action: This instance of the topology server terminates.

Operator Response: Contact your system programmer.

Operator Response: If you want to restart the server, stop the current instance of the server, then restart. Otherwise, no action is required.

IHS2020E

Corrupt/Missing corrupt_db databases detected. Restoring from the restore_db databases.

Explanation: The server attempted to load missing or corrupted databases.

Message Inserts:

corrupt_db
The directory that containted the missing or corrupted database.
restore_db
The directory containing the datbases that will be restored.

System Action: The databases in the restore_db are copied to the current database and initialization continues.

Operator Response: If the topology server initializes, no additional action is needed.

System Programmer Response: Restart the topology server. If the problem persists, contact IBM Customer Support.

IHS2021E

The topology server is ending due to an internal error. The databases will not be saved, therefore they may not reflect the latest changes.

Explanation: These errors are usually caused by a failure associated with the execution of a system function that is unrecoverable. The topology server is unable to save the databases because of this error. Therefore, any changes that have been made since the topology server was last started may be lost.

System Action: The topology server process terminates. It does not write the databases out to disk. Therefore, updates, such as added resources and customization, may be lost.

Operator Response: Contact your system programmer.

System Programmer Response: Stop the remaining server processes, then restart the topology server.

IHS2022E

The topology server is ending due to insufficient available threads. The maximum number of threads has been started.

Explanation: The topology server allows a maximum of 64 threads to run concurrently. The maximum number is already running. This error may be the result of an earlier error which has prevented previously started threads from terminating.

System Action: The topology server process terminates. All databases are written to disk before termination.

Operator Response: Contact your system programmer.

System Programmer Response: Restart the topology server daemon. If the problem persists, contact your Tivoli Support Center.

IHS2023E

The topology server is ending due to insufficient memory. Free or add memory in the system, then restart the topology server.

Explanation: The topology server tried to obtain (malloc) storage but was unable to.

System Action: The topology server process terminates. All databases are written to disk before termination.

Operator Response: Contact your system programmer.

System Programmer Response: Do the following:

  1. Increase the amount of swapping or paging space on the system.
  2. Add more memory, if possible.
  3. Restart the topology server. If the problem persists, contact your Tivoli Support Center.

IHS2025E

The topology server cannot continue due to insufficient memory.

Explanation: The system has a resource shortage, either with swapping, paging space, or physical memory.

System Action: The server process terminates.

Operator Response: Contact your system programmer.

System Programmer Response: Do the following:

  1. Add more swapping or paging space to the system.
  2. Add more physical memory, if possible.
  3. Restart the topology server. If the problem persists, contact your Tivoli Support Center.

IHS2026E

Corrupt backup databases detected. Restoring from the default databases.

Explanation: The backup databases are corrupted. The databases are located in one of the following directories:

System Action: The default database is copied to the current database and initialization continues.

Operator Response: If the server initializes ok, no additional action is needed.

System Programmer Response: Determine the cause of the database corruption. Possible causes are:

Erase the backup databases and restart the server using the default databases.

IHS2027E

The topology server cannot continue due to insufficient disk space. The topology server will terminate.

Explanation: One of the disks used by the topology server is full.

System Action: The topology server process will terminate.

Operator Response: Contact your system programmer.

System Programmer Response: Do the following:

  1. Add more space to the file system, if possible.
  2. If the disk that is full contains the topology server databases and additional space cannot be added to the drive or file system, move the topology server databases to a new disk and filesystem by copying all files and directories below and including $BINDIR/TDS/Server/db to the new disk. Set the topology_DB environment variable to the new location. Also make sure you update the $BINDIR/TDS/Server/bin/tserver.sh file.
  3. Restart the topology server.

IHS2028E

The workstation has received information that is not valid from the host.

Explanation: Data was received that did not contain valid header information. The topology server does not understand how to process the data. The data will be written to the error log and then discarded.

System Action: The data is written to the topology server error log and then discarded.

Operator Response: Contact your system programmer.

System Programmer Response: If the problem persists, stop and restart the topology server. If this does not correct the problem, contact your Tivoli Support Center.

IHS2030W

An incompatible version of Tivoli NetView for z/OS has attempted to establish a session to the topology server. The data sent over this connection is ignored.

Explanation:A NETCONV command was issued from an incompatible version of the Tivoli NetView for z/OS program and specified this workstation as the destination.

System Action: The data sent over this connection is ignored.

Operator Response: Contact your system programmer.

System Programmer Response:Install the correct version of the Tivoli NetView for z/OS program. This workstation cannot communicate with down-level versions of Tivoli NetView for z/OS. See the Tivoli NetView for z/OS Installation: Migration Guide for information on migration.

IHS2032W

The session between topology server and host Tivoli NetView had ended. Contact your system programmer responsible for the topology server.

Explanation: The communications session between Tivoli NetView for z/OS and the topology server has ended. The reason is unknown.

System Action: The topology server continues to run, but is unable to send commands to Tivoli NetView for z/OS or to query information.

Operator Response: Contact your system programmer.

System Programmer Response: Restart the connection between host Tivoli NetView for z/OS and the topology server by issuing the Tivoli NetView NETCONV command. If the connection continues to fail, contact your Tivoli Support Center. The topology server error and message logs may provide additional information.

IHS2035E

No backup databases found. Restoring from the default databases.

Explanation: The backup database was empty or missing files.

System Action: The default database is copied to the current database and initialization continues.

Operator Response: If the server initializes, no additional action is needed.

System Programmer Response: Determine why the backup database files were not found. The most likely reason is that files in the backup directory were deleted.

IHS2037E

The topology server is ending due to missing subdirectories. Contact the system programmer responsible for the topology server.

Explanation: The topology server is dependent on a specific directory structure below $BINDIR/TDS/Server/db. This structure does not exist, so specific files such as databases, icons, help, backgrounds, and BDF and CDF files may be missing.

System Action: The topology server terminates.

Operator Response: Contact your system programmer.

System Programmer Response: This problem is generally the result of directories missing below $BINDIR/TDS/Server/db. Restore the missing subdirectories and restart the topology server.

IHS2038E

The topology server is ending due to missing default databases. Contact your system programmer responsible for the topology server.

Explanation: The topology server could not find databases under the current or backup subdirectories, so it is looking for databases under the default subdirectory. The topology server must have a set of databases to start. The default databases under $BINDIR/TDS/server/db/default/datab (UNIX) or %BINDIR%/TDS/server/db/default/datab (Intel) are shipped with the product, but have either been erased or are inaccessible because of directory permissions.

System Action: The topology server terminates.

Operator Response: Contact your system programmer.

System Programmer Response: Restore the default databases in directory $BINDIR/TDS/Server/db/default/datab, then restart the topology server.

IHS2042E

IHS2042E: The topology server is ending due to a failure copying databases. Contact your system programmer responsible for the topology server.

Explanation: The topology server was writing data to its database when a write action failed. The specific write action that failed is written to the topology error log.

System Action: The topology server terminates.

Operator Response: Contact your system programmer.

System Programmer Response: Do the following:

  1. Ensure that there is sufficient disk space and proper permissions on the $BINDIR/TDS/Server/db directory and subdirectories.
  2. Restart the topology server.
  3. If the problem persists, contact your Tivoli Support Center.

IHS2048E

The topology server cannot initialize because the databases are being accessed by another process. The topology server will end.

Explanation: Only one process can access the topology databases at a time. Another process, possibly another instance of the topology server, has the databases open.

System Action: The topology server process terminates.

Operator Response: Contact your system programmer.

System Programmer Response: If the topology server is currently running, you will need to stop it before another image can be started. If the topology server is not running, do the following:

If the problem persists, reboot the machine. If this does not correct the problem, contact your Tivoli Support Center.

IHS2049E

The topology server is ending due to an error accessing a database. The databases will not be saved, therefore they may not reflect the latest changes.

Explanation: The topology server was trying to either read from or write to a database when the action failed.

System Action: The topology server terminates.

Operator Response: Contact your system programmer.

System Programmer Response: Restart the topology server. If the error persists, then contact your Tivoli Support Center.