"Maximum number of screen calls was exceeded"

[Collings, Tony]

Thanks, Richard.

 

Yes, I understand that exiting the application stops the error but this
has proven difficult to enforce upon the end-users. In practice, they
stay in the screen until the error throws them out to the AIX shell,
whereupon they restart and continue until the next occurrence. I've
considered implementing an AIX-level session-timeout, based upon a
defined idle time, but would rather hold out for a more elegant
solution.

 

Tony

Email: 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

 

From: powerh-l-bounces+tony.collings=obs-logistics.com at lists.sowder.com
[mailto:powerh-l-bounces+tony.collings=obs-logistics.com at lists.sowder.co
m] On Behalf Of Richard Witkopp
Sent: 25 June 2015 18:49
To: powerh-l at lists.sowder.com
Cc: Scott, Julie
Subject: RE: "Maximum number of screen calls was exceeded"

 

Have you tried backing out to the main menu or even out of the
application altogether, maybe after a couple hours? That should clear
the stack.

 

From: powerh-l-bounces+rwitkopp=phxa.com at lists.sowder.com
[mailto:powerh-l-bounces+rwitkopp=phxa.com at lists.sowder.com] On Behalf
Of Collings, Tony
Sent: Thursday, June 25, 2015 9:41 AM
To: powerh-l at lists.sowder.com
Cc: Scott, Julie
Subject: RE: "Maximum number of screen calls was exceeded"

 

Forgot to add:

 

PH =  8.43G

O/S = AIX 6.1.0.0

 

Tony

Email: 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

 

From: powerh-l-bounces+tony.collings=obs-logistics.com at lists.sowder.com
[mailto:powerh-l-bounces+tony.collings=obs-logistics.com at lists.sowder.co
m] On Behalf Of Collings, Tony
Sent: 25 June 2015 17:29
To: powerh-l at lists.sowder.com
Cc: Scott, Julie
Subject: "Maximum number of screen calls was exceeded"

 

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 Web:
http://www.obs-logistics.com
Tel: +44(0)151 448 0331, DDI: +44(0)151 448 2961 Fax: +44 (0)151 448
2989

 

OBS Logistics Limited is a limited company. Registered in England No
02439258. Registered Office: 140 Buckingham Palace Road, London SW1W
9SA.
The information transmitted is only for the entity or person for whom it
is intended and may contain confidential and/or privileged material. Any
review, retransmission, dissemination or other use of, or taking of any
action in reliance upon, this information by persons or entities other
than the intended recipient is prohibited. If you receive this in error,
please contact the sender and delete the material from any computer or
media on which it resides.
Internet communications are not guaranteed to be secure or virus free.
OBS Logistics Limited does not accept responsibility for any loss
arising from unauthorised access to, or interference with, any Internet
communications by any third party, or from the transmission of any
viruses.
Replies to this email may be monitored by OBS Logistics Ltd for
operational or business reasons.

securemail.phxa.com made the following annotations
---------------------------------------------------------------------

NOTICE: The information contained in this e-mail and 
any attachments is confidential and may be privileged 
or otherwise protected from disclosure.This e-mail is 
intended solely for the use of the named addressee. 
Any other use, printing, copying, disclosure or 
dissemination may be subject to legal restriction. If 
you are not the intended recipient, please contact the 
sender and delete all copies including any attachments.

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