RE: ODBC/QZDASOINIT Messages

While I'm not a db2-400 gear-head, I would expect this to be a simply
matter of db optimization (caching) enabling the results to be returned
without locking the file.

Joe Hayes
Fiserv Property and Casualty Solutions
direct: 319.398.1831
cell: 319.573.8877
800: 800.928.9926
Joe.hayes@xxxxxxxxxx
 
This email may contain confidential and privileged material for the sole
use of the intended recipient(s). Any review, use, distribution or
disclosure by others is strictly prohibited. If you are not the intended
recipient (or authorized to receive for the recipient), please contact
the sender by reply email and delete all copies of this message.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Monnier
Sent: Friday, March 09, 2007 1:39 PM
To: Midrange Systems Technical Discussion
Subject: RE: ODBC/QZDASOINIT Messages

Frank,

Could be several things.  Client closed the cursor(s), number of uses
was exceeded and an new job started, exit program closed the cursor(s)
(RCLRSC for example), etc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of fbocch2595@xxxxxxx
Sent: Friday, March 09, 2007 10:57 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: ODBC/QZDASOINIT Messages


Another question on these jobs.  
 
When I run the select statement (using winsql) and I get the results on
my screen I wrkjob qzdasoinit and I see open files (via option 14 from
wrkjob).  Then, when I run the very same select statement again I don't
see any open files.  I'm waiting for IBM to get back to me on this but
does anyone know why the job would display files then when the same
statement is run again, no open files? 
 
Thanks, Frank