IJ09106: GRAPHICAL ASSIGNMENT RELOADING DATA AFTER EACH CHANGE CAUSES PERFORMANCE PROBLEM

APAR status

• Closed as program error.

Error description

• In Graphical Assignment (GA) when the SKDPROJECTID for a Work
  List is over 1000 the Dispatch tab adds a thousands separator
  (1065 is shown as 1,065 in the log) which causes performance
  delays as it causes the previously cached model to be reloaded
  every time.
  The method used to retrieve the SKDPROJECTID is returning a
  localized string.
  In the logs, the SKDPROJECTID is returned as "1,107" containing
  a thousand separator.
  However the value used as a key to store the Schedule/Project
  data model in memory does not contain a thousand separator.
  The issue relies in the fact that they are both stored as
  different string objects.
  Steps to Reproduce:
             NOTE: You will need Database access
  1. Enter data needed for the Dispatch tab in GA for several WO:
   - Enable Maps on the Map Manager
   - Add Service Addresss and associate them with Locations (test
  that you can see the Service Address location on the Map tab).
   - Add WO with durations and Planned Labor.
   - Assign each of the WO a Service Address and make sure you
  can see its location on the Map tab in WOTrack.
  2. Use one of these to change the next value for SKDPROJECTID
  directly in the database:
   - Oracle:  ALTER SEQUENCE SKDPROJECTID RESTART WITH 1000;
   - SQL Server: update maxsequence set maxvalue = 1000
  where name =  'SKDPROJECTID'
  3. Create a new Work List in GA.   Use a valid Calendar with
  shifts applied.   Set the Start Date to today and the End Date
  to a week from today.
  4. For a Work Query use one to select the WO created above.
  5. Save.    Now go to the database and see what the value of
  SKDPROJECTID is for the new Work List.   It should be 1000 or
  more.
  6. Click on the Assignment View tab.
  7. Assign several of the Planned Labor requirements.
  8. Save.
  9. Click on Apply Street Level Routes.   You will see a message
  saying how many were created.   If it is zero your data needs
  fixing.
  10. Click on the Dispatch tab.
  ERRONEOUS RESULT:
  Performance will be bad.  Each time you return to the Dispatch
  tab it will take a long time.
  EXPECTED RESULT:
  For performance to be good.
  Enable SCHEDULER DEBUG log level logging, and you should see
  something like this in the log:
  Dispatch: loadProject(SKDPROJECTID), using cached model
  This tells you that the already cached model is being used
  which is why performance is better.
  VERSION: IBM Maximo Asset Management 7.6.0.8
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users of the Graphical Assignment application in Scheduler   *
  * 7.6.7.                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * GRAPHICAL ASSIGNMENT RELOADING DATA AFTER EACH CHANGE CAUSES *
  * PERFORMANCE PROBLEM                                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• A code fix has been delivered.
  

Temporary fix

Comments

APAR Information

• 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

• R767 PSY

     UP