Mark Taylor 9.Apr.12 03:46 PM a Web browser LC LSX LC LSX - All Releases iSeries
Long story short - I'm running a Domino webserver on an iSeries, connecting to databases on another iSeries.
Since about 2009 I've been having multiple issues running agents using LSXODBC. As activity increases, I have more and more agents fail with 'Error 720: LS:DO- ODBC could not complete the requested operation.'
IBM Support has recommended that I convert my ODBC agents from *LSXODBC to *LSXLC, since LSXODBC is no longer supported.
I haven't really found a lot of good material on the care and feeding of LSXLC, but over the past week I've been able to put together an agent that I've been successful in running from my client, then modifying to get it to run on the Domino server.
So, here's one issue - I'm trying to trace the activity to see if converting the agent(s) will actually resolve the issue using CLIITRACE.
However, the LSXLC activity is unreadable - for example the trace shows:
"ëá<áäè âñ+î â|êà â<ñ+á â&ñä. â&ê|à ãê|( ä|ê&â&äëã âñ ïçáêá âñ+î +à â|êà "
" |êàáê âß â<ñ+á â&ñä."
here is a similar trace of an agent using LSXODBC :
"SELECT * FROM MYTEST.MYFILE WHERE BMKEY = ? AND BMID=734. "
Interestly enough, the LSXLC agent DOES return the correct data - so I'm guessing (?) that LSXLC is using a different code page (?) to communicate to the remote iSeries.
Is there a way to set the connection to show in plain English?