HP3000-L Archives

December 1999, Week 1

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:
Erik Vistica <[log in to unmask]>
Reply To:
Erik Vistica <[log in to unmask]>
Date:
Mon, 6 Dec 1999 12:30:40 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
Try checking the ESC for doc MVAN000201 re: IBM Labeled Tapes Q/A. It
has examples of using Stan's workarounds with FCOPY.

Stan Sieler wrote:
>
> Re:
> > I am sending an IBM tape, EBCDICOUT. The record length as specified by the
> > recipient is 361 bytes. They report receiving 362 bytes, and cannot handle
> > it. (They must have figured out something, because the systems guy on that
> > end was able to tell me which fields on the test tape "need improvement",
> > but that's another matter.)
>
> AFAIK, tape records will always be an even number of bytes on an HP 3000.
>
> Workaround #1:
>
>    Write one record per tape block, of 362 bytes, and tell them to
>    only read 361 bytes...their hardware/software should do the same thing
>    ours does (if you read less data than is written): quietly ignore it.
>
> Workaround #2:
>
>    Write multiple records per tape block (an even number of records).
>    E.g., if you write two records of 361 bytes per tape block, that's
>    722 bytes...which is an even number of bytes.  They should be able to
>    easily handle deblocking the data.  If they can't, tell them they bought
>    the wrong computer system.  You can probably create this trivially with:
>          FILE TAPE;REC=-361,2,f,ASCII
>
> SS
> Stan Sieler                                           [log in to unmask]
> www.allegro.com/sieler/wanted/index.html          www.allegro.com/sieler

ATOM RSS1 RSS2