On Thu, 18 Sep 2008 20:19:51 -0500, Bass, Walter W wrote: > >I thought about that briefly but my file was too large for >ISPF edit and I also had the apparently mistaken impression >that it would only remove the trailing spaces from the >particular records that got otherwise changed. Kind of the >way it changes case when you have CAPS ON and edit a file >containing lower case data. It would not have expected edit >to alter records that you did not specifically touch. > Actually, no. Historically, it seemed that it discarded the RDWs on input, and regenerated them on output to be the position of the last nonblank character (plus 4 for the RDW itself).
Except that if there were no nonblank characters, or the last nonblank character was in position 8, it left one trailing blank. Who invented this silly thing, anyway? And the REGION requirement depended on the number of records times the LRECL in the label, even though no actual record exceeded even a small fraction of LRECL. And ISPF copy (3.3) had a similar behavior of trimming trailing trailing x'40'; very annoying when it shortened records containing binary data. >> -----Original Message----- >> [mailto:[EMAIL PROTECTED] On Behalf Of Roger Bolan >> Sent: Thursday, September 18, 2008 8:01 PM >> >> / Preserve VB record length >> Often not what I want, rather "Preserve actual trailing blanks", so if I turn HEX ON and type a trailing x'40', that gets preserved in the file rather than stripped. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
