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 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
ACS - RunSQL scripts - Add function usage feature to block Run SQL Scripts
We would like to use WRKFCNUSG entries to limit this access by specific user ID's at the partition level. The existing controls to disable 'Run SQL Scripts' in the ACS emulator and Base product option does not work at the partition level. Ideally this could be extended to Toolbox for Java calls as well.
Reasoning: There may be instances where a particular person may install ACS without the registration entries in Windows required to block it at that level. Additionally the block would not be desired on all partitions (example: a Developer would need ODBC access to a Development partition but not a Production partition.)
There is an existing support document: https://www.ibm.com/support/pages/restrict-users-accessing-functions-access-client-solutions-acs - Restrict Users from Accessing Functions in Access Client Solutions (ACS) (ibm.com) that explains the process.
However, this process does not appear to work at all with ACS regardless of the settings being changed on the QIBM_XE1_ODBC entry. We have tried testing this on multiple IBMi 7.4 (TR4 & TR5) partitions with no success.
Is there a way to limit access from the partition level that does indeed work..
The only other option (drastic) we can think of is to use the process of redirection of incoming ODBC workload by user ID to an inactive subsystem. (Basically the approach of workload capping for ODBC/JDBC traffic by user ID to force the undesired traffic to be terminated).
The reply to this ticket was as follows:
My colleague on the data access team provided the following feedback:
On the ACS client the Run SQL Scripts feature can be restricted using steps 1 or 2 in the technote referenced. There is no function usage feature for Run SQL Scripts so it cannot be prevented in that way. Run SQL Scripts hasn't used ODBC for a very long time (V4R4?) it uses the Toolbox JDBC driver for connections. If the customer would like to add a function usage feature for Run SQL Scripts, he will need to submit a Request For Enhancement (RFE).
Prevent access to Run SQL Scripts in ACS at the partition level by user id using WRKFCNUSG or another method to allow such control.
This will prevent users from running SQL scripts via ACS where the access is not wanted while allowing the user to run this on other IBMi partitions where it is desired.
ACS Run SQL Script - Block users with CHGFCNUSG Option
Ideally we would like to use the existing WRKFCNUSG entries to limit this access by specific user ID's reasoning: There may be instances where a particular person may install ACS without the registration entries in Windows required to block it at ...
Do not place IBM confidential, company confidential, or personal information into any field.