> -----Original Message-----
> From: IBM Mainframe Discussion List 
> [mailto:[EMAIL PROTECTED] On Behalf Of Shmuel Metz (Seymour J.)
> Sent: Sunday, October 22, 2006 7:11 PM
> To: [email protected]
> Subject: Re: Multiple FTP Problems
> 
> 
> In <[EMAIL PROTECTED]>, on 10/20/2006
>    at 07:04 AM, Edward Jaffe <[EMAIL PROTECTED]> said:
> 
> >It seems like there are a couple of options here. The first is to
> >split  all transfers up into individual ftp sessions, invoke each ftp
> >session  from REXX, interrogate the output, and make conditional
> >decisions based  on the results of each invocation. The other option,
> >extremely powerful  but not so easy, is to roll your own client code
> >using the REXX Sockets API:
> 
> Isn't RXFTP available in z/OS? If not, use NET::FTP in Perl.
>  
> -- 

I do hope you're kidding. Try to get a legacy z/OS COBOL programmer to
learn Perl and NET::FTP?!? I haven't tried, can z/OS Perl read/write
z/OS legacy datasets as well as UNIX files? If it can, then I guess that
I could write a user-runable Perl script. But it would still be "weird"
to them due to the unavoidable UNIX stuff if anything "goes wrong". It
would also violate our current policy of "no custom code" for things
like this.

--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
Information Technology

This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and its
content is protected by law.  If you are not the intended recipient, you
should delete this message and are hereby notified that any disclosure,
copying, or distribution of this transmission, or taking any action
based on it, is strictly prohibited. 
 

----------------------------------------------------------------------
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

Reply via email to