PM64085: SCHEDULER 'NEXTFIRETIME' IS NOT WORKING AS EXPECTED.

APAR status

• Closed as suggestion for future release.

Error description

• Context:  If the Application's scheduler is configured to run
  from the 1st to the 10th day of each month, from 7am until 7pm
  on the days when it is supposed to run.
  
  Issue: When the JVM is restarted after the 10th day of the
  month, WebSphere Application Server regenerates the
  nextfiretime field, setting the correct date (the 1st of the
  following month) but an incorrect time. The time it will set
  will be within half an hour of when the reboot occurred.
  What should happen instead is if JVM is restarted between 11th
  and 31st day of the month, the time component of the
  nextfiretime should always be set to 7am.
  
  Application Server generates "nextfiretime" as a value in the
  application's task table. When we run the following SQL to get
  this row:
  Select * from (application's task table row) where
  name='***********';
  
  Implications: The scheduled job is not kicked off when expected.
  Manual database update is needed if the starting time is too
  far from where it should be.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• APAR PM64085 is being closed SUG because resolving this
  problem in the service stream could introduce a behavior change
  which ccould affect existing applications. We will consider
  this for a future release.
  

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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels