HP3000-L Archives

March 1997, Week 4

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:
"Stigers, Gregory - ANDOVER" <[log in to unmask]>
Reply To:
Stigers, Gregory - ANDOVER
Date:
Mon, 24 Mar 1997 12:01:00 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (18 lines)
Our mainframe is an IBM-plug compatible Hitachi. I have a file on our
LAN, that in production will be created on our 3K. We will then want our
hardware outsourcer to send it to our printing outsourcer's mainframe,
which is in another city, so tape is not a reasonable solution. We plan
to use FTP, available on our 3K (I know you already knew that) and on
the mainframe. When I ftp the file, I get 128-byte slices of the file
instead of my 400 byte records. I am using type ASCII on the 3K and type
ebcdic on the mainframe, because the other combination that I have tried
tell me that data was truncated. We would prefer not to have to
reassemble the original record, although I know how to code this in
COBOL. What do I need to know about ftp to either get the records we
want, or realize that we can't?

On a related note, when I ftp to our 3K, I get a binary,variable file,
which is not what we want either. I assume that this is a symptom of
much the same problem. On this one, I am about to RT*M, although I have
no manual for the mainframe, so that question will live on regardless.

ATOM RSS1 RSS2