![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
TCP/IP RELAY started; Incoming connections will not be acceptedCommunications services will not accept incoming TCP/IP connections for this component.If the component needs to accept connections from TCP/IP then look in the job log for previous messages that will explain why connections will not be accepted. Look at your RELAY parameter file to ensure that the communication identifier for your component is defined correctly.Outbound connection rejected. Insufficient number of socket handlesTCP/IP connection could not be established because no more socket handles could be opened.Increase the maximum number of socket handles for the component using the RELAY parameter file. Either increase the maximum number of sockets for a TCP/IP RELAY TCB by incrementing the "maxtcbsockets" parameter or increase the number of TCP/IP RELAY TCBs by incrementing the "tcbnum" parameter.Attach of TCP/IP communications task failed with R15=%TCP/IP RELAY initialization failed when attaching a relay TCB. TCP/IP support for the Object Service Broker component is unavailable. R15 contains the return code from the ATTACH macro that failed.Refer to the description of the return codes for the ATTACH macro in the IBM MVS Authorized Assembler Services Reference manual to determine what action should be taken.Initialization of TCP/IP communications RELAY task failedInitialization of the TCP/IP RELAY failed. TCP/IP support for the component is disabled.Refer to the previous message for more information.Obtain of storage failed during intialization of TCP/IP RELAY with R15=%Initialization of the TCP/IP RELAY failed when allocating memory. TCP/IP communications support has been disabled. R15 contains the reason why the STORAGE macro failed.Refer to the description of return codes for the STORAGE macro in the IBM MVS Assembler Services Reference manual to determine the action to be taken.Communications identifier "%" not defined in the RELAY parameter fileOpen of communications node failed because the node was not defined in the RELAY parameter file.Assure the communications identifier is defined in the directory section of your RELAY parameter file.TCP/IP RELAY started; Accepting connections on interface address % socket port=%TCP/IP support for the component successfully initialized. New socket connections are being accepted on the adapter interface and port number displayed.TCP/IP support for the component has been terminated. New socket connections are no longer being accepted.Connection to node "%" failed; Host "%" is unavailableOpen of a TCP/IP connection failed because the host was unavailable.Assure that the correct host name or IP address was used in the definition of the communication identifier in the directory section of your RELAY parameter file.Connection to node "%" failed; CONNECT socket request failed with errno=%Open of a new connection failed because socket connect called error.Refer to the return code appendix of the IBM IP Sockets Application Programming Interface Guide and Reference to determine the meaning of the errno value and the action to be taken.Connection to the node was rejected or the socket port for the node was not open.Verify that the remote node has been started. If the node is running then check the job log for the node to determine why the connection was rejected.Socket receive error with errno=%; TCP/IP connection closedA socket receive error was detected during the exchange of data between the component and a TCP/IP remote communications node. The connection was closed.Refer to the return code appendix of the IBM IP Sockets and Application Programming Guide and Reference to determine the meaning of the errno and the action to be take. The most common cause is that the remote node closed the connection.Socket send failed during the exchange of data to the remote node. The connection was automatically closed.If this problem repeats then contact TIBCO Support.Failed to allocate DXE memory; TCP/IP connection closedThe TCP/IP RELAY failed to allocate memory for a buffer for a receive request. The connection was automatically closed.RELAY connection failed with RC=%; TCP/IP connection closedTCP/IP RELAY could not open a Cross Memory connection for the new TCP/IP connection. The new client connection was automatically closed.View the SYSLOG for additional data on the error, and contact TIBCO Support if further assistance is required.Remote connect sent data when it was not expected. The connection was automatically closed.A non Object Service Broker application may be attempting to use the Object Service Broker port. Otherwise contact TIBCO Support.Open of socket listening port failed; % request failed with errno=%Open of the Object Service Broken listing port failed. TCP/IP support was disabled.Refer to the return code appendix of the IBM IP Sockets Application Programming Interface Guide and Reference to determine the meaning of the errno value and the action to be taken.Could not determine socket port number for node communications identifier %The service name used in the definition of the port number for the communication identifier could not be resolved.Review the directory section of your RELAY parameter file and assure the correct service name has been specified. If the name is correct then assure that the service name is defined for your MVS system.Connection to node "#" failed; GETSOCKOPT socket request failed with errno=#Outbound connection to node failed. GETSOCKOPT was called to confirm whether non-blocking socket connect was successful but the call failed.Refer to the return code appendix of the IBM IP Sockets Application Programming Interface Guide and Reference to determine the meaning of the errno value and the action to be taken.Host name "%" for communications identifier "%" could not be resolvedHost name could not be resolved to an IP address.Assure that the host name for the communications identifier was entered correctly in the directory section of your RELAY parameter file. Otherwise the name specified may not be defined on your MVS command. Use the PING command on your MVS system to determine whether the host name is correct.Cannot open socket for communications identifier %Look at the previous message for more information.Communications identifier could not be found in the directory section of your RELAY parameter file.Assure the communications identifier has been entered correctly in your RELAY parameter file.Failed to put socket into nonblocking mode; FCNTL socket requestfailed with errno=#Call to FCNTL failed when attempting to put a socket into non-blocking mode. The new connection was automatically closed.Refer to the return code appendix of the IBM IP Sockets Application Programming Interface Guide and Reference to determine the meaning of the errno value and the action to be taken.Accept of new inbound socket connection failed; GIVESOCKET failed with errno=%New inbound connection was rejected because of a GIVESOCKET error.Refer to the return code appendix of the IBM IP Sockets Application Programming Interface Guide and Reference to determine the meaning of the errno value and the action to be taken.New inbound socket connection was rejected. ACCEPT socket API call failed.Refer to the return code appendix of the IBM IP Sockets Application Programming Interface Guide and Reference to determine the meaning of the errno value and the action to be taken.Cannot open new connection; maximum number of open sockets exceededNew socket connection was reject because the limit of open socket connections was exceeded.The number of socket connections is limited by TCP/IP configuration parameters in your RELAY configuration file. Depending on you circumstance either increase the number of sockets for each TCP/IP RELAY task by the maxtcbsockets parameter or increase the number of TCP/IP tasks by using the tcbnum parameter.Bad command code sent to TCP/IP RELAY select taskThe TCP/IP RELAY select task received a bad command code. The request was ignored and normal operation was continued.The TCP/IP RELAY detected a bad queue of work from its Communications Services SEND/RECEIVE exit. Some TCP/IP connections have been left in an indeterminate state but the relay is continuing processing.Object Service Broker expected that data is to be received from the TCP/IP Connection but Object Service Broker is attempting to SEND data to the connection. The connection was automatically closed.If this message is received as part of CANCELUSER/LOGOFF processing it should be ignored. Otherwise if it cannot be determined why Object Service Broker is attempting to SEND data to a connection whose next expected communication is to RECEIVE data then Contact TIBCO Support.A socket error was detected when data was sent to the TCP/IP client.Refer to the return code appendix of the IBM IP Sockets and Application Programming Guide and Reference to determine the meaning of the errno and the action to be take.Cross-Memory control error detected when a TCP/IP connection was closed.Contact TIBCO Support if this error persists.SOCKET socket request failed and new out-bound connection failed to open.Refer to the return code appendix of the IBM IP Sockets and Application Programming Guide and Reference to determine the meaning of the errno and the action to be take.Refer to the return code appendix of the IBM IP Sockets and Application Programming Guide and Reference to determine the meaning of the errno and the action to be take.Resolution of host name to an IP address failed.Refer to the return code appendix of the IBM IP Sockets and Application Programming Guide and Reference to determine the meaning of the errno and the action to be take.The TCP/IP protocol stack name defined by the tcpname parameter in your RELAY parameter file is not defined on your MVS system. TCP/IP support has been disabled.Assure the name entered is defined on your MVS system.The TCP/IP protocol stack name defined by the tcpname parameter in your RELAY parameter file is disabled. TCP/IP support has been disabled.Verify that the correct name was specified in the RELAY parameter file. If so then contact your TCP/IP system administrator to enable the image.The TCP/IP relay failed to initialize its connection to the MVS system TCP/IP image. TCP/IP support has been disabled.Refer to the return code appendix of the IBM IP Sockets and Application Programming Guide and Reference to determine the meaning of the errno and the action to be take.Socket SELECTEX failed with errno=#; the TCP/IP RELAY is terminatingSELECTEX socket called failed. TCP/IP support was terminated for the component.Refer to the return code appendix of the IBM IP Sockets and Application Programming Guide and Reference to determine the meaning of the errno and the action to be take.TAKESOCKET failed with errno=%; socket connection request rejectedIn-bound socket connection was rejected because TAKESOCKET socket call failed.Refer to the return code appendix of the IBM IP Sockets and Application Programming Guide and Reference to determine the meaning of the errno and the action to be take.Socket message contains an incorrect length; connection closedBad message was received from a socket client. The message length did not match the length of data read. The socket connection was closed.Assure that the client attempting a connection was a Object Service Broker client or component.Bad host address in HOSTENT entry; connection closedWhen opening an new out-bound TCP/IP connection a bad HOSTENT structure was detected from a GETHOSTBYNAME socket call. The new socket connection was not opened.Bad command code received by TCP/IP RELAY control taskThe TCP/IP RELAY control task received a bad internal message. The request was ignored and processing was continued.If this problem persists the contact TIBCO support.GETCLIENTID TCP/IP system call failed. The relay control task could not obtain the socket identifier for a new connection. This identifier is required to pass the socket to a TCP/IP relay select task.Refer to the return code appendix of the IBM IP Sockets and Application Programming Guide and Reference to determine the meaning of the error and the action to be take.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |