"Maximum number of screen calls was exceeded"

Lorry Litman LLitman at manitoba-ehealth.ca
Fri Jun 26 13:11:34 CDT 2015


Hi, this is a work around I used years ago for a similar "new user" pushing the envelope. And I thank him and all those that push the envelope as it keeps life interesting. :)
On VMS platform with PH 7.10E

High level
Users calls quick screen 'kick off'
User enters some info in fields....kicks off designer procedure (user does not have to exit screen as all processing is done under separate system processes)
Designer procedure passes variables to and executes a dcl command procedure
Separate job is submitted and the DCL command procedure calls quick screen 'work horse'
Quick screen work horse has an initialize procedure to do/control the processing and also has a FOR construct that uses the occurrence variable to count iterations.
If/when a certain count is reached the initialize procedure terminates and passes back info to the dcl command procedure that can (if required) call the work horse screen again passing new variables so it can continue from where it left off.

Hopefully this made sense (and you don't need to go there). It was very messy and I'm sure there are more elegant ways to do this.

Happy Friday :)

Thanx
Lorry Litman
Application Management
llitman at manitoba-ehealth.ca<mailto:llitman at manitoba-ehealth.ca>
204-926-9076

From: Collings, Tony [mailto:Tony.Collings at obs-logistics.com]
Sent: Friday, June 26, 2015 4:30 AM
To: Lorry Litman; powerh-l at lists.sowder.com
Cc: Scott, Julie
Subject: RE: "Maximum number of screen calls was exceeded"

Thanks, Lorry.

Yes, each new instance of quick is run from a new AIX shell.

I'm aware of the screen levels parameter and we have this set to 15. I'm not familiar with the concurrent screens parameter - this is the 'Screen Table' field in the 'Execution-Time ...' screen, right? I've just checked and it's set = the default 15. Although the description doesn't appear to be directly related to the error, I'll try upping it to 50.

I'll let you know if it works out.

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

From: Lorry Litman [mailto:LLitman at manitoba-ehealth.ca]
Sent: 25 June 2015 18:50
To: Collings, Tony; powerh-l at lists.sowder.com<mailto:powerh-l at lists.sowder.com>
Cc: Scott, Julie
Subject: RE: "Maximum number of screen calls was exceeded"

Not sure if different values for AIX PH8.4 but on VMS PH7.10, max screen levels is 15 and max concurrent screens on display is 50. Both can be set in the QKG execution time parameters.
Perhaps you could modify the code in order to log which screens are being called and count how many levels deep.
Was each new instance of quick for each batch run under a new/separate process?

Thanx
Lorry Litman
Application Management
llitman at manitoba-ehealth.ca<mailto:llitman at manitoba-ehealth.ca>
204-926-9076

From: powerh-l-bounces+llitman=manitoba-ehealth.ca at lists.sowder.com<mailto:powerh-l-bounces+llitman=manitoba-ehealth.ca at lists.sowder.com> [mailto:powerh-l-bounces+llitman=manitoba-ehealth.ca at lists.sowder.com] On Behalf Of Collings, Tony
Sent: Thursday, June 25, 2015 11:41 AM
To: powerh-l at lists.sowder.com<mailto: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<mailto:Tony.Collings at OBS-Logistics.co.uk> Web: http://www.obs-logistics.com</exchweb/bin/redir.asp?URL=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.com> [mailto:powerh-l-bounces+tony.collings=obs-logistics.com at lists.sowder.com] On Behalf Of Collings, Tony
Sent: 25 June 2015 17:29
To: powerh-l at lists.sowder.com<mailto: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<mailto:Tony.Collings at OBS-Logistics.co.uk> Web: http://www.obs-logistics.com</exchweb/bin/redir.asp?URL=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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sowder.com/pipermail/powerh-l/attachments/20150626/8dee53aa/attachment-0002.htm>
-------------- next part --------------
This email and/or any documents in this transmission is intended for the addressee(s) only and may contain legally privileged or confidential information.  Any unauthorized use, disclosure, distribution, copying or dissemination is strictly prohibited.  If you receive this transmission in error, please notify the sender immediately and return the original.

Ce courriel et tout document dans cette transmission est destin? ? la personne ou aux personnes ? qui il est adress?. Il peut contenir des informations privil?gi?es ou confidentielles. Toute utilisation, divulgation, distribution, copie, ou diffusion non autoris?e est strictement d?fendue. Si vous n'?tes pas le destinataire de ce message, veuillez en informer l'exp?diteur imm?diatement et lui remettre l'original.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sowder.com/pipermail/powerh-l/attachments/20150626/8dee53aa/attachment-0003.htm>


More information about the powerh-l mailing list