Autonomous agents

You can choose to configure stand-alone monitoring agents to run in autonomous mode (without communicating directly with a monitoring server). An autonomous agent can emit Simple Network Management Protocol (SNMP) traps and Event Integration Facility (EIF) events directly to a Netcool®/OMNIbus ObjectServer for agent-specific situations (but not for enterprise situations). Autonomous agents can be advantageous in environments where disk space or transmission bandwidth is in short supply.

An autonomous agent requires the DSEVT DDNAME in the monitoring agent started task in the rhilev.rte.RKANSAMU data set. This DDNAME points to the rhilev.rte.RKDSEVT data set.

The IBM Tivoli Monitoring: Installation and Setup Guide provides instructions for configuring Netcool/OMNIbus ObjectServers to receive the events. For information on specifying which situation events to forward, see the Tivoli Enterprise Portal online help and the IBM Tivoli Monitoring: Tivoli Enterprise Portal User's Guide.

For information about parameters to set for an autonomous agent, see the "Agent autonomy" chapter of the IBM Tivoli Monitoring: Administrator's Guide. You can add these parameters for an autonomous agent on a z/OS® system by editing the Kpp$PENV member of the PARMGEN WCONFIG library.

For instructions on enabling SNMP V3 passwords for autonomous agents, see Enabling SNMP V3 passwords for autonomous agents.