Quote:
Originally Posted by sharifhere
FTP doesn't work since they treat display and comp-3 fields same.
I don't see why that would be. A "ascii" transfer from unix to a non-unix box means that a newline character will be replaced with whatever the destination box deems appropriate. With a mainframe, (like dos) it will be replaced with a newline/carriage return combination. Since one byte is replaced with 2 bytes the file will grow in size should this happen. Did it? A unix newline character is hex 0A which is not legal in a comp-3 field. Still since you are not moving text, you should use a binary transfer. And comp-3, aka packed decimal, should bypass endian issues as easily as text does.
Don't be too quick to blame this on the transfer. I would suspect that the unix program which created the data and the mainframe program that is reading the data are not singing from the same songsheet.