HP3000-L Archives

April 2001, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
EBEN YONG <[log in to unmask]>
Reply To:
EBEN YONG <[log in to unmask]>
Date:
Wed, 18 Apr 2001 09:14:06 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (40 lines)
Hi,

I am attempting to transfer a file from our HP9000 to our HP3000.  The file
is a 633-byte record length datafile.  Using FTP on the e3000, I used these
statements:

ftp> get dhs_chdp CHDP;REC=-633,44,F,BINARY
200 PORT command successful.
150 Opening BINARY mode data connection for dhs_chdp (675411 bytes).
226 Transfer complete.
675411 bytes received in 0.64 seconds (1022.61 Kbytes/sec)

But on the MPE side, I get this:

FILENAME  CODE  ------------LOGICAL RECORD-----------  ----SPACE----
                  SIZE  TYP        EOF      LIMIT R/B  SECTORS #X MX

CHDP              317W  FB        1066     204800  44     2656  5  8

Instead of creating a 633-byte record length file, it created a 634-byte
record length file, an offset of only 1 byte, but causing an accumulating
shift of each record by 1 byte from one record to the next.  For example, in
the illustration below, the record should be 7 bytes long, but displays the
effect if it is converted to an 8-byte record length file:

Record1:  12345671
Record2:  23456712
Record3:  34567123
Record4:  45671234 etc...

Any input would be greatly appreciated.

Thanks,

Eben Yong
Health Plan of San Mateo

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

ATOM RSS1 RSS2