<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:HyperFont;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:HyperFont;
color:#002060;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Thanks, Tracy.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>The process is many years old and up ‘til now has proven robust. The error only occurs for one, relatively new client who processes a larger number of records per ‘batch’ than the norm. Given this, I think it’s a problem with the underlying PH code but was hoping (and still hope) that somebody, somewhere has seen it and dealt with it.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Tony</span><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Email:</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'> <a href="mailto:Tony.Collings@OBS-Logistics.co.uk">Tony.Collings@OBS-Logistics.co.uk</a></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'> Web: <a href="/exchweb/bin/redir.asp?URL=http://www.obs-logistics.com/" target="_blank">http://www.obs-logistics.com</a><br>Tel: +44(0)151 448 0331, DDI: +44(0)151 448 2961 Fax: +44 (0)151 448 2989<o:p></o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> powerh-l-bounces+tony.collings=obs-logistics.com@lists.sowder.com [mailto:powerh-l-bounces+tony.collings=obs-logistics.com@lists.sowder.com] <b>On Behalf Of </b>Johnson, Tracy<br><b>Sent:</b> 25 June 2015 18:28<br><b>To:</b> powerh-l@lists.sowder.com<br><b>Subject:</b> RE: "Maximum number of screen calls was exceeded"<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:HyperFont;color:#002060'>My first thought is to check the subscreens aren't calling themselves into a loop.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:HyperFont;color:#002060'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:HyperFont;color:#002060'>Like what happens when an mechanical engineer adds a lower level component in a Bill of Material that calls a higher level component containing the same lower level components and crashes MRP.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:HyperFont;color:#002060'><o:p> </o:p></span></p><div><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:Consolas;color:#002060'><o:p> </o:p></span></p><p class=MsoNormal><b><span lang=EN-US style='font-size:10.5pt;color:#002060'>Tracy Johnson<o:p></o:p></span></b></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;color:#002060'>00 1 757 766 4318 tel<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;color:#002060'>00 1 757 755-6470 mobile<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:Consolas;color:#002060'><o:p> </o:p></span></p></div><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:HyperFont;color:#002060'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a href="mailto:powerh-l-bounces+tracy.johnson=meas-spec.com@lists.sowder.com">powerh-l-bounces+tracy.johnson=meas-spec.com@lists.sowder.com</a> [<a href="mailto:powerh-l-bounces+tracy.johnson=meas-spec.com@lists.sowder.com">mailto:powerh-l-bounces+tracy.johnson=meas-spec.com@lists.sowder.com</a>] <b>On Behalf Of </b>Collings, Tony<br><b>Sent:</b> Thursday, June 25, 2015 12:29 PM<br><b>To:</b> <a href="mailto:powerh-l@lists.sowder.com">powerh-l@lists.sowder.com</a><br><b>Cc:</b> Scott, Julie<br><b>Subject:</b> "Maximum number of screen calls was exceeded"<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Good afternoon all,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>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.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Has anybody seen and dealt with the error? What was done to overcome it?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>All suggestions/ideas welcome.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Thanks<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Tony</span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Email:<span style='color:blue'> <a href="mailto:Tony.Collings@OBS-Logistics.co.uk">Tony.Collings@OBS-Logistics.co.uk</a></span> Web: <a href="/exchweb/bin/redir.asp?URL=http://www.obs-logistics.com/" target="_blank">http://www.obs-logistics.com</a><br>Tel: +44(0)151 448 0331, DDI: +44(0)151 448 2961 Fax: +44 (0)151 448 2989<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p><span lang=EN-US style='font-size:8.0pt;font-family:"Arial","sans-serif";color:black'>OBS Logistics Limited is a limited company. Registered in England No 02439258. Registered Office: 140 Buckingham Palace Road, London SW1W 9SA.<br></span><i><span lang=EN-US style='font-size:7.5pt;font-family:"Arial","sans-serif";color:teal'>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.<br>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.<br>Replies to this email may be monitored by OBS Logistics Ltd for operational or business reasons.<o:p></o:p></span></i></p></div></div></body></html>