<br><font size=2 face="sans-serif">Hi</font>
<br>
<br><font size=2 face="sans-serif">We've received a fix for our "dictionary is locked for update" error but have been informed it introduces the following error in QTP :-</font>
<br>
<br><font size=2 face="sans-serif">----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------</font>
<br><font size=2 color=blue face="Arial">Here is an explanation of the possible scenario which can cause QTP to abort...</font><font size=3> </font><font size=3 face="Times New Roman"><br>
</font><font size=3> </font><font size=2 color=blue face="Arial"><br>
When QTP creates a scratch file it creates a series of UserSpace objects which have a limit of 16MB. If the scratch file is larger <br>
than 16MB then QTP creates a linked list of the UserSpace objects. However when creating the linked lists it might <br>
miscalculate when to link two user spaces together. The miscalculation would vary depending on the record size and the number of <br>
records being processed. For some record sizes the problem would never occur. </font><font size=3> </font><font size=3 face="Times New Roman"><br>
</font><font size=3> </font><font size=2 color=blue face="Arial"><br>
So the problem would arise if <br>
1. QTP need to create a scratch file.</font><font size=3> </font><font size=2 color=blue face="Arial"><br>
2. The record size and the number of records cause the miscalculation to occur. Unfortunately, there are no specific details.</font><font size=3> </font><font size=3 face="Times New Roman"><br>
</font><font size=2 face="sans-serif">----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------</font>
<br>
<br><font size=2 face="sans-serif">Does anybody know how to locate/read the scratch files on iSeries/AS400 so we can analyze the impact of this "feature"?</font>
<br>
<br><font size=2 face="AR Sans Serif">Regards </font>
<p><font size=1 face="Arial"><b>Andrew Tymm<br>
Senior Analyst/Programmer / DBA</b></font>
<p><span style="font-family:'Arial';font-size:8pt;">**********************************************************************</span></p>
<p><span style="font-family:'Arial';font-size:8pt;">COMPUTACENTER PLC is registered in England and Wales with the registered number 03110569. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW</span></p>
<p><span style="font-family:'Arial';font-size:8pt;">COMPUTACENTER (UK) Limited is registered in England and Wales with the registered number 01584718. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW </span></p>
<p><span style="font-family:'Arial';font-size:8pt;"></span></p>
<p><span style="font-family:'Arial';font-size:8pt;"> </span></p>
<p><span style="font-family:'Arial';font-size:8pt;">The contents of this email are intended for the named addressee only.</span></p>
<p><span style="font-family:'Arial';font-size:8pt;">It contains information which may be confidential and which may also be privileged.</span></p>
<p><span style="font-family:'Arial';font-size:8pt;">Unless you are the named addressee (or authorised to receive mail for the addressee) you may not copy or use it, or disclose it to anyone else.</span></p>
<p><span style="font-family:'Arial';font-size:8pt;"> </span></p>
<p><span style="font-family:'Arial';font-size:8pt;">If you receive it in error please notify us immediately and then destroy it.</span></p>
<p><span style="font-family:'Arial';font-size:8pt;"> </span></p>
<p><span style="font-family:'Arial';font-size:8pt;">Computacenter information is available from:</span></p>
<p><span style="font-family:'Arial';font-size:8pt;">http://www.computacenter.com</span></p>
<p><span style="font-family:'Arial';font-size:8pt;">**********************************************************************</span></p>