CR_UPDATE syntax in tngwriterrule.dat file.

[Nauthiz]

I want to use CR_UPDATE keyword instead to log subsequent instances of the same event as comments to the same job. I want to match the job summary field as well as the default match fields. It says in the comments of the file that:

# CR_UPDATE - updates an existing request or requests (if they
# exists or creates new request if no requests are found. By
# default requests are located by matching on the log_agent and
# affected_resource (asset) fields. The user can overrid the
# defaults by specifying a list of any call request attributes.

However I just can't figure out what the syntax is to "specify a list of any call request attributes." I thought you could use the %SEARCH= keyword but this doesn't seem to work.

 

[bverkler]

Good afternoon.
here is a possible option:

MessageText.*:::.*:::*:::tng:::*:::CR_UPDATE:::Template_1:::::DM:::eventtoken&Parm:::%DESCRIPTION=&Message;%SEARCH=EVENT_TOKEN

This wrapped, but what it does is this:
--Any messages received by ehwriter that looks like MessageText<Anything> will trigger this. It will create a new request if there are no requests currently open with an EVENT_TOKEN of 'eventtoken<TheValueAfterTheCallToAHD.dllInTheMsgAction>'
When it creates a new request, it assigns the EVENT_TOKEN of 'eventtoken<TheValueAfterTheCallToAHD.dllInTheMsgAction>'
to that request, which can be searched based on future messages.
Also see the text_api.cfg for the values you can use after the SEARCH.

Thank You,
brent
send me an e-mail if you have further questions, and you can post the updates her, because I don't visit much.
bcverkler@west.com