Me asked...
>>Is the file bytestream on the 3000 side (see LISTFILE,2)?

You answered...
>No.

Ah, that is probably a clue to why the Samba transfer is so
much slower. Samba being a Posix app and living under the Posix
view of the world, only knows the notion of bytestream files.

The file system introduces a bytestream emulation to make the
Posix program "happy" when reading a fixed or variable record
structure file. This can introduce problems (e.g. overall length
of the file not matching the expected value due to trimming of
trailing blanks in text files and adding LF line delimiters) as
well as introduce (significant) processing overhead.

You might want to try a /bin/tobyte to create a bytestream copy
of your file and access that copy via Samba to compare transfer
times. (tobyte needs -a or -at if the file is not binary).

Or you might create the file in bytestream format right from the
beginning. Sometimes possible with a simple file equation like
FILE MYFILE;REC=,,B where it had ;REC=-80,,F,ASCII or somesuch
before.

Lars.


PS: What does LISTFILE,3 show? Fixed? Variable? Ascii? Binary?

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *