/SDF/SMON - Messages for ST-PI Monitoring tools
The following messages are stored in message class /SDF/SMON: Messages for ST-PI Monitoring tools.
It is part of development package /SDF/SMON in software component SV-SMG-DIA. This development package consists of objects that can be grouped under "Snapshot Monitor".
It is part of development package /SDF/SMON in software component SV-SMG-DIA. This development package consists of objects that can be grouped under "Snapshot Monitor".
Message Nr ▲ | Message Text |
|---|---|
| 000 | ABAP Statement cannot be displayed |
| 001 | SQL Statement cannot be displayed |
| 002 | Performance Trace could not be activated |
| 003 | Performance Trace has been activated |
| 004 | ABAP Trace could not be activated |
| 005 | ABAP Trace has been activated |
| 006 | Performance Trace has been deactivated |
| 007 | ABAP Trace has been deactivated |
| 008 | No Server selected. Local server is taken per default |
| 009 | No Server selected. All servers are taken per default |
| 010 | End time has already passed. |
| 011 | There is an overlapping analysis '&1' running or scheduled |
| 012 | There are already other analyses running |
| 013 | Please enter a description |
| 014 | Analysis &1 has already finished. |
| 015 | No detailed information available |
| 016 | Last entry reached |
| 017 | First entry reached |
| 018 | Analysis '&1' has been scheduled |
| 019 | Analysis '&1' has been started |
| 020 | No Analyses found for the given criteria |
| 021 | No valid Analysis selected |
| 022 | Frequency must be lower than parameter rdisp/max_wprun_time |
| 023 | Trace file cannot be diplayed |
| 024 | Problem when calling transaction &1 |
| 025 | Destination &1 not available |
| 026 | SAP Basis release of system &1 too low |
| 027 | ST-PI release in system &1 is not up-to-date |
| 028 | System &1 is already included via destination &2. |
| 029 | Work Process &1 on instance &2 locked |
| 030 | Work Process &1 on instance &2 unlocked |
| 031 | Error |
| 032 | Work processes for analysis will be locked. |
| 033 | Work processes for analysis will not be locked. |
| 034 | Monitoring the inbound queue may cause a high workload |
| 035 | Monitoring the outbound queue may cause a high workload |
| 036 | Monitoring the user sessions might cause a large data footprint |
| 037 | Multiple Selection not possible for this function |
| 038 | Start time after end time |
| 039 | Job cannot be scheduled |
| 040 | Job &1 has been created with start date &2. |
| 041 | Job &1 has been deleted |
| 042 | Collecting the enqueue entries may put a load on the enqueue table |
| 043 | File not saved |
| 044 | File saved under &1 |
| 045 | Start time must be earlier than end time |
| 046 | Job &1 with start date &2 has been adapted |
| 047 | Collectors of analysis &1 have been restarted |
| 048 | No statistical records found |
| 049 | Analysis &1 has already been moved to the cluster table |
| 050 | Analysis &1 has already been restored from the cluster table |
| 051 | Running analyses cannot be moved to the cluster table |
| 052 | The display of all SM50 data is not recommended! |
| 053 | No entry selected |
| 054 | No authority to read data |
| 055 | Data has different timestamp |
| 056 | Start Time is in the past |
| 057 | Only 1 Watchdog is allowed. All running /SDF/SMON_WATCHDOG are deleted. |
| 058 | Daily Analysis can only be stopped via New/Stop Daily Monitoring. |
| 059 | End time has been passed, Daily Monitoring sceduled for tomorrow only. |
| 060 | Over two days period Daily Monitoring must be scheduled instead. |
| 061 | Response time is estimated with the current timestamp. |
| 062 | Response time estimation failed. |
| 063 | Job deletion failed. Delete manually job /SDF/SMON_WATCHDOG. |