On Tue, 12 Jan 2021 12:34:20 -0800, Charles Mills wrote:
>http://www.longpelaexpertise.com/toolsTOD.php sez
>
>TOD: (STCK): x" D91B6D3E F6430440 "
>UTC Date and Time (Date + HH:MM:SS): 11-Jan-2021 21:25:22
>UNIX Date/Time: 1610400322
>
Some consequence of this impelled me to look for CVTLSO:
On Tue, 12 Jan 2021 17:24:52 -0600, Mike Schwab wrote:
>Request for information.
>To convert from STCK format to Unix time, what constants would you
>subtract from the STCK value for the same origin, then divide by what
>constant for the same time unit? Or divide / subtract if easier.
>
An
Request for information.
To convert from STCK format to Unix time, what constants would you
subtract from the STCK value for the same origin, then divide by what
constant for the same time unit? Or divide / subtract if easier.
On Tue, Jan 12, 2021 at 5:09 PM Paul Gilmartin
You can use IPCS LTOD stck-value to check that your calculation is correct
George Kozakos
z/OS Software Service, Level 2 Supervisor
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
On Tue, 12 Jan 2021 22:53:02 +0200, Itschak Mugzach wrote:.
>
>I tested that there already. My rexx returns a different time. I noticed
>that they only use the first four bytes. The code snip I gave is from the
>TOD IPCS rexx.
>
Regina gives me:
502 $ date
Tue Jan 12 15:59:30 MST 2021
503 $ rxx
--
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Itschak Mugzach
> Sent: Tuesday, January 12, 2021 10:00 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: STCK and epoch time
>
> This is the STCK value: D91B6D3EF6430440 (I have it in hex in
On Behalf
Of Itschak Mugzach
Sent: Tuesday, January 12, 2021 10:00 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: STCK and epoch time
This is the STCK value: D91B6D3EF6430440 (I have it in hex in variable TOD)
Converted to decimal : 15644217847788536896
Actual dat eof run is : Yesterday
the cod
] on behalf of
Itschak Mugzach [0305158ad67d-dmarc-requ...@listserv.ua.edu]
Sent: Tuesday, January 12, 2021 1:00 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: STCK and epoch time
This is the STCK value: D91B6D3EF6430440 (I have it in hex in variable TOD)
Converted to decimal : 15644217847788536896
On Tue, 12 Jan 2021 19:19:01 +0200, Itschak Mugzach wrote:
>
>So if I ignore leap seconds, Can I just divide the number by 409600 and
>subtruct 1.1.1970-1.1.1900?
>
Here's some code I wrote. The input data are the list of leap seconds
in PoOp.
Restriction: Presumes a system such as Linux
m: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf
> of Itschak Mugzach [0305158ad67d-dmarc-requ...@listserv.ua.edu]
> Sent: Tuesday, January 12, 2021 12:19 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: STCK and epoch time
>
> Paul,
>
> So if I ignore l
...@listserv.ua.edu]
Sent: Tuesday, January 12, 2021 12:19 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: STCK and epoch time
Paul,
So if I ignore leap seconds, Can I just divide the number by 409600 and
subtruct 1.1.1970-1.1.1900?
*| **Itschak Mugzach | Director | SecuriTeam Software **|** IronSphere
On Tue, 12 Jan 2021 19:19:01 +0200, Itschak Mugzach wrote:
>
>So if I ignore leap seconds, Can I just divide the number by 409600 and
>
409600?
>subtruct 1.1.1970-1.1.1900?
>
Are you doing it the hard way? Borrowing from seconds to minutes,
minutes to hours, hours to days, days to months
List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Itschak Mugzach
> Sent: Tuesday, January 12, 2021 9:19 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: STCK and epoch time
>
> Paul,
>
> So if I ignore leap seconds, Can I just divide the number by 409600 and
> subtruct 1.1.19
As @Shmuel says, it depends on how the clock is set.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Itschak Mugzach
Sent: Tuesday, January 12, 2021 9:19 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: STCK and epoch time
Paul,
So if I ignore leap seconds, Can I just divide the number by 409600 and
subtruct 1.1.1970-1.1.1900?
*| **Itschak Mugzach | Director | SecuriTeam Software **|** IronSphere
Platform* *|* *Information Security Continuous Monitoring for Z/OS, zLinux
and IBM I **| *
*|* *Email**:
On Tue, 12 Jan 2021 16:30:52 +, Seymour J Metz wrote:
>The TOD clock is just a counter; what you get out of it depends on what you
>put into it. There is a convention in PoOps, but if you want the correct time
>and date it is much easier to use system services than to do the adjustments
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: STCK and epoch time
How exactly STCK (not STCKE) stores the time? I took the value (8 bytes)
and converted it to decimal 10 characters. I expect it to be the same as
the EPOCH time returned by USS time call. However the returned value is July
29, 2019 (have
https://www.mail-archive.com/search?l=ibm-main@listserv.ua.edu=subject:%22Re%5C%3A+Converting+STCK%5C%28tod%5C%29+to+readable+format%22=newest=1
On Tue, Jan 12, 2021 at 9:37 AM ITschak Mugzach wrote:
>
> How exactly STCK (not STCKE) stores the time? I took the value (8 bytes)
> and converted it
How exactly STCK (not STCKE) stores the time? I took the value (8 bytes)
and converted it to decimal 10 characters. I expect it to be the same as
the EPOCH time returned by USS time call. However the returned value is July
29, 2019 (have a time from yesterday). I know there is a macro to do it,
19 matches
Mail list logo
