Hi John, I wrote an "FTPGET" rexx stage using RxSocket years ago. FTP is quite a simple protocol, and you only need to implement a small subset of it if you only want to do GETs in a controlled environment. So I'm sure you could roll your own if you wanted to. I'd use TCPCLIENT etc if I wanted to attempt it these days.
-Matt -----Original Message----- From: CMSTSO Pipelines Discussion List [mailto:[email protected]] On Behalf Of Larson, John E. Sent: 25 August 2011 18:11 To: [email protected] Subject: Re: FTP user exit, ultimately a PIPE stage? I am getting lost in Google-land, and seem to keep hitting dead ends. Something that I've wanted to do for a really long time but just assumed wasn't possible. Is it even possible...to write an FTP user exit that interfaces with the entire retrieval mechanism? Ultimately, I'd wish to have a PIPE stage that can filter my FTP GET of a 3000+ cylinder MVS dataset to a VM disk. I've always wondered why I have to find a VM disk large enough to complete the FTP GET, so that I can then turn around and "PIPE < FTP FILE | many filters | > much less data..." What would be the first step in even trying to attempt this? An FTP user exit? A socket program that does the LOGIN and entire FTP itself (rewriting FTP)?? Or is this just too complex to consider? The larger the MVS dataset (multi-volume), the more awkward current methods are, i.e., I use FILEAID to chop the MVS dataset into 5-10 more manageable datasets (each less than 3000 cylinders). Then I can FTP GET each one, do my PIPE processing, and when all done write a final PIPE to merge all of the individual files and combine into one final output file. I suppose that preprocessing on MVS is an obvious alternative, but I wish that I could figure out how to do this while staying at home (on VM:-) John
