|
Why does a query have want exclusive access? Shouldn't it be shared or do you mean that other users' have exclusive access so the query can't read the records? Thanks, Jenny -----Original Message----- From: Vernon Hamberg [mailto:vhamberg@attbi.com] Sent: 05 June 2002 13:39 To: midrange-l@midrange.com Subject: RE: Query Question... Hash tables are built for, among other things, joins when there are not suitable indexes. Don't remember, but there may be hash tables used for selection, too. I'd guess there are lock problems when users come on the system. At 09:49 AM 6/4/02 -0500, you wrote: >OK, > >This was running in QBATCH... > >I just fired it up interactively and see the info message: > >Building hash table from file POLTOL1 in HD1100PD. > >So it is having to do something extra I assume ? What does this mean in >query ? > >Thanks, > >Chuck > >-----Original Message----- >From: midrange-l-admin@midrange.com >[mailto:midrange-l-admin@midrange.com]On Behalf Of Chuck Lewis >Sent: Tuesday, June 04, 2002 9:45 AM >To: Midrange-L >Subject: Query Question... > > >Hi Folks, > >We have a query (via IBM's Query) that runs FINE when no one is on the >system (2 - 3 minutes) but horrible when users are on (2+ HOURS !)... > >It is going against some files in a third package we have (Mincron's HDS >package) and involves 3 files. Primary is NOT keyed, the other 2 are. > >I fired it up as a test and when it starts running and I do Display Open >Files I see: > > Display Open Files >Job . . : QDFTJOBD User . . : CHUCK Number . . . : >342472 >Number of open data paths . . . . . . . . . . : 2 > > Member/ Record File I/O ----Open--- > Relative >File Library Device Format Type Count Opt Shr-Nbr Record >*QUERY0001 >QTEMP *QUERY0001 PHY 0 > O NO >POLTOL1 HD1100PD POLTOL1 LGL 0 I NO > > >Is that *QUERY0001 an access path being built ? > >Been a LONG time since I messed with this stuff and a vague recollection >says yes... > >Thanks ! > >Chuck > >_______________________________________________ >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 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 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.