× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Dawn, could you please try updating to RDP 8.0.3.1, if you haven't already
done so? We addressed the issue with the member name showing escape
sequences as part of the fix for APAR SE49966, but I don't know if that
fixes this additional issue in debug.

Eric Chan
Rational Developer for Power
IBM Toronto Software Lab




From:
"Siegrist, Dawn (Penske)" <dawn.siegrist@xxxxxxxxxx>
To:
<wdsci-l@xxxxxxxxxxxx>
Date:
02/14/2012 12:58 PM
Subject:
[WDSCI-L] Member Name Issue with Underscores
Sent by:
wdsci-l-bounces@xxxxxxxxxxxx



In looking at the archives, I noticed that someone did mention the issue
with members that have underscores are loaded to the editor with a "5F"
after the underscore. I am having this issue as well. It doesn't cause
a problem with making changes to the source member and saving it.
However, it is causing a problem with debug.



I am trying to debug a program that is named P_SUPSRCH. However, the
source comes up in the editor as P_5FSUPSRCH. I put in my breakpoints,
but when I debug the program, it never stops at the breakpoints.



Is this issue being fixed?



Dawn Siegrist

Penske

Systems Analyst



T 610-775-6243

F 610-603-8402

E Dawn.Siegrist@xxxxxxxxxx <mailto:Dawn.Siegrist@xxxxxxxxxx>

GoPenske.com



PO Box 563

Reading PA 19603-0563 USA



Check out our blog for news and event info:

Blog.GoPenske.com




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.