RE: trimming trailing blanks in spooled output...

["GDS" <ggarner_gds@xxxxxxxxxxxxxx>]

In my experience this has not been a concern in the midrange world.  The
blanks are there when you display the spool file or when you copy the spool
file to a database file. 

Is this a concern about the storage size of the spool file on the disk?

Gregory A. Garner
Garner Data Systems, Inc.
4270 Grand Teton Parkway
Suwanee, GA 30024
Phone: 770 845 9636  Fax:770 614 3496
 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Rosinger
Sent: Monday, December 04, 2006 12:12 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: trimming trailing blanks in spooled output...

"GDS" <ggarner_gds@xxxxxxxxxxxxxx> wrote in message 
news:mailman.44.1165250748.1743.midrange-l@xxxxxxxxxxxxxxx
> Is this a situation where you are writing a paragraph and want to
> concatenate sentence fragments or insert variable names into the wording?

Gregory,

No. Perhaps I should have been more clear.

For standard 132-character wide reports, I am concerned about cases where a 
programmer has done something like this:

1) writes print line that is 132 bytes of spaces in order to skip a line
2) writes a line of 132 characters where the first 5 (for example) are 
significant followed by 127 spaces

Will the spooler on the iSeries truncate these trailing extraneous spaces?