We have a Native COBOL program that reads excel files using COM Automation. After upgrading Microsoft Office from 2010 to 2016, the program takes about twice as long. Processing the same 270 files before the upgrade took on average 3-4 seconds per file. After the upgrade it takes 7-8 seconds. Are there any know issues with accessing Excel 2016? The code is attached, any suggestions are appreciated. Thanks, Emi
↧
Forum Post: Performance degradation of Native COBOL access to Excel 2016
↧
Forum Post: RE: Calling NATIVE COBOL from cobjvm
$COBDIR/demo/jvm_cobol/JVMNativeInterop is a delivered demonstration on how to call native COBOL from JVM COBOL Regards Yvon
↧
↧
Forum Post: Visual Cobol - Dialog System - compataddpack_232
Hello, i'm getting an error when installing the compataddpack_232.msi (update 2) on a Windows 7 - 64 bit professional system. When installing the Micro Focus Compatibility AddPack for Visual Cobol Setup following error shows up: Error: Missing INSTALLDIR First i try to install it on a "clean machine" no Micro Focus software is installed before, i started which the compataddpack_232.msi Second i tried to install compataddpack_230.msi which succeeded. Then i tried to install compataddpack_231.msi (update 1) which also succeeded. Afterwards i tried to install compataddpack_232.msi (update 2) but no success - i get the same error as bevore when i try to install compataddpack_232.msi (update 2) directly on the clean machine. Even it uninstall the successfully installed compataddpack_231.msi (update 1) and deletes all the directories which have been created. I also redownloaded the compataddpack_232.msi (update 2) from the micro focus website to make sure the download is not corrupted and tried all the above which the freshly downloaded compataddpack_232.msi but the behavior and the error are still the same. Does anyone have a clue what the problem can be? Thanks for your help. Regards Frank.
↧
Forum Post: RE: Calling NATIVE COBOL from cobjvm
The sample Yvon described is your best starting point for now. If you have specific questions after trying it out we'll be glad to help. Paul Kelly, the author of Visual COBOL: A Developer's Guide to Modern COBOL , is working on a book for JVM COBOL. (Incidentally: Neither "Java" nor "Linux" are acronyms, just proper nouns. There's no need to write them in block capitals.)
↧
Forum Post: RE: Visual Cobol - Dialog System - compataddpack_232
You need to have version 2.3.2 (that is, 2.3 update 2) of Visual COBOL, Enterprise Developer, or COBOL Server installed before you install version 2.3.2 of the Compatibility Addpack. It's an add-on for the 2.3.2 COBOL products, not a standalone product.
↧
↧
Forum Post: RE: Visual Cobol - Dialog System - compataddpack_232
Thanks for your fast reply. So for Visual Cobol 3.0 there wont be a possibility to use dialog system anymore? Because also when i try first to install Visual Cobol 3.0 and afterwards install the compataddpack_232.msi i get the same error. For Visual Cobol 3.0 i couldn't find an adequate dialog system version on the Micro Focus website. Will maybee Visual Cobol 3.0 and compataddpack_231.msi word together?
↧
Forum Post: RE: Visual Cobol - Dialog System - compataddpack_232
compataddpack_231 is for Visual COBOL 2.3 Update 1. Addpacks are for specific product releases; you can't use them with different products. I don't know the status of Dialog System for Visual COBOL 3.0 offhand, though I thought there was an addpack for it. Your Micro Focus sales representative or Customer Care would be in a better position to answer that.
↧
Forum Post: RE: Visual Cobol - Dialog System - compataddpack_232
Quite the opposite - from Visual COBOL 3.0, the Dialog System functionality is included in the standard product. It continues to be supported for backward compatibility and not recommended for new development, but will no longer require installation of a separate AddPack.
↧
Forum Post: RE: Calling NATIVE COBOL from cobjvm
Thanks. I have got my test to run. I have one further question, I need to be able to invoke my mixed program with just the "java" command and not "cobjrun". It works with "cobjrun", but when I use "java" instead of "cobjrun" (the rest of the command is the same), I get this error. com.microfocus.cobol.program.COBOLProgramLoadException: 173 Called program file not found in drive/directory [ap01a.so] (107 Operation not implemented in this Run-Time System [Cannot load native COBOL programs in pure JVM COBOL runtime.]) Any ideas?
↧
↧
Forum Post: RE: Calling NATIVE COBOL from cobjvm
cobjrun has to be used. Regards Yvon MF DOC: Micro Focus Developer > Visual COBOL Development Hub 3.0 > Programming > Using COBOL and Java Together > Considerations Java/COBOL Application Launcher documentation.microfocus.com/.../GUID-7CA1C8A2-BFED-41A1-A7EA-599F01671A44.html
↧
Forum Post: RE: Calling NATIVE COBOL from cobjvm
That will not work for this situation, the "top" of the solution is a java class, and the whole thing is to run under TUXEDO as a service. TUXEDO will launch the JVM, I can set any environment variables and classpath as well as properties (java -D) but I cannot get it to call cobjrun.
↧
Forum Post: RE: Calling NATIVE COBOL from cobjvm
You might try creating a symbolic link for cobjrun named java, and place it on the PATH before the java binary would occur.
↧
Forum Post: RE: Calling NATIVE COBOL from cobjvm
TUXEDO does not actually use the "java" command, they have their own executable that instantiates the JVM (kind of like cobjrun does) but with more stuff going on.
↧
↧
Forum Post: RE: Calling NATIVE COBOL from cobjvm
Can you compile your COBOL code as JVM COBOL rather than native? Barring that, you'll probably have to run your native COBOL as a separate process and communicate with it using some form of IPC.
↧
Forum Post: RE: Calling NATIVE COBOL from cobjvm
I would like to get there eventually, but in the short term no. (SYBASE db precompile uses native Sybase SQL whereas OpenESQL uses a generic form of SQL and we have lots of embedded SQL). Separate Process would be quite a bit of work as well.
↧
Forum Post: RE: Performance degradation of Native COBOL access to Excel 2016
I do not believe that the performance issue has anything to do with the COBOL program or it's COM support. I Googled "excel 2016 macros slow" and received a number of hits from other non-COBOL users that are experiencing the same slow-down. One example would be: stackoverflow.com/.../excel-macro-sometimes-incredibly-slow-in-excel-2016-but-not-in-excel-2010-high Advice varies between different posts.
↧
Forum Post: RE: Creating an execution
COBOL Server is a Micro Focus product, not a Microsoft one and it is available for sale to customers that have a fully licensed Visual COBOL development product. If you are using the Visual COBOL Personal Edition version, which is a learning tool then the COBOL Server product is not available to you as you are not allowed to deploy your applications to other computers. For the Beep in a Windows Forms application you can use: Add this line to the top of your program or check System.Media on the namespaces tab of the Property page. $set ilusing"System.Media" Then you can emit the system beep using: invoke type SystemSounds::Beep::Play For a GUI app it would seem more likely that you would display a MessageBox to alert the user and you can do this with the MessageBox class. invoke type MessageBox::Show("This is a Message!") To create a web application you should select the ASP.NET Web Application project template. There is a very simple tutorial in the docs that demonstrate this and then there are some better examples in the Samples Browser available under the Micro Focus Visual COBOL group on the start menu. You might also want to get a copy of the book Visual COBOL: A Developers Guide to Modern COBOL.
↧
↧
Forum Post: RE: Authorisation code did not receive with the download of trial software.
If you have registered for 30 day Trial of Visual COBOL then you should have received an email containing a link to the software to download. If you click that link it should show you a web page allowing you to select which product version you would like. If you click on the version name then the Authorization code will be displayed below on that same page. You will have to copy and paste this into the License Manager dialog when prompted.
↧
Forum Post: RE: calling procedural cobol from java I get error
Have you added the mfcobol.jar file in the Visual COBOL bin folder to your CLASSPATH?
↧
Forum Post: RE: Performance degradation of Native COBOL access to Excel 2016
I see all these complaints. Will try some of the best practices described here blogs.office.com/.../ Thank you for pointing me in the right direction.
↧
