IBM Support

PM15930: EGL MODIFICATION ARE NOT EXPORTED TO JAR FILE AFTER FIRST JAVA G ENERATION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Environment:
    
     - OS (name, language, version or SP): Microsoft Windows XP SP2
     - Product name (Build ID or version/patch level): IBM Rational
    Business Developer v7.5.1.4
    
    Reproducible Y/N: Y
    
    Description of problem:
    
    
    When running externally an EGL program exported to a Jar file,
    recent modification are not visible.
    
    Steps to reproduce:
    
    1- Export an EGL project to a Jar file
    2- Modify a program within this project
    3- generate the Java code from the modified EGL file or from its
    package (not from the project)
    (opening the Java generated file shows the modification)
    4- export it again by overwriting the existing jar file
    5- run the program externally: modification is not there
    6- redo step 3, 4 and 5: modification is there
    
    Workaround:
    
    Different workarounds exists:
    1) either generate a second time from the file or package
    2) or generate from the wizard
    3) or generate from the project
    4) or test the modification in RBD (Run as? Java application)
    before exporting it to a jar file
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The auto build was not running after generation completed.
    This is causing missing and/or stale .class files.
    

Problem conclusion

  • The code was forcing an incremental build before generation
    to ensure that the .IR files were not stale. This caused the
    auto builder to not run after generation was complete.
    
    The forced incremental build has been removed. If a file is
    forced saved during the generate action, the code puts the
    UI thread to sleep for 1 second, so that the autobuild can
    run naturally.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM15930

  • Reported component name

    RATL BUS DEV

  • Reported component ID

    5724S5000

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-06-04

  • Closed date

    2011-05-06

  • Last modified date

    2011-05-06

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    RATL BUS DEV

  • Fixed component ID

    5724S5000

Applicable component levels

  • R750 PSN

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSMQ79","label":"Rational Business Developer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
06 May 2011