RE: QDZASOINIT

["Gary Monnier" <gary.monnier@xxxxxxxxxxxxx>]

Steven,

Since QZDASOINIT jobs are prestart jobs you can control then to some
extent.  Display subsystem QUSRWRK's (or what ever subsystem you have
QZDASOINIT running in) description and take option 10 to list prestart
job entries.  Then take option 5 against QZDASOINIT.  

You can fine tune the number of jobs active at any time by manipulating
the maximum number of jobs and maximum number of uses parameters.  If
you have an ever increasing numbe of QZDASOINIT jobs I suspect the max
number of jobs parm is at *NOMAX or some huge number.  Use the CHGPJE
command to alter the settings.  For example the command below will allow
for a maximum of 50 QZDASOINIT jobs active and each one is used 5 times
before ending and another starts in its place.

CHGPJE SBSD(QUSRWRK) PGM(QSYS/QZDASOINIT) MAXJOBS(50) MAXUSE(5) 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steven DONNELLAN
Sent: Friday, February 06, 2004 11:53 AM
To: midrange-l@xxxxxxxxxxxx
Subject: QDZASOINIT


We have a programmer who is using JDBC to access AS/400 data from a
'web' front end.  Every time he executes a Query to get data from the
AS/400 a job is started called QDZASOINIT.  One of these is created for
every Query (eg 1 for getting the Customer Details, another for getting
the Customer Transaction History etc etc).  The problem we have got is
that these jobs don't end, and the number of them grows at an alarming
rate affecting all over system performance.  Is this a known problem
with OS/400, or something that the programmer is doing wrong?  We are
V5R2, and coding in MS J++.  Code snippets would be nice, as I don't
speak Java, and it would help me get a better understanding of what's
going on at the client side.
PS, thanks to those of you who responded to me earlier this week on my
original Java question
 
Steven Donnellan
=========================================
This email has been scanned for viruses, because I care!
=========================================
 
_______________________________________________
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.