an update about syssrc & syscpu under systemrexx: I opened a PMR. IBM agrees it does not work. However, they supplied a long explanation how it works under TSO/E, why it doesn't work under SystemRexx, and a workaround based on Rexx STORAGE function. If I want the issue to be fixed, I need to open a requirement for this.
ITschak On Mon, Sep 17, 2018 at 3:54 PM Tom Marchant < [email protected]> wrote: > On Sat, 15 Sep 2018 15:29:48 +0800, David Crayford wrote: > > >On 14/09/2018 9:21 PM, Tom Marchant wrote: > >> > >> What model is that? How severely is it kneecapped? > >> > > > >We're pretty heavily kneecapped but I would still expect better > >performance than a emulated machine > > > >Processor Information from MXI. We run 3 LPARs > > > >CPU Model 2965 CPU Type Code 00 > >Physical CPUs 4 Processor Name Z10#T03 > >Total MIPS 375.52 SU/Second 4553.21 > >MIPS/CPU 93.88 CPU Adjustment 3514 > >MSU 66 > > This doesn't tell what model it is. What does D M=CPU show? > > 4 CPUs and 66 MSU for a z13s suggests that it is a 2965-F04. > If you look at the LSPR data at > > https://www-01.ibm.com/servers/resourcelink/lib03060.nsf/pages/lsprITRzOSv2r2?OpenDocument#z13s > you can see that a full speed z13s (2965-Z04) is 622 MSU, > not quite 10 times as fast as an F04. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- ITschak Mugzach *|** IronSphere Platform* *|* *Information Security Contiguous Monitoring for Legacy **| * ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
