IJ22159: CRONTASK INSTANCE IS FIRED RIGHT AFTER BEING ACTIVATED.

APAR status

• Closed as program error.

Error description

• Even with setting 1 for mxe.crontask.runonschedule,
  a crontask instance is fired right after being activated.
  
  STEPS TO REPRODUCE:
  Although this is originally reported in MAM 7.6.0.9,
  it can be reproduced even in MAM 7.6.1.1 with the following
  scenario.
  
  1) From Cron Task Setup, open JMSQSEQCONSUMER.
  
  2) Confirm "LASTRUN" value for SEQQIN instance is null.
  
  3) For SEQQIN instance, set the following value for "Schedule"
  field so that it will run at 19:00 every day.
  
  1d,0,00,19,*,*,*,*,*,*
  
  Then check both "Active?" and "Keep History?" check boxes and
  save the changes.
  
  4) After selecting "Reload Request" from More Actions,
  confirm that SEQQIN instance is fired at 18:37 unexpectedly.
  This is the problem.
  
  5) 23 minutes later, confirm SEQQIN instance is fired
  again at 19:00 as scheduled.
  
  Although JMSQSEQCONSUMER is used in this scenario
  as an example, this can happen with any crontasks.
  
  EXPECTED RESULT:
  The crontask instance should not be fired at 18:37
  because it is scheduled to be fired at 19:00.
  
  PRODUCT VERSION:
  Maximo Asset Management 7.6.0.9
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * MAXIMO                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * CRONTASK INSTANCE IS FIRED RIGHT AFTER BEING ACTIVATED       *
  ****************************************************************
  

Problem conclusion

• This was fixed by IJ01148.The fix for this APAR is contained in
  the following maintenance package:The fix for this APAR is
  contained in the following maintenance package: | release\fix
  pack for Release 7.6.1.3 Product
  

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

  SYSTEM CONFIG

• Fixed component ID

  5724R46S1

Applicable component levels