Job Priority in Submitted Jobs

From: Sharon Keeping

To: All

I created a new subsystem for a group of jobs the other day. I wanted the jobs to run at a high priority, so I created a job description for the jobs and put the routing data entry at QCMDI. In the routing steps, the QCMDI value used a class I created to run at priority 19. QCMDB used QBATCH (50 priority) and *ANY used the class I created for 19 priority. None of the jobs would run at 19 until I changed the routing step for QCMDB in the subsystem description to use the class I created.

I'm confused because I thought the job description provided the routing data for the jobs, but they were apparently using QCMDB. Where did they get it?

From: Richard Schoen

To: Sharon Keeping

I am making an assumption that you are submitting jobs to this new subsystem using the SBMJOB command. There is a routing data parameter on the SBMJOB command that defaults to QCMDB unless you specify otherwise. If you specify *JOBD on the routing data parameter, your job will use the routing data from the specified job description on the SBMJOB command.

You could also just key QCMDI in the routing data parameter on the SBMJOB command. This would give you basically the same effect as tying the routing data to the job description, except you don't necessarily have to specify a specific job description. Your jobs should then use the correct subsystem routing entry and class. Hope this helps.

From: Sharon Keeping

To: Richard Schoen

Ah-hah! I thought I had looked everywhere for the answer to that question, but you are right. There it sits in the SBMJOB command in the RTGDTA parameter: QCMDB. Thanks for your help.