What's new in OMEGAMON shared components

This topic summarizes the recent updates in the OMEGAMON shared documentation for various OMEGAMON shared components.

Table 1. What's new in OMEGAMON shared components
Description	Related APARs
The OMEGAMON® enhanced 3270 user interface introduces single-sysplex mode, a new operational mode that provides views that are narrowed in scope to data for managed systems in the sysplex where the enhanced 3270 user interface is running only. For more information, see Monitoring a single sysplex.	OA68871 OA69083
Tivoli Enterprise Monitoring Server REST services have been enhanced, as follows: You can now edit and create history collection configurations. To control permissions, you must use SAF resource profiles. For details, see Editing history collection configurations, Creating history collection configurations, and Define SAF profiles to control permissions for history collection configurations. You can now start and stop history collection, and check the history collection status. To control permissions, you must use SAF resource profiles. For details, see Starting and stopping history data collection, Retrieving history collection status information, and Define SAF profiles to control permissions for history collection configurations. When editing or creating a situation, new authorization verification has been added for access to the table that you are monitoring. In addition to being authorized to access the situation, you must now also have READ access to any target tables in the situation. For more information, see Define SAF profiles to control permissions for situations.	OA69091 OA69164
With situation status streaming, you can forward situation status updates from your OMEGAMON® monitoring agents to third-party analytics platforms, such as Instana, Splunk, Elastic Stack, Prometheus, Grafana, and others. For more information, see (Optional) Configure situation status streaming and Stream situation status updates to OMEGAMON Data Provider.	OA68099 OA68536
Starting with Tivoli® Management Services on z/OS® 6.4, IBM Z® OMEGAMON® Web UI, a browser-based graphical user interface that uses Grafana® dashboards, is included as a component. Also included is Grafana OSS Edition 12.1.1. For more information about the new interface, see IBM Z OMEGAMON Web UI.	—
Tivoli Enterprise Monitoring Server REST services have been enhanced, as follows: With the `PUT /situations` endpoint, you can now in one request create multiple situations or import multiple existing situations from one runtime environment into a different runtime environment. For more information, see Creating situations. With the `PUT /situations` endpoint, you can no longer replace existing situations. If you want to update existing situations, use the `PATCH /situations` endpoint. For more information, see Editing situations. When deleting a situation or a history collection configuration, in addition to the required NAME parameter, now you must also provide the timestamp when the situation or history collection configuration was last modified (the LSTDATE parameter). This timestamp value is used as a locking mechanism to prevent multiple requests aimed at the same situation or history collection configuration. For more information, see Deleting a situation and Deleting a history collection configuration.	OA68566
Tivoli Enterprise Monitoring Server REST services have been enhanced, as follows: You can now create new Take Action definitions and edit existing Take Action definitions. To control permissions, you must use SAF resource profiles. For more information, see Creating Take Action definitions, Editing Take Action definitions, and Define SAF profiles to control Take Action permissions. When using the `GET /spec` endpoint, the OpenAPI document is returned in YAML format. For more information, see Accessing TEMS REST services OpenAPI document. When deleting a Take Action definition, in addition to the required NAME parameter, now you must also provide the timestamp when the Take Action definition was last modified (the LSTDATE parameter). This timestamp value is used as a locking mechanism to prevent multiple requests aimed at the same Take Action definition. For more information, see Deleting a Take Action definition. The response body for the `/system/actions` endpoint has been aligned with the other endpoints. The KEY and the NAME parameter names have been updated. The parameter that was previously displayed as KEY in the response body is now displayed as NAME. And the parameter that was previously displayed as NAME is now displayed as FULLNAME.	OA68441 OA68455
Tivoli Enterprise Monitoring Server REST services have been enhanced, as follows: The following updates have been made to the `PUT /situations` endpoint, which you use to create or replace a situation, and the `PATCH /situations` endpoint, which you use to edit a situation: When creating, replacing, or editing a situation, now all parameters must be specified in the request body, including the NAME parameter and the LSTDATE parameter for editing a situation. For more information, see Creating situations and Editing situations. You can now create, replace, and edit correlated situations and embedded situations ("Situation Comparison" in Tivoli Enterprise Portal). For more information, see Creating situations and Editing situations. With the `PATCH /situations` endpoint, which you use to edit a situation, you can now update the situation `FULLNAME` property. For more information, see Editing situations.	OA68228
Starting with Tivoli Management Services on z/OS 6.3.4, IBM Z® OMEGAMON® Data Requester is included as a component. Use of this Grafana application plug-in requires Tivoli Management Services on z/OS APAR OA67404 (PTF UJ96676). For more information, see IBM Z® OMEGAMON® Data Requester.	—
Tivoli Enterprise Monitoring Server REST services have been enhanced, as follows: You can now create and replace situations. To control permissions, you must use SAF resource profiles. For more information, see Creating situations and Define SAF profiles to control permissions for situations. The following updates have been made to the `PATCH /situations` endpoint, which you use to edit a situation: You can now edit multiple situations in a single request. For more information, see Editing multiple situations in a request. Request body property `REFLEXACTION_OPTIONS` replaces `AUTOSOPT`. For more information, see Table 1. When requesting situation status information, to use the includeResults parameter set to `true`, you must now also specify either the name or originnode parameter in the request. For more information, see Retrieving situation status information. When executing a Take Action, you can now pass values for variables used in the Take Action. For more information, see Executing a Take Action.	OA67524
Tivoli Enterprise Monitoring Server REST services have been enhanced, as follows: The following updates have been made to the `/situations/status` resource: Endpoint `GET /situations/status` now returns information for current situation statuses only. Query parameters expand and timeFrom are no longer supported for this endpoint. New parameter includeResults, when set to true, retrieves the results for a current situation status. For more information, see Request current situation statuses. New endpoint `GET /situations/status/history` retrieves situation status history. For more information, see Request situation status history. New query parameter deltastat allows you to filter results by situation status. For more information, see Filter results by attributes. You can now delete history collection configurations. To control permissions, you must use SAF resource profiles. For more information, see Deleting a history collection configuration and Define SAF profiles to control permissions for history collection configurations. You can now delete situations. To control permissions, you must use SAF resource profiles. For more information, see Deleting a situation and Define SAF profiles to control permissions for situations. You can now delete Take Action definitions. To control permissions, you must use SAF resource profiles. Deleting Take Action definitions requires `ALTER` access to resource `O4SRV.ACTIONS.Kpp.key`. For more information, see Deleting a Take Action definition and Define SAF profiles to control Take Action permissions. Note: You can also use resource `O4SRV.ACTIONS.Kpp.key` for controlling access when retrieving Take Action definitions. Previously, resource `O4SRV.ACTIONS.VIEW.Kpp.key` was used. Although resource pattern `O4SRV.ACTIONS.VIEW.Kpp.key` is still supported when retrieving Take Action definitions, it is recommended that you use resource pattern `O4SRV.ACTIONS.Kpp.key`.	OA67404
Tivoli Enterprise Monitoring Server REST services have been enhanced, as follows: You can now retrieve history collection configurations. To control permissions, you must use SAF resource profiles. For more information, see Retrieving history collection configurations and Define SAF profiles to control permissions for history collection configurations. You can now edit situations. To control permissions, you must use SAF resource profiles. For more information, see Editing situations and Define SAF profiles to control permissions for situations.	OA66931
Starting with Tivoli Management Services on z/OS 6.3.3, IBM Z OMEGAMON AI Insights is included as a component. With IBM Z OMEGAMON AI Insights 2.1, the application is now containerized and deployed as a Docker container. For more information, see IBM Z OMEGAMON AI Insights.	—
Using Tivoli Enterprise Monitoring Server REST services, you can now execute a Take Action. To control permissions for users to execute a Take Action, you must use SAF resource profiles. For more information, see Executing a Take Action and Define SAF profiles to control Take Action permissions.	OA66461
Tivoli Enterprise Monitoring Server REST services have been enhanced, as follows: You can now start and stop situations using POST requests. To control permissions to the situations to start and stop, you must use SAF resource profiles. For more information, see Starting and stopping a situation and Define SAF profiles to control permissions for situations. When retrieving information for situations and applicable managed system data, you can now filter results by affinity ID (id). When requesting collection data, you can now specify an asterisk (*) for the cols parameter to include all table columns. When you request situation status information from the hub monitoring server, in addition to information from the hub monitoring server, the results now also include information about events from the remote monitoring server. For more information, see Tivoli Enterprise Monitoring Server REST services.	OA66540 OA66595
Tivoli Enterprise Monitoring Server REST services have been enhanced, as follows: You can now retrieve information about Take Action command definitions. When retrieving situation status information, you can now filter results by Origin Node (originnode) and Display Item (atomize). When using the expand parameter set to true, the name parameter is now required, you can now specify a start time using the timeFrom parameter, and historical information is included in the response. In addition to being able to restrict access to collection data, you can now use SAF profiles to also restrict access to situations, situation statuses, and Take Action command definitions. For more information, see new section Securing TEMS REST services. For more information, see Tivoli Enterprise Monitoring Server REST services.	OA66384
Tivoli Enterprise Monitoring Server REST services have been enhanced to retrieve information about situations for event monitoring, including situation status. You can also retrieve information about self-describing agent records. Additionally, support for user ID mapping for authorization has been added. For more information see Tivoli Enterprise Monitoring Server REST services.	OA65553
New Take Action command HTTPRQ (HTTP Request) creates an HTTP request when a situation occurs. For more information, see How to: Create an HTTP request for a situation.	OA65625
You can use OpenWebStart, an open-source Java Web Start replacement, to run your Tivoli Enterprise Portal client. For more information, see Tivoli Enterprise Portal and OpenWebStart.	—
A new OMEGAMON enhanced 3270 user interface parameter, CON_TIMEOUT, controls the number of seconds until timeout that the conduit manager uses when connecting to a data retrieval agent (DRA) socket. For more information, see Data retrieval delays/timeouts causing no data conditions. New parameter KOB_DRA_BACKLOG specifies the maximum number of queued connections for the DRA component of the OMEGAMON enhanced 3270 user interface. For more information, see KOB_DRA_BACKLOG.	OA65475
Tivoli Enterprise Monitoring Server REST services are available for accessing OMEGAMON collection data and select managed system data. For more information, see Tivoli Enterprise Monitoring Server REST services.	OA64983 OA65203
Starting from IBM Tivoli Monitoring V6.3.0.7, Docker technology is introduced to reduce the time and effort in installing the Tivoli Enterprise Portal Server. You can now run IBM Tivoli Monitoring - Tivoli Enterprise Portal Server Container in a Docker runtime environment on Linux on System z or on z/OS using z/OS Container Extensions. For more information, see Tivoli Enterprise Portal Server Container.	—
The IBM Tivoli Monitoring on z/OS framework now supports persistent data store V2 (PDS V2) for all history data sets. You can now use extended address volumes (EAV) for all history data sets. Using Configuration Manager or PARMGEN, you can configure the use of PDS V2 for the Tivoli Enterprise Monitoring Server using the new KDS_PDS2_* parameters. For more information, see Persistent data store V2 (PDS V2). Note: The IBM OMEGAMON for Storage on z/OS internal version of PDS V2 is no longer supported. IBM OMEGAMON for Storage users must use the OMNIMON Base version of PDS V2.	OA63242 OA63770 OA63966
Configuration Manager and PARMGEN now support PDS V2 parameters for the following IBM Advanced Storage Management agents: IBM Tivoli Advanced Allocation Management for z/OS 3.3 IBM Tivoli Automated Tape Allocation Manager for z/OS 3.3 IBM Tivoli Advanced Backup and Recovery for z/OS 2.4 See PDS V2 parameters and members and PDS data set names.	OA64006
Configuration Manager and PARMGEN now support PDS V2 parameters for IBM Tivoli Composite Application Manager for Application Diagnostics Agent 7.1.1. See PDS V2 parameters and members and PDS data set names.	OA63790
Configuration Manager and PARMGEN now support PDS V2 parameters for the following IBM Advanced Storage Management agents: IBM Tivoli Advanced Catalog Management for z/OS 2.6 IBM Tivoli Advanced Reporting and Management for DFSMShsm 2.6 IBM Tivoli Advanced Audit for DFSMShsm 2.6 See PDS V2 parameters and members and PDS data set names.	OA63566
A new configuration option is available for passphrase support for the OMEGAMON 3270 Classic user interface. For parameter Kpp_CLASSIC_PASSPHRASE (where `pp` is `C2`, `D2`, `I2`, or `M2`), you can now specify the value `MAX62`, which allows you to enter up to a 62-byte passphrase value on a single line when the screen width is 80 bytes. With a wider screen size, you can specify a passphrase value up to 100 bytes long. For more information, see How to: Configure passphrase and MFA support in the OMEGAMON 3270 Classic interface.	OA62991
Configuration Manager and PARMGEN now support PDS V2 parameters for IBM Z NetView Enterprise Management Agent. See PDS data set names.	OA63103
z/OS® data set encryption support has been added for persistent data store V2 (PDS V2). For more information, see How to: Use encryption for your PDS V2 data sets. With the installation of PTF UJ08510 for APAR OA62995, PDS V2 now requires z/OS 2.2 with OA50569 or later. Attention: After PTF UJ08510 is installed, if your system is not running z/OS 2.2 with OA50569 or later and you attempt to start the monitoring server or monitoring agent, PDS V2 initialization will fail and history data will be lost.	OA62995
The following commands have been added for managing persistent data store V2 (PDS V2) data sets: QUERY DATASTORE. For more information, see Displaying PDS V2 data set information. SWITCH. For more information, see Switching the active data set	OA62342
Support has been added for using the Tivoli administrative commands (tacmd) Command Line Interface (CLI) when your Tivoli Enterprise Monitoring Server resides on a z/OS system that is using multi-factor authentication (MFA). For more information, see (If applicable) Installing the tacmd CLI component.	OA62146
New messages have been added for support of IBM Z OMEGAMON Data Provider.	OA62052
For the OMEGAMON multi-tenancy solution, wildcard support for multi-tenancy user ID definitions has been added. For more information, see Creating tenant definitions in PDS members.	OA61889
A new type of user has been defined for the OMEGAMON multi-tenancy solution. Power users can access all menu options, icons and commands for all products assigned to their tenant. Power users also have additional navigational capabilities than the regular tenant user. For more information, see OMEGAMON multi-tenancy.	OA61210
Take Action command authorization and access settings can now be set using SAF profiles. This option provides centralized control to Take Action command access by a security administrator. For more information, see Configuring Take Action command access using SAF profiles.	OA61138 OA61140
Common parameters have been introduced for configuring PDS V2. RTE and agent-specific parameters can be used to activate the use of PDS V2 and to define data set allocation settings, improving the migration process from PDS V1 to PDS V2. These parameters are supported by PARMGEN and Configuration Manager. A utility is also provided that can be used to remove PDS V1 data sets after successful migration to PDS V2. For more information, see Persistent data store V2 (PDS V2).	OA60244 OA61008
Open Web Launch, an open-source Java Web Start replacement, can be used to run your Tivoli Enterprise Portal client. For more information, see Open Web Launch.	OA60952
Improvements have been made to PDS V2 data set allocation, management and usage. PDS V2 data set allocation and management behavior is now either space-based or time-based and depends on the Extent Constraint Removal (ECR) attribute of the SMS data class used when allocating the data sets. Additionally, the overall size of the PDS V2 data sets for an OMEGAMON product has been decreased and is now approximately equal to the size of the equivalent PDS V1 data sets. For more information, see Persistent data store V2 (PDS V2).	OA60782
IBM Z Monitoring Configuration Manager (Monitoring Configuration Manager) is a new tool for configuring runtime environments. Monitoring Configuration Manager evolved from Parameter Generator (PARMGEN). While PARMGEN and Monitoring Configuration Manager use the same parameters, Monitoring Configuration Manager simplifies the process of generating runtime members from those parameters. You can use PARMGEN or Monitoring Configuration Manager to configure, replicate, maintain, and update RTEs. For more information, see Configuring products and components on z/OS.	OA60562
For the OMEGAMON multi-tenancy solution, managed system types TCP, VTAM, and MFAD have been introduced for IBM OMEGAMON for Networks for z/OS. These new types replace managed system type MFN. For more information, see Creating tenant definitions in PDS members.	OA59694
IBM Z Service Management Explorer (IZSME) is a web-based replacement for the Tivoli Enterprise Portal (TEP). The same layout, workspaces, situations, and data available in the TEP are available in IZSME. IZSME is a web application running as a Zowe desktop plug-in, which eliminates the need to install and maintain Java and TEP software on client workstations as required with the TEP. For more information, see IBM Z Service Management Explorer. Note: IBM Z Service Management Explorer requires Tivoli Management Services V6.3.1.	OA59394
A new version of the persistent data store (PDS) has been introduced in OMNIMON Base Version 7.5.0. The new version (PDS V2) uses VSAM Linear Data Sets (LDSs) and replaces the original version (PDS V1), which uses BSAM data sets. PDS V2 is used for near-term history in all the OMEGAMON products. PDS V2 uses significantly less 31-bit virtual storage and less CPU usage than PDS V1, and there are no configuration changes required to use PDS V2. For more information, see Persistent data store V2 (PDS V2). PDS V2 supports agent history only; PDS V2 for ITM history is not supported. Note: PDS V2 was previously available for OMEGAMON for Storage only but is now available for all OMEGAMON products.	Multiple. See PDS V2 support.
OMEGAMON products support extended address volumes (EAV) for product data sets and agent history PDS data sets. PDS V2 for ITM history is not currently supported.	—
The OMEGAMON multi-tenancy solution allows the monitoring of distinctly separate sets of resources. With OMEGAMON multi-tenancy, general users can access information for resources assigned to their tenant only and cannot access information about the resources of another tenant. For more information, see OMEGAMON multi-tenancy.	OA57511
OMNIMON Base Version 7.5.0 provides enablement support for passphrase and multi-factor authentication (MFA). This support enables OMEGAMON 3270 (Classic) users to log on using passphrase and MFA credentials. This enhancement replaces the need for a user-customized assembler module (for example, a SAMPLIB Security exit) which generally defines the SAF Security class for OMEGAMON Classic started tasks. For more information, see OMNIMON Base Version 7.5.0 PTF UA98944 for APAR OA57133.	OA57133