Mainframe users

Mainframe environments have some unique considerations. There are features that are available only when running a z/OS® hub monitoring server and features that are available only when running a distributed hub monitoring server. This section outlines those considerations so that you can make the best choice for your environment.

Unique z/OS hub monitoring server features

The z/OS hub monitoring server allows you to take advantage of RACF® authentication. However, the OMEGAMON® for MQ Configuration product has some specific integration with RACF that requires a z/OS hub in order to take advantage of the RACF authentication OMEGAMON for MQ Configuration product.

The z/OS hub does not provide the Hot Standby feature. High availability is achieved using a moveable hub solution found in the Tivoli® Open Process Automation Library (OPAL) by searching for "moveable HUB TEMS z/OS" or navigation code "1TW10TM1W."

Note:

The z/OS environment does not support the Tivoli Universal Agent.

Unique distributed hub monitoring server features

Two features that are provided on a distributed hub monitoring server environment are not available on z/OS hub monitoring server environments.

• Remote deployment
• Hot Standby

  The distributed hub monitoring server has a feature called Hot Standby to assist with high availability and disaster recovery scenarios. Many users choose not to use the Hot Standby feature and instead deploy OS Clusters for high availability and disaster recovery.

Linux® on zVM systems

Many mainframe users run Linux on their zVM systems. Many different Tivoli Monitoring components can be installed in Linux on zVM environments, including the monitoring server, portal server, monitoring agent and warehouse-related components. Each Linux environment can be configured with monitoring server or portal server software, or both.

[ Top of Page | Previous Page | Next Page | Contents | Index ]