IBM Power Ideas Portal
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).
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 updates on 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
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.
IBM's recommendation is to add checks to the exit point processing program to determine the interface that is being used. If an interface is not interesting, the exit program should return immediately.
Db2 for i development team
IBM Power Systems Development
Just to confirm, you are using ACTGRP(*CALLER) for your exit point programs, right?
Also if you're using RPG IV and the RPG Logic Cycle is being used that too would severely impact performance. I would recommand either using the C or C++ language, or if RPG IV is desired, then be use to use the NON-Cycle form of RPG IV by including the MAIN keyword in the CTL-OPT (aka, Header spec) in that exit program.
Using MAIN along with ACTGRP(*CALLER) would help performance if you're not already doing that.
IBM will use this request as input to planning but no commitment is made or implied. This request will be updated in the future if IBM implements it.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Db2 for i
Operating system - IBM i
Source - Client
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Work Management and Messaging
Operating system - IBM i
Source - Client
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Work Management and Messaging
Operating system - IBM i
Source - Client
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Db2 for i
Operating system - IBM i
Source - Client
this also refers to ticket TS004052785
One customer reports massive performance issue using DB_OPEN on a single job (3 hours with, 1 hour without) so they stopped using that exit point which left a security problem due to not monitoring the access. They urgently ask for a comment or solution.
Due to the high number of calls even the call itself does create a lot of work even if the processing program in the exit point is simply exiting without further processing.
Hello Michael, the QZDA.. exit points request to build an own parser that checks the incoming sql statement. Such a statement can be very complex and it may fail to detect the files used. The DBOPEN exit point is 100% accurate in detecting the files even in the complexest sql statement.
Can't this functionality be accomplished via the QZDA_____ exit points instead of QIBM_QDB_OPEN?
These are not hit for native access.
The COMMON Europe Advisory Council (CEAC) has reviewed this requirement and recommends that IBM view this as a MEDIUM priority requirement that should be addressed.
Background: The CEAC members have a broad range of experience in working with small and medium-sized IBM i customers. CEAC has a crucial role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community and has therefore reviewed your RFE.
To find out how CEAC help to shape the future of IBM i, see CEAC @ ibm.biz/BdYSYj and the article "The Five Hottest IBM i RFEs Of The Quarter" at ibm.biz/BdYSZT
Therese Eaton – CEAC Program Manager, IBM
Niels,
maybe split between 127.0.0.1 and RestOfWorld, or (if internally possible)
to differentiate between RLA on Cobol/RPG and general ODBC/JDBC interfaces.
Main reason for this is a customer working on billions of records changes at night with some old RPG 2.5 code and
in parallel uses the tables from external.
I like your idea however it raises some questions:
How will you determine that ODBC is not from a "native" python or node.js program. The question here is: what is native to you? You can also say the same for any JDBC connection.