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:
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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
An application wants to connect , but the connection fails with...
2017-08-18-18.01.07.462096+120 I549A473 LEVEL: Error PID : 11862032 TID : 25959 PROC : db2sysc 0 INSTANCE: tdbi30 NODE : 000 APPHDL : 0-17839 HOSTNAME: iuts527 EDUID : 25959 EDUNAME: db2agent () 0 FUNCTION: DB2 UDB, common communication, sqlccMapSSLErrorToDB2Error, probe:30 MESSAGE : DIA3604E The SSL function "gsk_secure_soc_init" failed with the return code "402" in "sqlccSSLSocketSetup".
That means, the application does not support any of the CIPHER_SPECS or the TLS protocol. We do not have any chance to detect the application (no userid, no IP).
We wanted to use GSKTRACE to find the client/application accessing with not supported CIPHER_SPECS, but the GSKTRACE generates only binary output. We need a tool to format the binary on Linux/UNIX/Windows platforms ... similar to the tool available for DB2 z/OS:
Do not place IBM confidential, company confidential, or personal information into any field.