From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	FROM_STARTS_WITH_NUMS,INVALID_DATE autolearn=no autolearn_force=no
	version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,605b04e54783fbe5,start
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 1994-10-14 00:39:24 PST
Path: 
 bga.com!news.sprintlink.net!howland.reston.ans.net!cs.utexas.edu!convex!news.duke.edu!zombie.ncsc.mil!paladin.american.edu!auvm!COMPUSERVE.COM!73672.2025
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: comp.lang.ada
Message-ID: <941013034307_73672.2025_DHR76-1@CompuServe.COM>
Date: Wed, 12 Oct 1994 23:43:08 EDT
Sender: Ada programming language <INFO-ADA@NDSUVM1.BITNET>
From: Ken Garlington <73672.2025@COMPUSERVE.COM>
Subject: DEC Ada Question
Date: 1994-10-12T23:43:08-04:00
List-Id: <comp.lang.ada>

I'm using DEC Ada on VAX/VMS, and I have a problem with SEQUENTIAL_MIXED_IO.
I'm reading and writing a sequential binary file with fixed 512-byte records
(an executable image in Tartan Object File Format.) I can read the file fine,
and I can write a TOFF file OK, except for one small problem: The Tartan tools
that read/write TOFF files expect the end-of-file mark to point to the byte
immediately after the last significant data item in the last physical record.
As a consequence, the EOF mark may point anywhere within the last record, or
immediately after the last byte of the last record. However,
SEQUENTIAL_MIXED_IO _always_ places the EOF mark immediately after the last
byte of the last record. How can I change this behavior? I suspect I will have
to do some kind of RMS call to make this happen, but I can't find the solution
in any of the DEC manuals, so any help would be much appreciated.