Just when I thought that did it.   But that's what I sometimes get for 
thinking. :-)    This CLI methodology is still giving me fits.  The 
solution I had found, with assistance, has gotten me past the multiple CLI 
connections to the database but now I have another problem.
My second program is calling a procedure in a service program by using a 
stored procedure.   I know all of that is setup correctly because when I 
call the program first it runs just fine.   When it is the second called 
program SQLError() gives me an SQL0444 error message stating that the 
procedure cannot be found.  I know it's not the library list because while 
in debug when the error occurs I can check for the service program and 
wrkobj *LIBL finds it.   And the server job that starts with the 
connection contains the library where the service program is located.
Just curious if anyone else has an idea about this new set of information. 
  I have spent a lot of time in the manual (several releases) and google.  
Just wonder too if this is a bug that needs reporting.   Because of time 
constraints after spending all this time researching it I just don't have 
time to contend with gathering enough sample programs to prove it and turn 
in the issue.
Thanks again in advance.
Jack Long
CBK Ltd.
JLong@xxxxxxxxxx 
02/10/2008 10:44 PM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
To
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
cc
Subject
Re: SQLCLI program calling another SQLCLI program.
Big thanks to Scott Klement for getting me on the right track.
Trouble I was having with one CLI program calling another was that the 
second program was doing an additional connection to the database. 
According to the manual this additional connection in the same envrionment 
is not approved by the system.  The error I was getting was SQL0842 or 
08002.  It just doesn't imply what to do when you need to do this. (Unless 
I just missed it...)   Further digging I found the switch in the manual 
that changes the environments connection to server mode.   This 
essentially forces each connection into it's own server job so that 
multiple CLI programs can be called.
Thanks again
Jack Long
CBK Ltd.
As an Amazon Associate we earn from qualifying purchases.
	
 
This mailing list archive is Copyright 1997-2025 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.