Re: Embedded SQL and Remote D-Base Connectivity

It ain't going to happen with the CRTSQLRPGI command.  
Think about it.  Let's say you're a software developer 
designing a package to be distributed.  Having it create 
the SQL package with the compile command would make little 
sense, especially with the CONNECT to statement is probably 
going to parameter driven.

Before we delve any deeper let's try the following.
On the local machine:
STRSQL
connect to S1025Y8M
select * from rmtlib/rmtfile

And see if that works.  Then we'll see if it is a program 
issue.

You did do the WRKRDBDIRE on both machines did you?  And, 
you did add the *LOCAL on both, right?






bellis@ORIENTAL.COM on 04/25/2000 01:30:14 PM
Please respond to RPG400-L@midrange.com@Internet
To:     RPG400-L@midrange.com@Internet
cc:      
Fax to: 
Subject:        Re: Embedded SQL and Remote D-Base Connectivity



I have the "connect to xxxxx" statement  in the program.  However, it's still
looking for the SQL Package on the remote system.  The only way I can get the
program to not look for the SQL package is to specify *NONE on the RDB
parameter.  If I specify *NONE then I can't get connected to the remote
database.  It appears to me like the SQL Package is required.
If that's the case how do I get it to automatically create the package on remote
system with the CRTSQLRPGI command?

Thanks,
Brian Ellis










Rob Berendt <rob@dekko.com> on 04/25/2000 08:38:33 AM

Please respond to RPG400-L@midrange.com
                                                                                
                                                                                
                                                                                


                                                              
                                                              
                                                              
 To:      RPG400-L@midrange.com                               
                                                              
 cc:      (bcc: Brian Ellis/OTC)                              
                                                              
                                                              
                                                              
 Subject: Re: Embedded SQL and Remote D-Base Connectivity     
                                                              








You've made a great start with the WRKRDBDIRE.  I don't
believe you need the remote package.  Look up the SQL
statement CONNECT TO.  That will do it for you.





bellis@ORIENTAL.COM on 04/24/2000 02:46:53 PM
Please respond to RPG400-L@midrange.com@Internet
To:  RPG400-L@midrange.com@Internet
cc:
Fax to:
Subject:  Embedded SQL and Remote D-Base Connectivity



Can anyone point me to a good reference or example on how to create embedded SQL
programs that need to access remote databases in an multi AS/400 environment.
We are using the CRTRGPSQLI command.
Some of the issues I'm unclear on is:
1) Do we need an SQL package created on the remote system?
2) If we need it how do we automatically get the package created on the remote
system?
3) Is there an easy way to specify the remote system to connect to at run time?

I've got the DB2 for AS/400 SQL Programming and Distributed Database Programming
manuals in front of me. However, these do not clearly explain what I need to put
it all together.

Thanks in advance,
Brian Ellis.

P.S.
The databases are entered into the Remote Database Directory Entry.
The following is an example of how one of them is setup:
Relational database  . . . . . . :   S1025Y8M
Remote location:
  Remote location  . . . . . . . :   S1025Y8M
    Type . . . . . . . . . . . . :   *SNA
  Device description . . . . . . :   QYCTSOC
  Local location . . . . . . . . :   *LOC
  Remote network identifier  . . :   *LOC
  Mode . . . . . . . . . . . . . :   QYCTSOC
  Transaction program  . . . . . :   *DRDA



+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---