Are you describing the Debug window inBuilder? If so you will need to switch on Debugging (level 1 and verbose) togenerate the thread files in a running system. Switching this on will alsocause the generation of trace files if Oscript code fails.
Phil
From:eLink Discussion: Development Discussion[mailto:development@elinkkc.opentext.com]Sent: 10 September 2009 10:59To: eLink RecipientSubject: oScript log in realLiveLink
oScript log in real LiveLink
Posted by thanh.ho@mottmac.com (Ho, Thanh) on 2009/09/10 05:56
In Builder, when an oScript code is run, I can see output stream in an output window and when error occurs, the Builder opens up a debug window to tell me the error. I would like to know where I can find similar information in a real running system. I think there ought to be a file playing the role of an output stream (like the output window) and a file logging all errors from oScript. Additionally, if there is any reason that a piece of oScript code can not be loaded/run, I think it would be logged somewhere as well. Does anyone know about these? Thanks.
Correct with the debug=1 or (2 is finealso and may give more). Verbose is in the Options section. Both can beconfigured in the Admin Pages.
The files are dumped into the logs folder.
I would recommend an Livelink Administrationcourse or similar as this sort of stuff is required knowledge if you are coding.
From:eLink Discussion: Development Discussion[mailto:development@elinkkc.opentext.com]Sent: 10 September 2009 12:20To: eLink RecipientSubject: Phil,
Phil,
Posted by thanh.ho@mottmac.com (Ho, Thanh) on 2009/09/10 07:19
In reply to: RE oScript log in real LiveLink
Posted by philipforshaw (Forshaw, Philip) on 2009/09/10 06:29
Phil, how do I switch it on? Is that "Debug=1" in [general] section in opentext.ini? And where will the generated files be? Thanks, Thanh