|
|
|
Symptom:
A CA Automation Point server is monitoring z/OS messages and forwarding them to the CA NSM Event Manager. In my Event Manager message actions, I use the SENDOPER command to issue an NMFIND request. This NMFIND request is then to be executed by a second CA Automation Point server, which is dedicated to sending notifications. Why does the second CA Automation Point server not receive any NMFIND requests, even though it has been configured to monitor my CA NSM Event Manager host?
Solution:
CA Automation Point places the string "AutomationPoint" into the Source field of every message it sends to CA NSM, and refuses to read back any message whose Source field contains that value. Your CA Automation Point z/OS message had a Source value of AutomationPoint. Therefore, the CA NSM Event Manager SENDOPER action places the NMFIND command into the CA NSM log. By default, SENDOPER leaves the original Source value in the new message that it places in the CA NSM log. Thus, this new NMFIND request has a source value of AutomationPoint, and your second CA Automation Point server will not read that message. On the CA NSM dialog where you specify the SENDOPER action, select the Overrides tab, and enter an overriding value (for example, from CA NSM) in the Source field.
| Copyright © 2012 CA. All rights reserved. |
|