On Tue, 24 Apr 2012 19:46:54 -0500, Karl Severson wrote:
>We've always had a problem with FTP and non-text files (object files, binary,)
>that are variable length on our VM/ESA systems. When they get to where they
>are going they aren't the same as when they left the source system. This can
>be between two IBM's or between an IBM and any non-IBM system. Now that we are
>on a new z10 with zVM6.1 I thought that maybe this problem would have been
>fixed but nothing seems to have changed. Is this a problem or a feature? Using
>the BINARY "switch" doesn't help.
>
Within the next few hours here, you will get numerous, often
conflicting suggestions about how to employ variously:
TYPE EBCDIC
MODE BLOCK
STRU RECORD
My favorite, with a non-IBM client and an IBM server is:
BINARY
QUOTE TYPE EBCDIC
QUOTE MODE BLOCK
GET whatever
IBM thinks it's talking to another IBM; the non-IBM client just sees a stream
of bytes and saves them with loss of information. Then transfer _to_
another IBM server by reversing the process:
BINARY
QUOTE TYPE EBCDIC
QUOTE MODE BLOCK
PUT whatever
Most of this doesn't work for load modules for which z/OS FTP
contains specialized support. You can't fool it into thinking
it's talking to another z/OS.
What's a variable length object file? I thought they were always
F 80 (filetype TEXT?).
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
