Handle Autosys with DST Changes


 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users Handle Autosys with DST Changes
# 1  
Old 09-10-2010
Handle Autosys with DST Changes

Hi,

I have one confusion regarding DST chnages which are going to happen after October. Smilie Smilie

I have few jobs on Autosys which run as per Japan Time. they shoudl not be affected by switiching off of DST time.
Our autosys instance server is based on UK which is running on BST these days. When it switches tom GMT after DST switch-off, logically all jobs will be delayed by one hour. (If you see from India/Japan perspective )

For jobs which are dependent on UK business will run fine because eventually Business hours will also have the same shift.

One solution I can figure out is use the attribute timezone in autosys jobs and change the start mins accordingly should work.

For eg. If now job runs at 00:30, now onwards the job will have attributes as timezone:Tokyo-z and start_times: 08:30 Smilie

Will that work fine without issue ??

I just want to confirm if anyone has faced this kind of similar issue like running job specific to one region on instance which is based in different timezone/region.

Thanks
Sourabh
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Linux

How does Linux handle DST ( daylight saving time)?

Hello Can sombody please tell me how linux handles DST ( daylight saving time) ? Does the time change instantly , ex: if is is 3'o clock does linux instantly swich to 2'o clock ? plese give more info about this toppic (2 Replies)
Discussion started by: martonlorand
2 Replies

2. UNIX for Dummies Questions & Answers

Difference between handle to the thread HANDLE and thread identifier pthread_t

This question might be silly but its confusing me a bit: What is the difference between handle to the thread HANDLE and thread identifier pthread_t? ---------- Post updated at 01:52 PM ---------- Previous update was at 01:48 PM ---------- Sorry I saw details and HANDLE is in windows and... (0 Replies)
Discussion started by: rupeshkp728
0 Replies

3. UNIX for Dummies Questions & Answers

Autosys: How to change a machine name in Autosys JIL.

All the autosys jobs are on server-1 and server-1 has been crashed due to some reason, Now I have to run 5 autosys jobs on server-2 (failover server) which are on server 1. How to do with Autosys command (which command needs to fired on JIL) (0 Replies)
Discussion started by: tp2115
0 Replies

4. Shell Programming and Scripting

Determine if given date is in DST

Is there a way to figure out if given date is in DST or in EST? So imagine a shell script is_date_dst.sh sh is_date_dst.sh 2009-03-02 would return 0 and sh is_date_dst.sh 2009-03-22 would return 1 This script should not assume the timezone of the machine it runs on, but only the date passed... (7 Replies)
Discussion started by: asriva
7 Replies

5. UNIX for Advanced & Expert Users

Documentation and books on Autosys Job Control Tool from Autosys

My project uses Autosys. I am new to this product and I don't know where to start from. Q1. Please provide me the link where I can get Autosys documentation Q2. Please refer a good book on Autosys. (Beginner/Intermediate Level) (0 Replies)
Discussion started by: gram77
0 Replies

6. Solaris

DST Patch

How to update DST patch. Whatat are the necessary steps that have to be taken on the servers to update this patch?. (1 Reply)
Discussion started by: sandeepkv
1 Replies

7. AIX

AIX and DST

Just a quick last minute thing here. AIX 5.1. I ran the perl script referenced in the tutorials and found the AIX box is triggering DST on the 14th instead of the 11th. The 5.2 boxes come back with the right answers. The DST patches have been applied (or I'd have Apr 1st instead of the 14th). ... (0 Replies)
Discussion started by: BOFH
0 Replies

8. SCO

Dst - V 3.6.3

Hello, Anyone know where I can find the DST updates for SCO Xdesktop 3.6.3? Thanks (0 Replies)
Discussion started by: ddzc
0 Replies

9. SCO

DST script for 5.0.0

I checked SCO's site for DST fix for SCO 5.0.0 and there iis not one available. Can I run a script in the cron to read in and change the time? TiA (2 Replies)
Discussion started by: tbgeek
2 Replies

10. Solaris

DST on Solaris 2.6/7

I have several servers that are outside the country and are running Solaris 6 mainly with a few Solaris 7 boxes here and there. Because of that, we need to schedule time to change the time on March 11th and again in April, October and November. At least until the customer decides it's time to... (3 Replies)
Discussion started by: BOFH
3 Replies
Login or Register to Ask a Question
DateTime::TimeZone::SystemV(3pm)			User Contributed Perl Documentation			  DateTime::TimeZone::SystemV(3pm)

NAME
DateTime::TimeZone::SystemV - System V and POSIX timezone strings SYNOPSIS
use DateTime::TimeZone::SystemV; $tz = DateTime::TimeZone::SystemV->new("EST5EDT"); if($tz->is_floating) { ... if($tz->is_utc) { ... if($tz->is_olson) { ... $category = $tz->category; $tz_string = $tz->name; if($tz->has_dst_changes) { ... if($tz->is_dst_for_datetime($dt)) { ... $offset = $tz->offset_for_datetime($dt); $abbrev = $tz->short_name_for_datetime($dt); $offset = $tz->offset_for_local_datetime($dt); DESCRIPTION
An instance of this class represents a timezone that was specified by means of a System V timezone string or the POSIX extended form of the same syntax. These can express a plain offset from Universal Time, or a system of two offsets (standard and daylight saving time) switching on a yearly cycle according to certain types of rule. This class implements the DateTime::TimeZone interface, so that its instances can be used with DateTime objects. SYSTEM V TIMEZONE SYNTAX
In the POSIX extended form of the System V timezone syntax, a timezone may be specified that has a fixed offset by the syntax "aaaooo", or a timezone with DST by the syntax "aaaoooaaa[ooo],rrr,rrr". "aaa" gives an abbreviation by which an offset is known, "ooo" specifies the offset, and "rrr" is a rule for when DST starts or ends. For backward compatibility, the rules part may also be omitted from a DST-using timezone, in which case some built-in default rules are used; don't rely on those rules being useful. An abbreviation must be a string of three or more characters from ASCII alphanumerics, "+", and "-". If it contains only ASCII alphabetic characters then the abbreviation specification "aaa" may be simply the abbreviation. Otherwise "aaa" must consist of the abbreviation wrapped in angle brackets ("<...>"). The angle bracket form is always allowed. An offset (from Universal Time), "ooo", is given in hours, or hours and minutes, or hours and minutes and seconds, with an optional preceding sign. The maximum magnitude permitted is 24:59:59. The sign in the specification is the opposite of the sign of the actual offset. If no sign is given then the default is "+", meaning a timezone that is behind UT. If no DST offset is specified, it defaults to one hour ahead of the standard offset. A DST-using timezone has one change to DST and one change to standard time in each Gregorian year. The changes may be in either order within the year. If the changes are in different orders from year to year then the behaviour is undefined; don't rely on it remaining the same in future versions. A change rule "rrr" takes the form "ddd[/ttt]", where "ddd" is the rule giving the day on which the change takes place and "ttt" is the time of day at which the change takes place. The time may be given in hours, or hours and minutes, or hours and minutes and seconds, and if not stated then it defaults to 02:00:00. The time for the change to DST is interpreted according to the standard offset, and the time for the change to standard time is interpreted according to the DST offset. (Thus normally the change time is interpreted according to the offset that prevailed immediately before the change.) A day rule "ddd" may take three forms. Firstly, "Jnnn" means the month-day date that is the nnnth day of a non-leap year. Thus "J59" means the February 28 and "J60" means March 1 (even in a leap year). February 29 cannot be specified this way. Secondly, if "ddd" is just a decimal number, it means the (1+ddd)th day of the year. February 29 counts in this case, and it is not possible to specify December 31 of a leap year. Thirdly, "ddd" may have the form "Mm.w.d" means day d of the wth week of the mth month. The day is given as a single digit, with "0" meaning Sunday and "6" meaning Saturday. The first week contains days 1 to 7 of the month, the second week contains days 8 to 14, and so on. If "w" is "5" then the last week of the month (containing its last seven days) is used, rather than the fifth week (which is incomplete). Examples: MUT-4 Mauritius time, since 1907: 4 hours ahead of UT all year. EST5EDT,M3.2.0,M11.1.0 US Eastern timezone with DST, from 2007 onwards. 5 hours behind UT in winter and 4 hours behind in summer. Changes on the second Sunday in March and the first Sunday in November, in each case at 02:00 local time. NST3:30NDT,M3.2.0/0:01,M11.1.0/0:01 Newfoundland timezone with DST, from 2007 onwards. 3.5 hours behind UT in winter and 2.5 hours behind in summer. Changes on the second Sunday in March and the first Sunday in November, in each case at 00:01 local time. GMT0BST,M3.5.0/1,M10.5.0 UK civil time, from 1996 onwards. On UT during the winter, calling it "GMT", and 1 hour ahead of UT during the summer, called "BST". Changes on the last Sunday in March and the last Sunday in October, in each case at 01:00 UT. EST-10EST,M10.5.0,M3.5.0/3 Australian Eastern timezone, from 2007 onwards. 10 hours ahead of UT in the southern winter (the middle of the calendar year), and 11 hours ahead in the southern summer. Changes to DST on the last Sunday in October, and back on the last Sunday in March, in each case at 02:00 standard time (16:00 UT of the preceding day). CONSTRUCTOR
DateTime::TimeZone::SystemV->new(TZ_STRING) TZ_STRING must be a timezone specification as described in "SYSTEM V TIMEZONE SYNTAX". Constructs and returns a DateTime-compatible timezone object that implements the timezone specified by TZ_STRING. METHODS
These methods are all part of the DateTime::TimeZone interface. See that class for the general meaning of these methods; the documentation below only comments on the specific behaviour of this class. Identification $tz->is_floating Returns false. $tz->is_utc Returns false. $tz->is_olson Returns false. $tz->category Returns "undef", because the category concept doesn't properly apply to these timezones. $tz->name Returns the TZ_STRING that was supplied to the constructor. Offsets $tz->has_dst_changes Returns a boolean indicating whether the timezone includes a DST offset. $tz->is_dst_for_datetime(DT) DT must be a DateTime-compatible object (specifically, it must implement the "utc_rd_values" method). Returns a boolean indicating whether the timezone is on DST at the instant represented by DT. $tz->offset_for_datetime(DT) DT must be a DateTime-compatible object (specifically, it must implement the "utc_rd_values" method). Returns the offset from UT that is in effect at the instant represented by DT, in seconds. $tz->short_name_for_datetime(DT) DT must be a DateTime-compatible object (specifically, it must implement the "utc_rd_values" method). Returns the time scale abbreviation for the offset that is in effect at the instant represented by DT. $tz->offset_for_local_datetime(DT) DT must be a DateTime-compatible object (specifically, it must implement the "local_rd_values" method). Takes the local time represented by DT (regardless of what absolute time it also represents), and interprets that as a local time in the timezone of the timezone object (not the timezone used in DT). Returns the offset from UT that is in effect at that local time, in seconds. If the local time given is ambiguous due to a nearby offset change, the numerically lower offset (usually the standard one) is returned with no warning of the situation. If the local time given does not exist due to a nearby offset change, the method "die"s saying so. SEE ALSO
DateTime, DateTime::TimeZone AUTHOR
Andrew Main (Zefram) <zefram@fysh.org> COPYRIGHT
Copyright (C) 2007, 2009 Andrew Main (Zefram) <zefram@fysh.org> LICENSE
This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.10.1 2010-03-30 DateTime::TimeZone::SystemV(3pm)