First, my QSTRUP program and my backup only need to start the subsystem, and
the job will begin running.
Second, some places set a limit on how many threads the QBATCH job queue can
have.
Third, I can allocate a separate memory pool to my subsystem, and it can
have its own job queue as well.

It's just a matter of taste, but it works for me.

Paul Nelson
Cell 708-670-6978
Office 512-392-2577
nelsonp@xxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Rosinger
Sent: Tuesday, September 18, 2007 11:37 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: scheduled job to run every n minutes?

"Paul Nelson" <nelsonp@xxxxxxxxxxxxx> wrote in message
news:mailman.5713.1190132613.4459.midrange-l@xxxxxxxxxxxxxxx
I'd run the job in a separate subsystem as a prestart job.

Do you have a specific reason for that? Is there an impact on processing if
this job is running in QBATCH along with other jobs?


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.