James Byrne writes:
 
>I have a question regarding executable (program) file transfers between HP3000's
>vis the Internet.   Paul Gobes of Robelle and myself spent a great deal of
>Tuesday getting the HP3000 LYNX program transferred from his 3000 to mine.
>Eventually we succeeded but I am wondering if in our frustration with various
>bits and piece we engaged in a bit of overkill. The steps that we eventually
>took to transfer a file which could run on the target machine were these:
 
   Try this (using some of James' original steps):
1       Transfer file to public gateway machine (HP9000) using FTP.ARPA.SYS
 
1.1     Run FTP from HP3000
 
        syntax  FTP.ARPA.SYS
                >BINARY         (must use binary transfer even if ascii file)
                >OPEN HP9000    (substitute IP address or preconfigured target
                                 name)
                >PUT LYNX /bin/dock/LYNX    (substitute public access path)
                >EXIT
 
        note    HP3000 FTP commands are not themselves case sensitive,
                but target and sorce file and path names are.
 
1.2     Switch to gateway machine and release file for read using chmod.
 
        syntax  chmod 444 /bin/dock/LYNXTU      (subsitute public access path)
 
This completes the process of readying the program file for transfer via a unix
gateway.
 
 
2.      From target machine access gateway site and transfer file.  It is not
        necessary to enter the Posix shell at all.
 
2.1     Logon as MANAGER.SYS and CHGROUP into USRBIN
2.2     Run FTP.ARPA.SYS
 
        syntax  FTP.ARPA.SYS
                >binary
                >open gwhp9000  (substitute ip address or preconfigured host
                                 name)
                >cd /bin/dock
                >get LYNX;code=nmprg;rec=128,1,f,binary;disc=<known eof of LYNX>
 
                >exit
 
3.      You're done
 
   Using the code, rec and disc parameters of the HP3000 FTP will reconstruct
   the program in it's original form.  No need for uuencode/uudecode or
   compression via MOVER.  The only thing you need to know on your end
   is where the file is (/bin/dock in your case), and the EOF of the LYNX
   program, which Paul could e-mail you or tell you over the phone.
 
   I've been using this type of ftp transfer of NMPRGs to some of our
   Internet-connected HP3000 customers for over a half a year now.  We
   are both on 5.0, so I don't know if the 4.0 FTP has this capability.
 
   cv
 
--
Craig Vespe [log in to unmask] Unison Software 811 Barton Springs, Austin Tx. 78704
(512)478-0611 http://www.unison.com NASDAQ UNSN disclaimer quote ANSI graphics