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.

Add a new idea Subscribe
Status Not under consideration
Workspace IBM i
Categories RDi (Rational Developer for i)
Created by Guest
Created on Aug 7, 2018

RELATED IDEAS

Support UTF-8 and other non-job-CCSID character data in the RDi debugger

Character variables that do not have the job CCSID are not handled correctly in the RDi debugger. The value for the a_500 variable in the program below shows 'a|b' in the RDi debugger, and the a_utf8 variable shows '/ Â'. In the system debugger, all the variables show a value of 'a!b'.

dcl-s a_job char(3) inz('a!b');
dcl-s a_37 char(3) ccsid(37) inz('a!b');
dcl-s a_500 char(3) ccsid(500) inz('a!b');
dcl-s a_utf8 char(3) ccsid(*utf8) inz('a!b');
return;

Also, if UCS-2 and UTF-16 fields have data that cannot be converted to the job CCSID, the data is not handled correctly in the RDi debugger. For example, the utf16 variable in the program below has the characters U+2018 and U+2019. These are the "smart quotes" (Left Single Quotation Mark and Right Single Quotation Mark). The utf16 variable with the hex value x'201800612019' should display as ‘a', but RDi displays it as a.

dcl-s utf16 ucs2(3) ccsid(*utf16) inz(u'201800612019');
return;


Use Case:

The user is viewing and changing Unicode variables in a debug session on a Windows system, which should be able to display Unicode data even if it is not displayable in the EBCDIC job CCSID of the IBM i system that the program is running on.


Idea priority Medium
  • Guest
    Reply
    |     Aug 23, 2018

    This RFE is a duplicate of another RFE. See <122325> for current status.

  • Guest
    Reply
    |     Aug 14, 2018

    Hi Brian, the PTF for APAR SE68768 should fix the problem with breakpoints not being hit after a dump. http://www-01.ibm.com/support/docview.wss?uid=nas2SE68768.

    - 7.2 PTF SI66857
    - 7.3 PTF SI66858

  • Guest
    Reply
    |     Aug 13, 2018

    A follow-on from the code snippet given. I modified and tried it for myself:
    **Free
    dcl-s a_job char(3) inz('a!b');
    dcl-s a_37 char(3) ccsid(37) inz('a!b');
    dcl-s a_500 char(3) ccsid(500) inz('a!b');
    dcl-s a_utf8 char(3) ccsid(*utf8) inz('a!b');
    dump(a); // Breakpoint set here (1)
    a_job = 'ABC'; // Breakpoint set here (2)
    *InLR = *On;
    return;

    I found an odd inconsistency in RDi debug. I set two breakpoints (1) and (2) above. When the program was run under RDi debug, it halted at (1). When Resume or Step Into were invoked, the program continued to run to termination.
    The same program with the same breakpoints was run under the host debug facility, (STRDBG). Execution halted at (1), but when Resumed, the program to halted at (2) - as expected.
    It would appear that the RPG IV DUMP opcode causes the RDi debug to terminate program execution prematurely. An RFE or PMR?

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.