MVSFORUMS.com

[Arturo]

To All,

I there a parm that I can put in my jcl to make my job be the first in line to execute once it arrives in the input queue?

Scenario:
All initiators are being used and I have twenty jobs waiting in line for a initiator. But I want this job that I am submitting to get in front of those twenty jobs.

Any info appreciated.
_________________
Regards,
Arturo

[semigeezer]

Job schedulers may have some such option. I've never used one. If you know of a job class that has an open, active initiator, you can submit the job to that class, but be aware that job classes are intended as a system performance and work scheduling tool, and misusing them in this manner may get you in trouble at some sites. If you are just using a personal, test or lightly used z/OS system, then this is a perfectly reasonable use of job classes and initiators. Doing this in a production system can cause major problems if it causes required initiators to become unavailable.

There are many tools available to look at initiators and their associated classes and states: SDSF's INIT, TASID option 4, /$DI in SDSF if you have authority, etc.

[nevilh]

have you tried coding a prty= parameter on your jobcard.
Many installations stop its use but you never know you might be lucky

[Arturo]

I have changed the class and really did not want to go that route for the same reasons that you mention. I have also used the prty= and doesn't do anything except put the job in the last position.

I didn't mention in my original post that we use WLM.

Thank you both for your suggestion and hopefully along with others we'll find that parm.
_________________
Regards,
Arturo

[js01]

You have to talk with your system people to prioritize your jobs in spool.