Re: Embedded SQL and Remote D-Base Connectivity

[Rob Berendt <rob@xxxxxxxxx>]

I was just compiling an SQL program myself.  I stand 
corrected on the SQL package statement of the compile.

However did you do the steps I recommended regarding 
testing the CONNECT statement with interactive SQL first?





bellis@ORIENTAL.COM on 04/26/2000 04:03:22 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



Rob,
At the bottom of this message is an excerpt that came directly out of the DB2
for AS/400 SQL Programming V4R3 manual.
The way I read this is that the package is to be created on the remote database
that is specified in the RDB parameter.
I finally got it to work where it actually does create the package on the remote
 d-base.
I was trying to compile it as a *module object and needed it to created it as a
*pgm object.
What I need to know is do we absolutely have to have the package created to get
this to work?


24.3 SQL Package Support
The OS/400 program supports an object called an SQL package. (OS/400 object type
 is *SQLPKG.) The SQL
package contains the control structures and access plans necessary to process
SQL statements on the
application server when running a distributed program. An SQL package can be
created when:

  The RDB parameter is specified on the CRTSQLxxx command and the program object
 is successfully
    created. The SQL package will be created on the system specified by the RDB
parameter.

    If the compile is unsuccessful or the compile only creates the module
object, the SQL package will not be
    created.

Thanks,
Brian Ellis.








Rob Berendt <rob@dekko.com> on 04/26/2000 08:59:40 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     
                                                              








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?





+---
| 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
+---


+---
| 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
+---