Message Number list used by SAP ABAP Class CL_SQLM_ADMIN (Admin Tool for SQL Monitor)
SAP ABAP Class
CL_SQLM_ADMIN (Admin Tool for SQL Monitor) is using
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
| 1 | SQLM - 047 | Registry for "&1" could not be created, "&2" is already registered/active | ||
| 2 | SQLM - 034 | Server &1 cannot be reached | ||
| 3 | SQLM - 034 | Server &1 cannot be reached | ||
| 4 | SQLM - 036 | Activation of SQL monitor on server &1 failed | ||
| 5 | SQLM - 038 | SQL monitor state '&2' on server &1 has been refreshed | ||
| 6 | SQLM - 039 | Inconsistent activation state for server &1: Should be "&2" but is "&3" | ||
| 7 | SQLM - 040 | SQL monitor state '&2' is consistent for server &1 | ||
| 8 | SQLM - 041 | Deactivation of SQL Monitor on server &1 | ||
| 9 | SQLM - 042 | Activation of SQL Monitor on server &1 | ||
| 10 | SQLM - 042 | Activation of SQL Monitor on server &1 | ||
| 11 | SQLM - 043 | Ensure correct activation state for server &1 | ||
| 12 | SQLM - 045 | &1 servers could not be reached | ||
| 13 | SQLM - 034 | Server &1 cannot be reached | ||
| 14 | SQLM - 048 | Registry for "&1" could not be removed, "&2" is already registered/active | ||
| 15 | SQLM - 049 | RTM collect job could not be scheduled -> SQL Monitor activation canceled | ||
| 16 | SQLM - 051 | Periodic Job &1 was scheduled for &2 | ||
| 17 | SQLM - 051 | Periodic Job &1 was scheduled for &2 | ||
| 18 | SQLM - 052 | Job &1 (Jobcount &2, User &3) cancelled | ||
| 19 | SQLM - 053 | Job &1 for &2 could not created | ||
| 20 | SQLM - 054 | Server &1 does not fulfill requirements for SQL Monitor | ||
| 21 | SQLM - 058 | Failed to repair inconsistent subtest activation state | ||
| 22 | SQLM - 072 | Can't release update job. Check job release authorization and react. SQLM | ||
| 23 | SQLM - 073 | Can't release deactivation job. Check job release authorization. | ||
| 24 | SQLM - 024 | SQL Monitor is currently switched OFF by system profile parameter &1 | ||
| 25 | SQLM - 000 | &1&2&3&4 | ||
| 26 | SQLM - 003 | Data could not be deleted | ||
| 27 | SQLM - 004 | SQL Monitor activation not possible | ||
| 28 | SQLM - 005 | SQL Monitor could not be deactivated | ||
| 29 | SQLM - 008 | SQL Monitor is now active for &1 servers | ||
| 30 | SQLM - 009 | SQL Monitor could not be activated for selected servers | ||
| 31 | SQLM - 015 | &1 &2 is in the past. Please choose a date/time in the future | ||
| 32 | SQLM - 016 | Deactivation job could not be deleted | ||
| 33 | SQLM - 022 | No authorization for "&1" | ||
| 34 | SQLM - 023 | Not able to retrieve SQL Monitor data | ||
| 35 | SQLM - 000 | &1&2&3&4 | ||
| 36 | SQLM - 025 | Invalid value for profile parameter &1: No reliable SQL Monitor results | ||
| 37 | SQLM - 026 | &1 &2 entries updated | ||
| 38 | SQLM - 027 | &1 RTM events collected from server &2 | ||
| 39 | SQLM - 028 | SQLM cannot be started, latest kernel patch required (Note 1824769) | ||
| 40 | SQLM - 028 | SQLM cannot be started, latest kernel patch required (Note 1824769) | ||
| 41 | SQLM - 031 | User &1 is currently updating SQL Monitor data | ||
| 42 | SQLM - 033 | Exception &1 during call of function module &2 (Server &3) | ||
| 43 | SQLM - 033 | Exception &1 during call of function module &2 (Server &3) | ||
| 44 | SQLM - 033 | Exception &1 during call of function module &2 (Server &3) | ||
| 45 | SQLM - 034 | Server &1 cannot be reached |