/SOMO/JOBMON - Messages for Unified Job Monitoring
The following messages are stored in message class /SOMO/JOBMON: Messages for Unified Job Monitoring.
It is part of development package /SOMO/MA_6X_MAIN in software component SV-SMG-SDD. This development package consists of objects that can be grouped under "Release >=6.XX: Solution Monitoring: Data Suppliers".
It is part of development package /SOMO/MA_6X_MAIN in software component SV-SMG-SDD. This development package consists of objects that can be grouped under "Release >=6.XX: Solution Monitoring: Data Suppliers".
Message Nr ▲ | Message Text |
|---|---|
| 100 | &1 started late by &2 minutes at &3 |
| 101 | &1 current duration &2 minutes (maximum permitted is &3 minutes) |
| 102 | &1 will be started outside of time window (&2 - &3) |
| 103 | &1 finished at &2 outside of time window (&3 - &4) |
| 104 | &1 started at &2 finished at &3 outside of time window (&4 - &5) |
| 105 | &1 started at &2 outside of time window (&3 - &4) |
| 106 | &1 cancelled |
| 107 | Incorrect parallel processing - &2 &1(s) instead of &3 &4(s) |
| 108 | &1 finished with delay of &2 minutes on &3 at &4 |
| 109 | In log of &1 &2 x: &3 |
| 110 | &1 delayed by &2 minutes; not started yet; planned start time &3 |
| 111 | &1 will be finished outside of time window (&2 - &3) |
| 112 | Job |
| 113 | Chain |
| 114 | Chain element |
| 115 | &1 started on &2 at &3 |
| 116 | &1 is active for &2 minutes |
| 117 | &1 finished after &2 minutes |
| 118 | &1 aborted after &2 minutes |
| 119 | &1 finished on &2 at &3 |
| 120 | &1 aborted on &2 at &3 |
| 121 | &1 started on &2 at &3 and has a end delay of &4 |
| 122 | &1 aborted on &2 at &3 with end delay of &4 |
| 123 | &1 finished at &2 inside of time window (&3 - &4) |
| 124 | &1 aborted at &2 inside of time window (&3 - &4) |
| 125 | &1 with schedule date &2; not yet started |
| 126 | &1 delayed by &2 minutes; unable to find job; planned start time &3 |
| 127 | &1 started too late on &2 at &3 |
| 128 | No &1 was started by &2 |
| 129 | Counter with value &1 is greater than &2 |
| 130 | Counter with value &1 is less than &2 |
| 131 | &1 will finish with delay of at least &2 minutes |
| 132 | &1 is active |
| 133 | Last &1 was active until &2 at &3 |
| 134 | No &2 has been active in the last &1 minutes |
| 135 | &1 was found. But the job was not started. |
| 136 | &1 aborted on &2 at &3. |
| 137 | &1 finished on &2 at &3. |
| 138 | &1 finished with status: &2 |
| 139 | Number of sent records (&1) is below or reached minimum (&2) |
| 140 | Number of inserted records (&1) is below or reached minimum (&2) |
| 141 | Number of sent records (&1) reached or exceeded maximum (&2) |
| 142 | Number of inserted records (&1) reached or exceeded maximum (&2) |
| 143 | Number of data packages processed (&1) is below or reached minimum (&2) |
| 144 | Number of data packages processed (&1) reached or exceeded maximum (&2) |
| 145 | &1 current duration &2 minutes (minimum expected is &3 minutes) |
| 146 | Check status of &1 - Status &2 |
| 147 | &1 with value &2 |
| 148 | Number of sent records &1 |
| 149 | Number of inserted records &1 |
| 150 | Number of data packages processed &1 |
| 151 | &1 finished successfully |
| 152 | &1 is still running |
| 153 | &1 started at &2 inside of time window (&3 - &4) |
| 154 | Log message : &1 |
| 155 | Counter has value &1 |
| 156 | &2 parallel jobs were started. |
| 157 | Number of rows read (&1) is below or reached minimum (&2) |
| 158 | Number of rows read (&1) reached or exceeded maximum (&2) |
| 159 | Number of rows read &1 |
| 160 | Message Class '&1', Message Number '&2' |
| 161 | Error &1 in &2->&3 |
| 162 | Ready |
| 163 | Scheduled |
| 164 | Released |
| 165 | Canceled |
| 166 | Finished |
| 167 | Put Active |
| 168 | Unknown Status |
| 169 | Running |
| 170 | Chain Header: &1 (&2, &3) |
| 171 | Failed element |
| 172 | Failed elements |
| 200 | Metric & not defined for object id & - ( metric id & context id &) |
| 201 | Metric data for monid & could not be saved to database ( code & ) |
| 202 | No selection parameter information found |
| 203 | Conversion error for monitoring id & with Parameter ID & |
| 204 | Program for ST-API collector not found |
| 205 | Wrong chain start time & & & & |
| 206 | Monitoring object & is currently locked (context id & ) |
| 207 | Monitoring object & has no parameter defined (context id & ) |
| 208 | Monitoring id & with parameter & for job type & is not defined (&) |
| 209 | Monitoring id & parameter & is missing (&) |
| 210 | Monitoring id & job schedule is incorrect - error code & (&) |
| 211 | Message &1 x: |
| 212 | Message with class &1 and number &2 not defined |
| 213 | Counter for message variable &1 is &2 in message: |
| 214 | ST function E2E_BO_JOBS_JOBMON for BO job collection not found. |
| 215 | ST function E2E_BO_DATA_SERVICES_JOBMON for DS job collection not found. |
| 216 | Monitoring object & could not be activated (context id & ) |
| 217 | Fast Search Criteria locked for monitoring object & (context id & ) |
| 218 | Could not retrieve managed system time of system &1 |
| 219 | &1. &2 did not start by &3 on &4 |
| 220 | &1 started too late (on &2 at &3) relative to job &4 |
| 221 | No BACK destination found |
| 222 | FM AI_CUST_JOB_TYPE_PARAMS not available in Solution Manager |
| 223 | Alert parameters could not be read |
| 224 | The Log Status is Successful |
| 225 | The Log Status is in Error |
| 226 | The Log Status is in Warning |
| 227 | The Log Status is Aborted |