Topic
  • 1 reply
  • Latest Post - ‏2013-06-14T14:29:58Z by amccarl
amccarl
amccarl
73 Posts

Pinned topic SQL30081N TCPIP communication error

‏2013-06-11T20:49:37Z |

The SQL30081N error message has the following format:


SQL30081N A communication error has been detected. Communication protocol being used: protocol . Communication API being used: interface . Location where the error was detected: location . Communication function detecting the error: function . Protocol specific error code(s): rc1 rc2 rc3 

For example:
SQL30081N A communication error has been detected. Communication protocol
being used: "TCP/IP". Communication API being used: "SOCKETS". Location
where the error was detected: "". Communication function detecting the error: "connect".
Protocol specific error code(s): "111", "*", "*".

Technical article 1164785 lists specific errors that can occur on different platforms and the corresponding action plans to resolve these errors.

Updated on 2013-06-14T14:39:16Z at 2013-06-14T14:39:16Z by amccarl
  • amccarl
    amccarl
    73 Posts

    Re: SQL30081N TCPIP communication error

    ‏2013-06-14T14:29:58Z  
    Hello!  We've had a number of clients respond through feedback to our technical documents indicating that they have further questions or comments that require additional dialogue.  Unfortunately, our feedback is anonymous, so unless an email address or other contact information is included, we have no way to get back in touch with you.
     
    Within DB2 support, the management team asked if we could somehow link our documents to the forums so that we could invite more discussion - like this!   As a start, we chose a small set of  technical articles and "seeded" the forum with initial entries so that we could have a starting place for conversation.  The documents have now been updated with links to the forums as well.  
     
    Hopefully, we will make DB2 support better by providing more interaction around our technical information!