In <[log in to unmask]> [log in to unmask] writes:
 
> I have a question regarding executable (program) file transfers between HP3000
> 0'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.
 
As this is a subject close to my heart (I've also spent ALOT of time getting
posix files onto 3000s via various methods) I thought I'd throw out a method
I've used successfully - it's a kludge but it works.
 
First, notes on the ftp-antics used to transfer files. The uuencode step
shouldn't be necessary; ftp will transfer binary files just fine. The problems
stem from how HP's ftp store the file on your system once they get there.
 
I don't much like the way it handles posix stuff, but you should be able to
just copy the file (though it MAY have to be in the MPE name space? I know
the ftp server we use -Fransen/King's - doesn't recognize HFS files). Anyway,
assuming you can access it at all, select binary transfer mode (either a
button on GUI ftp clients, or the 'binary' command in line-mode versions);
then just copy it to a binary file on your system. After the transfer, it's
now a binary blob (as in icky-mess, not a database object). Your challenge
now is to find the right combination of FCOPY attributes and/or using the
TOBYTE program to get it into byte-stream format and useable.
--I've gotten this to work, but it's NOT very straightforward and I don't
  recall the steps I used to do. I really should write it down, but I got
  the whole process to work much more easily using WRQ's ftp and/or file
  transfer process, which I'll describe below.
 
The process I use uses Reflection 1 version 5.0 - which is really still
pretty broken when it comes to handling HFS files, but CAN be made to work.
 
One foreword; there are two types of files you need to be concerned with
when it comes to MPE and HFS; (1) plain old byte stream files - text or
binary - as long as they aren't executable files! and (2) executable files.
(1) files can be transferred in and out of HFS pretty easily, it's the (2)s
that take special setup. The reasons have to do with MPE expecting certain
attributes on NMPRG files, whether they're in the POSIX domain or not.
Among other things, these files need NMPRG (1030) filecodes, 256byte/128Wd
record sizes, and fixed records.
 
That said, if you capture the raw binary contents of an NMPRG file (like
Lynx - which I just successfully transferred via modem yesterday- or even
httpd/imagemap/getstats/the other www server NMPRG files - which I also was
able to copy to another system via modem yesterday) you can upload them to
the 3000 using Reflection 1 5.0 no fuss/no muss. *Even the ftp'd lynx you
copied to your 3000 above, could be downloaded to your PC as a binary -not
labelled- file and uploaded so it would be useable.
 
In R1, select file-transfer, select the setup button;
1) Select the preset configuration for To MPE/iX (POSIX)
2) select the WRQ/Reflection index tab
3) on that screen, select Transfer-Type BINARY
4)         also    select Record size: 256
5) select the "attributes" button
6) Fill in the following on this screen:
    Blocking factor: 1
    File Code: 1030
7) The other settings on the window should be selected to reflect:
   Domain: Permanent
   Record Type: Binary **
   File Type: Standard
   Record Format: Fixed **
  (The "**" fields will probably need to be changed)
8) select ok to leave the HP File attributes window
9) select ok on the file transfer setup/WRQ/Reflection window
10) Now select the from filename and to filename and transfer away.
    **Remember the filenames are case sensitive.
11) You may need to 'chmod' the file to allow it to be accessed/executed
   from wherever you plan on running it - for example:
    'chmod 111 lynx'  (allows anyone to execute it)
 
It may seem like alot of hassle, but the setup takes a couple seconds, then
transfers executable files without a problem. The nice thing here is that
you can pull the files down to your PC any way you like; ftp, web clients,
gopher; once they're there you can upload them to your 3000 easily and
quickly.
 
I just uploaded the entire httpd (www) server via modem this way and it
worked first time.
 
Hope this helps...
 
                               -Chris Bartram
 
 
______________________/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_
  Chris Bartram        Sales (US):   800 Net-Mail    Fax:+1 703 451-3720
   ______              -or-       +1 703 569-9189 E-Mail: [log in to unmask]
  /__ |  \__________   Sales (Europe):+44(0480)414131 Fax:+44(0480)414134
 /  / | / ________     Sales (Pacific Rim):+61 3 489 8216 (same for fax)
|  /_ |<  ______       Tech Support:+1 703 569-9189  Fax:+1 703 451-3720
 \ __)| \ ___          E-mail: [log in to unmask]   Personal(me): [log in to unmask]
  \______/ Associates  6901 Old Keene Mill Rd Suite 205 Springfield VA 22150
______________________/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_
Gopher: gopher.3k.com   Anon-FTP: ftp.3k.com  WWW: http://www.3k.com/