Page 1 of 1

Disable TIME parameter in JOB card

PostPosted: Fri Mar 18, 2011 5:08 pm
by XY09
Hi Guys,

I want to restrict the users who will use 'TIME=' parameter in JOB card, in such cases i want to abend with JCL error once he submit a job. I have googled but no luck Looking for helping hands.. :)

Thx,
xy09

Re: Disable TIME parameter in JOB card

PostPosted: Fri Mar 18, 2011 5:40 pm
by GuyC
you can enforce cpu limits in the job class , no matter which time they give.

Re: Disable TIME parameter in JOB card

PostPosted: Fri Mar 18, 2011 5:53 pm
by XY09
Hi GuyC,

Thanks for quick reply!!!

I have incorprated CPU limit to job class, the job class CPU time has been override by TIME parameter in the job card if the user coded, if not it will execute the job depends on job class.

Thx,
xy09

Re: Disable TIME parameter in JOB card

PostPosted: Fri Mar 18, 2011 6:52 pm
by steve-myers
GuyC wrote:you can enforce cpu limits in the job class , no matter which time they give.

I presume by "job class" you mean the TIME parameter specified in the JES2 JOBCLASS initialization statement or the $TJOBCLASS JES2 command. Unfortunately, this TIME parameter specifies a default job step limit, not a job level default or max value. See this link for z/OS 1.12.

Re: Disable TIME parameter in JOB card

PostPosted: Fri Mar 18, 2011 7:36 pm
by enrico-sorichetti
if I had to do it I would use jes exit02/exit06
( I do not remember right now which is better, most probably
EXIT02 for just checking and flushing
EXIT06 to modify something)

se the relevant jes2 manual for exit routine coding
for example
z/OS V1R10.0 JES2 Installation Exits
http://publibz.boulder.ibm.com/cgi-bin/ ... 0529125241

obviously the whole shebang being driven by the appropriate racf profile
with a facility/resource name along the line of
jesx.JOBCARDPARM.TIME

the same way You could protect other job card parameters ( class for example )

see the cbt tape for working examples

Re: Disable TIME parameter in JOB card

PostPosted: Sat Mar 19, 2011 12:56 am
by steve-myers
As enrico-sorichetti says, JES2 exits may be your best source, but you will find none of them are easy. If you use JES2 exit 2 you will also have to do JES2 exit 52 to process jobs from the internal reader.

It's not safe to do a RACROUTE macro in JES2 exit 2, but I think (I'm not certain about this) that it's safe to do a RACROUTE macro in exit 52, and I'm pretty sure it's safe in JES2 exit 6.