"Maximum number of screen calls was exceeded"

[Collings, Tony]

Good afternoon all,

 

We have an application process that is producing the Max screen calls
error on an almost daily basis. A potentially large number of data
records are being processed in a single batch and each record in the
batch runs at least one, perhaps more, sub-screens = a correspondingly
large number of screen calls. The users of the application process stay
in the top-level screen, without exiting, processing batch after batch,
and the error occurs after the session has been active for several
hours. We've tried running a new instance of quick for each batch,
assuming the process counters would be reset with each instance and stop
the error being tripped, but we're still getting it.

 

Has anybody seen and dealt with the error? What was done to overcome it?

 

All suggestions/ideas welcome.

 

Thanks

 

Tony

Email: Tony.Collings at OBS-Logistics.co.uk
<mailto:Tony.Collings at OBS-Logistics.co.uk>  Web:
http://www.obs-logistics.com
Tel: +44(0)151 448 0331, DDI: +44(0)151 448 2961 Fax: +44 (0)151 448
2989

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sowder.com/pipermail/powerh-l/attachments/20150625/c2290376/attachment.htm>