Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 42 |
Nodes: | 6 (0 / 6) |
Uptime: | 01:39:28 |
Calls: | 220 |
Calls today: | 1 |
Files: | 824 |
Messages: | 121,542 |
Posted today: | 6 |
On 9/18/2024 9:21 AM, Tom Wade wrote:yyyy
On 2024-09-18 00:25, Lawrence D'Oliveiro wrote:
But it’s not ISO 8601.
Very true, but better than the AM/PM stuff, and unambiguous (unlike
mm/ dd/yy or dd/mm/yy).
yyyy-mm-dd has better characteristics (sorting), but dd-mmm-yyy tend to
be more readable.
On 2024-09-18 00:25, Lawrence D'Oliveiro wrote:
But it’s not ISO 8601.
Very true, but better than the AM/PM stuff, and unambiguous (unlike mm/
dd/yy or dd/mm/yy).
I'm a great believer in ISO 8601 ever since we had a software license
expire on February 2nd when we were expecting it to last till March 3rd!
But it’s not ISO 8601.
On 9/19/2024 8:22 AM, Simon Clubley wrote:
On 2024-09-18, Tom Wade <nospam@void.blackhole.mx> wrote:
On 2024-09-18 00:25, Lawrence D'Oliveiro wrote:
But it?s not ISO 8601.
Very true, but better than the AM/PM stuff, and unambiguous (unlike
mm/dd/yy or dd/mm/yy).
VMS date/time formats are much more readable, but the main problem with
VMS timekeeping is that it doesn't have a local timezone offset from a base >> GMT/UTC timepoint built into it.
What is SYS$TIMEZONE_DIFFERENTIAL then?
On 2024-09-24, Arne Vajhøj <arne@vajhoej.dk> wrote:
On 9/19/2024 8:22 AM, Simon Clubley wrote:
On 2024-09-18, Tom Wade <nospam@void.blackhole.mx> wrote:
On 2024-09-18 00:25, Lawrence D'Oliveiro wrote:
But it?s not ISO 8601.
Very true, but better than the AM/PM stuff, and unambiguous (unlike
mm/dd/yy or dd/mm/yy).
VMS date/time formats are much more readable, but the main problem with
VMS timekeeping is that it doesn't have a local timezone offset from a base >>> GMT/UTC timepoint built into it.
What is SYS$TIMEZONE_DIFFERENTIAL then?
A joke. At least when compared to Unix.
VMS commands have no support for showing the active timezone.
Compare the output of the Linux date command with $ SHOW TIME.
In Unix, all timestamps are based on GMT/UTC and the user's timezone is
just an attribute of the user's process, which is the system timezone by default but can be changed by the user. Different processes can have different timezones and none of this affects what timestamp is actually written to the filesystem when the file changes.
Compare the output of the Linux "ls --full" command with $ DIR/FULL.
Note out the Linux command shows the timezone, and note how the timezone changes for each file depending on whether DST was active or not when the file was last modified.
On 2024-09-18 00:25, Lawrence D'Oliveiro wrote:
But it?s not ISO 8601.
Very true, but better than the AM/PM stuff, and unambiguous (unlike
mm/dd/yy or dd/mm/yy).
I'm a great believer in ISO 8601 ever since we had a software license
expire on February 2nd when we were expecting it to last till March 3rd!
February 3rd and March 2nd??
On 9/19/2024 8:22 AM, Simon Clubley wrote:
VMS date/time formats are much more readable, but the main problem with
VMS timekeeping is that it doesn't have a local timezone offset from a
base GMT/UTC timepoint built into it.
What is SYS$TIMEZONE_DIFFERENTIAL then?
Unix got this right and VMS did not.
VMS did not get it right in 1978 - VMS got it almost right in 1993.
I have't seen any mention here about the VMS Software Bootcamp coming up
next month in Boston. It is a 3-day event 23-25 October.
Details, including costs, can be found on the VMS Software main website.
https://vmssoftware.com/
On 9/6/2024 2:54 PM, William Cox wrote:
I have't seen any mention here about the VMS Software Bootcamp coming up
next month in Boston. It is a 3-day event 23-25 October.
Details, including costs, can be found on the VMS Software main website.
https://vmssoftware.com/
They have now published the agenda:
https://events.vmssoftware.com/bootcamp-2024/agenda
On 2024-09-13, Arne Vajhøj <arne@vajhoej.dk> wrote:
On 9/6/2024 2:54 PM, William Cox wrote:
I have't seen any mention here about the VMS Software Bootcamp coming up >>> next month in Boston. It is a 3-day event 23-25 October.
Details, including costs, can be found on the VMS Software main website. >>>
https://vmssoftware.com/
They have now published the agenda:
https://events.vmssoftware.com/bootcamp-2024/agenda
"Structured DCL Scripting". Hmmm... :-)
BTW, it's 12pm, not 12am (unless you really are having a 13-hour
lunch break). :-)
On 9/13/2024 1:56 PM, Simon Clubley wrote:
On 2024-09-13, Arne Vajhøj <arne@vajhoej.dk> wrote:
On 9/6/2024 2:54 PM, William Cox wrote:
I have't seen any mention here about the VMS Software Bootcamp
coming up
next month in Boston. It is a 3-day event 23-25 October.
Details, including costs, can be found on the VMS Software main
website.
https://vmssoftware.com/
They have now published the agenda:
https://events.vmssoftware.com/bootcamp-2024/agenda
"Structured DCL Scripting". Hmmm... :-)
BTW, it's 12pm, not 12am (unless you really are having a 13-hour
lunch break). :-)
I think it should actually be 12m
https://www.rmg.co.uk/stories/topics/noon-12-am-or-12-pm
What does am and pm mean?
The 12-hour clock divides the 24-hour day into two periods.
am stands for the Latin ante meridiem, translating to "before midday". This is the time before noon.
pm stands for post meridiem or "after midday" – the time after noon.
Noon is therefore neither 'ante' (am) nor 'post' (pm) meridiem. Midnight
is also neither am nor pm.
On 2024-09-13, Arne Vajhøj <arne@vajhoej.dk> wrote:
They have now published the agenda:
https://events.vmssoftware.com/bootcamp-2024/agenda
"Structured DCL Scripting". Hmmm... :-)
On 9/6/2024 2:54 PM, William Cox wrote:
I have't seen any mention here about the VMS Software Bootcamp coming up
next month in Boston. It is a 3-day event 23-25 October.
Details, including costs, can be found on the VMS Software main website.
https://vmssoftware.com/
They have now published the agenda:
https://events.vmssoftware.com/bootcamp-2024/agenda