This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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).
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:
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 updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
Using RBD & RDPi (Ver 8.0)
On the iSeries DB2 Database Connection Properties defining the Default Schema under Driver Properties is not working from the SQL Scrapbook/Script. I am under impression that opening the SQL Scrapbook/Script will always refer to the schema/library that was defined as Default Schema in the Connection Properties value. But while executing the sql query from the SQL Scrapbook/Script it's always referring to the user name as a default schema name.
What I am looking for is a concept of Library Lists (default to a list of schemas) in the DB2 Connection under Data perspective so that from a SQL Scrapbook or Script I don't have to mention the schema name/library names along with the table/file names. The query engine will be smart enough to first lookup in the Default Schema values for the files declared in the sql query. For example if I define the Default Schemas as SETHD; DIBYENDUS and if my SQL query is something like SELECT * FROM EMPMASTER, the query engine will lookup the file EMPMASTER first in schema/library SETHD, if not found then DIBYENDUS, if not will come up with the appropriate error. If the Default Schema values are not entered (left blank) then can be default to the user name (what it is doing currently).
For further reference please refer to the attached document.
Thanks & Regards
Dibs
Go to Data Perspective.
Connect to iSeries DB2 database
Right click of mouse on Connection and select Properties
Select Driver Properties option
Enter schema names on the field
Click OK
Now select the Connection and then select Open SQL Scrapbook
Execute a query without mentioning the schema/library name for the table/file and also make sure the table/file does not exists in the schema/library name which is same as user id in iSeries.
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Programming Languages
Product - Developer for Power Systems
For recording keeping, the previous attributes were:
Brand - Rational
Product family - Design & development
Product - Developer for Power Systems
Thank you for submitting the RFE. We have determined that the RFEs should be assigned to the IBM Data Studio team. Unfortunately IBM Data Studio is not on the RFE Community although we recommend you contact tech support for IBM Data Studio to submit the RFE.
I had submitted the same issue as a bug. APAR PM39632. The datatools are the responsability of the RAD application, so it has to fixed there first and will eventually get picked up by RD Power.
In the mean time, there is a work around, Instead of choosing the "ToolBox" driver, choose "Other" and specify all the properties there as they were on the Toolbox one. There is not input for the default schema, you need to put it in the URL: jdbc:as400:host/schema;property=value;
Attachment (Description): Screen Shots