Defining a Managed Systems List (MSL)

Edit online

Define the MSLs for a tenant.

The Managed Systems List (MSL) is a list of Managed System Name (MSN) entries (or, origin nodes).

Each OMEGAMON provides an out-of-the-box MSL that contains all discovered systems or subsystems that belong to it. This MSL is all that is needed for an environment consisting of only a single tenant.

For an environment that has multiple tenants, one or more MSLs must be defined for each tenant to limit the scope of collection to that of the tenant.

It is recommended that you use the TEP to create your MSLs.
Notes:
  • A managed systems list is also referred to as a managed system list and a managed system group.
  • The TEP Object Group Editor stores MSL and MSN data in the Hub TEMS to which it is connected. If the enhanced 3270 user interface is connected to the same Hub TEMS, it has access to that same stored data. Equally true, if the enhanced 3270 user interface Object Editor stores data into the TEMS, the TEP will have access to that same stored data.
Before you create your MSLs for your multi-tenant implementation, review the following considerations:

Naming convention

When creating managed systems lists, it is important to choose a naming convention that is meaningful. Although there are not any requirements or validation for the name, the following suggested format is recommended:
env_OMcode_customer
Where:
  • env is the environment, such as T for Test, P for Production, or D for Development
  • OMcode is the OMEGAMON product code, such as C5 for CICS or I5 for IMS
  • customer is the customer ID (up to 10 characters)

Additionally, the use of uppercase letters is recommended.

For example, T_C5_ACMECORP would be the MSL for CICS test regions for the ACME Corporation.

Note: A benefit of using this naming convention is that in the required Customer definition (described in Creating tenant definitions), if the MSL name ends with ?, then the customer ID will be substituted.

Scope of resources

Before you create your MSL, plan what managed system nodes to include; for example, you can create an MSL containing a single CICS region. One MSL must be created for each managed system type.

The following conditions apply when creating your MSL:
  • In IBM Z® OMEGAMON® for CICS, if you want to have a CICSplex per LPAR, you must define each one.
  • The IBM OMEGAMON for Networks on z/OS agent and the IBM Z® OMEGAMON® Network Monitor agent each require an MSL containing three types of managed systems. Each managed system name will include an LPAR name. The three managed systems can be described as follows:
    • AgentID:LPAR:KN3AGENT
    • TCPIP:LPAR
    • VTAM:LPAR

Procedure

To create your MSL in TEP, see Creating an MSL using TEP.