Dan Sugalski wrote:
>
> At 02:31 PM 2/18/00 -0500, Joe Kazimierczyk wrote:
> >I tried a plain perl 'open' of the file, and it works fine so I'm
> >surprised that ftp complains. But I can't take your suggestion because I
> >need to run this step in a larger program to 'get' the file. How does
> >the ftp code do the file open to get a remote file? (I looked in the
> >code, but was a little lost). I guess my other option is to spawn the
> >Multinet FTP command instead of using Net::FTP, which should work but is
> >not as elegant.
>
> Oh, well duh. If I'd looked closer at the code I'd see my solution wasn't
> going to do anything for you.
>
> If you've got multinet on both ends, then the ftp transfer with the command
> line tools is definitely working differently than with Net::FTP. The big
> difference is that the transfer takes place in VMS mode (STRU VMS) rather
> than binary mode, and I'd bet that alters the way the server opens the file
> for access. Unfortunately nobody's written code for Net::FTP to do VMS-mode
> transfers.
>
> You might want to check with Process to see if there's some magic you can
> do to convince the server to open this file anyway when in straight binary
> mode. Otherwise you're stuck either spawning off the DCL FTP command or
> writing the VMS transfer mode yourself. (And won't *that* be fun? :)
>
Just a note to finish off this old thread of mine (for the archives, and
in case anyone else is interested):
Process Software has provided me with a patch to Multinet's FTP that
allows me to do a plain binary get of open files from non-Multinet
clients (ie Net::FTP). This patch will eventually be made public.
Also, Hunter Goatley suggested that he may put this enhancement into his
fine MadGoat FTP product, but no definitive word on that yet.
