×
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.
An alternative to embedded SQL is using SQL CLI (call level interface). This is very similar to ODBC, and the SQL can be executed either in line in the job or in SQL server mode in a separate QSQSRVR job.
Perhaps program B has invoked SQL server mode for the job (given that it is interacting with a QSQSRVR job) which then restricts somewhat what can be done in SQL for the remainder of the job.
I am not aware of any way of revoking that SQL server mode for a job once it has been established.
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
On 29 November 2017 at 18:05, John R. Smith, Jr.
<smith5646midrange@xxxxxxxxx> wrote:
I know I can write a program on Windows or Unix that connects to DB2
via ODBC but is there an ODBC driver that runs on the iSeries to allow
an iSeries program to connect to the DB2 that it is running on?
I'm guessing at this point that Program B is not cleaning up after
itself
How do I get the job to disconnect from the QSQSRVR job before the
update in JOB_END?
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.
midrange.com
