No data condition

When you log on in multi-tenancy mode, the workspace loads but does not display any data.

Symptom

Multi-tenancy mode has been configured for the OMEGAMON enhanced 3270 user interface. The enhanced 3270 user interface address space has been started and you are able to log on, but your enhanced 3270 user interface is displaying an empty workspace.

Explanation

As described in OMEGAMON multi-tenancy concepts and architecture, in a single-tenant configuration, product-provided MSLs are used in the system-generated SQL queries for data collection while in a multi-tenancy configuration, user-defined MSLs are used, limiting the scope of collection to only those resources assigned to the tenant. If the user-defined MSLs are not set up correctly, it is possible that unexpected or no results will display.

To resolve the problem, you can analyze the system-generated SQL using trace. The following examples show how the queries appear in trace for single and multi-tenant configurations.

Single-tenant configuration

In a single-tenant configuration, a product-provided MSL name is used in the system-generated SQL query. The following example is of a standard trace of the enhanced 3270 user interface in a single-tenant configuration. The user is logging on to the CICS first workspace KOBSCICS. This example shows a typical workspace query that displays the CICS plexes defined to OMEGAMON:

KOBUIFD1I SQL1 Query Length : 00284
..SELECT CICSPLEX, NREGIONS, TRANRATE, CPUUTIL, AN+
YSOS, CBUFFW, CSTRINGW, ENQWAIT, IORATE, PAGERATE,+
 STGVIOL, AIDS, ICES, HIMAXTP, HIMAXTR, ALLACB, WP+
ERFINDX, WSERVCLAS, SOSREGION, ORIGINNODE  FROM OM+
CICS.KCPPLX  WHERE SYSTEM.PARMA('NODELIST','*IBM_C+
ICSplex',13)  ORDER BY CICSPLEX ASC

In this example, the query specifies a SYSTEM.PARMA value of NODELIST and "*IBM_CICSplex". "*IBM_CICSplex" is the product-provided MSL for the OMEGAMON AI for CICS product and will retrieve data from all Managed System Nodes (MSNs) defined within that MSL.

Multi-tenancy configuration

In multi-tenancy mode, the user-defined MSL name is substituted into the system-generated query. The substitution is reflected in the trace, as shown in the following standard trace excerpt:

============= MULTI-TENANCY MODIFY SQL ============
SYSTEM.PARMA('NODELIST','*IBM_CICSplex',13)  ORDER+
SYSTEM.PARMA('NODELIST','&CICSMSL',nn)       ORDER+
SYSTEM.PARMA('NODELIST','T_C5_TENANT_MSL',nn)     +
SYSTEM.PARMA('NODELIST','T_C5_TENANT_MSL',15)     +
===================================================
---------------------------------------------------
KOBUIGD1I SQL1 Query Length : 00291
SELECT CICSPLEX, NREGIONS, TRANRATE, CPUUTIL, ANYS+
OS, CBUFFW, CSTRINGW, ENQWAIT, IORATE, PAGERATE, S+
TGVIOL, AIDS, ICES, HIMAXTP, HIMAXTR, ALLACB, WPER+
FINDX, WSERVCLAS, SOSREGION, ORIGINNODE  FROM OMCI+
CS.KCPPLX  WHERE SYSTEM.PARMA('NODELIST','T_C5_TEN+
ANT_MSL',15        ORDER BY CICSPLEX ASC <ENDSQL><+

In this example, the multi-tenant customer was defined as having a CICS MSL of "T_C5_TENANT_MSL". The trace shows the step-by-step substitution process and the final SQL that will be sent to the TEMS.

Note: Only the OMEGAMON products that generate queries that use the following format are supported in multi-tenancy mode:

SYSTEM.PARMA=('NODELIST',"msl",nn)

Where msl is the product-provided MSL name and nn is the length of the name in characters.

Procedure

Initiate a trace.
Locate the following text: MULTI-TENANCY MODIFY SQL
Examine the details of the MSL substitution process and correct any errors.