UNIX for Advanced & Expert Users

You could try using "newform" to restore trailing spaces.

Kahuna,

What this 'newform' stands for?

Is it an option with form?

man newform

NAME
newform - change the format of a text file

SYNOPSIS
newform [-s] [-itabspec] [-otabspec] [-bn] [-en] [-pn] [-an] [-f] [-cchar] [-ln] [filename...]


Thinking about it, this will only work if you have fixed length records. But your posting indicated that VB records were being sent.

Kahuna

This command is applicable to make file in say fixed width upon its arrival. For this I have solution using 'awk'.

awk ' { printf("%-100s\n",$0) } ' fname1 > fname2

I need to know, during transmission from mainframes to Unix, is there anyway we can stop chopping off of trailing spaces.

Is the requirement that the transmission not truncate spaces or that you end up with a file with the right length records? Or are you saying that you have variable length records and so you can't restore the right number of trailing spaces?

If the requirement is for the transmission to not truncate spaces, Porter has already suggested transmitting in Binary and then translating to ascii using dd.

Hemangjani also suggested about FB vs VB. (I'm unfamiliar with this but assume it is a viable appoach)

I was simply suggesting an alternative way to approach the problem. If that failed to meet your requirments, I'm sorry I wasted your time and mine.

See if this helps.
MAINFRAME FORUM: FTP question from Mainframe to PC

We have found solution for this.

If we use 'record' keyword before 'put' in FTP transmission, then record truncation problem is not observed.