Subject: | |
From: | |
Reply To: | |
Date: | Fri, 3 Mar 1995 09:04:03 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On Thu, 2 Mar 1995, Rudderow, Evan wrote:
> Karl Hancock <[log in to unmask]> asks:
> >What are the options for having an HP3k write files to a network (netware
>
> I haven't actually done this. First I would look at FTP, if that didn't pan
> out then I'd look at NFS (an implementation is available from Quest
We bought NETWARE to run on the 3000 to do this. We can drive the NWCOPY
sub-system from the MPE side of the house and place files on any server
on the network. We can also go read a file from any server (of course
the standard network security applies both ways).
Problems:
1. You can't get a directory listing to determine what files are there.
2. ASCII transfers up from the network presume 80 byte records. Can't
override.
3. BINARY transfers up from the network presume 256 byte records. Can't
override.
4. Sending files to the network have trailing blanks stripped off. Only
way to override is to ensure the last byte of each record is non-blank.
Other than that, we have managed to do pretty much what we want to in
moving files to/from MPE and the network. It's also cheaper than the NS
or FTP route (or was a couple years ago).
+----------------------------------------------------+
| Steve Butler Voice: 206-464-2998 |
| The Seattle Times Fax: 206-382-8898 |
| PO Box 70 Internet: [log in to unmask] |
| Seattle, WA 98111 Packet: [log in to unmask] |
+----------------------------------------------------+
All standard and non-standard disclaimers apply.
All other sources are annonymous.
|
|
|