IV92891: WHEN USING THE OPTIMIZER WITH SCHEDULER ALL JOBS ERROR OUT WITH "CANNOT EXTRACT EXPRESSION"

APAR status

• Closed as program error.

Error description

• With Scheduler 7.5.2 in Maximo 7.5.0.10 whenever they try to
  use the Optimizer in Scheduler the job always fails with the
  same errors
  [16/12/16 13:35:38:348 GMT] 00000005               I [PROC-6]
  ilog.
  oplodm.util.IloDefaultReportHandler outputError
  syserr: -
  ERROR -OPL cannot extract expression:
  IloNumVarI#00000000105D8F78 <=
  IloNumVarI#00000000105D8F40.
  [16/12/16 13:35:38:348 GMT] 00000005               I [PROC-6]
  ilog.
  oplodm.util.IloDefaultReportHandler outputError
  syserr: -
  ERROR -OPL cannot extract model: IloAlgorithm cannot extract
  extractable.
  [16/12/16 13:35:38:364 GMT] 00000005 optimcore     I [PROC-6]
  ilog.odm.
  newService.IloEnginePilot solveScenario          CIVOO1020I:
  The engine
  run has failed.
  [16/12/16 13:35:38:411 GMT] 00000005 processingsvc I [PROC-6]
  ilog.odm.
  processingsvc.impl.IloAbstractScenarioTaskExecutionController
  execute          CIVOO0032I: The task Scenario=TEST
  9-CP2-CAPPLAN-
  1481895319677 task=Solve did not complete successfully.
  
  Upon investigation it was found that a function used by the 3.8
  ODME Optimizer, used in 7.6 Maximo, found its way into the
  Scheduler 7.5.2 models which run ODME 3.7.
  
  Development has already found and removed the new model element
  from 3.8 and provided new files to test with.
  
  To reproduce:
  
  1. Install Scheduler with 7.5.0.10.
  2. Install the ODME server.
  3. Enter the proper data in the fields for Configure
  Optimization Server in Graphical Assignment (GA) so that you
  can successfully deploy the models.
  4. Create a Work List in GA.
  5. Create a Scenario
  6. Run the Optimizer
  
  And the errors will be seen.
  

Local fix

• (none)
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo Users on Scheduler 7.5.2 using ODME 3.7               *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * A data structure that exists in ODME 3.8+ (but not in ODME   *
  * 3.7 or befor) found its way into Scheduler 7.5.2 models,     *
  * causing the GS model to fail every time                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixpack Release 7.6.0.5 of TPAE or request an interim  *
  * fix                                                          *
  ****************************************************************
  

Problem conclusion

• Fix has been made to remove this element from GS model; The fix
  for this APAR is contained in the following maintenance package:
  
  TPAE - IFIX 7.6.0.5
  

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

• R752 PSY

     UP

• R751 PSY

     UP