|
Hi, Vern: I think that DRDA might be part of the architecture; I think on newer OS/400 releases, it is called "DB2 Multisystem" -- all I know is, in ISQL (aka. STRSQL), it "all just works!"... (assuming the other machine is configured on the network, etc., and has been given a "Database name"... e.g. ADDRDBDIRE, WRKRDBDIRE) Mark ----- Original Message ----- From: "Vernon Hamberg" <vhamberg@attbi.com> To: <midrange-l@midrange.com> Sent: Wednesday, October 09, 2002 4:40 PM Subject: RE: DDM and SQL > Kirk > > Are you thinking of DRDA? That's how SQL gets to another system. I believe > the statement is sent to the other system (probably in a DDM session) and > then the work happens remotely, with only the result passed back. Terms > like RUW and DUW (remote and distributed unti of work, resp.) are used > here, so I suspect the work is at the other end. Hope so, anyway. > > Vern > > At 04:28 PM 10/9/02 -0600, you wrote: > >Kirk, > > When I use STRSQL or RUNQRY over a DDM file I get the message, > >"QRY1609 - File PCRPACHR in PCRDDMFILE is not a data base file, cannot > >query." Or "SQL7001 - File PCRPACHR in PCRDDMFILE not database file." > > > > > >Thank you, > >Matt Tyler > >Mattt@wincofoods.com > > > >-----Original Message----- > >From: Kirk Goins [mailto:kirkg@pacinfosys.com] > >Sent: Wednesday, October 09, 2002 16:22 > >To: Midrange-L (E-mail) > >Subject: DDM and SQL > > > >OK you database and DDM Gurus... > > > >I'm not looking for a why or why not to do this, I'm looking for HOW it does > >it.. > > > >Let's assume on a local machine I use SQL to select say 5,000 records from > >say a 100,000 record file and assuming that the query optimizer uses a seq > >read to get those 5,000 records... there is lots of I/O > > > >Now Let's move the data to a remote system and use DDM. Does the machine > >with the ACTUAL DATA do all the work and only return the 5,000 records > >across the link or does EVERY Record get passed via DDM the source machine > >which throws out the unwanted? > > _______________________________________________ > 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.