|
Paul, Interesting idea. I think it would work. But it'd be nice if Oracle would just allow you to use a basic built-in capability of ODBC. But of course they want you to pay the big extra $$$. Charles Wilt iSeries Systems Administrator / Developer Mitsubishi Electric Automotive America ph: 513-573-4343 fax: 513-398-1121 > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Paul Morgan > Sent: Friday, May 13, 2005 2:21 PM > To: midrange-l@xxxxxxxxxxxx > Subject: Re: Calling a DB procedure from another DB > > > Couldn't you set up a new DB2 table/trigger just to call this program? > > Have the table defined with all the fields required to call > the program > (including any possible returned values) plus some artificial > key if you > need to retrieve any returned values. Write the trigger > program to convert > the passed record image into a call to the program. If the > program returns > any values have the trigger program put those values in the record. > > To execute the call INSERT a row to the table using ODBC to call the > program. SELECT that row back from the table using the > artificial key if > you need any returned values. > > Paul > > -- > Paul Morgan > Senior Programmer Analyst - Retail > J. Jill Group > 100 Birch Pond Drive, PO Box 2009 > Tilton, NH 03276-2009 > Phone: (603) 266-2117 > Fax: (603) 266-2333 >
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.