× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Based on what is in the joblog, I am assuming it is not using the QSQSRVR
job. Without the library hardcoded, the below is written to the joblog.
With the library hardcoded, this does not exist.

SQL7908 Completion 00 11/28/17 12:18:14.407035 QSQROUTS
QSYS *STMT QXDAEVT QSYS *STMT
From module . . . . . . . . :
QSQSRVRC
From procedure . . . . . . :
SQSERVER
Statement . . . . . . . . . : 8315

To module . . . . . . . . . : QXDASQL

To procedure . . . . . . . :
QXDA_SQL
Statement . . . . . . . . . : 4458

Message . . . . : Job
517546/QUSER/QSQSRVR used for SQL server mode
processing.

Cause . . . . . : A Structured Query
Language (SQL) statement was executed
while running in SQL server mode.
SQL statements for this connection or
thread will be processed in job
517546/QUSER/QSQSRVR. Technical description
. . . . . . . . : SQL server mode
was requested by either setting the SQL
server mode job attribute, or by
setting the server mode environment
attribute via the SQL Call Level
Interface. When running in this mode, SQL
statements are processed by a
separate job, which runs under the user
profile specified for the connection.
The thread identifier is -1 and the
connection is to Relational Database
XXXXXXXXXX. If the Relational Database
name is *N, this means that all
connections for the thread will use the same
job.


-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Kevin
Wright
Sent: Tuesday, December 5, 2017 4:37 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
<rpg400-l@xxxxxxxxxxxx>
Subject: 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.

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.