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.
I've added the view named FUNCTION_INFO (or FUNC_INFO) to #SQLTools.
It contains the SQL Function or Procedure Name along with the Specific Name/Schema and includes the name of the program or service program that is actually run, and if it is an *SRVPGM then the procedure name is also included.
I see your point with this. You're asking that the actual program/srvpgm behind the UDF/UDTF be revealed in the resultSet. The use of the identified SQL Functions (in IBM's response) simply return the UDF or Proc name. But you want the program name behind it. I think I can do that with an existing (or possibly new) SQL Tools function. I'll post again if I get it completed.
Unfortunately, this solution failed to solve the problem of the ask.
IBM Please review this RFE again.
A solution to this request has been delivered with IBM i 7.4 SF99704 Level 15 and IBM i 7.3 SF99703 Level 26.
With this enhancement, the PARSE_STATEMENT table function returns information about calls to procedures. https://www.ibm.com/support/pages/node/1116561
To identify object references in embedded SQL statements, we recommend writing a query to use the QSYS2.PARSE_STATEMENT table function to examine the QSYS2.SYSPROGRAMSTAT and QSYS2.SYSPROGRAMSTMTSTAT views.
For example, to find all procedure and function references in SQL statements in library MYLIB, use the following query:
WITH program_statements(naming_mode, dec_point, string_delim, stmt_text,
system_program_name, program_type)
AS (SELECT a.naming, a.decimal_point, a.sql_string_delimiter, b.statement_text,
a.system_program_name, a.program_type
FROM qsys2.sysprogramstat a INNER JOIN
qsys2.sysprogramstmtstat b ON a.program_schema = b.program_schema AND
a.program_name = b.program_name AND
a.module_name = b.module_name
WHERE a.number_statements > 0 AND
a.program_schema = 'MYLIB' AND b.program_schema = 'MYLIB')
SELECT system_program_name, program_type,
c.name_type as object_type, c.schema as object_schema, c.name as object_name, stmt_text
FROM program_statements,
TABLE(qsys2.parse_statement(stmt_text, naming_mode, dec_point, string_delim)) c
WHERE c.name_type = 'FUNCTION' OR
c.name_type = 'PROC'
ORDER BY c.schema, c.name;
The CAAC has reviewed this requirement and recommends that IBM view this as a high priority requirement that is important to be addressed. Especially when modernizing, which is a key goal for many customers, it is important to understand the existing code base.
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
Nancy Uthke-Schmucki - CAAC Program Manager
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
The CEAC has reviewed this requirement and recommends that IBM view this as a HIGH priority requirement that is important to address.
We see this as a very important enhancement for tracing cross referencing, as the command DSPPGMREF offers the option to bring this information to a file, it might be a better idea to create an SQL service to make the requested information available.
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
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 - Core OS
Operating system - IBM i
Source - None