Re: QZDASOINIT jobs breeding like gerbils

Somewhat correct....

However, when a client is done and properly closes the connection, the
QZDASOINIT job will go back to program start request wait (PSRW) status.

Jobs with this status don't normally show up in WRKACTJOB, you have to
F14-Include to see them.

I've seen this issue occur when there's some problem in the client.
Specifically, the client is using connection pooling and while the app
"closes" the connection and returns it to the pool. The connection is
actually kept open by design. The problem is that the connection never
gets passed back out and instead a new connection gets started.

You can use
DSPACTPJ SBS(QUSRWRK) PGM(QZDASOINIT)

and
DSPSBSD, option 10 - Prestart jobs, option 5 on QZDASOINIT
Initial number of jobs . . . . . . . . . . . . . : 1
Threshold . . . . . . . . . . . . . . . . . . . : 1
Additional number of jobs . . . . . . . . . . . : 2
Maximum number of jobs . . . . . . . . . . . . . : *NOMAX
Maximum number of uses . . . . . . . . . . . . . : 200




On Thu, Jan 15, 2015 at 2:13 PM, Alan Campin <alan0307d@xxxxxxxxx> wrote:

QZDASOINIT jobs are pre-start jobs. The operating system starts them up so
it can start a job fast. How many it pre-start is based on subsystem
parameters. Also, if a job is set to re-use it will leave it hanging around
until it either times out or the job is re-used it's maximum times.

Do a dspsbsd on the subsystem and look for pre-start jobs and you will see
how many are pre-started and how many additional and how many times to
re-use.

On Thu, Jan 15, 2015 at 12:03 PM, Gary Thompson <gthompson@xxxxxxxxxxx>
wrote:

Ok, let's say I have an excel workbook with an sql statement and I've got
it open,
I expect I've got a QZ job.
Maybe my whole department has workbooks like that.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
James H. H. Lampert
Sent: Thursday, January 15, 2015 11:57 AM
To: Midrange Systems Technical Discussion
Subject: QZDASOINIT jobs breeding like gerbils

I've just received a report of hundreds of active QZDASOINIT jobs hanging
around on a customer box.

I know that a QZDASOINIT job is an SQL server job, but why would there be
hundreds of them hanging around like that? I haven't seen this behavior
before.

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.