Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!ucbvax!NMFECC.ARPA!KARNEY%PPC.MFENET
From: KARNEY%PPC.MFENET@NMFECC.ARPA.UUCP
Newsgroups: mod.computers.vax
Subject: Extra space in UAF records
Message-ID: <861222071633.0f2@nmfecc.arpa>
Date: Mon, 22-Dec-86 10:16:33 EST
Article-I.D.: nmfecc.861222071633.0f2
Posted: Mon Dec 22 10:16:33 1986
Date-Received: Tue, 23-Dec-86 18:48:55 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 24
Approved: info-vax@sri-kl.arpa


  I've written a program which updates records in the SYSUAF file.  I'm
using the layout of the SYSUAF file given by John Carosso in SYSUAFDEF.PAS
which Joe Meadows distributed as part of DELIVER.  The last two fields in
this record definition (uaf$b_filler5 and uaf$b_filler6) increase the
length of the record from 644 bytes to 1412 bytes.

  If you create a new SYSUAF.DAT, DIR/FULL shows that the record format is
"Variable length, maximum 1412 bytes", while DUMP/RECORD shows that the two
records (SYSTEM and DEFAULT) in the file both have only 644 bytes.

My questions are:
  What are these last two fields used for?
  Does it hurt to read in a 644 byte record and update it as a 1412 byte
record (with the extra bytes set to zero)?
  What's the easiest way in PASCAL to read and update variable length
records (from a file like SYSUAF.DAT) keeping the length of the record
fixed?

                    Charles Karney
                    Karney%PPC.MFENET@NMFECC.ARPA
CC:
        INFO-VAX@SRI-KL.ARPA
        KARNEY