IJ45443: WOGENWHERECLAUSE CAUSING PMWOGEN CRONTASK NOT TO GENERATE WORK ORDERS

APAR status

• Closed as program error.

Error description

• PMWOGEN does not generate work orders if notation ":user=" is
  used on WOGENWHERECLAUSE
  
  
  STEPS TO REPRODUCE:
  
  
  1.	Go to Security > Users and create a new user PMCRON
  2.	Make the default insert site Nashua and add it to the
  MAXADMIN security group
  3.	Go to Administration > Organizations and select EAGLENA
  4.	Under More Actions, click on PM Options
  5.	Select the Nashua site
  
  6.	WO Generation Where Clause: :user='PMCRON' and status =
  'ACTIVE'
  7.	Check Automatic PM WO generation
  8.	Go to System Configuration > Platform Configuration > Cron
  Task Setup
  9.	Open the PmWoGenCronTask
  10. 	Create a new instance:
  	- Instance Name: TEST
  	- Schedule: 1m
  	- Run as User: PMCRON
  	- Active: checked
  11.	Save it
  12.	Under More Actions, click on Reload Request
  13. 	Go to Preventive Maintenance application and create a new
  record for the Nashua site
  14. 	Fill all the required fields and make sure the PM is due.
  
  RESULTS:
  
  The Work Order does not get generated for the PM.
  
  If you remove ":user='PMCRON'" from the WO Generation Where
  Clause, then the work order is generated correctly.
  
  EXPECTED RESULTS:
  
  The Work Order should be automatically generated by the
  crontask.
  
  
  REPORTED IN VERSION:
  
  
  Tivoli's process automation engine 7.6.1.2 IFIX20210323-1206
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * MAXIMO                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * WOGENWHERECLAUSE CAUSING PMWOGEN CRONTASK NOT TO GENERATE    *
  * WORK ORDERS                                                  *
  ****************************************************************
  

Problem conclusion

• This problem does not exist in 7.6.1.3 GA, Manage 8.4 or Manage
  8.6 and later. It will be fixed in an IFIX for 7.6.1.2 and a
  Patch for 8.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:

Fix information

• Fixed component name

  MAXIMO ASST MGM

• Fixed component ID

  5724R46AM

Applicable component levels