CA WAAE Scheduler and Application Server hold timezone definitions in memory (cache) after they are read for the first time after startup. It does this by design for performance reasons as that prevents the Scheduler and Application Server from performing a database lookup every time it has to resolve a timezone.
The following steps are taken by the Scheduler to arrive at the appropriate value for the timezone specification in the job definition:
- Check for the time zone in locally maintained cache (whenever the Scheduler and/or Application Server restarts, the cache gets cleared off).
- If the time zone is not found in the cache then check operating system time zones list for a match (If found add this new time zone to the cache).
If the time zone is not found in the operating system zoneinfo database then check in the 'ujo_timezones' table in the AutoSys database. (If found add this new time zone to the cache.) If the time zone is not found in the 'ujo_timezones' table then check for a valid 'TZ' environmental variable string against posix standards. (If valid add this new time zone to the cache.) If unable find it in any of the aforementioned locations, indicate an error condition.
- If there's no time zone library on this platform, there's nothing to search; skip to step 3.
- Only in UNIX/Linux it will search the System's zoneinfo database (also known as tz database) for a matching time zone specification.