Tweet
Rachel, There are some options: 1) Free Statement Handle of the failing SQL statement 2) Disconnect to the database and Connect again 3) Free Connection and Environment Handles and start all over again. If you close all handles, you should be able to run the programmes again. If the CLI programma is run from a menu or the command line regularly, I would opt for free all handles, and disconnecting from the database. Regards, Carel Teijgeler
-
-
Problem with CLI errors
I am using SQL CLI from RPG ILE programs. If a CLI API has a problem, (e.g. a syntax error in the SQL statement), that statement fails to execute, and I can detect this by examining the return value. My problem is that all subsequent CLI calls in that job fail, even though they are perfectly correct. It behaves as though the error leaves the SQL environment in a damaged condition. Reclaim activation groups does not put things right. The only cure seems to be ending the job. Does anyone know how to prevent this? Thank you Rachel -
Problem with CLI errors
Thanks Carel, I'll try that.Comment
Comment