IBM Support

IJ28560: OPTIMIZATION IS CONVERTING MINUTES TO SECONDS CAUSING ROUNDING ISSUES

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

  • When optimizing a Work Order with a Job Plan of 40 minutes, the
    data file will show 2399 seconds, instead of 2400 seconds (40
    minutes). This will convert to 39,9833 minutes and that will
    optimize for 39 minutes instead of 40 minutes.
    
    STEPS TO
    REPRODUCE:
    1. Create an assignment with a Work Order and a Job
    Plan with 40 minutes of work
    2. Run optimization
    
    
    RESULT:
    
    Work is optimized for 39 minutes
    
    EXPEDTED RESULT:
    Work needs
    to be optimized for 40 minutes
    
    REPORTED IN VERSION:
    Tivoli's
    process automation engine 7.6.0.9
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * scheduler                                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When optimizing a Work Order with a Job Plan of 40 minutes,  *
    * the                                                          *
    * data file will show 2399 seconds, instead of 2400 seconds    *
    * (40                                                          *
    * minutes). This will convert to 39,9833 minutes and that will *
    * optimize for 39 minutes instead of 40 minutes.               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

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

    IJ28560

  • Reported component name

    MAXIMO SCHEDULE

  • Reported component ID

    5724R46SE

  • Reported release

    760

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-10-06

  • Closed date

    2020-11-11

  • Last modified date

    2020-11-11

  • 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":"760"}]

Document Information

Modified date:
12 November 2020