IJ01148: ESCALATION RUNS TWICE ON OCCASION

APAR status

• Closed as program error.

Error description

• STEPS TO REPRODUCE: - Should be set up on cluster
  1. Set up escalation to run  daily
  2. Wait for it to run twice.(Will need to check crontaskhistory
  table). The problem is random. But happens to all crontasks.
  
  If you set the system property mxe.crontask.runonschedule = 1,
  then the problem does not occur.
  
  
  
  Can see several days where it ran twice. Usually milliseconds
  before
  the 7am time (Crontaskhistory)
  
  CURRENT ERRONEOUS RESULT:
  escalation run several milliseconds before actual scheduled
  time, then
  runs again on scheduled time
  
  EXPECTED RESULT:
  run only only once.
  

Local fix

• mxe.crontask.runonschedule = 1, but this is not ideal as you
  may need to run when restarting a system etc..
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users                                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * With mxe.crontask.runonschedule set to 0, on a clustered     *
  * environment, crontasks can unpredictably run twice per day.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is included in the following package:
                          | Release 7.6.0.10 of Base Services
  

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

  ADMINISTRATION

• Fixed component ID

  5724R46A1

Applicable component levels

• R760 PSY

     UP