Set debug file before tracing stored procedures (-648)
Posted in 2000
Topics: Stored Procedures & SPL
Hi there, I am running Informix 7.31 TC7 on NT and everything is seems to be working fine except that nobody can write to the error log file that I specify in my procedures (using SET DEBUG FILE TO ...), even though the file is fully accessible by everybody when not accessed through informix. We've had a very similar problem with informix 7.31 UC2 running on SCO Unix 5.05 and we overcame this problem by starting up informix as a different user (I believe we were originally running it as root and then we changed this to user informix). We've tried all sort of things with NTs but we haven't been able to resolve this issue. Any ideas/suggestions are greatly appreciated. Ta lots -- Ioannis Demetriades CTL Ltd.
> I am running Informix 7.31 TC7 on NT and everything is seems to be working > fine except that nobody can write to the error log file that I specify in my > procedures (using SET DEBUG FILE TO ...), even though the file is fully > Any ideas/suggestions are greatly appreciated. Can you post your code concerning "SET DEBUG FILE TO ..." ? I got your error message when I used any path arguments in the string. Try "SET DEBUG FILE TO 'fred'"... does that work ? Hth, Chris
Chris,
Thanks for the hint. I will ask our client to try it and I will let you
know.
Here is the code:
Create DBA Procedure test()
Define fTest char(15);
set debug file to "\\tmp\\testing.txt";
Let fTest = "TESTING";
trace ' fTest= ' || fTest;
End Procedure
Document '<1=Lakis=20/06/2000 1:00:56 PM>Version X.Y.Z DESCRIPTION GOES
HERE';
The path of the trace file is a valid path.
----- Original Message -----
From: Chris Brauer <funky@funkytown.de>
Newsgroups: comp.databases.informix
Sent: Wednesday, June 21, 2000 11:02 AM
Subject: Re: Set debug file before tracing stored procedures (-648)
> > I am running Informix 7.31 TC7 on NT and everything is seems to be
working
> > fine except that nobody can write to the error log file that I specify
in my
> > procedures (using SET DEBUG FILE TO ...), even though the file is fully
> > Any ideas/suggestions are greatly appreciated.
>
> Can you post your code concerning "SET DEBUG FILE TO ..." ?
> I got your error message when I used any path arguments in the string.
> Try "SET DEBUG FILE TO 'fred'"... does that work ?
>
>
> Hth,
>
> Chris
>