After doing some more monitoring and seeing a big disparity between
NumQryExecuted under <@datasourcestatus> and NumQryServed under
<@serverstatus>, with the serverstats reporting far smaller number than the
datasourcestats....

I am wondering if the server is counting some sort of aggregate Tango
actions, while datasource counts SQL (Direct DBMS)'s.

Would also explain why the MaxQryProcTime is less for datasource stats
(doing smaller tasks,  thereby faster)

I hope this kind of Tango stuff is appropriate for this list server.  I, for
one, wouldn't mind more RTango talk, but certainly understand that others
may not feel the same, maybe even strongly so.

Brent Skean
Current Solutions

-----Original Message-----
From: Brent Skean <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Monday, September 24, 2001 5:48 AM
Subject: Tango Datasource metatag


>Troy,
>
>Checked out your admin.taf, very cool.
>
>On a side note (this has nothing to do with your code):
>
>I was reviewing <@datasourcestatus> and <@serverstatus>... specifically
>MaxQryProcTime.
>
>I just ran a small experiment.... (queried a datasource).  Whereas
><@serverstatus> reports MaxQryProcTime = 176, the largest MQPT shown by
><@datasourcestatus> is 1.
>
>Also,  I ran a taf that had a formatting error in it.  This will generate a
>NumQryErrors =1 under serverstatus but nothing under datasourcestatus
>ErrorsGenerated.  I wonder if serverstatus is tracking more comprehensively
>, ie, datasourcestatus will only report certain errors, while serverstatus
>reports more.
>
>Have you noticed this or am I missing something?
>
>Brent Skean
>Current Solutions
>
>
>-----Original Message-----
>From: Troy Sosamon <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
>Date: Saturday, September 22, 2001 10:08 AM
>Subject: RE: TANGO INSERT ON PK/AUTONUM TABLE. - Razzak's Reply
>
>
>>Manuel,
>>
>>Here is a screen I made for watching things on the Tango server and
getting
>>info about the users browser. I attached it as a file because I did not
>want
>>the html codes running in your e-mail.
>>Take this attached file and create a new page in your tango taf, and then
>call
>>it.  The commands that give you current odbc info are:
>>
>>DataSourceStatus: [@datasourcestatus>  -- gives you a list of all of the
>>current data  sources that the server has open.
>>
>>Connections: [@connections> -- gives you a list of the datasources that
all
>of
>>the users are using.
>>
>>If your datasource is not listed, you need to go access it and then look
at
>>this screen.
>>
>>This also has some cool Java scripts in it for looking at the clients
>window.
>>It should work for you.  I did modify it from the version I have running,
>so
>>this version has not been tested.
>>
>>Troy Sosamon
>>
>>>===== Original Message From [EMAIL PROTECTED] =====
>>>I think you guys missed the point.  The objective of Scott post is to
>obtain
>>>information from an RBase engine through ODBC.  If on the Tango editor
you
>>>pick SQL Query [Ctrl]Q and was to enter:
>>>      SHOW VERSION  or (CVAL('VERSION')), ODBC returns an error message:
>>>                         "This command is currently unsupported
>(1120)S1000"
>>>
>>>HOWEVER, if you type:
>>>             SELECT (CVAL('Version')) FROM anyloggedtable WHERE LIMIT= 1
>>>
>>>ODBC returns from RBase:
>>>
>>>                   Oterro 2000 v6.5++ Windows (32-bit), U.S. Version,
>Build:
>>>1.842xRT03
>>>
>>>This is a great trick to get RBase function  *** not a part of ODBC or
SQL
>>>*** from RBase!
>>>
>>>I LIKE IT!
>>>Thanks,
>>>Manuel
>>>
>>>
>>>
>>>Bill Downall wrote:
>>>
>>>> Jim,
>>>>
>>>> Take your anti-anxiety medications, and don't worry.  Scott is either
>>>> making extra work for himself, or being lazy, depending on your point
of
>>>> view.
>>>>
>>>> You could also do this:
>>>>
>>>> SET V vVersion = (CVAL('VERSION'))
>>>> SHO V vVersion
>>>>
>>>> Scott is using a technique that lets him do it with a single command,
>>>> by selecting the "expression" -- and no columns -- from a table that he
>>>> knows you have in your database. By the time he adds the WHERE
>>>> clause, so that you only see the answer once, it's probably as much
>>>> work as the two commands above.
>>>>
>>>> Many developers create a one row, one column table named Dummy to
>>>> enable tricks like Scott's.
>>>>
>>>> Bill
>>>>
>>>> On Fri, 21 Sep 2001 16:28:05 -0400, Jim Limburg wrote:
>>>>
>>>> >Where on earth did you learn a command like this...?
>>>> >Where is it in the docs?
>>>> >
>>>> >Someone's holding out on me...
>>>> >I,I,I just don't know what to think about how
>>>> >deprived I feel right now...
>>>> >
>>>> >OK, OK,,, I'm settled down now...
>>>> >Whew... I still am interested in learning more
>>>> >about this...
>>
>>Troy Sosamon
>>Denver Co
>>[EMAIL PROTECTED]
>>
>

Reply via email to