One VAGen customer is verifying the function that EGL/Java calls native C/C++ program on Windows to prove that
its VAGen legacy application( VG/C++ call native C/C++) can be migrated to RBD 9.0.
Its legacy application is client/server architecture ( GUI built by JBuilder calls VAGen/C++ through VAGen Java wrapper ).
By following the EGL linkage documents, I created a linkage entry for CP( C++ program) and set the
type= remotecall library=CP remoteComType=DISTINCT remotePgmType=externallyDefined
When generating the EGL calling program , the javaBuildOption with the CP linkage is used.
The CP DLL is placed in the same directory with EGL/Java jar file and the directory has been added to PATH and the
wrapperCompatibility = current is used
During the runtime trace message , the EGL0078E with RC=126 is returned.
Any hints or experience sharing is very welcome
BTW , RBD 9.0 and JRE 1.6 is used for both Java GUI and Java server in runtime.