Perhaps the OP deliberately put a simple test program into an infinite LOAD loop just to see what would happen. I find that much more likely. I have done similar things in the past; e.g., trying to run a job step with N and then N+1 DD statements, where N is the documented maximum number per step, testing a program that does only a SYNCH macro to see if the system can survive.
IBM has a huge number of test job streams that they run against each new release of z/OS to make sure that all previously fixed APARs are still fixed, that no fixes have regressed, etc. I'm sure many of them test various documented system limits. Bill Fairchild Rocket Software -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Gerhard Postpischil Sent: Friday, September 10, 2010 11:59 PM To: [email protected] Subject: Re: S906-08 However, you either have 32K concurrent users of IEFBR14, something I find unlikely, or a long-running task that fails to do a DELETE. While theoretically a storage overlay is possible, it's unlikely to hit only the count field. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
