If I understand your question correctly, you could be seeing a
difference because you're looking at the media record length in Image,
which includes bit maps, chain pointers, etc., depending upon the set
type.  Be sure you're looking at the actual data record length and not
the media record length of the Image entries.

If I've misinterpreted your request, please forgive the wasted bandwidth.  :)

Lee Gunter
Regence HMO Oregon

mailto:[log in to unmask]

voice...503-375-4498
fax.....503-375-4401
==========================================================
The opinions expressed, here, are mine and mine alone, and do not
necessarily reflect those of my employer.

______________________________ Reply Separator _________________________________
Subject: [HP3000-L] IMAGE sanity check
Author:  "Stigers; Gregory - ANDOVER" <[log in to unmask]> at ~INTERNET
Date:    8/15/97 12:04 PM


Our application is developed on the LAN, and the source is then uploaded
to the 3K, with one important difference. All I/O is manage thru called
objects; on the LAN we use Micro Focus ISAM, but on the 3K we use IMAGE.
So while the copybooks are identical, what the object does to READ /
DBGET or WRITE / DBPUT is platform specific.

I am changing the schemas to conform to record structure changes (thanks
to Adager Corp for making this easier!). Our Oracle DBA mentioned that I
might do a quick sanity check of my record lengths on both platforms.
That sounded like a great idea, until I did check my record lengths with
the Micro Focus Data File Editor and QUERY, FORM SETS, and found a
non-trivial difference.

I am using Visual Source Safe's diff to double-check the programmer
design specs, and am reasonably sure that I haven't missed anything that
was changed on the LAN, that I have failed to change in IMAGE. And what
is S9(4) COMP in the record structure is I1 to IMAGE, and so forth
(thanks to Robelle for their contributions to my understanding of this,
back when). Is there some other reason that record lengths could be out
of sync?