APAR status
Closed as program error.
Error description
Escalation status change fails of certain workorders after upgrading to 7612. Only certain workorders fail. They have integration to PeopleSoft. See IFACE reference in stack trace STEPS TO REPRODUCE: 1. In Escalation Application that applies to WORKORDER to run every minute. 2. Use a simple where clause to gather a result set of workorders for test purpose. 3. Add escalation point that has a Changestatus action APPR for WORKORDER, Do not activate yet. 4. Create a new workorders that meet the result set to be changed 5. On Plans tab -add 1 task -add 1 Labor row for craft -add 1 labor row for a crew 6. On Assignments tab verify 2 assignments rows show 7. On Plans tab manually change status of task to APPR 8. In Escalation app, activate the escalation 9. After 1 minute the workorders to be approved error RESULTS: [6/7/21 14:43:39:148 EDT] 00000381 SystemOut O 07 Jun 2021 14:43:39:147 [ERROR] [CRN-5] [CID-CRON-625] Failed to execute action on escalation: {xxxxxxxxxx} reference point: {2,698} for object {WORKORDER} with id {1415570} psdi.util.MXApplicationException: system#invalidfetch at psdi.mbo.MboSet.getDiscardableMbo(MboSet.java:2163) at psdi.mbo.MboSet.getMbo(MboSet.java:2066) at psdi.plust.app.workorder.PlusTAssignmentSet.getMbo(PlusTAssignme ntSet.java:142) at psdi.iface.mos.MOSStAXStructure.createStructure(MOSStAXStructure .java:636) at psdi.iface.mos.MOSStAXStructure.createXML(MOSStAXStructure.java: 887) at psdi.iface.mos.StAXStructure.serializeMboAsSet(StAXStructure.jav a:221) at psdi.iface.mic.PublishChannel.publish(PublishChannel.java:134) at psdi.iface.mic.MicListener.structureChanged(MicListener.java:144 ) at psdi.iface.mos.OSMboListener.postSaveInternalEventAction(OSMboLi stener.java:218) at psdi.server.event.EventTopic$Subscription.postSaveInternalEventA ction(EventTopic.java:751) at psdi.server.event.EventTopic.postSaveInternalEventAction(EventTo pic.java:441) at psdi.server.event.EventTopicTree.postSaveInternalEventAction(Eve ntTopicTree.java:917) at psdi.mbo.Mbo.fireEvent(Mbo.java:6444) at psdi.mbo.StatefulMbo.fireEvent(StatefulMbo.java:799) at psdi.app.workorder.WO.fireEvent(WO.java:23582) at psdi.mbo.MboSet.fireEventsAfterDB(MboSet.java:8000) at psdi.txn.MXTransactionImpl.fireEventsAfterDB(MXTransactionImpl.j ava:456) at psdi.txn.MXTransactionImpl.saveTransaction(MXTransactionImpl.jav a:229) at psdi.txn.MXTransactionImpl.save(MXTransactionImpl.java:156) at psdi.mbo.MboSet.save(MboSet.java:7540) at psdi.mbo.MboSet.save(MboSet.java:7464) at psdi.app.workorder.WOSet.save(WOSet.java:1484) at psdi.app.escalation.engine.EscalationTask.executeAction(Escalati onTask.java:1483) at psdi.app.escalation.engine.EscalationTask.executeActions(Escalat ionTask.java:1397) at psdi.app.escalation.engine.EscalationTask.executeReferencePoint( EscalationTask.java:658) at psdi.app.escalation.engine.EscalationTask.processReferencePoint( EscalationTask.java:524) at psdi.app.escalation.engine.EscalationTask.performTask(Escalation Task.java:179) at psdi.app.escalation.engine.EscalationCronTask.cronAction(Escalat ionCronTask.java:54) at psdi.server.CronTaskManager.callCronMethod(CronTaskManager.java: 2519) at psdi.server.CronTaskManager.access$1100(CronTaskManager.java:105 ) at psdi.server.CronTaskManager$CronThread.run(CronTaskManager.java: 3429) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.ja va:522) at java.util.concurrent.FutureTask.run(FutureTask.java:277) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFuture Task.access$201(ScheduledThreadPoolExecutor.java:191) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFuture Task.run(ScheduledThreadPoolExecutor.java:304) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec utor.java:1160) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe cutor.java:635) at java.lang.Thread.run(Thread.java:811) EXPECTED RESULTS: STatus chnage to approve occurs PRODUCT VERSION: Tivoli's process automation engine 7.6.1.2 Build 20200715-0100 DB Build V7612-284
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: * * Users of Maximo * **************************************************************** * PROBLEM DESCRIPTION: * * Escalation status change fails of certain workorders * ****************************************************************
Problem conclusion
The fix for this APAR is contained in the following maintenance package: Release 7.6.1.3 of Base Services
Temporary fix
Comments
APAR Information
APAR number
IJ33245
Reported component name
MAXIMO ASST MGM
Reported component ID
5724R46AM
Reported release
761
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-06-15
Closed date
2021-07-03
Last modified date
2021-07-03
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 ASST MGM
Fixed component ID
5724R46AM
Applicable component levels
[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Document Information
Modified date:
04 July 2021