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 Future consideration
Workspace IBM i
Categories Db2 for i
Created by Guest
Created on Nov 18, 2025

Extend the QCMDEXC SQL procedure and function to log the CL command run

Many SQL programmers using the QSYS2.QCMDEXC procedure and function are logging the CL command specified as parameter to the procedure / function, often to the joblog by calling SYSTOOLS.LPRINTF, just before calling QCMDEXC.

The idea is to have QCMDEXC procedure and function write the command string to the joblog with an optional parameter, e.g. "LOG => 'VERBOSE'" or "LOG => 'ERROR'", to have the command in the joblog every time or in case of an error. Currently no log is written at all, not even in case of failure, and you have no clue as to what CL command was executed or failed.

Having QCMDEXC writing the CL command to the joblog would reduce the coding effort required by any SQL programmer using the QCMDEXC procedure/function.

Idea priority Medium
  • Guest
    Nov 18, 2025
    IBM will use this Idea as input to planning, but no commitment is made or implied. This Idea will be updated in the future if IBM implements it.

    Db2 for i development team
    IBM Power Systems Development
5 MERGED

Add logging option to QSYS2.QCMDEXC procedure and scalar function

Merged
With the introduction of SQL services the work of an IBM i system admin has changed. Especially the introduction of the QSYS2.QCMDEXC scalar function allows you to execute CL commands based on your SQL selection. When doing this once in a while an...
2 months ago in IBM i / Db2 for i 1 Future consideration