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 Languages - RPG
Created by Guest
Created on Apr 23, 2017

Alias name for Indicators KA-KY

Provide an alias RPG RESERVED NAME for Indicators KA-KY.

Suggested alias names:

*INFK01-*INFK24
*F01-*F24


Use Case:

Indicators KA-KY are more simple to communicate with the DDS Dispaly,
since it does not use up indicatore 01-99.

But the problem with it that it is not user friendly.

Programmers came up with at least a dosen ways how to make them user friendly. The problem is extra code and lack of standard.

A simple Alias *INFK01-*INFK24 would simplify and standarize the coding.

For IBM part, it is almost no ivestment.


Idea priority Low
  • Guest
    Reply
    |
    May 5, 2017

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

  • Guest
    Reply
    |
    Apr 25, 2017

    to JonParis:

    You see, You gave name F17 through the data structure position369,

    Another great programmer does it in diferent way, by a pointer:
    https://archive.midrange.com/rpg400-l/199908/msg00555.html

    Another great programmer is doing it throguh INDDS.
    http://search400.techtarget.com/tip/Indicators-Two-ways-to-name-them

    Everything is great, but it is not STANDARD.

    Rememebr the old RPGIII days when every programmer had his own date routines, some of them were very easy to understand with an externa call etc, but it was not STANDARD! With the introduction of Date Operations in RPG4, things became standartd, and all private date routines from all great programmers became obsolete. So the programmers had more time to concentrate on real work instead of doing the jobs that the operating system should have done.

  • Guest
    Reply
    |
    Apr 24, 2017

    No - please do not implement this. This last thing RPG needs is yet another set of meaningless names!

    *INFK17 is every bit as meaningless as *IN17.

    If you have "run out" of indicator numbers and therefore cannot use the INDDS to give sensible meaningful names to the indicators, then use named constants for the values and give those constants meaningful names. Don't just continue the bad old ways of doing things.

  • Guest
    Reply
    |
    Apr 24, 2017

    You could also map the DSPF INF DS for the f key position 369. Then build constants that map the hex value returned.

    Now you don't have to wait to have a meaningful name to a function key pressed.

    DCL-F STD80LFM WORKSTN(*EXT) USAGE(*INPUT:*OUTPUT) INFDS(DSPFINFDS)

    D DSPFINFDS DS QUALIFIED
    D** Function Key pressed
    D FKey 369 369A

    D* HEX CONSTANTS FOR FUNCTION KEYS RETURNED IN 'FKEY'
    D F01 C X'31'
    D F02 C X'32'
    D F03 C X'33'
    D F04 C X'34'
    D F05 C X'35'
    D F06 C X'36'
    D F07 C X'37'
    D F08 C X'38'
    D F09 C X'39'
    D F10 C X'3A'
    D F11 C X'3B'
    D F12 C X'3C'
    D F13 C X'B1'
    D F14 C X'B2'
    D F15 C X'B3'
    D F16 C X'B4'
    D F17 C X'B5'
    D F18 C X'B6'
    D F19 C X'B7'
    D F20 C X'B8'
    D F21 C X'B9'
    D F22 C X'BA'
    D F23 C X'BB'
    D F24 C X'BC'
    D CLEAR C X'BD'
    D ENTER C X'F1'
    D HELP C X'F3'
    D PAGEUP C X'F4'
    D PAGEDN C X'F5'
    D PRINTKEY C X'F6'
    D HOME C X'F8'


    Select;
    // Home
    WHEN DSPFINFDS.FKEY = HOME;

    // Enter
    WHEN DSPFINFDS.FKEY = ENTER;

    OTHER;
    MSGSEND('ERR0183':*BLANKS);
    ITER;
    ENDSL;