Throughout the agent autonomy topics are references to
files and exceptions on z/OS-based monitoring agents. This topic consolidates
that information.
- Central configuration server
- The central configuration server must be on a distributed system;
the z/OS® system is not supported.
- Configuration load list
- The monitoring agent downloads all items in the configuration load list at agent startup. The agent
uses the initial file download timestamp as reference and begins keeping
track of the configuration file last modified time. A change to the
server copy of the file occurring after this timestamp is downloaded
and the timestamp for when the file was last modified is updated.
- Default names for z/OS monitoring
agent local configuration members in the RKANDATV data set
- Where PC is the two-character product code:
- PCCFGLST
- Local Configuration Load data set member name
- PCTHRES
- Local threshold override file name.
- PCTRAPS
- Local SNMP trap configuration file name
- PCSICNFG
- Local agent private situation configuration file name
- PCEIF
- Local Agent EIF eventmap configuration file name
- PCEVMAP
- Local Agent EIF destination configuration file name
- Activate="RESTART" is not supported on z/OS
- The RESTART option is used to restart the agent after a successful
file download. It is not supported on the z/OS or i5 operating systems. The agent process
must be restarted in another manner to activate the new configuration.
- Multiple agents running in the same address space
- Any override parameters defined in the KDSENV member
of the &hilev.&rte.RKANPARU data
set are used for all agents running within the address space. This
works well for IRA_EIF_DEST_CONFIG, because all
agents will likely share the same EIF event destination. The other
override parameters can also be used, but the data set members identified
might need to combine definitions for multiple agents, which is not
recommended. The best practice is to use the default naming convention
for local configuration data set members when running multiple agents
in the same address space.
- Password encryption
- Local configuration XML files include user credentials with passwords
that can be entered in plain text. Securing access to these configuration
files is usually adequate to secure the credentials. You can also
add a layer of security by storing passwords in encrypted format within
the configuration file.
- If you are enabling SNMP alerts from the agent, SNMP v1 &
v2c Community Strings and SNMP v3 Authentication and Privacy Passwords
can be stored in encrypted format in the PCTRAPS.RKANDATV
trap configuration file.
- If you are enabling Centralized Configuration, the ConfigServer
password attributes can be encrypted when they are stored in a xxCFGLST.RKANDATV
Configuration Load List file or using the IRA_CONFIG_SERVER_PASSWORD
environment variable.
- See the topic on "Password encryption in configuration files
on z/OS" in IBM Tivoli OMEGAMON XE and Tivoli Management Services
on z/OS Common Planning and Configuration for instructions.