Technical Blog Post
From the Maximo Support Desk - Cron Task Parameter to use if your database is restarted!
A Global System Property has been available in the last several Maximo Feature Packs, named mxe.crontask.runonschedule.
This added functionality is a response to an APAR (IV79558 - PMWOGEN CRON TASK DOES NOT RESUME SCHEDULE IF DATABASE IS RESTARTED) that was entered for the scenario whereby a client had experienced a server malfunction and subsequently fell behind on scheduled asset maintenance due to the inability to run the crontask for PM Work Order Generation during the database downtime.
*If you are using Maximo Feature Packs 18.104.22.168 through 22.214.171.124, the current cumulative IFIX is necessary to utilize this System Property; it is included in 126.96.36.199 and in Feature Packs 188.8.131.52 and newer.
0 is the default behavior; if a crontask is restarted/reloaded, any missed run will start immediately, and then resume the existing frequency schedule.
1 is the updated functionality; if a crontask is restarted/reloaded, it will not execute immediately for any missed runs; the crontask will execute at the next scheduled frequency.
To view this property and make any updates to the behavior:
-Go To System Configuration | Platform Configuration | System Properties
-In the Global Properties section, click Filter
-In the Property Name field enter "mxe.crontask.runonschedule" and press Enter
-Expand the details for this row
Tom Richardson is an IBM Maximo Support Engineer and frequent contributor to the Asset Management Blog community. For a complete index of links to his articles, visit
Index of articles by Tom Richardson, Support Engineer