Re: SQLCLI program calling another SQLCLI program.

Thank you so much Scott... I found all that information and more about the
API. I just could not decipher the conversion from C. I think I can
figure out the rest from here. Just downloaded your copybook too. We
have one copy already for SQL CLI but it never hurts to check out another.
I'll get this going and see what that darn error is.

Thanks again.



Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>
02/07/2008 06:02 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.






I'm not precisely sure what you're looking for, but... Here's the
prototype that I use for SQLError:

D SQLError PR extproc('SQLError')
D like(SQLRETURN)
D henv like(SQLHENV) value
D hdbc like(SQLHDBC) value
D hstmt like(SQLHSTMT) value
D szSqlState 6A
D pfNativeErr like(SQLINTEGER)
D szErrorMsg 513A options(*varsize)
D cbErrMsgMax like(SQLSMALLINT) value
D pcbErrorMsg like(SQLSMALLINT)

Here's a link to the page of the Information Center that describes the
API:
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/cli/rzadpfnerror.htm


Since you're trying to get error info on an SQLConnect, you won't have a
statement handle, so supply the constant SQL_NULL_HSTMT for the 3rd
parameter.

If you like, you can get my entire RPG copybook for SQL CLI from the
following link:
http://www.pentontech.com/IBMContent/Documents/article/53024_153_ProcWithParm.zip





JLong@xxxxxxxxxx wrote:

Now that my teeth are pretty well ground flat... Scott. Can you or
someone else assist me in how to get SQLError() to execute. Not asking

for much but an example in some form of RPG would be most excellent.

Thanks in advance
Jack Long
CBK Ltd.





JLong@xxxxxxxxxx
02/07/2008 02:07 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.






Scott wrote:
When an SQL CLI procedure fails, you need to call SQLError() to
determine why it failed. (-1 only means "SQL_ERROR", and doesn't tell
you anything more than "an error occurred".) Call SQLError to get an
SQLState or SQLCode that will tell you which error occurred.


Thanks Scott

I just pieced together a couple of things from a day and a half research

through everything Google and the manual.... Changes made were to have
ProgramB in ACTGRP(*CALLER) and pass henv and hdbc from ProgramA to
ProgramB and bypass the connection and disconnect code. Going to go

back

and see what SQL_ERROR tells me before gritting my teeth and leaving it
this way.