BMC Communities: Message List - Getting value of text parameter

forums@developer.bmc.com — Wed, 26 Feb 2003 17:23:30 GMT

I'm an idiot! Parameter name is LOGAlarms not LogAlarms. I'm sorry for taking your guys time for that crap! Thank you for all your responses and help.

Rob

forums@developer.bmc.com — Wed, 26 Feb 2003 16:44:01 GMT

OK Mike, the unique(matchedline) is condensing multiple instances of the same line from a text file into one. Yes, those lines contain a time stamp. As you can see in my latest example I am able to extract the data from the parameter when in the collector. So don't focus on the set() command because it is working, the data is in the text parameter LogAlarms. The issue is, why can't I pull the data from LogAlarms when in Standard Event Catalog 11.

Rob

forums@developer.bmc.com — Wed, 26 Feb 2003 16:36:58 GMT

Let's copy this in your even notification action for event 11.

I think that will explain what you have to use to get the data you want ...

<br/><br/># Retrieve event information in a &quot;safe&quot; way<br/>evstatus = &lt;&lt;&lt;END_OF_TEXT<br/>%&#123;EV_STATUS&#125; <br/>END_OF_TEXT;<br/><br/>thetime = &lt;&lt;&lt;END_OF_TEXT<br/>%&#123;EV_TIME&#125; <br/>END_OF_TEXT; <br/><br/>type = &lt;&lt;&lt;END_OF_TEXT<br/>%&#123;EV_TYPE&#125; <br/>END_OF_TEXT; <br/><br/>node = &lt;&lt;&lt;END_OF_TEXT<br/>%&#123;EV_NODE&#125; <br/>END_OF_TEXT; <br/><br/>origin = &lt;&lt;&lt;END_OF_TEXT<br/>%&#123;EV_ORIGIN&#125; <br/>END_OF_TEXT; <br/><br/>desc = &lt;&lt;&lt;END_OF_TEXT<br/>%&#123;EV_DESC&#125; <br/>END_OF_TEXT; <br/><br/>args = &lt;&lt;&lt;END_OF_TEXT<br/>%&#123;EV_ARGS&#125; <br/>END_OF_TEXT; <br/><br/>name = &lt;&lt;&lt;END_OF_TEXT <br/>%&#123;EV_NAME&#125; <br/>END_OF_TEXT; <br/><br/>severity = &lt;&lt;&lt;END_OF_TEXT<br/>%&#123;EV_NSEVERITY&#125;<br/>END_OF_TEXT;<br/><br/># Extract the additional information from the event     <br/>alm_range = nthargf&#40;args,1,&quot;\t&quot;&#41;;<br/>arg2 = nthargf&#40;args,2,&quot;\t&quot;&#41;;<br/>arg3 = nthargf&#40;args,3,&quot;\t&quot;&#41;;<br/>arg4 = nthargf&#40;args,4,&quot;\t&quot;&#41;;<br/>alm_min = nthargf&#40;args,5,&quot;\t&quot;&#41;;<br/>evvalue = nthargf&#40;args,6,&quot;\t&quot;&#41;;<br/>alm_max = nthargf&#40;args,7,&quot;\t&quot;&#41;;<br/><br/>appl = nthargf&#40;arg4,1,&quot;.&quot;&#41;;<br/>inst = nthargf&#40;arg4,&quot;2-&quot;,&quot;.&quot;,&quot;.&quot;&#41;;<br/>parm = arg3;<br/><br/>global = &#40;arg2 == &quot;global&quot;&#41;;<br/>parampath = sprintf&#40;&quot;/%s/%s/%s&quot;,appl,inst,parm&#41;;<br/>paramstatus = get&#40;parampath.&quot;/status&quot;&#41;;<br/>value = get&#40;parampath.&quot;/value&quot;&#41;;<br/><br/># Show some information about this event<br/>data=sprintf&#40;&quot;ORIGIN=%s\n&quot;.<br/>             &quot;NAME=%s\n&quot;.<br/>             &quot;NODE=%s\n&quot;.<br/>             &quot;TYPE=%s\n&quot;.<br/>             &quot;TIME=%s\n&quot;.<br/>             &quot;SEVERITY=%s\n&quot;.<br/>             &quot;ALARM_RANGE#=%s\n&quot;.<br/>             &quot;ALARM_RANGE_DEFINITION=&#91;%s,%s&#93;\n&quot;.<br/>             &quot;PARAM STATUS=%s\n&quot;.<br/>             &quot;EVENT STATUS=%s\n&quot;.<br/>             &quot;NAMESPACE VALUE=%s\n&quot;.<br/>             &quot;VALUE IN EVENT=%s\n&quot;.<br/>             &quot;APPLICATION=%s\n&quot;.<br/>             &quot;INSTANCE=%s\n&quot;.<br/>             &quot;PARAMETER=%s\n&quot;.<br/>             &quot;PARAMETER_IS_GLOBAL=%s\n&quot;.<br/>             &quot;DESCRIPTION=%s\n&quot;,<br/>             origin,<br/>             name,<br/>             node,<br/>             type,<br/>             thetime,<br/>             severity,<br/>             alm_range,<br/>             alm_min,alm_max,<br/>             paramstatus,<br/>             evstatus,<br/>             value,<br/>             evvalue,<br/>             appl,<br/>             inst,<br/>             parm,<br/>             global,<br/>             desc<br/>             &#41;;<br/>             <br/>print&#40;data.&quot;\n&quot;&#41;;<br/><br/>print&#40;&quot;get&#40;\&quot;&quot;.parampath.&quot;/value\&quot;&#41;; = &quot;.value.&quot;\n&quot;&#41;;<br/><br/>

-- Geert

forums@developer.bmc.com — Wed, 26 Feb 2003 16:19:08 GMT

I am really confused now Your original post shows that you are using three arguments for the set(). The third argument is meant to be a timestamp. You then indicated that the 3rd argument was a timestamp, and now you indicate that it is not? What is it? If the third argument to set() is not a timestamp I suspect that is causing the problem.

forums@developer.bmc.com — Wed, 26 Feb 2003 15:54:57 GMT

The set command doesn't contain a time stamp the text from the log file does. The unique was just to remove redundant lines of the same error from the text file. Yes your right that the parameter is set in a different parameter, kind of. I am setting the parameter from a collector and attempting to retreive it's contents from the Notification area of Event Catalog 11 to send on to our SNMP management system. Here is the output.

OUTPUT WITH YOUR CODE IN THE COLLECTOR:
20030226093102 TESTING print(get(/BIRCH_LOGMON/test_log/LOGAlarms/value)); = *************************************************************************************
20030226093102 *** New text between Wed Feb 26 09:21:16 2003 and Wed Feb 26 09:22:16 2003
20030226093102 *** Template: anytext
20030226093102 *** Alarm Level : 6
20030226093102 *************************************************************************************
20030226093102 This is a test message written to the log.

OUTPUT WITH YOUR CODE IN NOTIFICATION OF SEC 11
20030226093102 TESTING print(get(/kcbmcd01/kcbmcd01/LOGAlarms/value)); =

forums@developer.bmc.com — Wed, 26 Feb 2003 15:11:15 GMT

Strange ...

Just to help us move forward on this, could you remove the timestamp from the set instruction (for now) ?

Also after you set the paramter - looks like you are doing it from another parameter - just do the following :

<br/>set&#40;&quot;../LOGAlarms/value&quot;, errdisp &#41;; <br/>parampath = &quot;/&quot;.get&#40;&quot;../../name&quot;&#41;.&quot;/&quot;.get&#40;&quot;../sid&quot;&#41;.&quot;/LOGAlarms/value&quot;;<br/>print&#40;&quot;TESTING print&#40;get&#40;&quot;.parampath.&quot;&#41;&#41;; = &quot;.get&#40;parampath&#41;.&quot;\n&quot;&#41;;<br/>

Now see what get's printed in the SOW and try the same get from %PSL

Let us know what happens.

-- Geert

forums@developer.bmc.com — Wed, 26 Feb 2003 15:04:00 GMT

Hey guys, going back to msharpe's first comment, yes the lines are time stamped. The problem isn't that the lines of text aren't in the parameter or they aren't all making it. The problem is I can't pull anything from the text parameter. Any suggestions?

Rob

forums@developer.bmc.com — Wed, 26 Feb 2003 14:45:33 GMT

set() : sets a single value, with a single call on a single namespace variable.

batch_set() : allows you to combine multiple set()'s in a single PSL instruction, wasting less resources.

This is just to prevent
set()
set()
set()
...
set()

Nothing more !

-- Geert

bert@xpericon.be — Wed, 26 Feb 2003 14:32:36 GMT

What's the difference with Batch_set() then ...

I could do a search offcourse, because I did see a topic about this function, but since we're on the topic anyway ;-)

Bert

forums@developer.bmc.com — Wed, 26 Feb 2003 13:29:51 GMT

Indeed, this is undocumented in the manual, but already documented in the devcon forum since 2000 ...

See :
http://communities.bmc.com/communities/thread/14530

-- Geert