The configuration file ihscacm.cfg was not found. Verify that the file exists in the $BINDIR/TDS/Server/config directory and that the BINDIR environment variable is set.
Explanation: The topology communications server could not find the configuration file ihscacm.cfg. Verify that the BINDIR environment variable is properly set and that the file exists in the $BINDIR/TDS/server/config directory.
System Action: The topology communications server terminates.
Operator Response: Check that the file exists in the $BINDIR/TDS/server/config directory. If not, contact your system programmer.
System Programmer Response: Re-install the topology server.
The configuration file ihscacm.cfg is not valid.
Explanation: The format of the configuration file is not valid. This occurs when the file is unintentionally modified.
System Action: The topology communications server terminates.
Operator Response: Notify the system programmer.
System Programmer Response: Re-install the topology server.
An unexpected error occurred during initialization.
Explanation: A system error occurred during the initialization of the topology communications server. This error can be caused by an out-of-memory condition.
System Action: The topology communications server terminates.
Operator Response: When an out-of-memory condition exists, you can free some memory by stopping other applications or by adding memory 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-memory condition. If the condition does not exist, contact the Tivoli Support Center.
The communications server program is already active. Only one instance of the communications server can be active at a time.
Explanation: An attempt was made to start the topology communications server, but the program was already active.
System Action: The second attempt to load the topology communications server is ignored.
Operator Response: Contact your system programmer.
System Programmer Response: If you want to restart the server, stop the server that is currently running, then restart the server. Otherwise, no action is required.
The communications server program's name is not properly defined in the SNA communications server transaction program profile.
Explanation: The remotely attachable transaction program profile, in the IBM Communications Server configuration file, does not contain the topology communications server transaction program's name (30F0F4F4) or is not properly defined.
System Action: The topology communications server logs the error and continues operation.
Operator Response: Notify the system programmer.
System Programmer Response: Check the configuration of the IBM Communications Server. If you cannot resolve the error, contact the Tivoli Support Center.
The communications server program is ending due to an internal error.
Explanation: An internal error occurred in the topology communications server. This error can be caused by configuration errors.
System Action: The topology communications server terminates.
Operator Response: Notify the system programmer.
System Programmer Response: Check the configuration of the IBM Communications Server. If you cannot resolve the error, contact the Tivoli Support Center.
The APPC attach manager is not active.
Explanation: The IBM Communications Server LU 6.2 attach manager is not active. The topology communications server logs the error and continues.
System Action: The topology communications server retries the operation.
Operator Response: Activate the attach manager using the IBM Communications Server Subsystem Management menu. Notify the system programmer.
System Programmer Response: Modify the IBM Communications Server SNA base profile in the IBM Communications Server configuration file to automatically activate the attach manager.
The SNA processing is ending because the SNA communications server APPC subsystem has ended abnormally.
Explanation: The topology communications server is ending because the IBM Communications Server LU 6.2 subsystem stopped unexpectedly. Further LU 6.2 communications with the host are not possible. To re-enable LU 6.2 support, recycle the topology communication server.
System Action: Depending on the severity of the SNA error, the topology communications server may terminate.
Operator Response: Notify the system programmer.
System Programmer Response: Restart the SNA communications server, then restart the topology server.
The SNA communications server APPC subsystem is not loaded.
Explanation: The IBM Communications Server LU 6.2 subsystem was not active before the topology communications server transaction program was started.
System Action: The topology communications server logs the error and continues.
Operator Response: Notify the system programmer.
System Programmer Response: Check the configuration of the IBM Communications Server. For more information, refer to the IBM communications server online documentation. If you cannot resolve the error, contact the Tivoli Support Center.
An error occurred while attempting to start a thread in the communications server program.
Explanation: An out-of-memory condition causes the topology communications server to end.
System Action: The topology communications server terminates.
Operator Response: You can free some memory by stopping other applications, or by adding memory to the system. Also check that swapping is enabled. If the error still exists, notify the system programmer.
System Programmer Response: Confirm that an out-of-memory condition exists. If the condition does not exist, contact the Tivoli Support Center.
The communications server program is ending due to a memory allocation error.
Explanation: An out-of-memory condition causes the topology communications server to end.
System Action: The topology communications server terminates.
Operator Response: You can free some memory by stopping other applications, or by adding memory to the system. Also check that swapping is enabled. If the error still exists, notify the system programmer.
System Programmer Response: Confirm that an out-of-memory condition exists. If the condition does not exist, contact the Tivoli Support Center.
An error occurred while deallocating a SNA session.
Explanation: An LU 6.2 error occurred when the LU 6.2 session was deallocated. This warning can be caused by errors in other components, or by the unexpected stopping of the IBM Communications Server. This warning is not critical and does not impact the use of the topology server.
System Action: The server continues to run.
Operator Response: Notify your system programmer.
System Programmer Response: If the warning occurs often and you cannot resolve the error, contact the Tivoli Support Center.
The SNA processing is ending due to an APPC protocol error.
Explanation: An error occurred because a partner transaction program did not follow the correct protocol, or because an error was encountered in a partner transaction program. Further LU 6.2 communications with the host are not possible. To re-enable LU 6.2 support, recycle the topology communication server.
System Action: The topology communications server logs the error and continues.
Operator Response: Notify the system programmer.
System Programmer Response: Contact the Tivoli Support Center.
An APPC session has ended abnormally.
Explanation: The session with a partner transaction program ended unexpectedly. This warning is caused by the unexpected stopping of a partner transaction program, the IBM Communications Server, or VTAM.
Operator Response: Check for the cause of the session termination, and restart the session.
An error occurred while converting a string from EBCDIC to ASCII.
Explanation: This error can be the result of an error in the configuration of the IBM Communications Server.
System Action: The topology communications server logs the error and continues.
Operator Response: Notify the system programmer.
System Programmer Response: Correct the configuration of the IBM Communications Server.
Communications Server configuration file. Sense code code1. Primary Return Code code2. Secondary Return Code code3.
Explanation: The IBM Communications Server LU 6.2 subsystem is not properly configured.
Message Inserts:
System Action: The topology communications server logs the error and continues.
Operator Response: Notify the system programmer.
System Programmer Response: Correct the configuration of the IBM Communications Server.
An error occurred while attempting to allocate a session to LU luname. Verify that the LU is active.
Explanation: This error can occur because the destination LU is not active. The error can also occur when an LU 6.2 configuration error exists in the IBM Communications Server.
Message Inserts:
System Action: Communication to the destination LU is not established.
Operator Response: Check that the destination LU is active. If the destination LU is active and the error still exists, notify the system programmer.
System Programmer Response: Correct the configuration of the IBM Communications Server LU 6.2 subsystem.
The maximum number of transaction programs has been exceeded for LU luname.
Explanation: An LU 6.2 configuration error existed in the IBM Communications Server.
Message Inserts:
System Action: The transaction program ends.
Operator Response: Notify the system programmer.
System Programmer Response: Set the Maximum Number of Transaction Programs parameter to zero in the IBM Communications Server local LU profile. When the Maximum Number of Transaction Programs=0, IBM Communications Server allows an unlimited number of transaction programs.
The communications server program received bad data. The data will be logged to the error log.
Explanation: The topology communications server program received a data packet that contained a format that is not valid. This message can be caused by an error in another component of the topology server, or by another application erroneously sending data to the topology communications server.
System Action: The bad data is logged and the topology communications server continues.
Operator Response: Notify the system programmer.
System Programmer Response: If this error exists because an error occurred in another component of the topology server, disregard the error message. Check whether another application is sending data to the topology communications server and correct the error.
The topology communications server program encountered an error during initialization.
Explanation: The topology communications server program encountered an error while performing initialization processing. The error may be due to one of the following:
System Action: The topology communications server terminates.
Operator Response:
Stop the NMC Server, then start it again. If the problem persists, contact your system programmer.
System Programmer Response: Contact the Tivoli Support Center.
An operating system error occurred during initialization. The topology communications server program was unable to attach to the required shared memory or was unable to allocate required semaphores.
Explanation: A system error occurred during the initialization of the topology communications server. This error can be caused by the topology server being unable to attached to the required IPC resources.
System Action: The topology server terminates.
Operator Response: When the error occurs, stop all of the topology server processes by issuing tserver stop, then issue tserver stop -f to ensure that all of the IPC resources have been cleaned up. If the problem persists, contact your system programmer.
System Programmer Response: If the condition persists, contact the Tivoli Support Center.
The SNA communications server subsystem is not active. If SNA LU 6.2 communication services are needed, verify that the subsystem has been started.
Explanation: The topology communications server was unable to connect to the SNA communications server.
System Action: The topology communications server logs the error and continues.
Operator Response: When the error occurs, verify that the SNA communications server daemons have been started. If not, then start them. If the problem persists, contact your system programmer.
System Programmer Response: If the condition persists, contact the Tivoli Support Center.
The communications server program was unable to establish a connection with the host. Verify that the Transaction Program Name (TPN) 30F0F4F4 does not appear in a SNA Communications Server TPN Profile.
Explanation: The topology communications server was unable to establish an LU 6.2 connection, possibly due to an error in the Transaction Program profile.
System Action: The topology communications server logs the error and continues.
Operator Response: When the error occurs, verify that the Transaction Program Name (TPN) 30F0F4F4 does not appear in the SNA communications server TPN Profile. If the problem persists, contact your system programmer.
System Programmer Response: If the condition persists, contact the Tivoli Support Center.
The communications server program received incorrect data from the host during connection establishment. The connection failed.
Explanation: The topology communications server received incorrect data from the host during connection establishment.
System Action: The topology communications server logs the error and continues.
Operator Response: When the error occurs, verify that the profiles for the session that the topology server is using are correct. Check the host logs for additional information. If the problem persists, contact your system programmer.
System Programmer Response: If the condition persists, contact the Tivoli Support Center.
The communications server program was unable to establish a connection with the host. Data received from a GET_PARAMETERS request was incorrect.
Explanation: The topology communications server received incorrect data from the host during connection establishment. A GET_PARAMETERS request failed.
System Action: The topology communications server logs the error and continues.
Operator Response: When the error occurs, verify that the profiles for the session that the topology server is using are correct. Check the host logs for additional information. If the problem persists, contact your system programmer.
System Programmer Response: If the condition persists, contact the Tivoli Support Center.
The communications server program failed on a SNA OPEN request.
Explanation: The topology communications server received incorrect data from the host during connection establishment. An OPEN request failed.
System Action: The topology communications server logs the error and continues.
Operator Response: When the error occurs, verify that the profiles for the session that the topology server is using are correct. Check the host logs for additional information. If the problem persists, contact your system programmer.
System Programmer Response: If the condition persists, contact the Tivoli Support Center.
The communications server program failed on a SNA Open. The maximum number of allowed file descriptors is currently open.
Explanation: The topology communications server received incorrect data from the host during connection establishment. An OPEN request failed because the maximum number of allowed file descriptors has been reached.
System Action: The topology communications server logs the error and continues.
Operator Response: When the error occurs, stop daemons and programs that are running that are not needed. Increase the system limit for the number of allowed file descriptors. If the problem persists, contact your system programmer.
System Programmer Response: If the condition persists, contact the Tivoli Support Center.
The communications server program failed on a SNA ALLOCATE_LISTEN request. SNA processing is ending.
Explanation: ALLOCATE_LISTEN registers a list of LU 6.2 TPNs for which the server wants to accept allocate requests from remote transaction programs. This registration failed. This problem is generally caused by a configuration error. Further LU 6.2 communications with the host are not possible. To re-enable LU 6.2 support, recycle the topology communication server.
System Action: The topology communications server logs the error and terminates.
Operator Response: When the error occurs, verify that the profiles for the session that the topology server is using are correct. Check the host logs for additional information. If the problem persists, contact your system programmer.
System Programmer Response: If the condition persists, contact the Tivoli Support Center.
The communications server program failed on a SELECT request. Possible storage allocation problem.
Explanation: The SELECT function is used to check the I/O status of one or more connections. An unexpected error was returned from this function.
System Action: The topology communications server logs the error and terminates.
Operator Response: Stop all of the topology daemons with tserver stop. Run tserver stop with the -f flag and then restart the daemons. If the problem persists, contact your system programmer.
System Programmer Response: If the condition persists, contact the Tivoli Support Center.
The communications server program failed on a SNA GET_PARAMETERS request. SNA processing is ending.
Explanation: The server was attempting to retrieve data associated with the receipt of an allocate request for the server's TPN, when and error occurred on the connection.
System Action: The topology communications server logs the error and terminates.
Operator Response: Stop all of the topology server daemons by issuing tserver stop, followed by tserver stop -f. Then restart the daemons. If the problem persists, contact your system programmer.
System Programmer Response: If the condition persists, contact the Tivoli Support Center.
The communications server program encountered an error while allocating a conversation with the host. The session from the host to the workstation is terminated.
Explanation: The topology communications server encountered an error while allocating a conversation with the host. The session from the host to the workstation is terminated. This problem is generally caused by a configuration error.
System Action: The topology communications server logs the error and continues.
Operator Response: When the error occurs, verify that the profiles for the session that the topology server is using are correct. Check the host logs for additional information. If the problem persists, contact your system programmer.
System Programmer Response: If the condition persists, contact the Tivoli Support Center.
The communications server program encountered an error while allocating a conversation with the host. The session parameters conflicted with those at the host.
Explanation: The topology communications server encountered an error while allocating a conversation with the host. The session parameters conflicted with those at the host.
System Action: The topology communications server logs the error and continues.
Operator Response: When the error occurs, verify that the profiles for the session that the topology server is using are correct. Check the host logs for additional information. If the problem persists, contact your system programmer.
System Programmer Response: If the condition persists, contact the Tivoli Support Center.
The communications server program received an incorrect number of parameters from a GET_PARAMETERS request. The connection to the host has failed.
Explanation: The topology communications server received an incorrect number of parameters from a GET_PARAMETERS request. The connection to the host has failed.
System Action: The topology communications server logs the error and continues.
Operator Response: When the error occurs, verify that the profiles for the session that the topology server is using are correct. Check the host logs for additional information. If the problem persists, contact your system programmer.
System Programmer Response: If the condition persists, contact the Tivoli Support Center.
The communications server program was unable to allocate a session with the host. The connection to the host has failed.
Explanation: The topology communications server was unable to allocate a session with the host. The connection to the host has failed.
System Action: The topology communications server logs the error and continues.
Operator Response: When the error occurs, verify that the profiles for the session that the topology server is using are correct. Check the host logs for additional information. If the problem persists, contact your system programmer.
System Programmer Response: If the condition persists, contact the Tivoli Support Center.
The communications server program received a SIGUSR1 signal. Communications with the host may be lost.
Explanation: The topology communications server received a SIGUSR1 signal. The SNA communications server issues a SIGUSR1 when a connection is lost. It is possible the communications with the host may have been terminated.
System Action: The topology communications server logs the error and continues.
Operator Response: A SIGUSR1 is generated when the communications server is stopped. Restart the SNA communications server. If the problem persists, contact your system programmer.
System Programmer Response: If the condition persists, contact the Tivoli Support Center.
The communications server program was unable to send data to the host. Either the session was deactivated or data was delivered to the host in error. The session is terminated.
Explanation: The topology communications server was unable to send data to the host. Either the session was deactivated or data was delivered to the host in error. The session is terminated.
System Action: The topology communications server logs the error and continues.
Operator Response: When the error occurs, verify that the profiles for the session that the topology server is using are correct. Check the host logs for additional information. If the problem persists, contact your system programmer.
System Programmer Response: If the condition persists, contact the Tivoli Support Center.
The communications server program received a SIGDANGER signal. A paging space shortage may exist.
Explanation: The communications server received a SIGDANGER signal.
System Action: The topology communications server logs the error and continues.
Operator Response: A SIGDANGER signal indicates that paging space is low. Stop unneeded programs and/or increase paging space. If the shortage continues, stop the topology server. If the problem persists, contact your system programmer.
System Programmer Response: If the condition persists, contact the Tivoli Support Center.
TCP socket connection failed (connection refused).
Explanation: The topology communications server received a "connection refused" error code while attempting to set up a socket.
System Action: The topology communications server logs the error and continues.
Operator Response: When the error occurs, verify that the server that you are trying to connect to is running and ready to accept connections. Verify that a path exists to the server. If the problem persists, contact your system programmer.
System Programmer Response: If the condition persists, contact the Tivoli Support Center.
The topology communications server program was unable to load the SNA stack DLLs wappc32.dll and wincsv32.dll. The LU 6.2 communications function has been disabled.
Explanation: The topology communications server was unable to load the SNA DLLs wappc32.dll and wincsv32.dll. These DLLs are required if LU 6.2 communications is to be used for conversation with Tivoli NetView for z/OS.
System Action: The topology communications server logs the error and continues.
Operator Response: If LU 6.2 communications is not needed, then ignore this message. If LU 6.2 communications is needed, then verify that the location of these DLLs is included in the PATH environment variable. If the problem persists, contact your system programmer.
System Programmer Response: If the condition persists, contact the Tivoli Support Center.
Issue the tserver stop command to end this process.
System Action: After issuing tserver stop, the process is terminated.
Operator Response: Contact your system programmer.
System Programmer Response: Stop the process by issuing the tserver stop command from the $BINDIR/TDS/server/bin directory.
SNA communications have been disabled. Recycle the communications server to reestablish the service.
Explanation: The topology communication server thread controlling SNA communications has terminated. Refer to previous messages indicating why the thread was terminated.
System Action: The server continues to operate, but SNA communications are disabled.
Operator Response: If you need SNA communications, resolve the problem that caused SNA communications to terminate, then recycle the communications server.
The communications server is terminating due to an internal error.
Explanation: An unrecoverable error occurred in the topology communications server.
System Action: The communications server terminates.
Operator Response: Contact the system programmer responsible for the topology communications server.
System Programmer Response: Try to restart the communications server. If the problem persists, check the message and error logs. If you cannot correct the problem, contact your Tivoli Support Center.