On Fri, 15 Aug 2008 11:24:14 -0500, Paul Peplinski
<[EMAIL PROTECTED]> wrote:
>...
>ascii option did the trick and the data in question was periods, not
>non-displayable data, as in the following. Hard to see with this
formatting
>but the periods right before REILY are stripped out and REILLY goes
to the
>beginning of a new line.
>
>Source data (on mainframe)
>
>0 ! Then this morning, Coop
>said, 'BOB's not from around here.'..REILY: That's fun
>
>
>Target data (after FTP to server)
>
>0 ! Then this morning, Coop
>said, 'BOB's not from around here.'
>REILY: That's fun
>...
Boy, that's really strange! I'm glad you got it working so this is
now just idle curiosity on my part, but I'd really like to understand
this better.
This was data in an MVS dataset being FTPed to a remote non-MVS
server? And the original dataset was all printable data? (That is
sort of a meaningless question if I don't also ask what code page,
but I'm going to pretend I don't need to.) This was a single-
byte character stream transfer, wasn't it?
If you bring up the local FTP client and issue a "status" command
you will get many lines of config information (at least from the MVS
client). One of the lines mentions "Mode", "Structure", "type"
and "byte-size". What do you have for type? If it says "ASCII"
then your specifying it again should not have had any effect.
("ASCII" means it is going to assume a character transmission,
and is going to translate from EBCDIC into ASCII. It doesn't
mean the data is in ASCII on MVS.
Pat O'Keefe
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
