Re: ODBC performance problems

How many users are firing off these jobs? Normally, you'll get one
qzdasoinit job per user, but the gotcha is that if they get impatient, or if
they kill the query midstream, it can leave many instances of the qzdasoinit
job running. Been there, seen that.

Paul Nelson
Braxton-Reed, Inc.
630-327-8665 Cell
708-923-7354 Home
pnelson@braxton-reed.com
----- Original Message -----
From: <ouuch@t-online.de>
To: <midrange-l@midrange.com>
Sent: Tuesday, October 22, 2002 5:02 PM
Subject: ODBC performance problems


>
>     Hello,
>
>     I have a problem with an ODBC job here, running on an NT server
machine.
>     It read/writes to a single OS/400 file (via SQL). The software is
written
>     by a 3rd party programmer, so I can only give tips and hints. And I
have
>     no or minimal experience with ODBC access.
>
>     On the AS/400, there is an QZDASOINIT job running that handles the
ODBC
>     requests. I never see any error messages on the AS/400, but at a point
in
>     time, the job will end and another one start - several hundreds in an
>     hour, one after the other. After some time, these submits stop and the
>     job runs normally for some hours.
>     In NETSTAT (on the AS/400), I also see the NT server opening and
closing
>     one port after the other - the ports are in status "wait" and will
close
>     after a time-out, while the server opens new ports.
>
>     So, I'd like to know when OS/400 decides to end/start an QZDASOINIT
job
>     or which ODBC-Transactions will do this?
>
>     Basically, the NT server regularly checks for new records in the file,
>     processes these and will finally update the records.
>
>     The select/updates are working, but only very slowly sometimes.
>
>     I'd like some suggestions what to do on the AS/400
(trace/dump/whatever)
>     to get a handle on the problem.
>
>     Thanks for your input,
>
>     Oliver Wenzel
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> _____________________________________________________
> This message scanned for viruses by CoreComm
>