RE: Calling a DB procedure from another DB

Sorry, Ali ... can't help you as I've not actually used this myself.  Just 
happened to have run across it.

But if you do get it working, be sure and post back the details to this list.

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 
> ali.juzer@xxxxxxxxx
> Sent: Wednesday, May 18, 2005 10:00 AM
> To: midrange-l@xxxxxxxxxxxx
> Subject: RE: Calling a DB procedure from another DB
> 
> 
> 
> Thanks Charles!
> 
>  I am now able to call CL, COBOL, RPG programs using the
> DBMS_HS_PASSTHROUGH.EXECUTE_NON-QUERY function. But now, 
> another problem
> has popped up:
> 
> It works fine if my AS/400 program does not have any parameters or has
> only input parameters. But if my program has any output 
> parameters, then
> the call fails. I am using the proper sequence (open_cursor,
> parse,bind_variable etc)
> 
> Any pointers/idea on why is this happening?
> 
> Regards,
> Ali Asgar Juzer
> 
> -----Original Message-----
> From: midrange-l-bounces+ali.juzer=wipro.com@xxxxxxxxxxxx
> [mailto:midrange-l-bounces+ali.juzer=wipro.com@xxxxxxxxxxxx] On Behalf
> Of Wilt, Charles
> Sent: Friday, May 13, 2005 9:30 PM
> To: Midrange Systems Technical Discussion
> Subject: RE: Calling a DB procedure from another DB
> 
> Update....
> 
> While it remains true that you can't seem to use a simple 
> CALL statement
> with Generic Connectivity.
> 
> You may find DBMS_HS_PASSTHROUGH to be of use....
> 
> Good luck finding examples of how to use it though.  So far 
> I've found:
> http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPL
> AYID:47437
> 19073967
> 
> There's some information about Passthrough SQL using 
> DBMS_HS_PASSTHROUGH
> in the Heterogeneous Connectivity Administrator's Guide manual.
> 
> 
> HTH,
> 
> 
> 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 Wilt, Charles
> > Sent: Friday, May 13, 2005 9:12 AM
> > To: Midrange Systems Technical Discussion
> > Subject: RE: Calling a DB procedure from another DB
> >
> >
> > The problem is that the OBDC connection between Oracle and
> > DB2, called "Generic Connectivity" by Oracle, does _NOT_
> > support the SQL CALL statement.
> >
> > To invoke stored procedures on an external database from
> > Oracle, you need Oracle's Transparent Gateway product; which
> > costs big $$$.
> >
> >
> >
> >
> >
> > Charles Wilt
> > iSeries Systems Administrator / Developer
> > Mitsubishi Electric Automotive America
> > ph: 513-573-4343
> > fax: 513-398-1121
> > 
> >
> > > -----Original Message-----
> > > From: midrange-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx
> > > [mailto:midrange-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx]On
> > > Behalf Of
> > > R Bruce Hoffman
> > > Sent: Friday, May 13, 2005 8:16 AM
> > > To: Midrange Systems Technical Discussion
> > > Subject: Re: Calling a DB procedure from another DB
> > >
> > >
> > > On Fri, 2005-05-13 at 01:13, ali.juzer@xxxxxxxxx wrote:
> > > > We have two databases - Oracle 8i running on a Windows 2K
> > > machine and
> > > > DB2/400 running on a AS/400 machine. There is an ODBC
> > > connection between
> > > > these two databases. We use SQL commands in Oracle to
> > access DB2/400
> > > > files.
> > >
> > > > Our requirement is to call a Cobol program residing in 
> AS/400 from
> > > > Oracle. Is this possible? Can anyone help me with some code
> > > snippets?
> > >
> > > Nothing unique about the COBOL program. Just use the SQL 'create
> > > procedure' statement to make it a stored procedure on the
> > 400. Then a
> > > standard SQL CALL can get at it.
> > >
> > >
> > > --
> > > "Bigamy is having one wife too many. Monogamy is the same."
> > > -- Oscar Wilde
> > >
> > > --
> > > 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.
> >
> >
> 
> --
> 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.
> 
> 
> 
> 
> Confidentiality Notice
> 
> The information contained in this electronic message and any 
> attachments to this message are intended
> for the exclusive use of the addressee(s) and may contain 
> confidential or privileged information. If
> you are not the intended recipient, please notify the sender 
> at Wipro or Mailadmin@xxxxxxxxx immediately
> and destroy all copies of this message and any attachments.
> 
> -- 
> 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.
> 
>