Yes, EXTERNALCOM did the trick. Thanks, Rob -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Friday, March 18, 2005 2:05 PM To: [email protected] Subject: RE: [SA-list] HTML Output
EXTERNAL is for external errorlevel checks. For com checks it's EXTERNALCOM that should be used (I know it's not within the doc, that's a doc bug :-)) As for the CASE question, I'll have a look at an example for it. The check time for a specific entry is not kept, that's why there is no HTML tag for it. Sa_nr_up/down can't be used within the saif.... Dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Morgan Sent: Friday, March 18, 2005 7:46 PM To: [email protected] Subject: [SA-list] HTML Output Hi Everyone, I believe I have detected a bug using the HTML tag SAIF when checking the variable sa_check when its value is EXTERNAL. Even though I am using plenty of COM External checks the condition is never detected. However, it does correctly detect for others such as SERVICE, etc.. There is a documentation error for use of sa_check_response when using under <SAIF>. The operator CON works but NC0 is mispelled. It should be spelled with the letter 'O' not the number zero. Can you provide some further explanation for the use of <sa_select_case STATUS> and <sa_case>? I don't understand how this is used. 'STATUS', is this a variable, the actual value, some other special word? Which tag encloses which <sa_select_case> or <sa_case>? The documentation shows <sa_select_case STATUS> with a closing tag, but not one for <sa_case>. Is this true? --- It would be useful if a Case-like statement could be used within the report body and not just in the headers and footers. I do use SAIF for conditional processing, but using CASE would make it easier when there are many conditions to check for. Maybe this could be a future enhancement. Also, can SAIF be changed to intelligently recognize the numeric response given by such tags as <sa_nr_up>, <sa_nr_down>, etc., so that conditional formatting can be done based on counts? I've tried and can't get it working. How about adding <sa_checkdescription> and <sa_threshold> to the list of variables that SAIF can check against, including the use of the operators CON and NCO with each? Could the Last Check Time for a particular test be added as an output variable option for HTML? This is useful when cycles are set to skip at such-and-such intervals. Thanks, Rob Morgan To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
