What you are describing is a mode 8 read. A mode 8 gets the primary record
only not any secondaries. I would possibly check that the mode is correct
and of the correct data type and such. The record in question maybe a
secondary and all the others are primary.

James

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
Behalf Of william l brandt
Sent: Thursday, October 07, 1999 12:55 AM
To: [log in to unmask]
Subject: weird IMAGE code 17


Here's one for the books - I know that IMAGE is so bulletproof that it is
something in my app.

I am reading a file and use a field to extract a key and do a mode 7 DBGET.

There are 7000 records and it does fine until it gets to this 1 record. The
data entry is actually there but I get a mode 17 (no master entry)

Now, here's the strange part. To debug I display the key - which is
CORRECT until I get the return of the DBGET call - then I display the key
and I have a different key. Both good and bad keys have corresponding master
entries.

This would imply a memory problem but I run BASIC/3000 on the old Classic,
and usually bounds violations and similar stuff show up when I run
interpretively.

Now a hint of the problem is that this particular record, when removed - the
program runs and ends normally.

So you'd think there's something wrong with the record - but I can't see
anything.

Just musing I guess - I'll try & see ifthis record has any strange
characters.

I've been playing with this for 2 days and will let you all know when I find
the culprit.

Any of you have any ideas?

Since BASIC/3000 has slightly different image calls - with variable length
strings - I've seen some weird stuff over the years!

Bill