On 24 October 2011 17:41, Lizette Koehler <[email protected]> wrote:
> I have tried several tests. Either I only get one record up on the mainframe > or the data is definately in bin format when it arrives. I have tried BIN > FB, BIN VB, ASCII FB and ASCII VB. So far the 44 records I have to test > with are just not behavingin. As long as your original data doesn't contain binary fields, i.e. is all text in some reasonably normal variant of ASCII, then you should do fine with character-mode transfer on both legs. Given the platforms you have, it's unlikely that using BINary on either leg will lead to anything good. As for the RECFM, if you can preallocate on z/OS, do so. Then things should Just Work (tm), and of course you will have allocated enough space. If you can't preallocate, and you are FTPing *from* Windows *to* z/OS, you'll need to specify with QUOTE SITE RECFM=FB, and QUOTE SITE LRECL=946, and if needed, a suitable BLOCKSIZE. You may also need to allocate a more appropriate amount of space than the default. > The odd thing is that NOTEPAD cannot read this file well. It wraps it (yes > tried the WRAP FORMAT in Notepad no luck). So I can see the records circle > around in the notepad window. This is classic Notepad behaviour when it sees a file that's been transferred from UNIX in BINary mode, and therefore has only LFs as line delimiters The WRAP option in Notepad doesn't do anything different about interpreting the ending sequences; it just wraps the lines so they fit on the screen. > However, Notepad++ sees it as individual records. Notepad+ and almost all editors other than Notepad are just that wee bit smarter. Tony H. ---------------------------------------------------------------------- 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
