IV93599: WHEN ENLEGACYSTARTOFDAYEVALUATION SET TO YES, ABSOLUTE AND PREVIOUS FOLLOWS DEPENDENCIES NOT WORKING

APAR status

• Closed as program error.

Error description

• I have set up a variety of job streams to test the
  ability to have a job come into today's plan and
  depend on a job from the previous day's plan. Only
  the dependencies defined with a relative interval
  are following the previous day's job. Ones defined
  with an absolute interval of the previous day or
  with PREVIOUS are following the jobs in the current
  plan.
  .
  I would like to know why the absolute interval and
  PREVIOUS are not working to hook to the previous
  day's jobs that have carried forward. I would prefer
  to use PREVIOUS if it would actually hook to the most
  recent previous scheduled time predecessor, as that
  is more flexible.
  Absolute interval findings:
  I have found that setting the predecessor to have a
  start time afterthe first minute of the plan makes
  the previous day dependency attach to it properly
  with the absolute interval of FROM start of day¿
  - 1 DAYS TO end of day¿ - 1 DAYS. However with the
  same absolute interval and the predecessor scheduled
  at the start minute of the day the successor ties to
  the job stream of the current day which is not even
  within that interval. This seems like a bug to me.
  .
  PREVIOUS keyword findings:
  When the keyword PREVIOUS is added to a dependency
  to a different job stream, it ties to the other job
  stream that is most recent up to and INCLUDING the
  same time as the successor. This seems like bug, as
  something that is the same time as the successor is
  not previous to it. Perhaps we need to find a
  different name for this keyword that is semantically
  correct? ANTEPOST perhaps, for "before the minute that
  is after it"? or maybe we can get PREVIOUS to actually
  act as previous?
  .
  Relative Interval findings:
  RELATIVE FROM -2400 TO -0001 works consistently to
  tie to job streams from the previous day.
  .
  L3 has been able to reproduce the issue using the
  optman parameter enLegacyStartOfDayEvaluation set to
  YES. If it is set to NO, TWS is working fine, and I
  think enLegacyStartOfDayEvaluation is YES in customer
  environment.
  

Local fix

• Set enLegacyStartOfDayEvaluation set to NO
  

Problem summary

• The setting of enLegacyStartOfDayEvaluation to yes causes some
  erroneus calculation of dates and time evaluating dates and
  times
  

Problem conclusion

• The apar will be fixed in TWS 9.1 fp3, TWS 9.2 fp3, TWS 9.3 fp4,
  TWS 9.4 fp2
  

Temporary fix

• see local 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

  TIV WKLD SCHDL

• Fixed component ID

  5698WKB85

Applicable component levels

• R8A5 PSY

     UP