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.
new accounting trace field to indicate if distributed connection was secure or not
We have recently enabled the SECPORT in all our Db2 subsystem. And now it is possible for a distributed client to use the SECPORT (instead of TCPPORT) and establish a secure SSL/TLS connection to the Db2.
Ideally, I would like to shut down the unsecure TCPPORT in the future. It would make some auditor or security people happy.
I would imagine that many Db2 shops in the world are beginning to have the requirement for all clients to exclusively use TLS/SSL and the SECPORT. This seems very likely to me. And therefore,, IBM and Db2 should make it easier for us to make this transition!
Of course, I will do my best to give client config updates and instructions to all known client computers of Db2. This is my first step.
But some people will not receive instructions or not follow instructions.
I would like some assistance from Db2 in knowing who is using a secure or regular connection to Db2!
I have learned that some IFCIDS like 180 exist and give the Db2 port (thanks to Norbert Jenninger via IDUG-listserv). But this is an expensive trace to run and a hassle to effectively report.
I think it is reasonable for the Db2 accounting trace to include some new field/indicator to indicate if the distributed/DRDA connection was secure or not.
Or give me some information in the accounting trace that will help me easily identify who is using a secure connection.
With this new accounting information, I should be able to automate a search of my client computers and how they connect. This will help me reach the end-users who do not update their client config and then go encourage them to update their computer.
Of course, after this new information is available in accounting trace … then I want the OMEGAMON XE for DB2 performance database (db2pmfacct_general) to be updated to accept this new information.
The benefit of this idea is that it will help me more quickly identify all clients who do not update their config. Otherwise, there is a risk, when I turn off TCPPORT, that some important client (who ignored me) breaks and we have problem.
Do not place IBM confidential, company confidential, or personal information into any field.