Re: *BLANKS = spaces?

Yeah, the AS/400 does that when transfering files to a PC I've noticed, it 
dropps
the trailing blanks.

This can be a bit annoying, especially if you want to import the file 
transfered into a
data base file on the PC using fixed width format.

One possible solution for you is to just make it 802 characters and put 
something in
the 802nd byte, such as an '.' or 'x' or something.  Not elegant, I agree.  In 
my case
we were just able to modify the routines that expected the data to not expect 
each line
to be the same length.

Now, this is using an FTP transfer using ASCII mode.  I am not sure what 
happens using
other file transfers, or BINARY mode.  Although Binary mode would pretty much 
be worthless
to you, unless you knew and wanted to convert from EPSDIC (sp?) to ASCII.

Regards,

Jim Langston

Sean Porterfield wrote:

> If I MOVE *BLANKS to a field, is that the sames as *ALL ' ' or having
> spaces?  I've noticed that the AS/400 generally doesn't seem to
> distinguish between a blank and a space in most instances.
>
> This goes back to my 801 character field - when I FTP it to a PC, the
> record is only as long as the real data and does not include the
> trailing blanks.  I need the PC file to also be 801 characters.
>
> I tried sending the database file first, then converted to a PC Document
> and transferred it.  Same result both times.  This may have just gone
> off topic for this list...
>
> Thanks!

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---