Agreed on that point. Not all sites have the routines in place to handle the VIO part. Wasn't a big deal to define an IODF in HCD to include a VIO device and/or define an entry in the EDT.
Agree on second point too. We are generally NOT resource consumed these days. In the past we were concerned with the needs of the many, and wanted to protect running out of anything. Example, in the past we were definitely concerned about exhausting the paging subsystem. Bad things happened at that point (or Operating training on how to IPL). But I would say paging is not much of an issue these days. But still need to be sure there are sufficient page volumes. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Tom Brennan Sent: Thursday, May 19, 2016 5:23 PM To: [email protected] Subject: Re: What was a 3314? Not if the jobs run fine. To change the subject beyond VIO: In my experience, arbitrary limits on mainframe resources do nothing more than result in job reruns. Jobs killed because of time/space/spool/etc might need double the CPU because of the rerun after the limits are increased. What a waste of a good CPU that could be used for a nice game of chess. Norman.Hollander wrote: > Maybe a bunch of JCL with UNIT=VIO is a cause to make you fuss? ---------------------------------------------------------------------- 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
