Re: Embedded SQL and Remote D-Base Connectivity

[bellis@xxxxxxxxxxxx]

Sorry, I neglected to mention the results on the interactive SQL.
Yes, we are able to connect to and access data on the remote databases using the
"Connect to" statement within an Interactive SQL session.
Back to the Embedded SQL program. If I don't have the package on the remote
system the program fails on the local system and I get the following error (see
below).  Basically it says I need the SQL Package.  If the SQL Package exists
the program runs correctly.  I'm going to continue with the assumption that the
SQL Package MUST be on the remote system for this to work using DRDA.

Message ID . . . . . . :   SQL0805       Severity . . . . . . . :   30
Message type . . . . . :   Diagnostic
Date sent  . . . . . . :   04/27/00      Time sent  . . . . . . :   09:07:17

Message . . . . :   SQL package LSTCLSFCN in PRDOTCOBJ not found at DRDA
  Server.
Cause . . . . . :   A remote request was attempted to S1025Y8M for SQL package
  LSTCLSFCN in PRDOTCOBJ. The SQL package was not found.  If you are using
  Interactive SQL or Query Manager, an attempt to create a package on the
  remote system failed (see common cause below) and the package requested does
  not exist.
Recovery  . . . :   The most common cause of this problem in an Interactive
  SQL session to a non-AS/400 server is that the connection is not updateable.
   In that case the package cannot be automatically created.  To ensure the
  connection is updateable, do a RELEASE ALL command followed by a COMMIT
  before connecting to the remote system.
  In other cases, the SQL package can be created by using the CRTSQLPKG
command.  Also, precompiling an SQL program with the RDB parameter specified
will create an SQL package on the remote system.  Create or restore the SQL
package.  Run the application again.
  If you are using Interactive SQL or Query Manager, exit the product and
enter a CL COMMIT or ROLLBACK command. This will enable you to continue
processing at the local system. Determine why the package creation failed by
examining the job log. Correct the problem and attempt the Interactive SQL
or Query Manager session again.


Thanks for all of your suggestions.
Brian Ellis





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