Spooky: authorized records don't go in live file

We faced the following strange situation in several ocassions: either through EBS or OFS authorized records were lost like in a 'black hole'. You authorize but nothing gets to the live file, while records vanish from exception if they have been in IHLD for example to be used with EBS. With OFS even funnier thing happened, the errors were recorded by our program (based on OFS.GLOBUS.MANAGER), but the good records did not end in the live file.

The only thing we think we have done was resize before that. But it finished regularly and the session was closed before authorization in all separate cases. Any ideas what this may be?

Speaking about jBASE 4.1.5.8 / R06.

Chris

I suspect this problem is because of transaction boundaries. In R6 you should use OFS.POST.MESSAGE instead of OFS.GLOBUS.MANAGER.



See this thread also click


___________

Thanks

Thanks for replying. But I don't quite agree. That does not explain the same problem that we had with EBS autofunction. The only correlation is that we had performed resize several minutes before the authorization in both separate cases. It might be related to how jBASE performs memory cashing, but... that's a gray zone.

Regarding OFS.GLOBUS.MANAGER, it is not standard in R06, probably due to future design considerations, but was eventually recomended to us by helpdesk as a workaround because we have certain functionality that cannot be accomplished with OFS.POST.MESSAGE. So far it works perfectly, except this isolated case when we had resize and after that records went into nowhere. And I did not mention, same happened first when some of the tables used in the transactions were moved to ram disk. Then we got them back to disk with updated voc entries, again the authorized records went nowhere. We closed all processes, restored database backup before resize and the problem with authorization did not occur again with the same records.

With EBS autofunction we had this problem few times. Now, I just remember having another similar case when one exception table showed none records, while the count on jshell of the same file but with different session returned around twenty five. It was so spooky, I checked that many times, but after logoff from the sessions the commands worked well. The interesting point is that this time I did not perform resize. Unfortunately, I did not document this case and I swear I didn't drink at all that day, heh :)
So... we are now planning upgrade of jBASE, maybe that would help, what do you think?

cheers,
Chris

That seems to be a BUG. You shoud upgrade to Jbase 4.1.5.17. There are many scary stories about lost transactions, missmatches, etc. Temenos recomendation was to upgrade to 4.1.5.17, don't take 4.1.5.16 as this version has SORT problems in SELECT statement!!.

Cheers.