Skip to Main Content
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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.

Status Not under consideration
Workspace IBM i
Categories Db2 for i
Created by Guest
Created on Sep 25, 2017

Logging / Monitoring SQL activity after and within a DRDA connection session

The IBM i O/S does not have the ability to monitor SQL transactions via DRDA connection from a remote system. This would be from the exit point DDM/DRDA request access in the network attributes (DSPNETA).


Use Case:

I would like to have the ability to block SQL transactions via DRDA connection from a remote system. For example, 1.) Perform this on a development system - ADDRDBDIRE RDB(production-system) RMTLOCNAME(production-system) 2.) Use an SQL connect from the development-system to the production-system 3.) Once the connection is made, prevent an SQL update or delete from an SQL session on the development-system to a file on the production-system. I would like to allow the DRDA connection and SQL selects but block any SQL updates or deletes from within the DRDA connection session.


Idea priority Urgent
  • Guest
    Reply
    |
    Nov 13, 2020

    IBM does not intend to provide a solution to this request at this time, so it is being closed. .

    IBM believes you can use the existing DDM/DRDA exit point to implement a solution for this problem.

  • Guest
    Reply
    |
    Jul 9, 2019

    The CAAC has reviewed this requirement and recommends that IBM not implement this request. We are in agreement with Scott's recommendation below -- use the exit point.

    Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key 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.

    For more information about CAAC, see www.common.org/caac

    For more details about CAAC's role with RFEs, see http://www.ibmsystemsmag.com/Blogs/i-Can/May-2017/COMMON-Americas-Advisory-Council-%28CAAC%29-and-RFEs/

    Nancy Uthke-Schmucki - CAAC Program Manager

  • Guest
    Reply
    |
    May 17, 2019

    Hi,
    Can you please elaborate as to why you cannot use the existing DDM/DRDA exit point to implement a solution for this problem?
    I would expect that you can utilize QSYS2.PARSE_STATEMENT() to recognize an in-coming UPDATE, DELETE, etc.
    Regards, Scott Forstie
    forstie@us.ibm.com

  • Guest
    Reply
    |
    May 17, 2019

    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 - None

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Security
    Operating system - IBM i
    Source - None