Agree -- that way you can have the same code run against different hosts, etc and be separated from the userid/pw pair to use. And updating a NETRC DATA file through automation is much easier than updating an EXEC - if you need a way to keep up with pw changes.
It's really not any more secure, though.. it's still readable text in a file. Just better separation of code from 'data'. Scott On Thu, Jan 14, 2010 at 8:57 AM, Stricklin, Raymond J < raymond.j.strick...@boeing.com> wrote: > > -----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. >
