STSI give you information about the machine capacity, etc. (standard engines) but it doesn't show IFLs. Until 5.3, you couldn't really tell if you were running on IFLs or CPs. If you're a Class G user, the CP IND and Q PROC commands don't tell you either, even on 5.3 or 5.4. You need to use the Q V CPUS command and see what type of virtual CPU you have. But note that on 5.4 you can configure it to run a virtual IFL on a real CP so you may not really know even then. What you really need is the CP monitor data that Perfkit or ESAMON uses.
On Sun, Dec 7, 2008 at 10:20 PM, Alan Ackerman <[EMAIL PROTECTED]> wrote: > > What puzzles me is that the STSI instruction seems to show nothing about > IFLs. > > Config 122 Basic-machine CPUs: > Format: 1 = x01 > ACC Offset: 300 = x012C > Secondary CPU Capability: 904 = x00000388 > CPU Capability: 904 (binary) > Total CPU Count: 64 = x0040 > Configured CPU Count: 13 = x000D > Standby CPU Count: 0 = x0000 > Reserved CPU Count: 51 = x0033 > > I think those 13 Configured CPUs are the standard engines. Is there any > information about IFLs in the STSI output? I though you weren't supposed > to be able to see the standard engines from the IFL LPARs, and vice-versa. > > ESAMON ESALPAR shows: > > <--Complex--> > Phys Dispatch > CPUs Slice > ---- -------- > 15 Dynamic > > > So the STSI may ignore the IFLs. > > Alan Ackerman > Alan (dot) Ackerman (at) Bank of America (dot) com > -- Bruce Hayden Linux on System z Advanced Technical Support IBM, Endicott, NY
