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?
Instrumentation is built in to Visual Studio, and appears to work on parts of COBOL code, but not all. Is the Micro-Focus answer to this that we have to purchase DevPartner to get full Instrumentation on COBOL code?
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?
I'm afraid it appears you'll have to open an incident for this with your Micro Focus Customer Care representative, since it doesn't appear that anyone from the Visual Studio team has seen it.
I haven't tried to use VS instrumentation with native COBOL code myself, so I don't know if this is an issue just in your environment or if it's a general restriction in the product. There are, broadly speaking, some inherent complexities in mapping traditional COBOL sources to the symbol model used by Windows (and various Linux/UNIX flavors), since COBOL paragraphs and sections have to be converted by the compiler into a more complex structure of entry points in order to accommodate COBOL's control-flow mechanisms (like PERFORM THRU).
DevPartner, the last I checked, wasn't suitable for instrumenting COBOL. That's not one of the languages it supports.
Micro Focus COBOL includes its own profiler:
documentation.microfocus.com/.../GUID-B24815C1-3707-4806-9CDC-80FC98E046C4.html
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?
We are not trying to Instrument Native COBOL. We are trying to Instrument Visual COBOL product.
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?
We are not trying to Instrument Native COBOL. We are trying to Instrument Visual COBOL product.
