EGL Development User Group

EGL Development User Group

EGL Development User Group

The EGL Development User Group is dedicated to sharing news, knowledge, and insights regarding the EGL language and Business Developer product. Consisting of IBMers, HCL, and users, this community collaborates to advance the EGL ecosystem.

 View Only
  • 1.  EGLSDK

    Posted Fri March 20, 2015 11:49 AM

    Hi,

    I tried to execute EGLSDK to generation batch with egl command file:

    <EGLCOMMANDS
    eglpath="C:\Workspace\VisualAgeMig_Baseline_3.2.1\SourceProject\EGLSource;C:\Workspace\VisualAgeMig_Baseline_3.2.1\CommonProject;C:\Workspace\BuildProject\EGLSource;C:\Workspace\VisualAgeMig_Baseline_3.2.1\BuildProject;">
    <generate
    file="SourceProject\EGLSource\MYPROG.egl">
    <buildDescriptor name="CobolToCics"
    file="BuildProject\EGLSource\ToCobolGen.eglbld">
    </buildDescriptor>
    </generate>

    after execute,

    C:\Appl\IBM\Rational\SDP\jdk\jre\bin>java EGLSDK "C:\User\EGLGenout\MYPROG.xml"

    Returned the message error:

    IWN.VAL.3992.e - 0/0 - Error occurred while retrieving contents of file 
    C:\Appl\IBM\Rational\SDP\jdk\jre\bin\BuildProject\EGLSource\ToCobolGen.eglbld. 
    Error text = C:\Appl\IBM\Rational\SDP\jdk\jre\bin\BuildProject\EGLSource\ToCobolGen.eglbld 
    (The system cannot find the path specified.)

    Question:

    Why the EGLSDK put the current path "C:\Appl\IBM\Rational\SDP\jdk\jre\bin" into the ..\ToCobolGen.eglbld file path ? and not eglpath ?

    the right is C:\Workspace\VisualAgeMig_Baseline_3.2.1\BuildProject\EGLSource\ToCobolGen.eglbld

    Thanks !

    Hsieh

    Hsieh


  • 2.  Re: EGLSDK

    Posted Fri March 20, 2015 01:31 PM

    After consulting the online guide I found the following note:

    Note: The eglpath option is not used to find the build descriptor, so the bdFile parameter must specify the correct file.

    I do not understand is why developers have left it out ?

    I'm using Generate with wizard to generate the eglcomand.xml file and I need to edit the xml file to enter the path of DBFile ?

    is very incoherent !  

    I need to automate the process for use with RTC Build Server and with this hole, the developer must edit the xml file.

    Is there any other alternative ?

    Hsieh

    Hsieh


  • 3.  Re: EGLSDK

    Posted Fri March 20, 2015 01:56 PM

    Hsieh,

    I am not sure why the physical path was not added to the eglcommand file.   It could be that the build file could reside anywhere and not necessarily in the build path, so they did not fill it in.   It would have to be investigated.

    A couple of questions/comments:

    a.) I would strongly recommend you looking at the use of ant scripts/ant tasks if you are talking about automating a build/generate process.  This is the future way.  See the egl.generate ant task for more information (as well as other available egl ant tasks).   It uses a headless workspace (workspace with no UI).   You can use Ant to load the workspace, "build it" and then invoke a generate, along with many other items.  

    b.) Assuming you are still going to use EGLSDK, then it would seem from your description that there is still a manual process to create the eglcommand.xml file.    Is this being done for each program?  If so, just creating them even if they did not need editing sounds pretty manual vs automated.  So assuming the values build descriptors and files do not change very often, why don't you just use a common xml file as a template and just create what you need by changing the program/package/project names.

    markevans


  • 4.  Re: EGLSDK

    Posted Fri March 20, 2015 02:18 PM

    Hi Mark,

    It's my first step to integrate EGL with RTC Build Server and I'm not familiar with ant script, i need study.

    My idea was to create eglcommand.xml generation and deliver to RTC Build Server to generation. I'm still in the initial solution and trying to cook it.  I still do not know if it would be correct, I am working with the IBM team responsible for the RTC and I with EGL.

    Hsieh

    Hsieh


  • 5.  Re: EGLSDK

    Posted Fri March 20, 2015 03:19 PM

    Again, I would look at the Ant Tasks.... usage of ant scripts is a pretty natural process within RTC.

    Also, there are blog entries that might be of interest.   One was using EGLCMD within an ant script, but switching to the egl ant tasks would be easily done.

    https://www.ibm.com/developerworks/community/blogs/3e2b35ae-d3b1-4008-adee-2b31d4be5c92/entry/egl_headless_build_integrated_with_rtc?lang=en

    https://www.ibm.com/developerworks/community/blogs/3e2b35ae-d3b1-4008-adee-2b31d4be5c92/entry/headless_hint_build_and_deploy_an_multiple_project_application?lang=en

    Mark

    markevans