Sure. The sysprogs wanted to try and be sure they could get into the system in times of stress. We run a single LPAR on a machine with two processors, so CICS (our loved one) in a loop can monopolize one and leave the other struggling to service the remaining workloads. We didn't even bother with experimenting with a TSOHOT service class - we felt like we had enough service classes defined already.
Greg -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Elardus Engelbrecht Sent: Wednesday, May 27, 2015 8:07 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Slow storage creep in SYSTEM.SYSSTC Greg Shirey wrote: >We put the systems programmers' TSO sessions there, for instance. TSO sessions not at TSOHOT, TSOHI, TSOMD, TSOLOW, etc.? Hmmm? Just curious, if you don't mind please. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
