I FIND THIS DISCUSSION TROUBLING. It will not likely ever affect me of my
installation, has we haven't (and unfortunately are not likely to) used zLinux
and Z/VM.
But, is the z/OS MIPS/MSU pricing model (IMO, one of the major drags on the
platform) really being extended into this arena.
>
I run SCRT on my z/VSE Systems, and have been for a couple years, or so, now.
So, no, SCRT isn't just for z/OS.
Dave
Dave Stuart
Principal Info. Systems Support Analyst
County of Ventura
805-662-6731
david.stu...@ventura.org
-Original Message-
From: Linux on 390 Port
Isn't the ibm tool just for z/os and at the LPAR level? nothing to do
with what goes on inside z/vm. nothing to do with what goes on inside
linux for specific licensing.
I've been asked to provide such information by another vendor, and that
function will be released shortly. This allows the
Rick,
As we discussed on phone, but for benefit of others. My last append forgot
to point out that the TRACE needs to be done for all the virtual processors
in the virtual machine. Otherwise only, only the base VMDBK is protected.
This can be done by using the "CPU" command:
CPU ALL CMD TRACE
The circumvention of using the TRACE PROG 28 did not work for us. We had
some servers that failed and could not re-boot - most likely related to the
trace being active.
We are booting Linux back to the older kernel level that was not
experiencing the problem - 2.6.32-696.18.7.el6.s390x.
Clearly
