Home > IBM Tivoli Monitoring, ITM > IBM Tivoli Monitoring Enhanced 3270 User Interface Overview

IBM Tivoli Monitoring Enhanced 3270 User Interface Overview

This article will cover the basic features and architecture of the IBM Tivoli Monitoring (ITM) OMEGAMON XE Enhanced 3270 User Interface (E3270UI).

Introduction

The E3270UI provides the user with a 3270 based display of many of the data attributes available to TEP users via the IBM Tivoli Monitoring (ITM) Tivoli Enterprise Portal (TEP).

Currently the E3270UI supports IBM OMEGAMON XE on z/OS v510 and IBM OMEGAMON XE for CICS on z/OS v510 with more products becoming available in the future.

The following shows a typical /E3270UI screen on a 43×80 display:

Major Parts of the E3270UI Screen

Home and Command Line

You can enter product and workspace specific commands in these input fields.

Panel Name

This is the name of the panel member from the RKANWENU DD panel library in the E3270UI started task JCL. The two letters after the K indicate the product code that owns the workspace. In this case, CP indicates CICS.

Toolbar Menu

Dropdown tools. You can place your cursor on the toolbar entry name and press ENTER or type the underscored letter into the Home input field and press enter to show the dropdown.

Context & Auto Update

The auto update field shows if screen auto update is enabled or not. You can overtyped the ‘off’ value with a number of seconds from 5 to 999 to enable auto update of the screen, or type the word ‘off’ to disable it.

The title text and contents of the Context fields will change as you more around the product workspaces. In some cases you will be able to overtype these fields to switch context, for example to look at the same workspace for a different CICS region, instead of having to navigate back to the start.

Detail Subpanel

Detail sub panels show information for a single entity. The data may be displayed in one or more columns. The layout may change depending upon the 3270 screen size in use.

Displaying Truncated Data on a detail sub panel

If the data to be displayed is to large to fit in the available space on a detail sub panel, then the data is displayed and highlighted:

To see the complete data, place the cursor on the data to be displayed and press ENTER:

Press f3 to close the pop up.

Summary Subpanel

Summary sub panels typically show data from multiple rows of an ITM attribute group as a scrollable table.

There are a number of areas of interest in a summary sub panel.

Selection Input Field

On the left of each row is an input field. You can enter a / character here to see a list of the available options. You can enter options either from that list or, if you know the option letter, you can enter it directly against the required row in the summary sub panel.

Here I entered a / against one of the tasks in the ‘Highest CPU Tasks’ sub panel:

If you just place the cursor in the input field on a summary row and press enter, the default action is taken. This is normally whatever action is assigned to the ‘S’ option and is chosen to be the most logical place you are likely to want to go to from that sub panel.

Columns Indicator

The columns part of the sub panel title area (if shown) shows you how many columns of data there are in the sub panel in total and which columns are currently displayed. You can overtype the first column number to go to a specific column.

Note that in this example the first column number is 2. This is because the first column is fixed and does not scroll (in this example). The number of fixed columns may vary depending upon the workspace. The Fixed column separator indicates which columns (to the left of it) are fixed:

Scroll Buttons

The scroll buttons on a summary workspace indicate if there is more data to the left, right, above or below the data that is currently displayed by being shown as white.

You can use the standard function keys to scroll the sub panel:

F7 – Up

F8 – Down

F10 – Left

F11 – Right

Note that to scroll only that sub panel when the MORE indicator is showing you must place the cursor within the sub panel, otherwise the whole screen will scroll.

The rows part of the sub panel title area (if shown) shows you how many rows of data there are in the sub panel in total and which rows are currently displayed. You can overtype the first row number to go to a specific row within the output.

Sorting

If the column title is highlighted and contains the sort indicator to the left of it:

Then you can place the cursor on the column title and press ENTER to sort the displayed data. The sort indicator changes to indicate the current sort order of the displayed data:

Collapse Subpanel

The collapse sub penal twisty enable you to reduce the size of a sub panel on a workspace so that only the title bar is displayed. To collapse a sub panel, place the cursor on the twisty and press ENTER.

Before:

Collapsed:

Note that the twisty changes to indicate that you can expand the sub panel by placing the cursor on the twisty and pressing ENTER.

The number of rows contained by the sub panel is display in reverse text on the right of the title bar.

Minimize and Delete Subpanel

 Minimize

If you place your cursor on the minimize icon (the small white square with the underscore in it) and press ENTER, the sub panel will be minimized down to the ‘task bar’ at the bottom of the screen.

Sub panels below the minimized one move up onto the available screen space.

To restore the minimized sub panel to the workspace, place the cursor on the entry on the task bar and press ENTER

Delete

If you place your cursor on the delete icon (the small white square with the cross in it) and press ENTER, the sub panel will be removed from the workspace:

The difference between minimize and delete is that when you minimize a sub panel, if you press enter to refresh the workspace, the query associated with the sub panel is still executed.

When you delete a sub panel from the workspace, pressing enter no longer runs the query associated with it.

To restore a deleted sub panel to the screen, you must navigate back to the previous workspace by pressing F3 and then navigate forward again to this workspace.

MORE Indicator

The MORE indicator in the bottom right corner of the screen shows if there are additional sub panels to display on the workspace that are not currently displayed on the physical screen.

The arrow indicates the direction of the additional sub panels. You can use the vertical scroll keys (F7 and F8) to scroll the workspace.

Note that the cursor must NOT be within a sub panel in order to scroll the entire workspace. If the cursor is within a sub panel, scrolling only applies to that sub panel.

Navigation

 Navigating around the E3270UI is designed to by quick and simple with the default options taking you to the most sensible places.

 Navigating from summary panels

 Navigating from a summary sub panel row is as simple as placing the cursor in the input field next to the desired row of data and pressing ENTER which will cause the E3270UI to take the default navigation action.

 If you don’t know what actions are available for the data in a summary row, you can enter a / character next to the row and pres ENTER to display a popup menu of available options. The default option, that is the one taken when you just put the cursor in the input field and press enter, is indicated by the S option.

 

Zooming

 Zooming is a navigation feature whereby you place the cursor on a data field’s caption or value and press enter which then takes you to another workspace. The target workspace may be fixed or it may be determined dynamically, based on the data in the field that you are zooming on.

Normal
0

Zooming from Detail sub panels

In the following sub panel, the Transaction ID field is highlighted indicating that it is zoomable.

Normal
0

By placing the cursor on the caption and pressing enter the user will be taken to another workspace. In this particular instance the user will be taken to the “Transaction Details” workspace for the transaction id displayed in the sub panel (OMEG in this case).

Zooming from Summary sub panels

In the following summary sub panel, the CICS Transaction ID field is highlighted indicating that it is zoomable.

 

By placing the cursor on the highlighted data in the required data row and pressing enter the user will be taken to another workspace. In this particular instance the user will be taken to the “Transaction Details” workspace for the selected transaction id (OMEG in this case).

 Navigating Back

 As you navigate forward through workspaces as a result of selections and zooms, you create a hierarchy of workspaces. To traverse back up that chain of workspaces to previous ones, press F3.

Architecture

In this section I shall take a brief look at the E3270 architecture.

The E3270UI environment is built on top of the IBM Tivoli Monitoring (ITM) agent framework. What this means is that it collects its data from existing ITM agents using the ITM framework that is already in place. You do not have to use the Tivoli Enterprise Portal (TEP) in order to use the e3270UI.

The Tivoli OMEGAMON Manager Address Space

The E3270UI 3270 sessions are hosted by the Tivoli OMEGAMON Manager (TOM) address space. A single TOM address space can support multiple 3270 sessions. The TOM obtains data from ITM by sending the requests to Data Retrieval Agents (DRAs) that execute within IBM Tivoli Monitoring Server (TEMS) and agent address spaces within the sysplex.

The Data Retrieval Agents

There can be one or more DRAs executing on one or more LPARs within the sysplex. Each DRA registers itself with the z/OS Workload Manager (WLM) as a service. The TOM then queries WLM in order to locate all the DRAs that are available within the sysplex.

TOM location within the sysplex

As a result, a TOM can be anywhere within the sysplex, it does NOT have to be on the same LPAR as a DRA.

Performance and Security

You can run multiple TOM address spaces, spread across the sysplex for performance, fail over and security reasons, depending upon your requirements and installation. When multiple DRAs are available, the TOM will dynamically select different ones to service query requests in order to prevent any one DRA hosting TEMS or agent address space from becoming overloaded.

Typical setup

This diagram shows a possible implementation. In this example the TOM is running on one LPAR and communicating with two DRAs. One DRA is with an agent or TEMS address space on the same LPAR while the other DRA is within an agent or TEMS address space on another LPAR within the same sysplex.

Each DRA registers itself with the common WLM environment, from where the TOM can locate them.

Notice that the hub TEMS is not shown. The ITM hub can be on a z/OS LPAR, possibly on an other sysplex or even off platform such as on an AIX machine.

TOM Registry

 The TOM periodically queries WLM for the list of available DRAs and the ITM environment in order to discover the available ITM managed system components, lists and managed system names.

In order to display data for a managed system such as a z/OS LPAR known to the ITM environment via an IBM OMEGAMON XE on z/OS agent executing on that LPAR, the TOM must have discovered and registered the managed system (the LPAR) from ITM via its registry refresh process.

It is possible that a managed system can be known to the ITM environment and even be viewed on the TEP and yet not be visible to E3270UI users because the TOM has not run it’s refresh process since the managed system came online.

You can drive the TOM registry refresh process manually at any time via the tools menu on the Tool bar dropdown menu.

You can also initiate a registry refresh by issuing the REGREFRESH operator modify command to the TOM address space via an interface such as SDSF.

 E.G.

 F tomstc,REGREFRESH

 Where tomstc is the job, started task or modify name of the tom address space. However most users will not have the necessary authority to do so, at least in a production environment.

Query Flow

 When an E3270UI workspace issues a query, the TOM directs the query to one of the DRAs that it knows about that are running in an agent or TEMS address space that connects to the desired hub TEMS.

The DRA then sends the query to the hub TEMS which then distributes it to the managed system agent on the desired system.

The response from the agent is sent back the hub TEMS and from there to the DRA and then back to the TOM.

Remember that the DRA selected by the tom may not be on the same physical LPAR as the agent that the query is destined for. This architecture ensures that the query can reach the required agent, even if there is no direct connection between the system the DRA is executing on and the system that the agent is running on.

Advertisements
Categories: IBM Tivoli Monitoring, ITM
  1. Willy Unger
    February 17, 2016 at 12:27 am

    Great article, Dave!

    Trying to get this working at our shop in Telefonica.

    Greetings from Argentina

    Willy

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: