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.
DB2 listener not activated after DB process killed by OS and restarted automatically by TSA in HADR environment
We had DB2 HADR primary/standby configuration. Due to one application job,DB2 consumes all memory and OS killed db2sysc process. db2 restarted automatically by TSA but listener wasn't activated . There was no evidence in logs which process was usi...
To monitor system resource usage at database level in a pureScale environment
All current monitoring facilities can not meet customer requirements to monitor overall system resource consumed for a specific database, in a database consolidation scenario of pureScale.PMR#: TS000078803
In a HADR configuration typically customers use db2pd -hadr on the standby to monitor the state. On the standby if there is a problem with one of the tablespaces it'll be marked invalid and future log records against the tablespace will be skipped...
Invoke the DB2 call-out scripts (COS) for ALL First Occurrence Data Collection (FODC) events
Currently the DB2 call-out scripts (COS) will not be invoked for all ALL First Occurrence Data Collection (FODC) events. For instance the only time that FODC_AppErr% events will invoke the db2cos script is when the condition happens on a sub-agent...
Begin / End COMMIT instrumentation for DRDA, CICS/IMS
Complex CICS/IMS or DRDA transactions (involving multiple programs with an implicit Commit at the end) are incorrectly presented on the Omegamon Accounting Report/Trace. By design the costs of the tough SYNC (COMMIT) operation are added to the las...
Enhancement regarding the .ftok file and the DB2 instance.
I will suggest the following:1. Let Db2 log a simple message 'The .ftok file is missing, last seen ' when the instance started.2. Also, suggest to execute ~/sqllib/bin/db2ftok or go ahead and execute it
Lack of information about Queries from Federated DBs - particulary from DB2 z/OS
From DSM we should be able to see the transactions from federated databases. In the case when we are having some federated transaction contention we are not able to see on the source database on DSM getting more difficulty to diagnose a performanc...
Lock event monitor does not log hex values of prepared statements
When using the lock event monitor to track prepared statements involved in lock timeouts/deadlocks, it was observed that parameter marker values for hex entries are not logged even though the option for history and values is enabled. This works fi...
reduce I/O activity to /etc/services upon each connect
Using filemon, we see 191 accesses to /etc/services for each Connect statement. It seems this file should only be accessed once or twice. This has been verified by IBM personnel with ticket TS001677150.
Do not place IBM confidential, company confidential, or personal information into any field.