Hi Rob,
Nice to double it, but that still gives some (hardcoded) limit. For VMC USER it
still discards data, when there are more than (for example) 200 users in z/VM.
Even VMC LPAR might be bigger than 200 records when you have a high number of
LPARs with multiple processors.
Meanwhile, thanks
We got to 2 solutions for it:
* print to reader of a user: pipe vmc perfsvm print user (to SOMEUSER
* print to file on perfsvm: PIPE vmc perfsvm PRINT USER (SORT %CPU PAGESIZE
OFF TOFILE XYGUEST LISTING A CLOSE
The last one also gets a listing without headers in between, both are also no
On Sat, 24 Oct 2020 at 03:03, van Sleeuwen, Berry <
berry.vansleeu...@atos.net> wrote:
> Hi All,
>
> The PIPE VMC stage apparently has a fixed 8K buffer, though I don’t know
> for sure if that limit is in the VMC stage or a limit in the Performance
> toolkit. When retrieving data it only returns 1
On Saturday, 10/24/2020 at 01:03 GMT, "van Sleeuwen, Berry"
wrote:
> Hi All,
>
> The PIPE VMC stage apparently has a fixed 8K buffer, though I don’t know
for
> sure if that limit is in the VMC stage or a limit in the Performance
toolkit.
> When retrieving data it only returns 101 records of 80
