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 Feb 21, 2020

have STRSQL inform user about *POINTER output in table functions

playing around with new functions like qsys2.ifs_object_statistics.
First was confused when using STRSQL that PATH_NAME is reported as *POINTER; using the iACS GUI execute SQL function the result was ok.
Have STRSQL either display correct values (even for long CLOB fields) or give informational message that cast() of value is needed.

example (thanks, Simon):
***SNIP***
select path_name,object_type,create_timestamp,last_used_timestamp,
data_size from table(qsys2.ifs_object_statistics('/home','NO'))
where path_name like '/home/s%'
***SNAP***
STRSQL on Green Screen cannot display PATH_NAME as it is a big CLOB 16M,
Execute SQL scripts in iACS can do.


Use Case:

same SQL statement delivers different output on screen which can confuse programmer whilst testing some SQL.
for green screen STRSQL, the following is needed:
SELECT cast(path_name as char(100))
,object_type,create_timestamp,last_used_timestamp,
data_size FROM table(qsys2.ifs_object_statistics('/home', 'NO'))

where path_name like '/home/s%'


Idea priority Medium
  • Guest
    Reply
    |
    Apr 23, 2020

    The IBM i database team does not intend to change STRSQL to provide additional information when returning CLOB data. While this interface is still supported, it is no longer being enhanced.

    IBM i Access Client Solutions (ACS) Run SQL Scripts is the recommended interface for running SQL statements, especially for data types such as CLOBs and DBCLOBs.

  • Guest
    Reply
    |
    Mar 17, 2020

    The CEAC has reviewed this requirement and recommends that IBM view this as a MEDIUM priority requirement that should be addressed.

    Background: The COMMON Europe Advisory Council (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