Please,

What's the correct location path of the EGLSDK ?

...SDP\bin\EGLSDK\runtime\eglbatchgen.jar

or

...\SDPShared\plugins\com.ibm.etools.egl.batchgeneration_7.200.1.v20141124_1029\runtime\eglbatchgen.jar

When I install the fixtest, which one is applied ?

Thanks !

Hsieh,

The default location to use is the one in the SDP\bin folder.

The fixtest installer actually creates/updates two copies:

a.) It copies the one from the Shared\plugins directory into the nonShared\dropins\EGLFixtests folder.

b.) It updates the one in the SDP\bin folder.

I copied this from a EGLFixtest.log

Applying changes (no APAR specified) on Aug 26, 2015
   Applying all changes for com.ibm.etools.egl.batchgeneration
      Copy plugin com.ibm.etools.egl.batchgeneration from shared directory to nonshared directory
      Copy plugin com.ibm.etools.egl.batchgeneration from shared directory to nonshared directory - results successful
      Updating manifest
      Updating manifest - results successful
      Updating jar C:\RBD91_64_Test\dropins\EGLFixtests\plugins\com.ibm.etools.egl.batchgeneration_7.200.1.v20141124_9999\runtime\eglbatchgen.jar
      Processing class files against jar - results successful
      Applying fix test to bin/EGLSDK/runtime/eglbatchgen.jar
      Applying fix test to bin/EGLSDK/runtime/eglbatchgen.jar - results successful

So, after installing a fixtest, you can use either the "9999" version in the dropins folder or continue to use the one out of the "bin" folder.   You control this by your Classpath setting.

Mark

Thanks !  Mark.

I saw this log after the post.

Please, one more question:

The cobol source generated has the comment

* GENERATION SYSTEM : ZOSCICS

* GENERATION DATE : 2015/07/15

* GENERATION TIME : 09:14:08

* GENERATOR LEVEL : V9110

* INSTALLED APARS

* PI41665

* PI42081 - solve import path compile error issue

* PI44526

* XX50403

These APARS list is generated by EGL both in  IDE and EGLSDK, correct ?

Why of my the question ?

Because the customer have generated using EGLSDK in the Build Server and the source cobol has not these APAR List comment.

then I suppose the fixtest was not applied in Build Server.

Thanks !

Hsieh,

Unfortunately, the APARs are not displayed in the comments using EGLSDK.     The way the APAR info is obtained is not available in the EGLSDK method.

The only way to verify is to compare the generated code to see if the changes are there after using EGLSDK.

Mark

Woww !  Then ok ! :-)