Once, in my first months here, a program appeared to be looping, but maybe not. It was impacting the system, but I insisted it be allowed to run and it was for a while. It was a Cobol program. Perform until some COMP field reached zero. The Cobol of the time did not recognize negative zero (X'80000000') in a COMP field as zero.
> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Elardus Engelbrecht > Sent: Wednesday, September 14, 2016 5:30 AM > To: [email protected] > Subject: Re: Bypassing s322 > > Scott Chapman wrote: > > >Of course, when anybody came to me complaining about an S322, assuming > it was already in one of the classes that allowed them to get the max we > allowed of 1 or 2 hours of CPU time, my first reaction was always something > along the lines of "Are you sure you aren't looping? Are you sure you don't > have a tuning opportunity that needs to be fixed?" An hour of CPU time is > usually a whole lot of work. > > Agreed. > > Watch the CPU usage of that job. If it is very high in relation of the other > tasks, then there is a possible loop. Or lots of I/Os. Or you see excessive > SMF > records being written. Or you see that job is spitting out gazillion lines. > > Scott, I would go the same tuning route as you (and slap that complainer hard > and loud. ;-D ) > > Groete / Greetings > Elardus Engelbrecht > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
