| RT048 |
File systems for the application server |
| RT049 |
Runtime messages for self-monitoring of CCMS monitoring architecture |
| RT050 |
Messages regarding delivered data collectors |
| RT051 |
Monitoring Object: File system |
| RT052 |
Technical name for the file system |
| RT053 |
Monitoring object: CPU |
| RT054 |
CPU: Average usage |
| RT055 |
CPU: Average number of waiting processes |
| RT056 |
Monitoring object: Paging (page overlapping) |
| RT057 |
Paging: Page in: Pages per second |
| RT058 |
Paging: Page out: Pages per second |
| RT059 |
Monitoring object: Swap Space |
| RT060 |
Available Swap Space |
| RT061 |
Percentage of Swap Space used |
| RT062 |
Monitoring object: OS collector (SAPOSCOL) |
| RT063 |
CCMS monitoring architecture self-monitoring: RFC problems |
| RT064 |
Monitoring object: Buffer |
| RT065 |
Buffer: Percentage use of directory |
| RT066 |
Buffer: Percentage usage of buffer memory |
| RT067 |
Buffer: Hit rate |
| RT068 |
Application server: Number of logged-on users |
| RT069 |
Error occurred when calling an SALS function: &1&2 |
| RT070 |
System log log attribute: various |
| RT071 |
System log log attribute: application |
| RT072 |
System log log attribute: background processing |
| RT073 |
System log log attribute: Basis System |
| RT074 |
System log log attribute: operation tracking (CCMS) |
| RT075 |
System log log attribute: database |
| RT076 |
System log log attribute: customer message |
| RT077 |
System log log attribute: communication |
| RT078 |
System log attribute: spool / print |
| RT079 |
System log log attribute: security |
| RT080 |
System log attribute: transport system |
| RT081 |
System log log attribute: batch input |
| RT082 |
SAPMSSY8 started |
| RT083 |
SAPMSSY8 completed |
| RT084 |
Update of table ALCONSEG complete |
| RT085 |
Customizing data compared with DB |
| RT086 |
Tool assignment compared with DB |
| RT087 |
Startup methods started |
| RT088 |
CCMS monitoring architecture self-monitoring: SAPMSSY8 messages |
| RT089 |
>> Tool dispatching started for application server segment |
| RT090 |
CCMS monitoring architecture self-monitoring: SAPMSSY8 runtime |
| RT091 |
CCMS self-monitoring: Runtime of the SAPMSSY8 &1 &3 exceeds &2 &3 |
| RT092 |
CCMS monitoring architecture: Sample data supplier: MO |
| RT093 |
CCMS Monitoring Architecture: Sample data supplier: Performance MA |
| RT094 |
CCMS Monitoring Architecture: Sample data supplier: Status message MA |
| RT095 |
Parameter &1 = &2 invalid (valid: &3 ... &4) |
| RT096 |
Invalid parameter combination: &1 >= &2 necessary! |
| RT097 |
CCMS self-monitoring: Number of completed alerts in the database |
| RT098 |
Number of completed alerts in database &1 exceeds threshold value &2 |
| RT099 |
>> Tool dispatching started for segment & using CCMS agent |
| RT100 |
&1 &2 |
| RT101 |
&1 successfully completed |
| RT102 |
&1 [&2] in &3 on &4 |
| RT103 |
Method dispatcher &1 for segment &2 started |
| RT104 |
Invalid tool dispatcher name: &1 |
| RT105 |
Invalid dialog mode: &1 |
| RT106 |
Invalid tool start mode: &1 |
| RT107 |
System could not determine which methods to execute: &1 &2 |
| RT108 |
System could not read RFC destination (&1), MTE: &2 |
| RT109 |
System could not determine technical method information for tool &1 |
| RT110 |
Method starter cannot start a method as no method selected |
| RT111 |
Method dispatcher &1 for segment &2 ended |
| RT112 |
Tool starter cannot start any tools as user/dispatcher name missing |
| RT113 |
Invalid maximum runtime value (&1) |
| RT114 |
Invalid tool start mode (&1) |
| RT115 |
Unable to set runtime status for data collection method (&1), MTE: &2 |
| RT116 |
Could not set alert status for auto-reaction method (&1), MTE: &2 |
| RT117 |
& |
| RT118 |
Segment name &1 is invalid |
| RT119 |
Cannot start tool &1 |
| RT120 |
Method &1: Runtime exceeded (&2 seconds) |
| RT121 |
Unable to determine the tool that terminated: &1 |
| RT122 |
Method &1 terminated. This affects MTE: &2 |
| RT123 |
Method dispatcher &1 already running for segment &2 |
| RT124 |
Error in lock management - cannot start method dispatcher &1 |
| RT125 |
Monitoring object: dialog service |
| RT126 |
Average response time of dialog service |
| RT127 |
&1 &3 > &2 &3 Dialog response time exceeds threshold (&4 dialog steps) |
| RT128 |
Average dispatcher wait time per dialog step |
| RT129 |
&1 &3 > &2 &3 Dialog wait time exceeds threshold (&4 dialog steps) |
| RT130 |
Average load and generation time for GUI objects |
| RT131 |
&1 &3 > &2 &3 Dialog load/gen. time exceeds threshold (&4 dialog steps) |
| RT132 |
Average time for processing logical database requests |
| RT133 |
&1 &3 > &2 &3 Dialog DB request time exceeds threshold (&4 dialog steps) |
| RT134 |
Average usage of dialog work processes of an application server |
| RT135 |
&1 &3 > &2 &3 dialog workprocess utilization exceeds threshold value |
| RT136 |
Average usage of dispatcher wait queue for dialog work processes |
| RT137 |
&1 &3 > &2 &3 dialog workprocess queue length exceeds threshold |
| RT138 |
Average time for long-running dialog work processes |
| RT139 |
Long-running report &4 has been running &1 &3 in dialog. Threshold: &2 &3 |
| RT140 |
ABAP program terminations in dialog work processes |
| RT141 |
CCMS monitoring architecture: data supplier example: message log MA |
| RT142 |
ABAP error: &1 in SNAP: &2 (client &3) |
| RT143 |
ABAP SQL error: &1 in SNAP: &2 |
| RT144 |
Response time exceeds one hour for report &1 (user: &2 client: &3) |
| RT145 |
Average number of dialog steps per minute |
| RT146 |
Average time for monitoring during a dialog step |
| RT147 |
&1 &3 > &2 &3 number of dialog steps per minute exceeds threshold |