Skip to content
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

Closed
mstram opened this issue Feb 20, 2013 · 4 comments
Closed

TZOFFSET 0000 not accepted #2

mstram opened this issue Feb 20, 2013 · 4 comments

Comments

@mstram
Copy link

mstram commented Feb 20, 2013

TZOFFSET 0000 gives :

HHCCF023S Error in hercules.cnf line 7: 0000 is not a valid timezone offset

Either TZOFFSET +0000 or -0000 do work

@mstram
Copy link
Author

mstram commented Feb 20, 2013

TZOFFSET 0000 works in Feb 14 sandhawk (Win 32 build)

@rbowler
Copy link
Owner

rbowler commented Feb 22, 2013

I think the intention was that the syntax should be +nnnn or -nnnn.
So in my view it is correct that +0000 or -0000 do work and 0000 is not a valid timezone offset.

@mstram
Copy link
Author

mstram commented Feb 22, 2013

Then the easy fix is to update the manual :)

0000 GMT time (0000 is the default value). Please note that this is
also the correct setting if
your system time (the time of the operating system on which
Hercules is running) is set to
local time rather than GMT.

On 2/22/13, Roger Bowler notifications@github.com wrote:

I think the intention was that the syntax should be +nnnn or -nnnn.
So in my view it is correct that +0000 or -0000 do work and 0000 is not a
valid timezone offset.


Reply to this email directly or view it on GitHub:
#2 (comment)

@rbowler
Copy link
Owner

rbowler commented Feb 23, 2013

Then the easy fix is to update the manual :)

Agreed, and done.

0000 GMT time (0000 is the default value).
Please note that this is also the correct setting if
your system time (the time of the operating system
on which Hercules is running) is set to local time
rather than GMT.

Surely that is true only if you want your TOD clock to be set to local time as well?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants