RE: Question on QZDASOINIT jobs in QUSRWRK

Mike,

IBM monitors QZDASOINIT jobs and ends jobs if they feel there are more
running than are needed. This can cause some very unique and perplexing
things to occur. What occurs is a timing issue: The QZDASOINIT monitor
issues a controlled job end but a client was directed to the ended
QZDASOINIT job before the monitor was notified. So what you end up with is
a job that was ended being used.

I discovered the condition when a customer reported the exit program I wrote
for the SQL2 exit point showed an external program looping 30 times before
ending. The external program was only executed when a QZDASOINIT job ended.
They swore it was the exit program causing problem but it couldn't have been
since the exit program did not call the program in question. A call to IBM
resulted in the above explanation.

The solution, as I remember, was to change the number of initial jobs to the
average number of QZDASOINT jobs running at any one time. So if your system
has an average of 200 QZDASOINIT jobs running then change the number of "
Initial number of jobs" to 200. It doesn't eliminate the issue but it does
minimize it.

- Gary

-----Original Message-----


message: 8
date: Thu, 8 Jan 2009 12:35:50 -0500
from: Mike Cunningham <mcunning@xxxxxxx>
subject: Question on QZDASOINIT jobs in QUSRWRK

We current have a lot of tasks/applications/processes that use the
QZDASOINIT pres-start jobs in the QUSRWRK subsystem. Right now there are 28
of these jobs running only 5 are in the Status of PSRW (waiting for someone
to connect). The other jobs are all in use with connections from various
native java applications and windows .net applications that run all day long
(time clocks for us). According to the Subsystem description entry for the
pre-start job it is set to the shipped defaults to only start 1 at startup
(see below). We are seeing some errors at random times about these jobs
being ended that we can't explain although the value we found here for
Maximum number of uses= 200 might explain some of them. We are just
wondering if anyone has changed these shipped defaults to other values and
if so what did you change them to? Based on our normal use I would change
the Initial number of jobs to around 30. Not sure where to set the Maximum
number of uses

Program . . . . . . . . . . . . . . . . . . . . : QZDASOINIT
Library . . . . . . . . . . . . . . . . . . . : QSYS
User profile . . . . . . . . . . . . . . . . . . : QUSER
Job . . . . . . . . . . . . . . . . . . . . . . : QZDASOINIT
Job description . . . . . . . . . . . . . . . . : QDFTSVR
Library . . . . . . . . . . . . . . . . . . . : QGPL
Start jobs . . . . . . . . . . . . . . . . . . . : *YES
Initial number of jobs . . . . . . . . . . . . . : 1
Threshold . . . . . . . . . . . . . . . . . . . : 1
Additional number of jobs . . . . . . . . . . . : 2
Maximum number of jobs . . . . . . . . . . . . . : *NOMAX
Maximum number of uses . . . . . . . . . . . . . : 200
Wait for job . . . . . . . . . . . . . . . . . . : *YES