Re: Using SYS$INPUT for input into an FTP command.




"Stephen Hoffman" <Hoff@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:ejv7rt$31gv$1@xxxxxxxxxxxxxxxx
Ade wrote:

Using this command in a command procedure:
$FTP/INPUT=myfile.ftp

where myfile.ftp contains
connect node
username
password
ascii
put myfile.txt someotherfile.txt
quit

works fine. I would like to combine the two files and direct FTP to take
the input from the command file, ie DEFINE/USER SYS$INPUT SYS$COMMAND
before the FTP/INPUT=SYS$INPUT command and the rest of myfile.ftp to
follow in the procedure. This method however, doesn't work.

I've also tried this on an Itanium running OpenVMS 8.2, TCP/IP 5.5 and it
still doesn't work

The reason I'm asking is we have to change a LOT of procedures due to the
removal of decnet from a customers network meaning everything changes to
an IP based solution and I was hoping to minimize the number of changes
and/or extra files required for the job.

Any suggestions?

On V6.2 and later...

$ HELP COPY /FTP

As for your specific command requirements...

$ COPY/FTP/ASCII -
myfile.txt -
host.no.where"username password"::someotherfile.txt

Or install DECnet-Plus over IP, and avoid changing anything.

The networking folks that are seeking to avoid non-IP protocols will be
happy with DECnet-Plus over IP (or at least, happier with not seeing DDCMP
wandering around the networks), and the folks that are using DECnet will
be happy (having avoided changes), and there will be little or no
requirement to change existing procedures and processes that are using
DECnet. (Well, I've met some networking folks over the years that would
be more happy if the OpenVMS hosts were off their network -- but I think
these same folks might be really happy if all the pesky hosts were off
their IP network. :-) )

And as I've mentioned else-posting, Cisco and other modern gear can
continue to operate non-IP networks. Cisco can set up a private LAN, and
can bridge the SCS, MOP and DECnet protocols among multiple sites, for
instance. And can continue to route IP. According to the roadmap,
clustering is moving onto IP, and DECnet is already there with DECnet-Plus
and its IP transport support. MOP service requests, however, are somewhat
more of a problem as that's built into the system consoles and the
existing bootstrap pieces -- the project adding SCS over IP might or might
not deal with this MOP stuff, I don't know.






Hoff,

Thanks for the reply. I did actually try the copy/ftp method but found that
the file on the target end (an IBM MVS system) retained the original
filename in the dataset rather than the one I specified in the command. This
led me to look elsewhere.

As far as the networking side of things go, we have absolutely no control
over it, hence the scramble to find a working solution.

Many thanks,

Ade


.



Relevant Pages

  • Re: Using SYS$INPUT for input into an FTP command.
    ... The reason I'm asking is we have to change a LOT of procedures due to the removal of decnet from a customers network meaning everything changes to an IP based solution and I was hoping to minimize the number of changes and/or extra files required for the job. ... The networking folks that are seeking to avoid non-IP protocols will be happy with DECnet-Plus over IP, and the folks that are using DECnet will be happy, and there will be little or no requirement to change existing procedures and processes that are using DECnet. ... MOP service requests, however, are somewhat more of a problem as that's built into the system consoles and the existing bootstrap pieces -- the project adding SCS over IP might or might not deal with this MOP stuff, I don't know. ...
    (comp.os.vms)
  • Re: OpenVMS Security
    ... >> You are absolutely right Andrew, however it seems you define 'network' ... > DECnet would at this point be a better option is laughable. ... Within a pure VMS ... or I use the IP stack for DECnet over IP to copy sofware over the ...
    (comp.os.vms)
  • Re: General question about Digital history
    ... biggest factor giving IP its win over DECnet. ... nice network architecture people inside DEC decided that the OSI ... and Windows never did OSI properly, so OSI never really caught on. ...
    (comp.os.vms)
  • Re: General question about Digital history
    ... I was under the impression that DECnet specs were freely available, ... nice network architecture people inside DEC decided that the OSI ... and Windows never did OSI properly, so OSI never really caught on. ... Unix vendors weren't about to start using a parallel competing network ...
    (comp.os.vms)
  • Re: Routable Protocol for Clustering
    ... I added tcp/ip support for connections to the ... communication is always vms to vms, and decnet is always available, right? ... Some sites have network dickweeds who ban the decnet protocol. ...
    (comp.os.vms)