R. Skorupka wrote: >The following scenario: z13 2964-N30 401 (yes, the smallest CPU) and ~1,5TB of >memory. z/OS 1.13 with RSU at Oct-2015 (plus 2964DEVICE, AFAIK).
Is that ONE CPU? How many LPARS are using that CPU? >D M=STOR causes weird effects. System freeze for a while. For 2GB LPAR system >behavior is normal, for ~64GB LPAR there is few-second freeze, but for 1,1TB >LPAR system freeze for approx half a minute, TSO sessions are broken, the >*$HASP9211 JES2 MAIN TASK NOT RUNNING is issued. HMC monitor show 100% CPU >utilization. It seemed like WAD, because all processes are competing for that 1 CPU, but the system gives that command a high priority, because the memory is made 'freezed' to give a reliable output. Which memory is NOT RECONFIGURABLE or RECONFIGURABLE? What is your Storage increment size? Question: Are those messages shown during processing of that command or AFTER the output is shown. This may give a clue. >IMHO such behavior is unacceptable even for testing activities. Indeed. Time for a PMR. >Is it bug or feature? It is a buggy bug! Apparently the response time is worsening with increasing memory size. I'm smelling a badly designed D M=STOR command handler. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
