The problem recently was investigated on the machine and it was detected that Mercator 6.7 reads the mercator.ini faulty. This is hopefully the main cause for the mentioned start latency and a correction should bring up a fix for all Mercator users.
Time stamping would not help as this indicates...
When calling Mercator 6.7 Command Engine on HP-UX (from the shell) I detect a varying latency of 2-20 seconds before this instance processes a specified map or asks for a map.
If I concatenate several maps to be processed by one Mercator instance Mercator takes this "warm up time" only...
I like to give Pacos question from JAN 15 2002 another chance - we experience the same problem with these lists where we need to pick up an item by cursor:
Paco wrote: We need to select one line, but the problem is that the cursor is no visible (We determine the cursor position with SET...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.