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.
In SPSS Deployment Manager, I have a Job with a Job Step, where the "Mode" of one of the ODBC Data Sources in the underlying SPSS Modeler Stream was recently changed from "Table" to "SQL Query". After refreshing the job step to use the version of the Modeler Stream, the "Database" column on the "ODBC Data Sources" tab is still showing the name of the table that was previously used by the Data Source node. However, when executing the job it correctly uses the "SQL Query" stored in the Data Source node from the underlying Modeler Stream. It would seem that the "Database Table" column on the "ODBC Data Sources" tab will always show the "Table name" from the "Table" mode of the Data Source (unless changed by the user in the job step). Since the "ODBC Data Sources" tab has no indication of the "Mode" used by the Data Source node, there is no way to determine the table/query that the individual data source in the job step is referencing without examining the Data Source node in the underlying Modeler Stream. Steps to recreate: 1) Create a Modeler Stream with at least one "Database" source node. 2) Edit the "Database" source node and select a "Data Source". 3) Enter the name of a valid database table in the "Table name" box. 4) Change the "Mode" to "SQL Query" and enter a valid SQL query that queries data from a different table than the one used in step (3). 5) Store the stream in the repository. 6) In Deployment Manager, connect to the repository where the stream from step (5) is stored and create a job that uses that stream as a job step. 7) Select the job step and go to the "ODBC Data Sources" tab. The "Database Table" column will show the table name entered in step (3). 8) Complete the configuration of the job and execute it. 9) The job step will execute the SQL Query entered in step (4).
Do not place IBM confidential, company confidential, or personal information into any field.