JR35233: ISSUES SCHEDULING WITH TYPE "NEXT" WITH DAY LESS OR EQUAL TO CURRENT DAY. THIS MAKE DS TRIGGER THE JOB IMMEDIATELY.

Download Fix Pack 2 for InfoSphere Information Server Version 8.1

APAR status

• Closed as program error.

Error description

• My date on machine is 21st december 2009. I scheduled a job /
  jobsequence with Next
  
  With following cases:
  1.       DaY = 3, Job triggered immediately
  2.       Day = 19, Job triggered immediately
  3.       Day = 21, Job triggered immediately
  4.       Day = 28, Job scheduled to run next 28 (which is next
  month,
  January 2010)
  My conclusion is there is an issues scheduling with type "Next"
  with day
  less or equal to current day. This make DS trigger the job
  immediately.
  I?ve suggest the customer to use Every-schedule on the actual
  day
  (day=3) for now so they do not need to go to work on Sunday
  3.january
  2010 to trigger the job.
  

Local fix

• Identified this as a problem with the 'at' scheduling on Linux.
  The problem will only happen when scheduling during December.
  For dates that are past we request next month so for say next 3
  we ask for the job to run on January 3.
  
  Linux says this has past so runs the job immediately, Solaris
  however schedule for January next year.
  
  Please raise an APAR as this can be fixed with a simple bug fix.
  
  
  This fix is included in 8.0.1 fixpack 3
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Redhat DS Scheduling
  ****************************************************************
  PROBLEM DESCRIPTION:
  If a DS job is schedule to run using NEXT and a date which has
  passed then next month is assumed. In December this means
  JANUARY is specified. On Linux if the month has passed then the
  job is run immediately. On other UNIXes if the month has passed
  next year is assumed.
  ****************************************************************
  RECOMMENDATION:
  If the customer wants to resolve the issue then the patch will
  need to be applied.
  ****************************************************************
  

Problem conclusion

• Modified the schedule module to explicitly set a year if it is
  running on Linux.
  

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:

Modules/Macros

• SERVER
  

Fix information

• Fixed component name

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R751 PSY

     UP