IBM Support

IJ44947: GRAPHICAL WORK WEEK PERFORMANCE DEGRADING WHEN QUERIES ARE GENERATED WHICH GATHER ASSIGNMENTS FROM WMASSIGNMENT VIEW

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

  • Performance issues experienced in Graphical Work Week
    The issue has its root with the queries generated to gather the
    assignments from the WMASSIGNMENT view
    
    Steps to observe slow Resources query behavior
    1. Log in to Maximo
    2. Go To Planning and Scheduling > Graphical Work Week
    3. Select a Project to view:
       a. Project for this scenario has the following
            i. Rolling = 1
           ii. Duration in Days = 14
          iii. Rolling Offset in Days = 0
          iv. Work Query = (siteid = 'WIS' AND status != 'A-COMP'
    and (worktype = 'PM' or worktype = 'PME'))
           v. Restrict Resource Availability query is not defined.
    4. Click on Graphical View
         a. Page loads in 32 seconds with 19 Assignments.
            i. Work list in that 32 seconds
           ii. Resources takes 7 minutes and 27 seconds (total)
    (almost 7 minutes longer than Activities/Assignments)
          iii. For reference, the same worklist query and settings
    in Graphical Scheduling takes 1 minute 29 seconds to load.
          iv. This data was for first time load.
    
    Second time load is as follows
    1. Graphical Work Week Graphical View Page Load: 3 seconds
    2. Graphical Work Week Graphical View Resources Load: 6 minutes
    18 seconds
       b. Adding a Labor Query to the Restrict Labor Availability
    still requires over a minute to load when narrowing Labor
    records to 29 records which are further restricted by Scheduler
    to 6 records.
    
    Reported Version
    
    Tivoli's process automation engine 7.6.1.2
    
    IBM Maximo Asset Management Scheduler 7.6.8.0
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Scheduler users                                              *
    ****************************************************************
    

Problem conclusion

  • A fix for this APAR will be included in a future release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ44947

  • Reported component name

    MAXIMO SCHEDULE

  • Reported component ID

    5724R46SE

  • Reported release

    768

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-01-12

  • Closed date

    2023-01-31

  • Last modified date

    2023-01-31

  • 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

[{"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":"768","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
31 January 2023