We have developped a little tool to monitorize the amount of MSU's used and a
consecuence of this we can obtain the CAPPED value and others.
You can download all the code, sorry in spanish, from the following url
http://perso.wanadoo.es/rptv2005/msumon/index.html
angel luis domínguez
bbva-spain
As an example, the information obtained about all CPC, from only one LPAR, is
the following (copy an put with courier font to column it)
MSUM001I MONITOR INICIALIZADO
MSUM001I TIMER INICIALIZADO
MSUM001I LISTENER INICIALIZADO
MSUM002I EMPIEZA LA MONITORIZACION DE MSU'S
>>>>>>>>>--START-->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>ZOS140P>
NOMBRE DEL HARDWARE MIZAR 2094 708 0000000000065976
QVSCECCAPACITY (MSU'S) 000000000000532
LPDATPHYCPUADJFACTOR 000000000000866 14/12/2006 08:10:47
LPDATFLAGS POR DEFECTO
PROCESADORES FISICOS: 011 (CP: 008 ICF/IFL: 003)
======== ======== ======== === === ===== === ==== ======= ===== ===== =========
SYSPLEX ??? LP. PROCS MSUS. MSUS.
LPARNAME NAME SYSNAME ID. ID. LOGI. CAP PESO MEMORIA LPAR. HMC NOTAS
======== ======== ======== === === ===== === ==== ======= ===== ===== =========
MIZAR26 PLXSYS >TC0Z 0C 06 02 0020 0002048 00133 00000
MIZAR2A 01 00 00 0000 0000000 00000
MIZAR2B 02 00 00 0000 0000000 00000
MIZAR2C 03 00 00 0000 0000000 00000
MIZAR2D 04 0D 01 DED. 0008192 00000
MIZAR2E 05 0E 01 DED. 0008192 00000
MIZAR2F 06 0F 01 DED. 0006144 00000
MIZAR21 PLXPRD CR02 07 01 08 YES 0586 0010240 00000
MIZAR22 PLXPAR PAR1 08 02 02 0052 0004096 00000
MIZAR23 PLXDYD DYD2 09 03 03 0213 0007168 00000
MIZAR24 0A 00 00 0000 0000000 00000
MIZAR25 0B 00 00 0000 0000000 00000
MIZAR27 PLEX01 FOR1 0D 07 02 0015 0002048 00000
MIZAR28 PLXBKP BK02 0E 08 01 0008 0002048 00000
MIZAR29 0F 00 00 0000 0000000 00000
MIZAR31 10 11 01 0104 0000064 00000
MIZAR32 11 00 00 0000 0000000 00000
MIZAR33 12 00 00 0000 0000000 00000
---- ------- -----
TOTALES DEFINIDOS ............. 0998 0050240 00000 NO VERIF.
-------------------------------------------------------------------------------
Shannon Collinson, from SunTrust Bank wrote
Does anyone know a field in a control block somewhere that I can check to see
if an LPAR is currently capped? I was using the IRALPDAT data area and
comparing the defined capacity to the 4-hour average to determine capping, but
of course if we drop our defined capacity down after a period of heavy
activity, that info tells me we're capping when somehow RMF and WLM know that
we're not. I think it has something to do with LPDATSERVICECAPPEDTIME, but I'm
not sure how the LPDATSERVICETABLE is updated so don't know where I should be
looking. A flag that indicates "capping!" for this service period would be
ideal, but I'm open to any suggestions. Thanks!
---------------------------------
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
----------------------------------------------------------------------
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
