On Mon, 26 Feb 2018 19:28:22 -0500, Tony Harminc wrote:
>
>My apologies. Clearly I also misled myself by allowing memory to override
>logic.
>
Thanks for your kind followup.
>Though I think I did accomplish my point in pointing out that Timer
>Units of either size are not TOD Clock units, or
On 26 February 2018 at 13:42, Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Mon, 26 Feb 2018 18:03:58 +, Seymour J Metz wrote:
>>...
>>Why should the descriptions of a software construct agree with the
hardware used to support it. A TU represents the
On Mon, 26 Feb 2018 18:03:58 +, Seymour J Metz wrote:
>...
>Why should the descriptions of a software construct agree with the hardware
>used to support it. A TU represents the effective interval for changing bit
>30, not bit 31.
>
I feel badly misled by the ply that said:
Timer
lf of
Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu>
Sent: Monday, February 26, 2018 12:46 PM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: Timer Unis (was: ... time change ...)
On Mon, 26 Feb 2018 17:07:50 +, Seymour J Metz wrote:
>Timer units are the same for the S/360 and the S/370
018 11:32 PM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: Timer Unis (was: ... time change ...)
On 23 February 2018 at 19:16, Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> But now I'm confused. The description of TIMER says:
> For TUINTVL, the address
On Mon, 26 Feb 2018 17:07:50 +, Seymour J Metz wrote:
>Timer units are the same for the S/360 and the S/370. From GA22-7000-4 :
>"In each case, the frequency is adjusted to give counting at 300 cycles per
>second
>in bit position 23. The cycle of the timer is approximately 15.5 hours. "
>
From: IBM Mainframe Discussion List <IBM-MAIN@listserv.ua.edu> on behalf of
Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu>
Sent: Saturday, February 24, 2018 12:34 AM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: Timer Unis (was: ... time change ...)
[I meant "Un
du/~smetz3
From: IBM Mainframe Discussion List <IBM-MAIN@listserv.ua.edu> on behalf of
Bill Godfrey <bgodfrey...@gmail.com>
Sent: Sunday, February 25, 2018 3:41 PM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: Timer Unis (was: ... time change ...)
On Fri
On Fri, 23 Feb 2018 23:32:07 -0500, Tony Harminc wrote:
>On 23 February 2018 at 19:16, Paul Gilmartin <
>000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
>
>> But now I'm confused. The description of TIMER says:
>> For TUINTVL, the address is a fullword containing the time interval.
>>
[I meant "Units".]
On Fri, 23 Feb 2018 23:32:07 -0500, Tony Harminc wrote:
>
>> ... The description of TIMER says: ...
>> the low-order bit has a value of one timer unit (approximately 26.04166
>> microseconds).
>>
>> That has to be right, or else programmers would have noticed.
>
>I
On 23 February 2018 at 19:16, Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> But now I'm confused. The description of TIMER says:
> For TUINTVL, the address is a fullword containing the time interval.
> The time interval is presented as an unsigned 32-bit
On Fri, 23 Feb 2018 14:12:37 -0800, Charles Mills wrote:
>That is what I thought. How can a national grid work if SCE is zigging when
>PG is zagging?
>
>-Original Message-
>From: Jesse 1 Robinson
>Sent: Friday, February 23, 2018 1:49 PM
>
>Long before I came to work for one, I heard that
Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Jesse 1 Robinson
Sent: Friday, February 23, 2018 1:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Timer Unis (was: ... time change ...)
Long before I came to work for one, I heard that power companies
: (External):Timer Unis (was: ... time change ...)
On Fri, 23 Feb 2018 14:54:18 -0500, Tony Harminc wrote:
>
>Timer Units are not TOD clock units. Timer units are approximately
>26.04167 microseconds. They come from the long-gone S/360 Interval
>Timer, which was the fullword at locat
Sent: Friday, February 23, 2018 3:13 PM
To: IBM-MAIN@listserv.ua.edu
Subject: Timer Unis (was: ... time change ...)
On Fri, 23 Feb 2018 14:54:18 -0500, Tony Harminc wrote:
>
>Timer Units are not TOD clock units. Timer units are approximately
>26.04167 microseconds. They come from the lon
On Fri, 23 Feb 2018 14:54:18 -0500, Tony Harminc wrote:
>
>Timer Units are not TOD clock units. Timer units are approximately
>26.04167 microseconds. They come from the long-gone S/360 Interval
>Timer, which was the fullword at location 80 (x'50'). This was defined
>so that bit position 23 is
16 matches
Mail list logo
