NOTICE: Our Community is moving. Get more information.
Welcome to the Visual COBOL Knowledge Base. The Knowledge Base contains a large amount of information that may answer any technical questions you may have. To take full advantage of the Knowledge Bases across the Community please use the site search found in the top right hand corner of your Internet page. This search offers a wide range of customisation to narrow down your search to find your article. If you fail to find a solution here SupportLine will be able to assist you further.
Actual wiki pages seem to be unavailable
I'm trying to use System.Windows.MessageBox and get red lines under it.
What am I missing?
Today we P5 processor development and production have at least P7, the issue becomes more complex since we are compiling in P5 processors and these binaries will be promoted to Production.
At least we need to have to use the maximum P7 processors operating time production, on the other hand ask microfocus provider they point out the differences to try a compiled P5 and P7 certificate and exploited in binary.
Many Thanks in advanced.
I am tasked with trying to find ways to improve performance of Visual COBOL application. The Visual Studio Instrumentation appears to match to symbols from COBOL code for some functions, but in many cases can not match source. I tried to VS Premium 2013 and VS Premium 2010 and get similar results to below.
The "Summary" of instrumentation process will show long running Functions, but when selected it will display "Source code not available. You may not have the appropriate symbol paths or there was an error loading symbols.". I have double checked the symbols path. Is there any known issues with using VS Intrumentation? Any suggestion for determining which functions in our COBOL app are taking most of the time?