IJ38492: GRAPHICAL ASSIGNMENT QUERY SLOW AS IT INCLUDES CLOSED WORK ORDERS

APAR status

• Closed as program error.

Error description

• PROBLEM:
  Graphical Assignment OOB query is very slow to save due to WO
  history flag including closed work orders. The following query
  is very slow (from Scheduler class/OOB query).
  
  If we include wo.historyflag=0 then the results are faster.
  
  STEPS TO REPRODUCE:
  The following query:
  Have checked logs and found that inserting records into
  SKDRESOURCE object takes a long time. insert into skdresource
  (id, initialized, name, skdprojectid, objectid, objectname,
  refobjname, objrowstamp) (select id = ('CRAFT'+ '_' + c.craft +
  '_' + c.orgid), 0, name = c.description, 19201 , objectid =
  c.craftid , 'CRAFT', 'CRAFT', objrowstamp = c.rowstamp from
  assignment wl, craft c , workorder wo, skdactivity act where
  wl.craft is not null and wl.orgid = 'SAWATER' and wl.siteid =
  wo.siteid and wl.wonum = wo.wonum and wo.workorderid =
  act.objectid and act.objectname = 'WORKORDER' and
  act.skdprojectid = 19201 and wl.craft = c.craft and wl.orgid =
  c.orgid and c.craftid not in (select objectid from skdresource
  where skdprojectid = 19201 and objectname = 'CRAFT' and
  refobjname = 'CRAFT' ) group by c.craft, c.description,
  c.craftid, c.orgid, c.rowstamp);
  
  RESULTS:
  The query takes 2-3 minutes.
  
  EXPECTED RESULTS:
  If we include wo.historyflag=0 the results are much faster,
  customer would like to exclude closed work orders
  (historyflag=0) from the work list.
  
  BUSINESS IMPACT:
  Planning team users (18 users) unable to use the Graphical
  Assignment application and impacting their planning and
  Scheduling of workorder assignments.
  
  
  REPORTED IN VERSION:
  Tivoli's process automation engine 7.6.1.2-IFIX20210819
  IBM Maximo Asset Management Scheduler 7.6.8.0
  

Local fix

• Change the query to exclude closed work orders
  

Problem summary

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

Problem conclusion

• The fix for this APAR is contained in the following
  maintenancepackage:
  Release 7.6.1.3 of Base Services
  

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:

Fix information

• Fixed component name

  MAXIMO SCHEDULE

• Fixed component ID

  5724R46SE

Applicable component levels