Java re

1. Calling NATIVE COBOL from cobjvm I am working my way through "Visual COBOL, a developer's guide to modern cobol". I found an example on page 99 of "calling native code from managed COBOL". Now our environment is LINUX and we use Java not .NET. Does anyone have an example of this for JAVA and LINUX or is this even possible?#nativecobol#COBVJM 2. RE: Calling NATIVE COBOL from cobjvm $COBDIR/demo/jvm_cobol/JVMNativeInterop is a delivered demonstration on how to call native COBOL from JVM COBOLRegardsYvon 3. RE: Calling NATIVE COBOL from cobjvm Best Answer 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.) 4. 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? 5. RE: Calling NATIVE COBOL from cobjvm 6. 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. 7. 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. 8. 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. 9. 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. 10. 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. 11. RE: Calling NATIVE COBOL from cobjvm I have been goggling around "Java TUXEDO" and see no evidence of TUXEDO which would be using "their own executable that instantiates the JVM (kind of like cobjrun does) but with more stuff going on"...Would you elaborate on this. I found in TUXEDO DOC the PATH has to point to the bin directory of the installed JRE ... which would indicate TUXEDO/java use the java launcher ... !?Also, taking this URLdocs.oracle.com/.../pgapi.htmlWould you be trying to invoke JVM COBOL here?...rply = myAppCtxt.tpcall("SVC", rqStr, TPNOTIME|TPSIGRSTRT);/* !? Invoke JVM COBOL here !? */rtn = TuxAppContextUtil.tpappthrterm();...I don't have right now TUXEDO on line and never played so far with TUXEDO/Java ...docs.oracle.com/.../javaservadmin.htmlOracle Tuxedo Java Server Administrationdocs.oracle.com/.../pgint.htmlIntroduction to Oracle Tuxedo Java Programmingdocs.oracle.com/.../index.htmlIntroduction to Oracle Tuxedo Java ProgrammingRegardsYvon

For example while installing Servoy and then later switch to Java 64 bit, you have a problem.So again: removing Servoy and all Java installs, then install Java 8 64 bit, then install servoy should work. It’s all about the dll in the “service” directory of application_server… Westy March 26, 2017, 2:22pm 13 “At the time of installation the installer uses the one that matches the Java environment that is currently active.”Is that true for the Servoy 6.x installer?Dean patrick March 26, 2017, 2:30pm 14 That is true for every installer we ever had. The installer can just ask: hey, what Java is running and then decide what dll to install. You could have 10 different Java versions on your machine… Westy March 26, 2017, 2:33pm 15 Per instructions, I have removed Servoy and all Java installs, then installed Java 8 64 bit, then re-installed servoy. I ALSO changed wrapper.java.maxmemory=1280 in the wrapper.conf file to wrapper.java.maxmemory=6400 (server has 12GB of RAM), because we have up to 300 simultaneous webclient users. After re-starting the Servoy Application Server service, the .service_log.txt file now reads:Wrapper Started as ServiceJava Service Wrapper Standard Edition 64-bit 3.3.5Copyright (C) 1999-2009 Tanuki Software, Ltd. All Rights Reserved. to Servoy for ServoyApplicationServerLaunching a JVM…IWrapperManager: Initializing…Java HotSpot™ 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0on_exit trigger matched. Restarting the JVM. (Exit code: 1)Launching a JVM…WrapperManager: Initializing…Java HotSpot™ 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0on_exit trigger matched. Restarting the JVM. (Exit code: 1)Launching a JVM…WrapperManager: Initializing…Java HotSpot™ 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0on_exit trigger matched. Restarting the JVM. (Exit code: 1)Launching a JVM…WrapperManager: Initializing…Java HotSpot™ 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0on_exit trigger matched. Restarting the JVM. (Exit code: 1)Launching a JVM…WrapperManager: Initializing…Java HotSpot™ 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0on_exit trigger matched. Restarting the JVM. (Exit code: 1)There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.There may be a configuration problem: please check the logs.SIf I uninstall the service, delete the .service_log.txt file, reset the wrapper.conf file’s wrapper.java.maxmemory back to 1280, re-install service, and then restart the service, the resulting new .service_log.txt file shows the same failures. What to do?Dean patrick March 26, 2017, 2:45pm 16 Westy March 26, 2017, 6:09pm 17 I re-installed Servoy 6.x yet again and now the service starts with no errors. Thank you for the information and the link. Now I will read about managing memory.Dean Westy March 26, 2017, 6:48pm 18 I have read the memory instructions at the above link. Our solution is webclient only. In the wrapper.conf file (from this latest