Re: Truncating records on CPYTOPCD

>Well, if you know it's gonna be 400 bytes long on the 400, why not move it
>to a structure that's subdiv'd at 94 bytes and write (400/94)+1 records to
>the workfile to get the banks needed 400 bytes of info...?  Would that
>work?

Well, the file's actually 94 bytes long on the /400, but the problem is 
that by definition, CPYTOPCD truncates blanks from the end of the
record for *TEXT transfers.  If we go *NOTEXT, then we get fixed
length records, but no CR/LF.  This behaviour is what IBM intended,
and is supported by the documentation.  Our problem is that the
bank getting this data doesn't want it that way...

Because blanks get truncated first, then the record is translated into
ASCII, we stumbled on the idea of putting a "place holder" character
in column 94 (which eliminates the blank truncation) and then using
a custom translate table to translate the place holder into a blank.

Thanks for the ideas!

Buck Calabro
Commsoft

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