Interesting information. Thanks. Didn't realize that LRECL > 80 was supported. (Everything I am about to say about the FTP doc is based on the 2.10 doc which is what I have most readily at hand. It may be obsolete.)
The doc in one spot specifically says LRECL must be 80, and in another spot says LRECL can range up to 2080 (where do they get these numbers?). Interestingly, it also says that RECFM must be FB, but I figured FTP must be using LE which should not care, and sure enough, I tested RECFM=VB,LRECL=104 and it worked just fine. Seeing as there is almost no "cost" for large LRECLs if RECFM=VB, you might just as well make any FTP command file dataset LRECL=2080,RECFM=VB and avoid continuation problems altogether (unless you are a real HFS, UNIX, or Windows pathname masochist). Annoying FTP quirk: comments, whether at the end of a command or on their own line, don't print in the OUTPUT dataset. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Jim Keohane (MPI) Sent: Wednesday, October 12, 2005 4:10 PM To: [email protected] Subject: Re: FTP continuation character Two possible solutions that worked with earlier versions of IBM FTP: 1: Instead of instream //INPUT DD * or //SYSIN DD * (or whatever) just point DD to a sequential file/dataset with line length or record length greater than 72. Say 200. That will be your command file. ---------------------------------------------------------------------- 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
