I second the idea about creating multiple JOBDs as needed. Chances are most of your production jobs can run under the same JOBD. At worst you'll need just a handful (ie daily/weekly/monthly/etc.). Avoids all that typing of library names! (:

I've always felt that JOBQs, OUTQs, and JOBDs are 'inexpensive' as far as system resources go, so why not make a bunch?!

Of course, -administering- all of those objects once you've got them can be interesting.

Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.