×
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.
1) In RDP 9 in 2013, when I opened a member for *browse* it did not trim
trailing spaces. (Thread here:
http://archive.midrange.com/wdsci-l/201311/msg00064.html )
My post:
"In RDP 9 I opened up a colleague's source for Browse with Ctrl-Shift_A.
Then I printed it. The lines came out double spaced.
I copied his source member to my library (using PDM, horrors!), opened
it for edit, and immediately printed it. It was single spaced as expected.
I had this problem in RDP 8.5 and probably RDP 8 as well. Seems like it
only occurs when browsing."
Reply from Mike Hockings of IBM"
"Let me first say that I have not investigated but my *guess* is that
when you open for edit the process strips trailing blanks to make it
more natural to edit but if you open for browse there is no reason to do
this so each line is padded with blanks to it's max.. When you are
printing isthe page wide enough accept the full line without wrapping?"
2) Thinking about it, what good does trimming trailing spaces do on a
save to a source physical file? It couldn't save any disk space could
it, since the fields in a source PF are fixed length? But it presumably
would save space when saving to the IFS.
Sam
On 2/17/2015 12:40 PM, Buck Calabro wrote:
On 2/17/2015 12:40 PM, Vernon Hamberg wrote:
Buck just posted that the editor has never trimmed the trailing spaces.
Michael, you say the exact opposite. I'm inclined to go with your view,
but see my thoughts here.
I was so certain, but now...
Time to test. I had a self-induced immolation that ended up with me
deleting every version of WDSC / RDi and re-installing 9.1.1 so I can't
test with WDSC. But I can test it with the Code/400 editor that came
with WDSC v7 (Code/400 v6).
Test conditions:
1) STRSEU, update a line in a source member, save. The member now has
trailing blanks.
2) Open for edit with RDi 9.1.1, press End - cursor goes all the way to
column 101 on my H-specification, which ends at column 41. Close member.
3) Open member for edit in Code/400, press End - cursor goes to column
42. Close member.
4) Open member for edit in SEU, press End - cursor goes to column 42.
Conclusion:
SEU trims trailing blanks on open.
Code/400 did in fact trim trailing blanks on open.
RDi 9.1.1 does not trim trailing blanks on open.
Michael is correct. I am wrong.
---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com
As an Amazon Associate we earn from qualifying purchases.
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.