| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3032.1 | GT works in some cases, not in others.... | DADA::DITMARS | Pete | Tue May 19 1992 19:05 | 25 |
| >If Current Memory Usage GT 85 then alarm
If the attribute is supported by SHOW, then it should be at least recognized
by alarms. If it's using a funky datatype, alarms might not support it, but
they should tell you that (and not what it's currently telling you). Try a
show <entity> Current Memory Usage and see what happens.
Here's another possibility:
Are you using the Iconic Map's interface and clicking on the "Comparison Rule"
entity in the toolbox and then filling in the fields at the bottom of the
form with the above?
Or are you attempting to do this from FCL?
GT works only as a value in the "Relational operator" field of the "Comparison
Rule" alarm rule format.
If you're doing it any other way, try something like
expression = (tsam foo Current Memory Usage > 85)
I know you've said you successfully created other rules, but sometimes when
I'm hopping back and forth between DCL and MCC I put a few .GT.'s in there
and it takes me a minute to figure out what's up.
|
| 3032.2 | I still think its a bug... | RADBOX::ANDERSON | | Tue May 19 1992 19:32 | 23 |
| >If the attribute is supported by SHOW, then it should be at least recognized
>by alarms. If it's using a funky datatype, alarms might not support it, but
>they should tell you that (and not what it's currently telling you). Try a
>show <entity> Current Memory Usage and see what happens.
I will try this on thursday. Current Memory Usage shows up with the show command
in the iconic interface.
>Here's another possibility:
>Are you using the Iconic Map's interface and clicking on the "Comparison Rule"
>entity in the toolbox and then filling in the fields at the bottom of the
>form with the above?
Yes.
I have successfully created a rule for "High Memory Usage", which is the very
next attribute after "Current Memory Usage". They are both the same data type
(Percent). I have tried it several times with other attributes in the same SHOW
category, and they all seem to work except "Current Memory Usage".
I will try to add the rule via the FCL and see what happens.
|
| 3032.3 | could be a bug | DADA::DITMARS | Pete | Wed May 20 1992 13:10 | 4 |
| I just had to ask some questions to narrow down where it's happening.
Try the "show" from FCL. It could well be a parsing problem. Alarms
uses FCL's parser to parse the rule expression.
|
| 3032.4 | More info | TOOK::FONSECA | I heard it through the Grapevine... | Wed May 20 1992 15:07 | 22 |
| I've tried getting the show to work, and I get the following
syntax error message:
MCC> show terminal_server .ts.damien current memory usage
%MCC-I-NOPARCMD, current memory usage
^
%MCC-I-SYNTAXERR, Syntax error -- unable to interpret remainder of line
%MCC-W-ATTRAMBIG, attribute CURRENT is ambiguous; enter more characters
This appears to be happening for most or all of the TSAM attributes
which start with the word current. Simlarly defined attributes
starting with other words do not have the problem. As far as I can
tell there are no duplicate or conflicting names being used. There is
no attribute defined for the word current alone. Most of the attributes
starting with current have similarly defined attributes starting
with the words high and max, they do not have this problem.
Bill-
I'll try to work this through with the DECmcc developers, and get back to you.
-Dave
|
| 3032.5 | | RADBOX::ANDERSON | | Thu May 21 1992 19:45 | 7 |
| Thanks for checking it through for me, I was supposed to work on the MCC station
today, but other things have come up. (The MCC station is not onsite with me).
I will be waiting for your response.
Thanks.
-bill
|