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
Created by Guest
Created on Dec 29, 2020

Allow CL to Pass Strings to RPG OPTIONS(*STRING) Parameters

Please allow the CALLPRC command to pass a string to an RPG procedure parameter that is defined as POINTER OPTIONS(*STRING).


Use Case:

Currently, I still have to pass a pointer to such a parameter:

dcl &p_code *ptr
|
chgvar &code 'AAT990'
chgvar &p_code %addr(&code)
callprc ENTI01 ((&p_code)) &sequence

Since OPTIONS(*STRING) is designed to have a string passed to it, it would be good if CL could do that. Also, the string would be correctly delimited with x'00'.

chgvar &code 'AAT990'
callprc ENTI01 ((&code)) &sequence

or

callprc ENTI01 (('AAT990')) &sequence


Idea priority Low
  • Guest
    Jan 4, 2021

    When calling from CLLE, for an RPG parameter that is defined as POINTER VALUE OPTIONS(*STRING), you can either pass a pointer by value or a character variable by reference. Either way, you need to ensure that the value ends with x'00'.

    Assuming the RPG parameter is defined with the VALUE keyword, your call could be like this.

    chgvar (&code 'AAT990' *tcat x'00') /* append the x'00' */
    callprc ENTI01 ((&code)) &sequence /* pass &code *byref */

    Again, assuming the RPG procedure has the VALUE keyword, when you pass the pointer, you should add *BYVAL:
    chgvar (&code 'AAT990' *tcat x'00') /* append the x'00' */
    chgvar &p_code %addr(&code)
    callprc ENTI01 ((&p_code *byval)) &sequence /* add *BYVAL for the pointer */