Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Using Messages With Identifiers : UM: HCS

UM: HCS
S6BUM001E
Unable to allocate % bytes from system heap
HCS
The system has a temporary shortage of real memory.
If this problem occurs regularly, the system administrator should address the resource shortage in terms of system load, system configuration, and machine capacity.
S6BUM003E
Unable to open port, node '%' is not accessible via %
HCS
Communication with the node is not possible.
Either the node has not been configured for the appropriate transport mechanism, or the system you are on does not have access to that transport mechanism.
Keep in mind that Object Service Broker uses IPC to communicate with a node on the same system, otherwise it chooses TCP/IP.
Examine the HCS configuration file to ensure that the target node is properly configured. Ensure that it is addressable via the appropriate transport mechanisms.
S6BUM004E
Unable to open port, node '%' is not local and is not accessible on any network
HCS
Communication with the node is not possible. The node has not been configured for TCP/IP connectivity and it is not local to this system.
Examine the HCS configuration file to ensure that the target node is properly configured. Ensure that it is addressable via the appropriate transport mechanisms.
S6BUM013E
Inbound connection rejected, system resource shortage
HCS
An inbound connection could not be accepted due to a system resource shortage. This is likely a temporary shortage that should be alleviated when other processes end, or other users logoff.
No action required.
S6BUM014E
Unable to connect to node '%'
HCS
A connection could not be made to the target node. The specific reason for the failure may be indicated by an errno value that is part of the message, or by a previous message.
Review the errno and previous messages to determine the appropriate action.
S6BUM016E
Unable to connect to node '%', connection rejected
HCS
A connection was made to the target node, but the node rejected the logon. If this message occurs on a peer connection it may mean that the peer Data Object Broker has not been configured to expect a peer connection from the originator. It may also indicate that target node has run out of resources and is not able to accept the connection.
If the reasons for the rejected connection are not obvious, examine the Data Object Broker log at the target node for more information.
S6BUM018E
Unable to open % port for node '%'
HCS
The Data Object Broker could not open a port on the particular transport mechanism. The specific reason for the failure may be indicated by an errno value that is part of the message, or by a previous message.
Review the errno and the previous messages to determine the appropriate action.
S6BUM020E
Invalid connection information detected
HCS
This message may indicate a Data Object Broker internal problem.
Contact TIBCO Support. Be prepared to submit a copy of the Data Object Broker log file and any core file produced as a result of this problem.
S6BUM021E
Unable to perform SNA request, SNA libraries were not linked during installation
HCS
During the installation process, the installer indicated that SNA support was not available on the system. Consequently the current installation of TIBCO(r) Object Service Broker has not been linked to use the system's SNA services. The Data Object Broker, however, has been configured to use SNA to communicate with a peer Data Object Broker.
Either modify the Data Object Broker configuration so that connections to SNA nodes are not required, or (assuming that SNA services are available on the system) re-link TIBCO(r) Object Service Broker so that SNA connectivity is enabled. Refer to the Installation and Operations manual for instructions on how to re-link TIBCO(r) Object Service Broker to enable SNA connectivity.
S6BUM050E
Syntax error '%', expecting %
HCS
A syntax error was detected while parsing the HCS configuration file. The offending token is included in the message along with a description of what was expected. A subsequent message should indicate the file name and line number where the problem occurred.
Verify the syntax of the node definition.
S6BUM051E
Line exceeds % characters
HCS
A line in the HCS configuration file was longer than the expected maximum length. A subsequent message should indicate the file name and line number where the problem occurred.
Edit the file to ensure that the lengths of all the lines are within the limit specified.
S6BUM052E
Unrecognized keyword '%'
HCS
While scanning the HCS configuration file an invalid keyword was encountered. A subsequent message may identify where the problem occurred.
Verify the syntax of the node definition.
S6BUM054E
Node name not specified
HCS
A definition in the HCS configuration file does not have a NAME attribute. A subsequent message should indicate the file name and line number where the problem occurred.
Verify that the node definition is complete.
S6BUM055E
Unknown host name '%', node='%'
HCS
The HOST name specified in the node definition is not known at this system. The HOST name may be misspelled, or it may not be defined locally (in /etc/hosts) or at the name server.
Verify that the HOST name is spelled correctly. If the HOST name is correct then contact the system administrator to have the name defined using the appropriate facility. Adding the IP attribute to the node definition may allow you to proceed if you are simply trying to connect to a node.
S6BUM056E
Host name and specified IP address do not correspond, node='%'
HCS
A HOST attribute and an IP attribute have both been specified in the definition of the node, but the IP address does not correspond to the HOST name.
Ensure that the IP address is the correct one for the HOST name.
S6BUM057E
System host name '%' is not known to network
HCS
The local system has not yet been fully configured. The system name is not defined locally (in /etc/hosts) or at the name server.
Contact the system administrator to have the system name defined using the appropriate facility.
S6BUM058E
Unable to determine system host name
HCS
The local system has not yet been fully configured. The system name has not been set.
Contact the system administrator to have the system name set.
S6BUM059E
Unknown service name '%', node='%'
HCS
The SERVICE name specified in the node definition is not known at this system. The SERVICE name may be misspelled, or it may not be defined locally (in /etc/services) or at the name server.
Verify that the SERVICE name is spelled correctly. If the SERVICE name is correct then contact the system administrator to have the name defined using the appropriate facility. As an alternative replace the SERVICE name with an actual PORT number.
S6BUM060E
Service name and specified port do not correspond, node='%'
HCS
A SERVICE attribute and a PORT attribute have both been specified in the definition of the node, but the PORT number does not correspond to the SERVICE name.
Ensure that the PORT number is the correct one for the SERVICE name.
S6BUM061E
Alias or LU name not specified, node='%'
HCS
The node NAME is greater than 9 characters long and no ALIAS or LU name has been given for the node. Although node names can be up to 16 characters in length, Object Service Broker requires an 8-character identifier that tags the node both internally and on administrative controls. On z/OS, this is the LU name. On Windows and Solaris, this is either the LU name (if it is given), the node NAME (if it is 8 characters or less in length), or the ALIAS.
Add an ALIAS to the definition on the node.
S6BUM062E
Node '%' is not defined in directory '%'
HCS
The node is not defined in the HCS configuration file.
Verify that the node name is spelled correctly both as it is given and in the HCS configuration file.
S6BUM063E
Error detected at line % of directory '%'
HCS
An error occurred while scanning through the HCS configuration file. A previous message should indicate the specific error detected.
Review the previous messages to determine the appropriate actions to take.
S6BUM064E
Unexpected end of file encountered
HCS
While scanning a node definition in the HCS configuration file, the end of file was encountered. This probably means that the last attribute in the last node definition had a comma indicating there were more attributes to come.
Verify the syntax of the node definition.
S6BUM070E
Unable to open directory '%'
HCS
The HCS configuration file could not be opened. The specific reason for the failure is indicated by the errno value that should be part of this message.
Review the errno to determine the appropriate action to take.
S6BUM071E
Unable to read directory '%'
HCS
The HCS configuration file could not be read. The specific reason for the failure is indicated by the errno value that should be part of this message.
Review the errno to determine the appropriate action to take.
S6BUM072E
Unable to close directory '%'
HCS
The HCS configuration file could not be closed. The specific reason for the failure is indicated by the errno value that should be part of this message.
Review the errno to determine the appropriate action to take.
S6BUM102I
TCP/IP library call failed: %
HCS
This message traces the failure of a TCP/IP function. In most cases a subsequent message will indicate the effects of the failure (for instance, the loss of connection). The error description and/or errno value may be useful in determining TCP/IP communication problems.
Consult the appropriate TCP/IP programming manuals for your system to determine the meaning of the error information.
S6BUM103I
System call '%' failed, errno=% [%]
HCS
A System call failed during the attempt to open a socket listing port or a remote location. A subsequent message will detail the impact of the error.
Review the error code for the system call and the following message to determine what action to take.
S6BUM105E
Procedure % address not found; Windows extended message %
HCS
This message indicates a failure of the Windows GetProcAddress function to find the indicated procedure. The Windows extended message gives additional information. Most likely cause is a corrupted DLL.
Get a fresh copy of the WAPPC32.dll or WINCSV32.dll files.
S6BUM106I
ioctl() request % failed, errno=%
HCS
This message traces the failure of an ioctl call. A subsequent message indicates the effects of the failure. The errno value can be useful in determining the problem.
Consult the system documentation for network interfaces to determine the meaning of the error information for the ioctl request.
S6BUM107E
Unable to get network interface configuration list
HCS
The list that fully describes all network interface configurations for the local machine cannot be obtained. This list is needed when determining if a node is local.
Contact TIBCO Support. Be prepared to submit a copy of all log files containing this message. Any Data Object Broker log file submitted should be from a Data Object Broker configured such that the ERRNOTRACE parameter has not been set N. This will ensure that the Data Object Broker log file will contain system and internal error tracing.
S6BUM108E
Keep-alive monitor error, pthread call ';' failed with return code ;and errno ;
HCS
TCP keepalive processing failed when making a call to the Pthreads library. Keepalive processing for the Execution Environment was likely terminated.
TCP keepalive polls can be activated by a user by using the keepalive parameter for a node in the huron.dir configuration file. On the Solaris platform TCP keepalive polls are implemented using a keepalive monitor thread and out-of-band TCP/IP messages. An error was detected when starting the monitor thread or when interfacing with the thread. Review the errno value to determine the cause of the failure.
S6BUM109E
Keep-alive probe sent to node ';' failed with errno=;, keep-alive probes for connection disabled
HCS
The send of a TCP keepalive probe to a remote node failed. Keep-alive probes will no longer be sent to the remote location.
TCP keepalive probes are enabled for a remote node by using the keepalive parameter for the definition of the node in the huron.dir configuration file. Review the errno to determine why the socket send of the keepalive probe failed.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved