Re: Truncating records on CPYTOPCD

Buck,

That's not such an uncommom problem.  We had sufficient 
customer requests for a solution that we included a 
"fixed-length text" format to our file trensfer 
package.

Joe Frank
Synapse Communications, Inc.



Buck Calabro wrote:
> 
> Hi, all!
> 
> 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.
> 
> Any thoughts?
> 
> Buck Calabro
> Commsoft  Albany, NY
> 
> +---
> | 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
> +---
+---
| 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
+---