For in house we have no problem with REXX exec's from VM to LINUX, UNIX, 
or windows 

For outside FTP,s we have to use a FTP proxy server and that can not be 
put into EXEC's or SCRIPT's

Bill Munson 
Sr. z/VM Systems Programmer 
Brown Brothers Harriman & CO.
525 Washington Blvd. 
Jersey City, NJ 07310 
201-418-7588

President MVMUA
http://www2.marist.edu/~mvmua/
http://www.linkedin.com/in/BillMunson




"Stricklin, Raymond J" <raymond.j.strick...@boeing.com> 
Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>
01/14/2010 10:57 AM
Please respond to
The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>


To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
Re: advise on a simple REXX script to automate FTP from zVM to Linux 
server






> -----Original Message-----
> From: The IBM z/VM Operating System 
> [mailto:ib...@listserv.uark.edu] On Behalf Of Hughes, Jim
> Subject: Re: advise on a simple REXX script to automate FTP 
> from zVM to Linux server
> 
> This is a sample rexx procedure and runs as a VMFTP macro.
> 
> ++++++++++++++++++++++++++++++++++++++++++++++++++++
> /*  */
> Parse arg $cd "," $in "," $out
> 
> "open ftp.server.com"
> "myuseridgoesjhere"
> "myPassWordGoesHere"

Not to pick on Jim, since everybody's given the same advice so far, but...

Just as a matter of clarification, can I ask why someone would put login 
credentials inside of an EXEC that calls FTP, in preference to making use 
of NETRC DATA ?

ok
r.


*************************** IMPORTANT
NOTE*****************************-- The opinions expressed in this
message and/or any attachments are those of the author and not
necessarily those of Brown Brothers Harriman & Co., its
subsidiaries and affiliates ("BBH"). There is no guarantee that
this message is either private or confidential, and it may have
been altered by unauthorized sources without your or our knowledge.
Nothing in the message is capable or intended to create any legally
binding obligations on either party and it is not intended to
provide legal advice. BBH accepts no responsibility for loss or
damage from its use, including damage from virus.
********************************************************************************

Reply via email to