How to avoid crash errors for executing a DCI case with isCOBOL2016R1? (DBMR2783)

~ 0 min
2016-06-17 04:44

When users execute DCI case in command lines, an error happens as following:

>java.exe ISMIGRATE

Exception in thread "main" java.lang.UnsatisfiedLinkError: com.iscobol.dci.Dci.dci__getenv(I[B[B)I

at com.iscobol.dci.Dci.dci__getenv(Native Method)

at com.iscobol.lib.DCI_GETENV.call(DCI_GETENV.java:43)

at com.iscobol.lib.DCI_GETENV.call(DCI_GETENV.java:24)

at com.iscobol.rts.Factory.call(Factory.java:3780)

at com.iscobol.rts.Factory.call(Factory.java:3689)

at ISMIGRATE.GET_DCI_CFG(ISMIGRATE.java:4382)

at ISMIGRATE.GUI(ISMIGRATE.java:2250)

at ISMIGRATE.MAIN(ISMIGRATE.java:2129)

at ISMIGRATE.perform(ISMIGRATE.java:1752)

at ISMIGRATE.call(ISMIGRATE.java:1736)

at ISMIGRATE.main(ISMIGRATE.java:43)

 

This problem is caused by the incompatible DCI library for isCOBOL2016R1. In order to fix MR10307 - "iscobol multi-thread with thin-client", both iscobol’s iscbol.jar and dbmaker’s dci lib have been modified, which makes JNI of DCI different from before.

 

That's to say, isCOBOL2016R1 must use the 2016 version of DCI library. In new DCI zip, users will find dci_2016.dll and libdci_2016.so and need to rename them to dci.dll and libdci.so separately for isCOBOL2016R1.

 

Version: DBMaker 5.4.x

Product: Bundle/Bundle

Platform: Windows/Linux

Average rating 0 (0 Votes)

You cannot comment on this entry

Tags