Page 1 of 1

changing parameter value after submission of job

PostPosted: Mon Oct 10, 2011 12:46 pm
by Moni_P
Hi,

can anybody help me out in this.

At what stage,operator can change the class and priority of a submitted job?

Thanks in advance !

Re: changing parameter value after submission of job

PostPosted: Mon Oct 10, 2011 1:38 pm
by enrico-sorichetti
if You count to ten and make Your neurons spin a bit faster You will certainly be able to answer Yourself :D

Re: changing parameter value after submission of job

PostPosted: Mon Oct 10, 2011 1:52 pm
by enrico-sorichetti
follow on, hit enter too fast...
meditate on the meaning and effects of the CLASS and PRIORITY parameters in the JOB card

here
z/OS V1R6.0-V1R10.0 MVS JCL User's Guide
http://publibz.boulder.ibm.com/cgi-bin/ ... 0712160458
z/OS V1R10.0 MVS JCL Reference
http://publibz.boulder.ibm.com/cgi-bin/ ... 0604022956

not the latest ones, but more than enough for a reply to your questions

if there is something You do not understand in the manuals, just ask and somebody will be glad to explain

Re: changing parameter value after submission of job

PostPosted: Mon Oct 10, 2011 10:14 pm
by dick scherrer
Hello and welcome to the forum,

At what stage,operator can change the class and priority of a submitted job?

Why would the operator want to change these?

If you explain what you really want to know someone may be able to help.

Re: changing parameter value after submission of job

PostPosted: Tue Oct 11, 2011 11:10 am
by Moni_P
one of my friend asks this question to me.

i know:based on the class the priority will work and the job get execute.
if there are 3 jobs with the class A(priority 8),A(priority 12),B(priority 6) are submitted at the same time the class A with priority 12 will get executed first and the class A with priority 8 and the class B will get executed.

but i don't know after submitting a job we can able to change the class parameter or not?
that too at what stage?

Re: changing parameter value after submission of job

PostPosted: Tue Oct 11, 2011 11:24 am
by BillyBoyo
Until the job is selected, OPS would be able to make changes which could affect selection. Once a job is running, they can only make changes which affter its running.

A job does not only wait on the input que for "priority" reasons, there may be "resource" reasons as well. If for instance something has DISP=OLD and that dataset is being used, you can do what you like to the priority but the job will not be selected.

Re: changing parameter value after submission of job

PostPosted: Tue Oct 11, 2011 3:42 pm
by NicC
I believe that the smaller the priority number the higher the priority - not the other way round. And nothing will run if there is no initiator set for that class and a lower priority B class job will run before any priority A class job if the initiators all have B before A.