Re: Error 243

----- Original Message ----- To: csmith@unitedtexas.com At: 3/17 14:00 Most commonly these are transient locks by another session causing a session performing a table scan without SET LOCK MODE TO WAIT to error out when encountering a temporarily locked row. One solution is to make sure that all of the tables have their statistical distributions updated using the recommended suite of UPDATE STATISTICS commands found in the Performance Guide (and implemented for you in several scripts and in my dostats utility all available from the IIUG Software Repository). Table scans are often unneccessary and caused by out-dated stats. Dostats is part of the package utils2_ak. BTW if you run onstat -g ses <sessid> immediately after the 3rd party app reports its error, if it has not aborted, the last SQL and ISAM errors for the session are reported there. Art S. Kagel ----- Original Message ----- From: Chad Smith <csmith@unitedtexas.com> At: 3/17 13:09 > Using a third party software as the front end to our database, an error code of > 243 was returned while running a job. I looked up the error, but I'm still > unsure as to why this error occurred. Also, I could not find the associated ISAM > error code that was said to contain more information (S1000). Any information on > what would cause this type of error or any solutions going forward would be > greatly appreciated!