Copy or transfer catalog and attribute files to the monitoring server on z/OS

The requirements for catalog and attribute files depend on your setup.

• For monitoring agents in the same CSI with a monitoring server on z/OS®, catalog and attribute files are added automatically to the monitoring server when its runtime libraries are loaded. However, if you want to store long-term history data, you must still transfer catalog and attribute files to the monitoring server on z/OS for the Warehouse Proxy agent and the Summarization and Pruning agent.
• For a monitoring agent that is not installed in the same CSI as a z/OS monitoring server through which the agent's data flows, you must copy or transfer the agent's catalog and attribute files (KppATR and KppCAT) from the thilev.TKANDATV library in the CSI where the monitoring agent is installed to the rhilev.rte.RKANDATV library for the runtime environment in which the monitoring server is configured. You can use IEBCOPY or FTP file transfer to put the files into the rhilev.rte.RKANDATV data set.
• For distributed monitoring agents reporting to a monitoring server on z/OS, you transfer catalog and attribute files to the monitoring server on z/OS from Manage Tivoli Monitoring Services on a system where a portal server is installed and where either the portal server or a monitoring server is configured to communicate with the monitoring server on z/OS.
• If you want to store long-term history data, you transfer catalog and attribute files for the Warehouse Proxy agent and the Summarization and Pruning agent to the hub monitoring server on z/OS from Manage Tivoli Monitoring Services on a system where a portal server is installed and where either the portal server or a monitoring server is configured to communicate with the monitoring server on z/OS.