- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: DCL script to FTP files
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2010 10:51 AM
тАО07-30-2010 10:51 AM
Re: DCL script to FTP files
Personally, I have used bare FTP and COPY/FTP. As Hoff has noted, whether COPY/FTP exists depends on the version of OpenVMS with which one is dealing.
That said, if one is dealing with different versions of invoking FTP, in many cases one can deal with this by defining a DCL symbol for FTP (e.g., FTPUTILITY to avoid confusion) whose value is either "FTP" or "MULTINET FTP" (or others) depending on what is available on that node. That way, the dependency is limited to a a highly localized point in the script (you may guess why I make this recommendation).
I do not disagree with Hoff's comments, however, FTP is often used as a lingua franca between a variety of systems, and thus may be unavoidable, despite its age and admitted security-related drawbacks.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2010 11:27 AM
тАО07-30-2010 11:27 AM
Re: DCL script to FTP files
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2010 09:22 PM
тАО07-30-2010 09:22 PM
Re: DCL script to FTP files
FTPCMD.COM
$ wo="WRITE SYS$OUTPUT"
$ wo "cd /VAX/OUT/SHARE/"
$ wo "put ''source_file' ''target_file'"
$ wo "bye"
You can execute the procedure and PIPE it into an FTP command to be executed:
$ PIPE @FTPCMD | -
FTP/INPUT=SYS$PIPE 10.37.2.23 /username=ftp_to_share/password="1password23"
The PIPE can, of course be inside a procedure. Saves all the hassle of dealing with temporary files.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-31-2010 03:10 AM
тАО07-31-2010 03:10 AM
Re: DCL script to FTP files
$1$dga418:[ftp.temp]*.*;* -
192.168.249.12"UserName PassWord"::"ftp-temp/"
You may use logicals and/or symbols instead
og the specifics
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-02-2010 06:00 AM
тАО08-02-2010 06:00 AM
Re: DCL script to FTP files
Dave.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-02-2010 07:52 AM
тАО08-02-2010 07:52 AM
Re: DCL script to FTP files
How do you ensure that files are not left "hanging"?
Cheers
Craig
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-02-2010 08:33 AM
тАО08-02-2010 08:33 AM
Re: DCL script to FTP files
> "hanging"?
What's a "hanging" file?
If the command hangs, then you can pretty
safely conclude that the transfer was not
complete. If the command completes, then its
status value should tell you whether the
command succeeded or failed. Right?
If you want a serious test, then suck the
file back in, and compare it with what you
sent. Or start using fancy checksums or
other data integrity tests. (A truncated
Zip archive, for example, will be identified
as corrupt by any reasonable UnZip program.)
Many things are possible. What's your goal?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-02-2010 08:41 AM
тАО08-02-2010 08:41 AM
Re: DCL script to FTP files
I take the view that that the network link will always fail at the most inopportune time.
Therefore, I wish to mitigate the effect of a transfer failing and, thus, potentially causing a remote trigger job from picking up a file fragment.
On that basis, I can think of no useful reason to use COPY/FTP rather than a script that has a degree of intelligence in it.
Craig
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-02-2010 09:18 AM
тАО08-02-2010 09:18 AM
Re: DCL script to FTP files
> a transfer failing and, thus, potentially
> causing a remote trigger job from picking
> up a file fragment.
I always wonder how a "remote trigger job"
can distinguish between a partial transfer
and a complete transfer. Everything's
complicated.
Did the original inquiry here mention any
"remote trigger job"? Why work hard to solve
a problem which doesn't exist (here)?
> On that basis, I can think of no useful
> reason to use COPY/FTP rather than a script
> that has a degree of intelligence in it.
_I_ wasn't the one who was pushing COPY /FTP,
but it certainly "has a degree of
intelligence in it." On the other hand, to a
casual reader, it's not immediately obvious
where all the "intelligence" might be in the
scripts/fragments exhibited here, so far. I
can _imagine_ writing a fancy script which
would detect a hung transfer, but that script
might or might not use COPY /FTP.
If it does what you want, then use it. If
something else is better at doing what you
want, then use _that_. I don't care. In any
case, deciding exactly what to do often
requires knowing exactly what you want to do.
"How do I make FTP work" is not a detailed
enough problem specification to get me all
excited about the relative merits of using
COPY /FTP or some other FTP client.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-02-2010 12:01 PM
тАО08-02-2010 12:01 PM
Re: DCL script to FTP files
Don't know what the trigger is for your remote processing but it seems that if you want to drive it from the FTP client side you could just base the trigger decision on whether or not the COPY/FTP returned a successful status. Or, if you're driving the processing of the transferred file from the remote end you might choose to do something like transfer a FILE.TRIGGER (could even be zero blocks) upon a successful transfer status from the COPY/FTP of the FILE.DAT and have the remote end use the presence of that file as an indicator that the transfer was successful and as a trigger for processing.