APAR status
Closed as program error.
Error description
STEPS: 1. Create a new PM Location AIR105, Job Plan INS11200, Work Type PM, Work Order Status WSCH. Make note of the PM number. e.g. FORECAS1 2. On the Frequency tab leave the Use Last Work Order's Start Date to Calculate Next Due Date checked. 3. Set Frequency to 1 MONTHS and pick an Estimated Next Due Date of the 1st of next month e.g. June 1st,2018 4. Change the status to ACTIVE. 5. Duplicate the PM to make a second one, set estimated next due date to the 1st of next month. e.g. FORECAS2 7. Duplicate the PM ten times. e.g. FORECAS3, FORECAS4, FORECAS5 8. Go to the List Tab , change the status to ACTIVE for all these PM records. Then go to the "Generate Forecast" action and generate forecast for 265 days 9. Go to Graphical Scheduling and create a new Schedule with these values: - Type - WORK - Left the defaults to Rolling Start Date 1 day, and Rolling Project checked - Calendar- 'DAY' for EAGLENA organization - Shift- Day - Preserve Existing Records on Refresh- unchecked - Work Query Data Source- PM - Query Name- PM - Where Condition: parent is null and status = 'active' and pmnum like 'FORECAST%' - go to the bottom of the screen and specify a Resource query. workgroup = 'SP-WSHP' and crewid = 'SP-EF' and status= 'active' 9. Save the record. 10. Go to the Graphical Scheduling application, create a new Schedule e.g. schedule 'PMTEST' Calendar DAY Shift DAY Type 'WORK' start date 4/14/18 12:00 AM end date 4/28/19 12:00 AM Enter a work Query: Data Source = PM enter a query name Enter a where condition: parent is null and status = 'ACTIVE' and pmnum like '764%' 11. Save the record 12. Review the log. Log shows a select count(*) rom PM query with the use of 'EXISTS' keyword Excerpt from the log: select count(*) from pm pm, pmancestor pman where pm.pmnum = pman.pmnum and pm.orgid = 'EAGLENA' and pm.orgid = pman.orgid and pm.siteid = pman.siteid and ( (pman.pmnum) in (select pmnum from pm where siteid = pman.siteid ) or (pman.pmnum) in (select pmnum from pm x where siteid = pman.siteid and parent in (select pmnum from pm where pmnum = x.parent and siteid = pman.siteid )) ) and ( (pman.ancestor) in ((select pmnum from pm where siteid = pman.siteid and (((exists ( select siteid from siteauth a,groupuser b where a.groupname=b.groupname and b.userid = 'MAXADMIN' and a.siteid = pm.siteid)) and (((status in ( 'ACTIVE' ))))) and ( (parent is null and status = 'ACTIVE' and pmnum like 'FORECAS%') ) )) ) and (pman.ancestor) not in ((select pmnum from pmancestor where hierarchylevels > 0 and ancestor in (select pmnum from pm where siteid = pman.siteid and (((exists ( select siteid from siteauth a,groupuser b where a.groupname=b.groupname and b.userid = 'MAXADMIN' and a.siteid = pm.siteid)) and (((status in ( 'ACTIVE' ))))) and ( (parent is null and status = 'ACTIVE' and pmnum like 'FORECAS%') ) )) and siteid = pman.siteid ) ) and (pman.pmnum) not in ((select pmnum from pmancestor where siteid = pman.siteid and ancestor = pman.pmnum and hierarchylevels > 0 and pmnum in (select pmnum from pm where siteid = pman.siteid and (((exists ( select siteid from siteauth a,groupuser b where a.groupname=b.groupname and b.userid = 'MAXADMIN' and a.siteid = pm.siteid)) and (((status in ( 'ACTIVE' ))))) and ( (parent is null and status = 'ACTIVE' and pmnum like 'FORECAS%') ) ))) ) ) and (pman.pmnum) in (select pmnum from pm where pmnum = pman.pmnum and siteid = pman.siteid and ( ( (status in ( 'ACTIVE' )) ) ) or exists (select * from pm where parent = pman.pmnum and siteid = pman.siteid and (status in ( 'ACTIVE' )) ) ) and (pm.pmuid not in (select objectid from skdactivity where skdprojectid = 127 and objectname = 'PM')) and (exists (select pmnum from pmforecast where pmforecast.siteid = pm.siteid and pmnum = (select ancestor from pmancestor where pmnum = pm.pmnum and siteid = pmforecast.siteid and hierarchylevels = (select max(hierarchylevels) from pmancestor where pmnum = pm.pmnum and siteid = pm.siteid)))) Also, EXISTS keyword is in the insert into skdactivity query as well RESULTS: It takes 15-30 min to save a schedule EXPECTED RESULTS: It should only take a few seconds to save a schedule PRODUCT VERSION: Maximo Asset Management 7.6.0.8 IFIX 8 Scheduler 7.6.5.0 SQL SERVER 12 SECURITY IMPACT (Y/N): N
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: * * maximo scheduler users * **************************************************************** * PROBLEM DESCRIPTION: * * TAKES A LONG TIME TO SAVE A SCHEDULE IN GRAPHICAL SCHEDULING * **************************************************************** * RECOMMENDATION: * * Apply fixpack Release 7.6.1.0 of Base Services (Scheduler * * 7671)or request an interim fix * ****************************************************************
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.0 of Base Services(Scheduler 7671)
Temporary fix
Comments
APAR Information
APAR number
IJ06569
Reported component name
MAXIMO SCHEDULE
Reported component ID
5724R46SE
Reported release
765
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-05-22
Closed date
2018-06-01
Last modified date
2018-06-01
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
R765 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9NUN","label":"Maximo Asset Management Scheduler"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"765","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
01 June 2018