1. The monitor tree suddenly disappears...
Every monitor tree is classified by a visibility level (RZ20 -> "Extras" -> "Display options"). This way, only objects which correspond to this level are displayed in the tree. However, if an alert appears for any object in the tree, the entire subtree is visible regardless of the visibility level. This behavior may lead to the tree disappearing after an alert is reset and the node is displayed with a gray background.
2. Actions in the tree are executed for elements other than those expected.
In the tree (RZ20), selections for nodes are retained and also saved when the monitor is saved. This happens even if the selected nodes are not visible because the corresponding subtree was not expanded.
This way actions can be executed for selected nodes although the nodes are not visible.
Remedy: In case of doubt click the "Deselect all" button and then reselect the required nodes again.
3. The cursor position has no effect.
When you analyze the open alerts of an MTE, it is absolutely necessary to make a selection by setting the corresponding flag (checkbox).
The position of the cursor has no effect here.
4. Automatic refreshing
An automatic refreshing of the displayed alerts is available in Release 4.5A along with the newest SAPgui version.
5. Externalizing alerts
The externalization of the R/3 alerts will not be carried out until further notice on an SNMP basis, which was previously not the case either. However, various partners (see SAPNet) offer agents which read our MIB and proceed with the help of SNMP. SAP makes corresponding C libraries available for this which can be downloaded from SAPSERV*.
It is also not planned to link external tools directly via SNMP to the monitoring infrastructure.
In the case of a possible MIB enhancement, the partners are informed.
6. Syslog threshold value maintenance
Unlike other MTEs, threshold value maintenance of the syslog is carried out with Transaction RZ06 up to and including Release 4.0B.
7. Authorization check
To start transaction RZ20 you need an authorization for object S_RZL_ADM. Within RZ20, no further authorization checks are carried out.
8. Time differences
The time zones are not active. Use Notes 91667 and 0100442.
9. ORACLE monitoring
You can monitor the ORACLE database in Release 4.5A from within Transaction RZ20.
10. Significance of the attribute EnqueueTime
It is the waiting time till setting a lock.
11. Shutting down the CCMS monitor architecture for an application server.
Monitoring an application server is hidden in the display Transaction RZ20 as follows,
RZ21 ('Monitoring: Settings and Tool Maintenance') --> "Contexts/segments"--> "Segments". Select a segment --> "Edit data" --> Set the status to 'Offline' and save.
With this, only the monitoring of the RZ20 is hidden. The monitoring runtime environment continues (report values, possibly triggers alerts, etc.). If the monitoring runtime environment is turned off, the profile parameter alert/MONI_SEGM_SIZE=0 should be set as described in Note 135503.
12. The CCMS monitor architecture profile parameter
see Note 135503
13. Only nodes with icons are in the tree, but without node names.
Cause: The monitoring segment (in the shared memory) is full. No additional nodes can be created correctly. Solution: Increase the profile parameters alert/MONI_SEGM_SIZE on the affected application server (see Note 135503) and restart the application server.
14. Only 4.0B (as of patch level 81): missing Syslog-Alerts
are solved using patch level 271 (see Note 135977).
15. Swapping the values for 'Single Record' and 'Generic Key' in the display of RZ20:
This error is corrected with the application of Hot Packages SAPKH40B19 (4.0B) or SAPKH45B03 (4.5B).
16. Logical command as tool (RZ21) is not started
Up to and including Release 4.5B you can select 'external command' in the tool definition under 'Call type' in RZ21. However, a function that executes the logical command when starting the tool via RZ20 is missing in the source code of RZ20 so that the execution of the tool has no effect. As of Release 4.6A you can no longer select 'external command' in RZ21.
In some releases, there is a method CCMS_NT_EVENT in RZ21 which is intended to execute the logical command Z_SEND_ALERT. This method definition can be deleted in RZ21.
17. How do I write a Data-Supplier?
See the document stored on SAPNET:
"Writing a Data Supplier for the R/3 Release 4 Alert Monitor"
under the alias System Management -> System Monitoring and Alert Management
18. All segments in RZ21 are on shutdown although the instances are visible in SM51 (precise symptom: function module RFC_GET_LOCAL_DESTINATIONS delivers an empty table as the result).
Cause: Incorrect TCP/IP configuration. Implement Note 52959.
19. Current status of an MTE red, but no allert exists
Sometimes a node in the 'Current status' displays a red message but no alerts exist for it.
Scenario:
(1) A red message is displayed and triggers an alert.
(2) Someone completes the alert but no other message is displayed
in the meantime
Since the alert is completed for 'Open alerts' everything is green. However, since the last red message is still the currently valid message, the 'Current status' is still red.
Via RZ20 -> Properties -> Methods
'In absence of values deactivate after'
you can specify, when a note is displayed in grey, if no new values are reported. CAUTION: If this value is set to 0, the node will never become inactive.
20. How can I set specific nodes to 'disabled'?
Activate the maintenance function in RZ20, select the required node and
RZ20->Edit->Alert->Configurate generation -> Suppress. In this way an entry is made in the shared memory for MTE that the alert generation is 'disabled'. In order to make this work correctly, you should use the 4.6D kernel.
As of Release 6.20, this function can be selected via the following menu entry:
RZ20-> Edit->Node->Deactivate
21. Method dispatching for data acquisition programs
Short-term data acquistion programs are controlled by the SAPSYS within the AutoABAP SAPMSSY6. You do not need to define anything here. Long-term data acquisition programs run in the background job SAP_CCMS_MONI_BATCH_DP. This job is activated by pressing a button; it is then automatically planned and activated. The long-term data acquisition programs executed in the background run under the user (and relevant user authorization) who activates the background job as follows: Technical Infrastructure-> Method execution -> Activate background processing. Please activate the background job once for each monitored system.
22. RZ21: Execute function modules as methods
If a new method is to be created in RZ21 that executes a function module, the interface definition of this module must meet the requirements described in the White Paper
'How to write a data supplier'.
Module SALT_TOOL_REFERENCE_MODULE delivered by SAP can be used as template for an individual module.