/SDF/ZQLM - SQL Monitor messages
The following messages are stored in message class /SDF/ZQLM: SQL Monitor messages.
It is part of development package /SDF/ZQLM in software component SV-SMG-DIA. This development package consists of objects that can be grouped under "Package for SQL Monitor".
It is part of development package /SDF/ZQLM in software component SV-SMG-DIA. This development package consists of objects that can be grouped under "Package for SQL Monitor".
Message Nr ▲ | Message Text |
---|---|
000 | &1&2&3&4 |
001 | SQL Monitor already activated globally |
002 | SQL Monitor activated globally |
003 | Data could not be deleted |
004 | SQL Monitor activation not possible |
005 | SQL Monitor could not be deactivated |
006 | SQL Monitor not active |
007 | SQL Monitor deactivated |
008 | SQL Monitor is now active for &1 servers |
009 | SQL Monitor could not be activated for specified servers |
010 | Transaction canceled |
011 | Select at least one server for activating the SQL Monitor |
012 | Selected servers activated |
013 | No data found to delete |
014 | &1 SQL Monitor records have been deleted |
015 | &1 &2 is in the past. Please choose a date/time in the future |
016 | Deactivation job could not be deleted |
018 | Deactivation has been canceled |
019 | Deactivation has been scheduled |
020 | Enter date/time for deactivation of the SQL Monitor |
021 | No data found |
022 | No authorization for "&1" |
023 | Not able to retrieve SQL Monitor data |
024 | SQL Monitor is currently switched OFF by system profile parameter &1 |
025 | Invalid value for profile parameter &1: No reliable SQL Monitor results |
026 | &1 &2 entries updated |
027 | &1 RTM events collected from server &2 |
028 | /SDF/ZQLM cannot be started, latest kernel patch required (Note 1824769) |
030 | Deactivation scheduled for &1 &2 |
031 | User &1 is currently updating SQL Monitor data |
032 | &1 SQL Monitor records exist before action |
033 | Exception &1 during call of function module &2 (Server &3) |
034 | Server &1 cannot be reached |
035 | Deactivation of SQL monitor on server &1 failed |
036 | Activation of SQL monitor on server &1 failed |
037 | No messages exist |
038 | SQL monitor state '&2' on server &1 has been refreshed |
039 | Inconsistent activation state for server &1: Should be "&2" but is "&3" |
040 | SQL monitor state '&2' is consistent for server &1 |
041 | Deactivation of SQL Monitor on server &1 |
042 | Activation of SQL Monitor on server &1 |
043 | Ensure correct activation state for server &1 |
044 | SQL Monitor reset on all servers |
045 | &1 server(s) could not be reached |
046 | &1 server state(s) checked correctly |
047 | Registry for "&1" could not be created, "&2" is already registered/active |
048 | Registry for "&1" could not be removed, "&2" is already registered/active |
049 | RTM collect job could not be scheduled -> SQL Monitor activation canceled |
050 | Top n limit count must be between 1 and &1 |
051 | Periodic Job &1 was scheduled for &2 |
052 | Job &1 (Jobcount &2, User &3) cancelled |
053 | Job &1 for &2 could not created |
054 | Server &1 does not fulfill requirements for SQL Monitor |
055 | &1 records exist after update |
056 | Transaction &1 is outdated. Use transaction SQLM |
500 | SQL Monitor History is activated, but no collector is scheduled |
501 | History of SQL Monitor is not active |
502 | SQL Monitor is not activated. Activation in SQL Administration. |
503 | SQL Monitor history: &1 top statements updated. |
504 | SQL Monitor history: &1 statements saved in history, timestamp &2 |
505 | SQL Monitor reorganization: &1 records deleted in history |
506 | SQL Monitor reorganization: History has been reduced by &1 records |
507 | SQL Monitor history has been activated |
508 | SQL Monitor history has been deactivated |
509 | Job &1 has been deleted |
510 | Historical data has been deleted |
511 | SQL Monitor is not active. Therefore no history is created. |
700 | Enter today's date or an earlier date |