IBM Support

IJ18464: GRAPHICAL SCHEDULER - PERCENTAGE AND TASK COMPLETE METHODS NOT WORKING WITHOUT LOGGING OUT FIRST

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 the skdprojectid is greater than 1000, sometimes it is
    incorrectly formatted internally as 1043 or as 1,043, which is
    causing confusion with the internal models.
    Once you have a project with a skdprojectid that is greater
    than 1000, for example 1043, the SKDAppService.cachedModels
    will be corrupted.  You will have two MXGanttModel for the same
    project in the cache:  one with key *1043, the other with key
    *1,043.
    Sample cachedModels entries:
    {01361_MAXADMIN2=java.util.concurrent.FutureTask@99103949,
    01361_MAXADMIN1043=java.util.concurrent.FutureTask@2283121d,
    01361_MAXADMIN3=java.util.concurrent.FutureTask@e8362c5c,
    01361_MAXADMIN1,043=java.util.concurrent.FutureTask@59f2370f,
    01361_MAXADMIN1,042=java.util.concurrent.FutureTask@20f18c9f}
    This is due to some code using getString("skdprojectid") to
    cache (1,043) while some code uses the long value to string
    (1043) to
    the cache.  This double caching may cause some parts to use one
    model and some parts to use another model.  This will cause
    problematic behaviors.   Not populating the Task % Complete is
    one of them.
    STEPS TO REPRODUCE:
    Prerequisite:   Use database tools to set it so that the next
    value selected for SKDPROJECTID will be greater than 1000.
    1. Create 3 new work orders in the Work Order Tracking
    application.
    2. For the first one give it Duration 5 and Physical Percent
    Complete of 50.
    3. For the second one give it Duration 8 and Physical Percent
    Complete of 25.
    4. For the third one give it Duration 10 and Physical Percent
    Complete of 0
    5. Create a new Schedule in Graphical Scheduler.
    Calendar/Shift DAY/DAY.
    6. Create a Work Query to select the new work order.
    7. On the More Information tab pick PHYSICAL for the Percent
    Complete Calculation Method.
    8. Save and click on the Graphical View.
    9. Click on Calculate % Complete on More Actions.   You will
    see the summary bar go partially green as it rolls up the PC.
    10. On work order 3, right click and go to Work Order Tracking.
    11. Change its Physical Percent Complete to 5.   Save and
    Return.
    12. Click on Discard Changes and Refresh to see the 5 update on
    work order 3.
    13. Click on Calculate % Complete from  More Actions.
    RESULTS:
    The log makes references to the SKDPROJECTID with the
    "thousands" separator in it.  The Percent Complete would not
    summarize until the user logged off
    and then logged back in.   The thought being that somehow the
    internal structures broke into 2, one for 1003 and one for
    1,003 (or whatever value you have for SKDPROJECTID over 1000)
    EXPECTED RESULTS:
    The Percent Complete to summarize correctly and for the first
    time as well.
    REPORTED IN VERSION:
    Scheduler 7.6.1.0
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of the Graphical Scheduling application in Scheduler   *
    * 7.6.7.                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * PERCENTAGE AND TASK COMPLETE METHODS NOTWORKING WITHOUT      *
    * LOGGING OUT FIRST                                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • A code fix has been made.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ18464

  • Reported component name

    MAXIMO SCHEDULE

  • Reported component ID

    5724R46SE

  • Reported release

    767

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-08-20

  • Closed date

    2019-09-02

  • Last modified date

    2019-09-02

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

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

Modules/Macros

  • MAXIMO
    

Fix information

  • Fixed component name

    MAXIMO SCHEDULE

  • Fixed component ID

    5724R46SE

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"}, "Product":{"code":"SS9NUN","label":"Maximo Asset Management Scheduler"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"767","Edition":""}]

Document Information

Modified date:
02 September 2019