gavin_wusj
21st November 2003, 05:09
Hi,
Which table can I find session list in, I need view all the sessions ,I have found the sessions table "ttadv200",but it have not description, and I need it, what can I do?
Gavin
11/21
OmeLuuk
21st November 2003, 09:00
Did not try to resolve it with setting a DBSLOG=410 did you?
It is ttadv130
gavin_wusj
21st November 2003, 09:23
OK,thanks, I have found it .
OmeLuuk
21st November 2003, 09:34
Did you also run the session ttadv2100m000 with DBSLOG=410?
Please do and check the output in the file dbs.log. You will learn a way to solve these kind of doubts!
gavin_wusj
21st November 2003, 09:39
NO, I don't know how to do it?
Gavin
OmeLuuk
21st November 2003, 09:45
Start Baan with this commandline-- -set DBSLOG=410 ttadv2100m000
like in
ba6.1 -- -set DBSLOG=410 ttadv2100m000After the session has started you should close the session again (without changing or modifying anything). Now in the dbs.log file search for the description that was shown for your current session. You will find its data, scroll up to see where the data comes from.
BTW, you can put the text of the command line also in the command box of bw-configuration.
On Unix the dbs.log file will be created in your home dir, on NT in the $BSE/tmp
gavin_wusj
21st November 2003, 10:02
thanks, I'll try it ,thanks for ur help!
Gavin
lbencic
21st November 2003, 17:48
Hi Gavin -
Odd that you would post this now - I just got a call from a client asking the same. Many of his session descriptions were blank, I am wondering if some Baan patch did not update this properly. They seem fine on our system - this was on Baan Vc. Not sure it that's related - are yours all blank?
They are stored on ttadv130, as you found. This is a language dependent description table.
Good luck
NPRao
21st November 2003, 23:39
Lisa,
In the BaaN-5 series, onwards (called the LTS project/functionality) the labels are all stored in the table ttadv140 and there is a new field called the context of the label.
I am not sure if the LTS is implemented in BaaN-4 series.
The alternative way to check a bad fix from the tools patches is to check the object - ttdlllabels or ttdllfindlabel.