IBM Support

IJ28660: ENVIRONMENT WITHOUT "COMMONS-LANG-2.5.JAR" FILE DOESN'T SHOW THE ISSUE FROM APAR IJ12937

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Customer can see the error from APAR IJ12937 on the Development
    environment but not on the QA environment. Copying the file
    commons-lang-2.5.jar to the Dev environment solved the issue.
    In the QA environment the jar file is not present but the issue
    cannot be seen. Both environments are identical and kept in
    sync.
    This APAR needs to investigated why the issue is not
    present on a environment where the above jar file is not
    present
    
    
    
    STEPS TO REPRODUCE:
    1. Apply the steps from APAR
    IJ12937 in Dev environment
    2. Apply the steps from APAR IJ12937
    in QA environment
    3. Add commons-lang-2.5.jar in the Dev
    environment in the following path
    MAXIMO-HOME/application/maximo/lib
    4. Check if
    commons-lang-2.5.jar is present on QA
    
    
    RESULT:
    1. Both
    environments have the APAR IJ12937 issue solved
    2. QA
    environment doesn't have the commons-lang-2.5.jar file present
    in the following path MAXIMO-HOME/application/maximo/lib
    
    
    
    REPORTED IN VERSION:
    Tivoli's process automation engine
    7.6.1.1
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * maximo scheduler                                             *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Customer can see the error from APAR IJ12937 on the          *
    * Development                                                  *
    * environment but not on the QA environment.                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Apply fixpack  Release 7.6.1.3 of Base Services (Scheduler
    768x)or request an interim fix
    	- Problem Conclusion:   Fix has been made to fix....The fix for
    this APAR is contained in the following maintenance package:
    		 | release\fix pack\interim fix for  Release 7.6.1.3 of Base
    Services(Scheduler 768x)
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ28660

  • Reported component name

    MAXIMO SCHEDULE

  • Reported component ID

    5724R46SE

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-10-12

  • Closed date

    2020-10-15

  • Last modified date

    2020-10-15

  • 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

    MAXIMO SCHEDULE

  • Fixed component ID

    5724R46SE

Applicable component levels

[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9NUN","label":"Maximo Asset Management Scheduler"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761"}]

Document Information

Modified date:
16 October 2020