RE: ODBC job priority

Mark,

All the jobs in the QSERVER subsystem run under the QPWFSERVER class. If
you want to affect the priority of all of them change this class to have
a priority of, say, 30. If you want to affect only QZDAINIT, then create
a dupilcate of the class and change that. Then add a routing entry
pointing to it. The entry should be just like the one that currently
runs QZDAINIT, (sequence 400 on my system) but with a lower sequence
number and, of course, your new class. If you want to go back to the
default you can then just remove your new routing entry and the original
one will come into force again.

Note that as QZDAINIT is, or should be, a pre-start job you will have to
end however many existing instances of it there are. This will force the
system to create a new job with your chosen priority next time you do a
transfer.

HTH

Dave Kahn, TCO, Kazakstan
=========

kahn@tengizchevroil.com   (to November 25)
dkahn@cix.compulink.co.uk (from November 26)

>-----Original Message-----
>From:  Mark Welte [SMTP:MWelte@dmtn.com]
>Sent:  Tuesday, November 11, 1997 1:46 PM
>To:    'MIDRANGE-L@midrange.com'
>Subject:       ODBC job priority
>
>We are starting to use ODBC to the AS/400 from a Windows NT PC using 
>CA/NT and the 32-bit ODBC driver. When we are sending SQL statements 
>to the AS/400 via the driver, it seems that the prestart job that is 
>executing the SQL on the AS/400 (QZDAINIT) is running at a priority of 
>20. Is there a way to set the job's priority so it will always be 
>lower?
>
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---