Looks like that is the right value; the QvsImgCapacity value returned is documented as:
Note that the capacity of a virtual server can change dynamically. One example of a dynamic capacity change is a CPU upgrade on demand of the underlying hardware. A second example is a dynamic change of the defined capacity limit for a logical partition. If an unauthorized program is interested in knowing about dynamic capacity changes, it must poll the virtual server ID and capacity query service. Given dynamic capacity changes are rare, a low polling rate should be sufficient. Unfortunately, what I really wanted was a nice fullword I could grab through a couple of lines of Rexx. But I'll whittle away at LPINFOX, see if I can get down to just this value in a few lines. (The idea is for a customer to be able to cut & paste a few lines, and to trust that it's OK to run without having to wade through a long program--and calling IWMQVS may be off-putting to them as well.) But I don't mean to sound ungrateful--thank you! On Thu, Mar 2, 2017 at 4:15 AM, John Gateley <j...@spurtle.biz> wrote: > Hi > > Is this rexx what you are looking for? > > http://www.longpelaexpertise.com/toolsLPinfoX.php > > Regards > John > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- zMan -- "I've got a mainframe and I'm not afraid to use it" ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
