Re: Truncating records on CPYTOPCD

[Pete Hall <peteh@xxxxxxxxxx>]

At 03:10 PM 3/20/98 -0500, Buck Calabro wrote:
>We have a scenario where we're sending records to a bank 
>via a PC file.  We format the file on the 400, then CPYTOPCD
>to the PC and use a PC comm pkg to send it to the bank.  The
>problem is that the bank demands "fixed" (94 byte) records
>with CR/LF appended.  Some of the records have data that takes
>up only 30 columns.  These records get "truncated"; on the PC
>we see 30 columns of data, then a CR/LF.  The bank insists that
>their application requires the record be padded with blanks:
>no other pad characters are acceptable to them.
>
>As a workaround, we put a "~" in the last column and created
>a translate table that translates the "~" (x'A1') to an ASCII
>blank (x'20')  This works fine, but I can't help but think 
>there's a simpler solution.  I recall a thread about FTP and
>Win95 reacting this way, but I don't recall the details.

Buck,

That's the normal behavior for FTP, and I think I just recently read an apar 
that said that the same thing has been PTFd into CA. I think you're limited to 
3 possible solutions:
1. Do what you're doing now (my preference)
2. Reprocess the file on the PC and pad it.
3. Use ODBC (or I suppose APPC, CPIC or DDM)

Pete

Pete Hall
peteh@inwave.com 
http://www.inwave.com/~peteh/

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