This is an IBM Automation portal for Integration products. 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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
WMB - provide ODBC information in a configurable service
ODBC data source configuration information is current provided to Unix platform WMB brokers in a single flat file (odbc.ini). This file is very sensitive to small changes, such as a trailing blank on the stanzas causing problems. Also a problem may affect every ODBC connection definition as they are all in the same file. This makes updating this file a risky process and we want to see an alternative that is more like the FTP configurable service.
So a new type of configurable service should be made available that can contain the same information that currently resides in ODBC.ini. There would be one configurable service entry of this type per Data Source and so updating one of these would not risk any inadvertant change or loss of service to other ODBC data sources.
It would also facilitate the automation of ODBC information updates using commands in scripts - currently this would be very hard to achieve.
The configurable service entry would, at a minimum be able to hold the hostname, database name (SID or SERVICE NAME), port number and other frequently updated values. Clearly there would have to be some allowance for the dfifferent types of Database and it would be acceptable to have different types of configurable service for Oracle, Sybase, DB2, and SQL Server.
The use of these service definitions would be optional but would override any entry in ODBC.ini for the data source and keywords specified (in the event that both entries existed). Longer term the use of ODBC.ini should be deprecated as it is a cumbersome way to hold configuration data.
Alternatively the configurable service entry for the data source could refer to a particular ODBC.ini file, so that it was possible to isolate the definitions into separate files - again achieving the aim of removing the risk of affecting unrelated items during a change.
Do not place IBM confidential, company confidential, or personal information into any field.