Re: SQL CLI question

[thomas@xxxxxxxxxxx]

Michael:

On Thu, 07 February 2002, J Michael Smith wrote:

> Can anyone shedd some light on why this is happening, because my perference
> is to not have the "COMMIT" statement in the program if possible.

Without knowing some details about the transactions and configurations, it's 
hard to say much about the need for COMMIT. But in really general terms, I can 
at least list a few statements from the end of an RPG SQL CLI that I use. 
Multiple connections aren't a problem for me. Statements are:

C                   eval      SQL_RC = SQLFreeStm(
c                                                  hstmt     :
c                                                  SQL_DROP
c                                                )
C                   eval      SQL_RC = SQLTrans(
c                                                henv        :
c                                                hdbc        :
c                                                SQL_COMMIT
c                                              )
C                   eval      SQL_RC = SQLDisconn( hdbc )
C                   eval      SQL_RC = SQLFreeCon( hdbc )
C                   eval      SQL_RC = SQLFreeEnv( henv )

and I suppose the place to start looking is just before SQL_RC = SQLDisconn( 
hdbc ).

Although I don't have an explicit COMMIT, I do use the SQLTrans() API with the 
SQL_COMMIT value specified. SQLTrans() is the prototyped SQLTransact(). If this 
is what you are referring to, can you describe why a COMMIT is not desired?
Have you researched SQLTransact()?

Tom Liotta


--
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone  253-872-7788
Fax  253-872-7904
http://www.400Security.com


___________________________________________________
The ALL NEW CS2000 from CompuServe
 Better!  Faster! More Powerful!
 250 FREE hours! Sign-on Now!
 http://www.compuserve.com/trycsrv/cs2000/webmail/