This error is usually a programming logic error, and reading by record
number can cause problems. It is best to avoid if possible, but I use it
all the time ;-)
If the logic in your program is such that it DBGET's records, and stores
the RECORD-NUMBER's for use later within the same program, then the
following should be true.
You should have put a lock around all associated records. Even if you
are not going to DBUPDATE the record, another process can delete your
Before you call DBGET with mode=4, you should of previously called dbget
to read a record from this data set 'xxxx', using mode 1, 2, 3, 5, 6,
or possibly 7. I don't know of any other way to retrieve a valid
The program should have stored (MOVE) the RECORD-NUMBER to another
variable, eq MY-RECORD-NUMBER.
Before you call DBGET with mode=4, you'll first need to move
MY-RECORD-NUMBER to RECORD-NUMBER.
The TurboImage/SQL Manual:
Jai Kishan wrote:
> Hello Guys,
> I'm trying to below turbo image debug error but I couldn't get any clue.
> Could you please help me out?
> TURBOIMAGE error- Directed end of file - DBGET, mode=4 on xxxx (dataset) of
> YYYY(database name)
> Through ADAGER, we examined all paths for the dataset. It didn't report any
> Please help.
> Thank you,
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *