|
That depends on the driver being used to connect. If you are using a DB2 driver then you may be connecting using DRDA. In that case you will need a DDM exit program but it only fires for DRDA connects. You can connect with OLEDB, which can be configured to do record io, and it will also use the DDM server. If you are using the Client Access ODBC driver then you will using the QIBM_QZDA_* exits. INIT will always be called, NDB may be called but not for processing an SQL request. If you have a program registered on SQL2 then it will always be called even if you have a program registered on SQL1. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren Sent: Wednesday, September 15, 2004 7:55 AM To: Midrange Systems Technical Discussion Subject: RE: Crystal Reports and Exit Points. Tim, I am guessing you are connecting to the iSeries with ODBC so the QIBM_QZDA_INIT would be invoked at connection time and I think the QIBM_QZDA_NDB1 for DB I/O. Pete Helgren > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Hatzenbeler, Tim > Sent: Tuesday, September 14, 2004 5:24 PM > To: 'Midrange Systems Technical Discussion' > Subject: Crystal Reports and Exit Points. > > > Does anybody know what exit points are used when Crystal Reports makes an > SQL Call? I thought it would be _sql1 and _sql2 but it doesn't seem to be > that one... Unless my test case is wrong, but when I do an excel > transfer it > uses _sql2 > > any ideas.. > > Thanks, tim > This e-mail message, including any attachments, is for the sole use of the > intended recipient(s) and may contain confidential or privileged > information. Any unauthorized review, use, disclosure or distribution is > prohibited. If you are not the intended recipient, please contact the > sender by reply e-mail and destroy the message. > -- > 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. > -- 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.
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.