Re: Life cycle of QZDASOINIT

Kind of and maybe.

The QZDASOINIT jobs are Pre-started by the OS, so by design, there
should be jobs waiting to service clients before the request comes in.
If you get enough requests at once, some requests may have to wait
till more jobs are started. Look at the ADDPJE command:

Start jobs . . . . . . . . . . . STRJOBS *YES
Initial number of jobs . . . . . INLJOBS 3
Threshold . . . . . . . . . . . THRESHOLD 2
Additional number of jobs . . . ADLJOBS 2
Maximum number of uses . . . . . MAXUSE 200

So when the subsystem starts, the system will start 3 jobs (INLJOBS).
Once the available jobs drops below 2 (THRESHOLD) the system will
start 2 more jobs (ADLJOBS).

When a connect is closed, by default the QZDASOINIT job goes make into
the available pool for reuse. Each job will be reused up to 200
(MAXUSE) times. If you set MAXUSE to 1, then the job will be ended
when the connection is closed.

A nice description of the Lifecycle of the QZDASOINIT jobs:
http://www.centerfieldtechnology.com/publications/archive/August%202005%20Newsletter.pdf


HTH,

Charles

On Mon, Jul 13, 2009 at 9:47 AM, Lim
Hock-Chai<Lim.Hock-Chai@xxxxxxxxxxxxxxx> wrote:

Is it correct for to say that QZDASOINIT job will get auto started by
the OS when client request a JDBC/ODBC connection.  This job will get
ended by the OS OS when client closes the JDBC/ODBC connection?

thanks
--
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.