You can transfer the counter statuses of the UDS monitor’s counter mask to openSM2 and present them there in graphical form using, for example, INSPECTOR. Some of these counter statuses can also be output on the terminal using the UDS SQL report of openSM2 or be evaluated in the SM2R1 reports.
A detailed description of openSM2 is provided in the "openSM2 (BS2000)" manual.
Prerequisite in UDS/SQL
When the UDS monitor is started, you initiate the transfer of the counter statuses in the counter mask to openSM2 using the following statement:
MEDIUM=S,n
During operation (see “Statements and commands for UDSMON”) you start the transfer of the counter statuses to openSM2 with the command
INFORM-PROGRAM MSG=’ADD MEDIUM=S,n’
You terminate the transfer of the counter statuses with the command
INFORM-PROGRAM MSG=’FINISH MEDIUM=S’
n defines the interval in seconds (5 <= n <= 999) at which the UDS monitor supplies the data to SM2. It should be considerably lower than the measuring interval set in SM2 so that data can be transferred several times within an SM2 measuring interval.
The counter statuses can be transferred to openSM2 by means of a monitor instance which also initiates other outputs (outputs on the terminal, to a list or, in a special format, to a file). However, to guarantee uninterrupted supply it is recommended that you use a separate monitor run in the background to transfer the counter statuses to openSM2. When monitor instances run in the foreground, there is a risk that interruptions to change output media, masks or intervals will have undesired repercussions on the presentation of the counter statuses in openSM2.
Prerequisite in BS2000
A prerequisite for transferring data to openSM2 is that the receipt of the data is activated in the collector in SM2 with the following statement:
START-MEASUREMENT-PROGRAM TYPE=*UDS-SQL
If this interface is not activated or was deactivated with the STOP-MEASUREMENT-PROGRAM TYPE=*UDS-SQL statement, UDS/SQL issues a corresponding error message (UDS0536) once only.
However, an attempt is still made to supply openSM2 with the data so that after the UDS-SQL collecting program has been started the data can be transferred to openSM2 without any further measures being required in the UDS monitor.
To use the transferred data in INSPECTOR it is necessary for the INSPECTOR’s agent to be active in BS2000 (START-INSPECTOR).
The duration of one or more UDS/SQL intervals is used to standardize the measurement intervals to within a second. The values are therefore exact, but they only match the SM2 interval to a certain degree.
Displaying the counter with INSPECTOR
The INSPECTOR component of openSM2 enables you to present the data of the counter mask in graphical format on a workstation and to display it together with other usage values of the BS2000 system. In the UDS-SQL report group you select which counter statuses are to be displayed. At all times you can trace the development of the counter statuses over time, and thus assess the system behavior and detect problems at an early juncture.
In particular you can monitor the data on the basis of user-defined rules and thus recognize unusual statuses. In a rule conditions and actions can be specified. If the conditions apply, the associated actions are performed, e.g. SNMP traps can be triggered which lead to messages being sent to a connected SNMP station via the SM2 performance subagent, or emails relating to events can be sent.
A description of how to use INSPECTOR and a list of UDS/SQL counters which can be displayed there is provided in the "openSM2 (BS2000)" manual. A description of the SM2 performance subagent is provided in the "SNMP Management (BS2000)" manual.
Outputting the UDS SQL report of openSM2
You can also output some counter statuses of the counter mask on the BS2000 terminal using the UDS SQL report of openSM2. A detailed description of the UDS SQL report of openSM2 is provided in the "openSM2 (BS2000)" manual.