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.
[This requirement originates from JPMC EDW/RTC group] The db2diag.log is an extremely useful reference for both customers and db2support persons. We are able to identify milestones events, find errors, and gather clues to their issues, all before engaging DB2 Support. Over the past few releases, the db2diag.log has become cluttered with informational messages (even at diaglvl 3) which makes examining the db2diag.log for milestones and clues very very difficult if not impossible. For example, in v10, this HADR message litterally clutters the db2diag.log 2013-02-08-00.10.22.845483-300 I3432132512A534 LEVEL: Info PID : 7864458 TID : 10966 PROC : db2sysc 0 INSTANCE: vpcinp01 NODE : 000 HOSTNAME: cto2a191n1.svr.us.jpmchase.net EDUID : 10966 EDUNAME: db2lfr.0 (VPCDB) 0 FUNCTION: DB2 UDB, data protection services, sqlplfrFMRefreshXhdr, probe:5233 DATA #1 : LFR Scan Num = 80721764 LFR Scan Caller's EDUID = 22791 Refreshing Xhdr for log S0002480.LOG with page count of 499984 and extent size of 499984 The purpose of this requirement is to generate visibility/change within the DB2 Development teams to use precaution when adding db2diag.log entries: use diaglvl 4 when possible, be aware of repetitious entries, be user friendly. Alternately, if the db2diag.log is to be used as an ibm-internal mechanism, then this requirement is to add more value to the notify .nfy log file. Currently the notify .nfy log file is not useful to customers or support persons.
Do not place IBM confidential, company confidential, or personal information into any field.