search

rbowler / spinhawk

spinhawk is the repository for the production-quality version (release 3.xx) of the Hercules mainframe virtualization platform
Other
100 stars 40 forks source link

TZOFFSET 0000 not accepted #2

Closed mstram closed 11 years ago

mstram commented 11 years ago

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 commented 11 years ago

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

rbowler commented 11 years ago

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 commented 11 years ago

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: https://github.com/rbowler/spinhawk/issues/2#issuecomment-13946705

rbowler commented 11 years ago

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?