RE: SQL with connections to multiple databases

Hi Nathan,

Look up limitations on what SQL can be run when a job is in SQL server mode?

I think you will find that it is still presenting the SQL UPDATE statement to the QSQSRVR job, but now it is successful.

Regards,

Kevin Wright | IBM i Developer, LPC
+61 2 8907 0284
LANSA
Blog | Facebook | LinkedIn | Twitter
 
There's a quiet revolution afoot: lansa.com/game-changer

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin
Sent: Wednesday, 6 December 2017 5:58 AM
To: RPG programming on the IBM i (AS/400 and iSeries) <rpg400-l@xxxxxxxxxxxx>
Subject: Re: SQL with connections to multiple databases

Can you explain how hard coding a library name in an SQL update statement would bypass an QSQSRVR job? I'm afraid that I've missed the point.

On Tue, Dec 5, 2017 at 11:50 AM, John R. Smith, Jr. < smith5646midrange@xxxxxxxxx> wrote:

For everyone that was following this, I never figured out how to get
the job to disconnect from the QSQSRVR job so I gave up and hard coded
the library in the SQL update statement and that causes it to bypass
the QSQSRVR job.
I
didn't like the solution but it worked.