Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Not under consideration
Workspace Informix
Components Informix Server
Created by Guest
Created on May 31, 2016

Log DRDA listener messages to online.log similar to current logging of the SQLI listener.

The DRDA listener (drsoctcp) is not logging any error messages to the online.log. The SQLI listener (onsoctcp) does log messages when, for example a wrong username is being used to connect to the instance:

15:45:00 listener-thread: err = -951: oserr = 0: errstr = wrong_user@hostname: Incorrect password or user wrong_user@hostname is not known on the database server.

When the same test is done using drsoctcp, there is no message generated in the online.log. This difference makes tracing problems confusing for the DBA.

The listener also won't report errors/messages whenever garbage is being sent over the connection. When you connect to the onsoctcp listener using telnet and disconnect the session, or when you send some random characters the listener will generate the following messages:

15:49:39 listener-thread@soc_be.c:3073: err = -25582: oserr = 4: errstr = from 192.168.190.1 to server ids1210_tcp : Network connection is broken.
System error = 4.
15:49:57 listener-thread@asfslsqi.c:1484: err = -408: oserr = 0: errstr = from 192.168.190.1 to server ids1210_tcp : Invalid message type received from the sqlexec process.


In the case of the drsoctcp listener, again no messages are being reported. These messages are very useful when somebody is scanning/probing the database server ports.