Well, it looks like I goofed saying you could do as many DBOPENS as you want on a dataset.  I haven't looked at the Image manual lately and forgot about the 63 limit.  I don't think I have ever done more than 2 on the same database in one program.  

                  Edwin Clements



--- On Mon, 9/21/09, Denys Beauchemin <[log in to unmask]> wrote:

> From: Denys Beauchemin <[log in to unmask]>
> Subject: Re: [HP3000-L] TURBOIMAGE error- Directed end of file - DBGET, mode=4 on xxxx (dataset) of YYYY(database name)
> To: [log in to unmask]
> Date: Monday, September 21, 2009, 9:16 AM
> Ah, there is you problem.  The
> current limit is 63 opens for the same
> database, not 64.  I hope this helps.  :-)
> 
> Denys
> 
> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]
> On Behalf
> Of Roy Brown
> Sent: Monday, September 21, 2009 1:26 AM
> To: [log in to unmask]
> Subject: Re: [HP3000-L] TURBOIMAGE error- Directed end of
> file - DBGET,
> mode=4 on xxxx (dataset) of YYYY(database name)
> 
> >> Besides the list initialization I noted and
> the  "specifically 
> >>arranged and maintained" and  BOM use cases
> you mentioned, the only 
> >>other situation where  I can recall using a
> directed  read was to 
> >>re-establish record currency after
> interrupting  the processing of a 
> >>chain to  access some other record in the
> dataset. Of course that's 
> >>actually very similar to your  BOM use case.
> 
> In message <[log in to unmask]>,
> Edwin 
> Clements <[log in to unmask]>
> writing at 17:08:19 in his/her local time 
> opines:-
> 
> >If you want to access another record in the same
> dataset without 
> >interrupting the processing of a chain, the best way to
> do that is to 
> >open the database twice, and use the base established
> by the second 
> >open to access the other record(s) or chains or
> whatever, and that will 
> >not interfere with the first one (unless maybe you
> delete something). 
> >can do as many opens as you want as long as you keep
> all the data 
> >separate in separate working storage areas, etc.
> 
> Indeed so, for many cases, and I've had programs with a
> database opened 
> up to three times in order to keep enough current pointers
> into a given 
> dataset for what I needed.
> 
> But unless the limit in TurboImage has been changed
> recently, you can 
> only open a database 64 times in a given program - not
> always enough for 
> BoM usage.
> 
> But I daresay a few of us have seen the '64 opens' limit? I
> know I have, 
> debugging a program (not mine!) that looped round opening a
> database for 
> each user transaction, but not going through the close.
> 
> On busy days, the program would crash. But we never quite
> knew why it 
> was busy days only (apart from the general observation that
> programs are 
> ornery) until we caught it. Only on busy days would the
> user make 64 
> straight passes through the program without doing anything
> else. On any 
> other day, and even mostly on busy days, using another menu
> option 
> before hitting the 64 limit would reset things back to
> zero.
> 
> -- 
> Roy Brown        'Have nothing in your
> houses that you do not know to be
> Kelmscott Ltd     useful, or believe to
> be beautiful'  William Morris
> 
> * 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 *