-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TZOFFSET 0000 not accepted #2
Comments
TZOFFSET 0000 works in Feb 14 sandhawk (Win 32 build) |
I think the intention was that the syntax should be +nnnn or -nnnn. |
Then the easy fix is to update the manual :) 0000 GMT time (0000 is the default value). Please note that this is On 2/22/13, Roger Bowler notifications@github.com wrote:
|
Agreed, and done.
Surely that is true only if you want your TOD clock to be set to local time as well? |
TZOFFSET 0000 gives :
HHCCF023S Error in hercules.cnf line 7: 0000 is not a valid timezone offset
Either TZOFFSET +0000 or -0000 do work
The text was updated successfully, but these errors were encountered: