Re: SQLIDEBUG environment variable

The trouble with this genious program sqliprint is that you get enough information on its syntax by typing sqliprint -? But the output of sqliprint is unreadable with standard editors like "vi", so what option must we put in the commandline of sqliprint to get a readable Output? Jonathan Leffler wrote: > > Dbsv wrote: > > > Hello everybody, > > > > Does anyone know the differents values that you can set this environment > > variable in order to trace SQL statements. > > > > I know that sqliprint will allow to view the resulting file containing the > > trace, but I don't have all of the values or event some of them for the > > SQLIDEBUG variable. > > Check the archives (at www.deja.com if necessary). > > The main usable value is, IIRC, SQLIDEBUG=2:somename > This creates a binary file such as somename_22319 for process 22319, and you > can use sqliprint on that file. > > You need to go to the archives 'cos I'm working from memory and I'm not sure > I've > got it right, but I gave the correct answer, oh, 6 months ago. > > -- > Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) > Guardian of DBD::Informix v0.95 -- see http://www.perl.com/CPAN > #include <disclaimer.h>

Christian Winterhager wrote: > The trouble with this genious program sqliprint is that you get enough > information on its syntax by typing > > sqliprint -? > > But the output of sqliprint is unreadable with standard editors like > "vi", so what option must we put in the commandline of sqliprint to get > a readable Output? > Christian, since the output of sqliprint is supposed to be plain ascii format vi should work fine. Are you getting anything different? Did you set the SQLIDEBUG environment variable to "2:filepath"? If the value of SQLIDEBUG starts with characters other than "2:" the file written may not be readable by sqliprint. Hope this helps, Heiko