Re: *BLANKS = spaces?

Sean,

>If I MOVE *BLANKS to a field, is that the sames as *ALL ' ' or having
>spaces?  

It is the same.  There is no difference between a "blank" and a
"space" -- they are synonyms for x'40' in EBCDIC.

>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.

IBM added some commands to their FTP server and client programs to let
you specify how to handle trailing blanks (or spaces :).  You need to
set the desired state prior to issuing a GET or PUT operation.

If using the AS/400 FTP server, use SITE TRIM n, where n is described
below.  If using the AS/400 FTP client, use LOCSITE TRIM n instead.

Values for n can be:

0 - Do NOT trim blanks when sending files from the database
   (QSYS.LIB) file system.
1 - Only trim blanks when sending files from the database file
   system when the transfer structure is set to File and the
   transfer mode is set to Stream.  This is the default
   setting, and provides the trim behavior introduced in
   V3R1M0.

2 - Always trim trailing blanks when sending files from the
   database file system.  This setting provides the trim
   behavior from V3R0M5 and previous releases.

Note:  TRIM settings do not apply to TYPE I (binary) file
transfers.  Blanks are never trimmed for TYPE I file transfers,
regardless of the TRIM setting.

You may need a PTF to get this to work prior to V4R4:

 V4R1 - SF49576
 V4R2 - SF51972
 V4R3 - SF52486
+---
| 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
+---