Points to consider Time limit on the entire job and or step level Limit based on time of day job is executing vs. time submitted. Allow TIME= specified at any time or always ignore Exceptions to the above (they always seem to happen and you don't want to be on the losing side of a management war).
What is the real goal, to limit individual jobs or to limit overall CPU usage by development during prime shift? A WLM resource group with CPU limits may be appropriate depending on your exact needs. I used to have a UJV exit that required TIME= to be coded for certain job classes and specific maximums for a given class. TSO submit exit (IKJEFF10) was used to enforce job classes development could use. It wasn't perfect, you could bypass IKJEFF10 a number of ways and you could change your job class after submit through SDSF (Yes I know there are more complete ways of securing this but it wasn't worth the effort). Now with only a dozen or so Mainframe developers we can easily say don't do that and they won't. Ken -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Kelman, Tom Sent: Tuesday, July 28, 2009 4:36 PM To: [email protected] Subject: Re: [IBM-MAIN] Enforcing CPU Time Thanks John. That looks like it's exactly what we need. I've passed this on to my MVS sysprogs who'll be doing any necessary exit writing. Tom Kelman Enterprise Capacity Planner Commerce Bank of Kansas City (816) 760-7632 > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of McKown, John > Sent: Tuesday, July 28, 2009 3:15 PM > To: [email protected] > Subject: Re: Enforcing CPU Time > > > -----Original Message----- > > From: IBM Mainframe Discussion List > > [mailto:[email protected]] On Behalf Of Kelman, Tom > > Sent: Tuesday, July 28, 2009 3:05 PM > > To: [email protected] > > Subject: Enforcing CPU Time > > > > Management here has requested that we determine a way to enforce a CPU > > time limit on test jobs during the prime shift. That is we do not > > want the user to be able to override the default CPU time limit with > > the TIME= parameter on the EXEC card. Is the best place to do this > > the IEFUSI exit, or can it be done at all? It's been a long time > > since I've been involved with doing anything like this, and I'm now > > a capacity planner, not an MVS system programmer. > > > > Tom Kelman > > The book recommends using IEFUJV. > > http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2E490/2.25 > > At the preconversion point, you might use IEFUJV to: > > * Validate any accounting fields included in the JOB and EXEC > statements (except symbolic parameters) by comparing them to a standard > list. > > * Validate or assign the REGION request. > > * Validate or assign job TIME and job step TIME parameters. > ... > Sample IEFUJV exit routines are provided in SYS1.SAMPLIB in members > SMFEXITS and IEEUJV. The routine in SMFEXITS checks the validity of a > continued JOB statement and of values supplied for the REGION, PRTY, TIME, > and accounting parameters in the JOB statement. The routine uses > characters from the account number to index a table that contains > allowable values for these parameters. If any value is not valid, the > sample IEFUJV routine terminates the job. > > The sample in IEEUJV changes the SYSOUT class to SYSOUT=* for jobs in > specified JOB classes and for specified SYSOUT classes. Assembled into the > exit routine is a list of eligible job classes and a list of eligible > SYSOUT classes. Thus, if a job enters the system in one of the specified > job classes and contains a DD statement specifying SYSOUT=class, where > class is one of the specified SYSOUT classes, then the SYSOUT class will > be changed to '*'. > > -- > John McKown > Systems Engineer IV > IT > > Administrative Services Group > > HealthMarkets(r) > > 9151 Boulevard 26 * N. Richland Hills * TX 76010 > (817) 255-3225 phone * (817)-961-6183 cell > [email protected] * www.HealthMarkets.com > > Confidentiality Notice: This e-mail message may contain confidential or > proprietary information. If you are not the intended recipient, please > contact the sender by reply e-mail and destroy all copies of the original > message. HealthMarkets(r) is the brand name for products underwritten and > issued by the insurance subsidiaries of HealthMarkets, Inc. -The > Chesapeake Life Insurance Company(r), Mid-West National Life Insurance > Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM > > > ---------------------------------------------------------------------- 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
