Due to a new 4 layer structure in our Natural applications the number of program- and DB calls per online transaction increases dramatically, thus we have lots of NAT1009 (DB-calls) and NAT1029 (module calls). To avoid applications of crashing we have build in frequent calls to a module, that checks used and available number of calls - but this method is just doing bad things worse! And all applications have to do this call, and all applications have to keep track of how many DB- and module calls have beeing made at a given point. This is not a stable situation!
I therefore have made EP3617 “User exit just before NAT1009 or NAT1029” on this topic, to be discussed on the User Group conference in Lisboa June 20-24 2005. But I would like to take the “user temperature” first, to see how other customers are handling this problem.
In the Enhancement Proposal I suggest that Natural Nucleus keeps track on those counters (it does it already), and just BEFORE giving a NAT1009 or NAT1029 error, a new User Exit should be triggered. In this user exit we should be able to:
- Show a window to the user, containing a text like “Working… Press Enter to continue or F3 to cancel operation”
- Resume the running program at the point where the user exit was triggered, or…
- Return a status to the running program, containing *CANCEL with the value FALSE or TRUE.
Any oppinions on that?