We have begun to make use of the object browse subp in a few applications. Right now, we only use it for web to mainframe data access for the retrieval of multiple records. And maybe in the not so far future, I hope we will try to make use of it with the object browse dialogs.
I’m seeing something that I don’t really like about how these programs continue to read records from a previous call and the key being used is not unique. It is re-reading records. And this could possibly re-read a lot of records before it finds where it left off last time. My question to this is why doesn’t it make use of the STARTING WITH ISN = statement like the browse models do?? And is there a way around this?
Here is another scenario that I don’t understand:
Object browse is called with USE-UNIQUE-ID = TRUE. Then it is called a second time and USE-UNIQUE-ID = FALSE with intentions of continuing where it left off last time. But it doesn’t. It re-reads the last set of records and returns them. I see the code that causes this in the CHECK-FOR-RESTART subroutine and I all I have to do is RESET #COMPARE-DATA.USE-UNIQUE-ID(#CURRENT) in the INITIALIZATIONS user exit. So my question is, why does it assume a restart in this situation??
Natural 3.1.6 (soon to be 4.1.4)