Place the following in a file TESTCP ESAMON and
execute by issuing ESAMON TESTCP
/* TESTCP */
'EXTRACT FROM INTERVAL',
'LPAR * CPU ALL',
'FIELD',
'SYTCUP.CALFLGS'
Do While RC = 0
If BITAND(X2C(SYTCUP.CALFLGS),'80'x) = '80'x Then
Do
If BITAND(X2C(SYTCUP.CALFLGS),'10'x) = '10'x Then
say 'VM LPAR is CP '
ELSE say 'VM LPAR is IFL'
Exit
End
Address ESAMON 'RETRIEVE'
End
Say 'Not in an LPAR'
Exit
Dennis Andrews
Velocity Software
>From: Barton Robinson <[log in to unmask]>
>Help with this rexx macro would of course be part of
>normal customer support. should be posted shortly.
>And the architecture supports identifying all the processor
>types. haven't seen ziip/zaap data yet, but expect them
>easily identified.
>>From: Dave Jones <[log in to unmask]>
>>
>>Barton's correct...I had forgotten that the Velocity suite of products
>>can tell you information about the LPAR configuration.
>>
>>Of course, if IBM ever changes the rules and allows different engine
>>types to be in the same LPAR, the problem changes considerably....:-)
>>
>>DJ
>>
>>Barton Robinson wrote:
>>> And with an ESAMON macro - written in REXX, you can obtain
>>> this data. Even zMON would have this capability (I say zMON
>>> because that is a very low cost solution)
>>>
>>>
>>>>From: =?iso-8859-1?Q?Brian_Nielsen?= <[log in to unmask]>
>>>>
>>>>Even better, the Velocity HDR report shows what processor type
>>>>you're running on:
>>>>
>>>> Operating on IFL Processor(s)
>>>>
>>>>Brian Nielsen
>>>>
>>>>On Mon, 12 Jun 2006 11:38:53 -0500, Brian Nielsen
>>>><[log in to unmask]> wrote:
>>>>
>>>>>processor type is CP or ICF for each LPAR. Then the question becomes
>>>>>which LPAR you're runing in.
>>>>>
>>>>>Brian Nielsen
>>>>>
>>From: "Stracka, James (GTI)" <[log in to unmask]>
>>
>>And a sample of that ESAMON macro would be giving away free code?
