Are you using comp SYNC by any chance?  If so, the UX box may be adding some
padding bytes that the MPE box isn't adding.

As I re-read this, however, I see you say, "On UX the field containing the
COMP3 formatted data has special control characters in it ( ie:  ^L ) that
appears as 2 chars but in reallity is only a single char."  How are you
viewing this file to see the "^L" in the first place?  Actually, now that I
think about it, ^L is 12 decimal, or 0x0C in hex, which is NOT a legal
"COMP3" value -- COMP3 is actually PACKED DECIMAL data, not pure binary
data, and viewing COMP3 values "in hex" displays their numerical value.
i.e., the decimal value "76" corresponds to an upper-case "L" when stored as
an ascii character (it's "pure binary value"), but as a lower-case "v" when
stored as COMP3 -- a lower-case "v" is character 118 in the ascii code --
and the hexadecimal representation of 118 is 0x76, or the original decimal
value...



> -----Original Message-----
> From: Michael Rothwell [mailto:[log in to unmask]]
> Sent: Monday, December 11, 2000 9:32 AM
> To: [log in to unmask]
> Subject: Binary file from HP UX to 3000 box.
>
>
> I searched in dejanews for this and didn't find anything, so
> I'm hoping
> that someone out there will be able to help me.
>
> I'm writing a file that contains binary data ( Cobol COMP3 format ) on
> an HP UX box.  I need to be able to transfer this file to a
> HP 3000 box,
> but when I do the data does not appear correctly on the 3000.
>  On UX the
> field containing the COMP3 formatted data has special control
> characters
> in it ( ie:  ^L ) that appears as 2 chars but in reallity is only a
> single char.  When it gets to the 3000, it actually shows up
> as 2 chars
> instead of 1 as it should.  I've tried FTPing the file in
> binary format,
> and using Batchnet to transmit the file.
>
> If anyone knows what I'm doing wrong, I'd greatly appreciate it.
>
> Michael.
>