Steve, I guess it would have been appropriate for me to have learned more about the pipeline ftp stages. I am still learning on a daily basis.
Thanks for your post. Best regards, ____________________ Jim Hughes Consulting Systems Programmer Mainframe Technical Support Group Department of Information Technology State of New Hampshire 27 Hazen Drive Concord, NH 03301 603-271-5586 Fax 603.271.1516 Statement of Confidentiality: The contents of this message are confidential. Any unauthorized disclosure, reproduction, use or dissemination (either whole or in part) is prohibited. If you are not the intended recipient of this message, please notify the sender immediately and delete the message from your system. -----Original Message----- From: CMSTSO Pipelines Discussion List [mailto:[email protected]] On Behalf Of Steve Hayes Sent: Wednesday, April 13, 2011 1:47 PM To: [email protected] Subject: Re: Issue with FTP REXX All, I couldn't resist the temptation to drop in and see if Bob's post sparked any interest (though I'm still officially a retired plumber). This bit of FTP REXX implements section 3.4.1 of RFC 959, specifically the second paragraph, record structured files sent using stream mode. The comment below assumes the use of file structure (which is by far the most common, of course). http://tools.ietf.org/html/rfc959 > Like I said, the RFC says text data is sent as ASCII with CR/LF at the > end of each record. > > If the data is sent as binary, then the file is sent as is. No > translation takes place and no record separators are added by the > sender. > > > ____________________ > Jim Hughes Steve Hayes Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
