=================================================
-----Original Message-----
From: "Binyamin Dissen" <[EMAIL PROTECTED]>
Sent: 7/17/2006 9:24 AM
To: "[email protected]" <[email protected]>
Subject: Re: cross memory assembler program help

On Mon, 17 Jul 2006 11:02:58 EDT "(IBM Mainframe Discussion List)"
<[EMAIL PROTECTED]> wrote:

:>In a message dated 7/17/2006 9:54:55 A.M. Central Daylight Time,  
:>[EMAIL PROTECTED] writes:

:>>LPAR?  I have seen some pretty horrible delays in traces  before that
:>>could be attributed to LPAR configuration especially with  high virtual
:>>to real CP ratios and too many LPAR's.
:>The situation I described was occurring on an LPAR, so I will attribute  the 
:>apparent elongation of CPU time due to using two STCKs to the  
LPAR/hypervisor 
:>effect.
 
:>Next question:  is there any program-accessible clock, timer,  etc. that is 
:>updated only when the LPAR is dispatched?

CPU timer, though MVS will change it when different work is dispatched. 

The CPU timer is documented to not decrement when the CPU is in a stopped
state, which would seem logically equivalent to not being dispatched on an
LPAR.

--
Binyamin Dissen <[EMAIL PROTECTED]>
http://www.dissensoftware.com
=================================================

I don't think that was the OP's intent. Of course, the CPU
timer runs while (any) LPAR is dispatched on the specific
CPU is not in a wait state. However, two consecutive stores
of the CPU timer can show wildly different values if the
unit of work is pre-empted between the two instructions.

The OP is apparently looking for a timer that shows active LPAR
cpu or elapsed time.


Jeffrey D. Smith
Farsight Systems Corporation
24 BURLINGTON DR
LONGMONT, CO 80501
303-774-9381 direct
303-709-8153 cell
303-484-6170 fax

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to