RE: source file download via CA/400

[BORING David <dboring@xxxxxxx>]

How about create a file that has the same field name for the source data
as the source file. Then do a CPYF to the new file, and download that
file as a text file to the PC. I believe that the file transfer will
drop the trailing spaces.

The other option would be to use FTP to download the member, but you
would still have the same problem without copying it to another file
first.

Or you could store the file in the QDLS directory (folder) and it would
stay in ASCII. Do this ONLY if it does not need to be in a source member
for some reason.

Then again, you could teach all of your web developers how to use SEU...
 ;)

David Boring
Systems Engineer
MCI Systemhouse
Direct: (562) 809-5460
E-mail: dboring@shl.com

>----------
>Date: Fri, 12 Dec 1997 10:02:39 -0500
>From: Richard Baird <rbbaird@premsys.com>
>Subject: source file download via CA/400
>
>Seasons greetings!!!
>
>I was wondering if someone could help me with a minor problem.
>
>We're doing a lot of cgi programming for web pages using rpg.  We store
>the html in source file members on the as400.
>
>Typically, our html developers design the pages on PCs, and I transfer
>them to the 400 via client access.  The problem is that, sometimes, I
>need to do the reverse - download the files to a pc, so that the web
>developers can make changes.
>
>The problem lies in the fixed record length nature of source files.  All
>the records have padded spaces at the end, making it more difficult to
>edit using pc based editors.   It's not a big deal, just an annoyance.
>
>My question is this, does anyone have a decent way of downloading fixed
>length records, but only transfering the non-blank portions of the
>records, I assume by somehow appending a carriage return to the end of
>each record?
>
>Thanks in advance,
>
>rick
>
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---