# |
Message |
Message Short Text |
Documentation status |
Authorization check |
1 |
001 |
Delete aggregation level of reorganization for: |
The short text describes the object sufficiently |
|
2 |
002 |
Entry deleted successfully |
The short text describes the object sufficiently |
|
3 |
003 |
Insert new aggregation level of reorganization for: |
The short text describes the object sufficiently |
|
4 |
004 |
Entry created |
The short text describes the object sufficiently |
|
5 |
005 |
Change aggregation level of reorganization for: |
The short text describes the object sufficiently |
|
6 |
006 |
Entry changed |
The short text describes the object sufficiently |
|
7 |
007 |
Check aggregation data for: |
The short text describes the object sufficiently |
|
8 |
010 |
Process group: <&1> Process type: <&2> |
The short text describes the object sufficiently |
|
9 |
011 |
Cumulation level: <&1> |
The short text describes the object sufficiently |
|
10 |
012 |
Cumulation level <&1>: Delay <&1> is long enough |
The short text describes the object sufficiently |
|
11 |
020 |
Error when determining process group of process type <&1> |
The short text describes the object sufficiently |
|
12 |
022 |
You cannot delete the only cumulation level of the fallback |
The short text describes the object sufficiently |
|
13 |
023 |
No suitable entry found in table |
The short text describes the object sufficiently |
|
14 |
024 |
Entry already exists |
The short text describes the object sufficiently |
|
15 |
025 |
This entry does not already exist |
The short text describes the object sufficiently |
|
16 |
026 |
No suitable administration data exists for the cumulation |
The short text describes the object sufficiently |
|
17 |
027 |
No data found. Check cumulation for: |
The short text describes the object sufficiently |
|
18 |
028 |
No administration data exists for the cumulation |
The short text describes the object sufficiently |
|
19 |
029 |
Cumulation level <&1>: Delay <&1> must be greater than <&3> |
The short text describes the object sufficiently |
|
20 |
030 |
Cumulation level <Delete Data> missing |
The short text describes the object sufficiently |
|
21 |
040 |
Settings saved |
The short text describes the object sufficiently |
|
22 |
041 |
Process activated |
The short text describes the object sufficiently |
|
23 |
042 |
Unable to activate process |
The short text describes the object sufficiently |
|
24 |
043 |
Process deactivated |
The short text describes the object sufficiently |
|
25 |
044 |
Could not deactivate process |
The short text describes the object sufficiently |
|
26 |
050 |
&1 entries deleted from administration table for high event volume |
The short text describes the object sufficiently |
|
27 |
051 |
&1 entries deleted from administration table 'Step/Transport Job' |
The short text describes the object sufficiently |
|
28 |
060 |
Select a process type and metric |
The short text describes the object sufficiently |
|
29 |
100 |
Start of Cumulation: &1 |
The short text describes the object sufficiently |
|
30 |
101 |
Everything aggregated successfully |
|
|
31 |
110 |
No cumulation intervals exist |
The short text describes the object sufficiently |
|
32 |
111 |
An error occurred during tool retrieval |
The short text describes the object sufficiently |
|
33 |
112 |
No tools found for process |
The short text describes the object sufficiently |
|
34 |
113 |
<&1> to <&2> |
The short text describes the object sufficiently |
|
35 |
114 |
<&1> was successful |
The short text describes the object sufficiently |
|
36 |
115 |
<&1> had errors |
The short text describes the object sufficiently |
|
37 |
116 |
A total of &1 process instances were collected for cumulation (&2) |
The short text describes the object sufficiently |
|
38 |
117 |
A total of &1 process instances were updated in the process store (&2) |
The short text describes the object sufficiently |
|
39 |
118 |
Deleting data up to <&1> |
The short text describes the object sufficiently |
|
40 |
119 |
A total of &1 cumulation sets were deleted (&2) |
The short text describes the object sufficiently |
|
41 |
120 |
Error when calculating cumulation intervals |
The short text describes the object sufficiently |
|
42 |
121 |
Exception when generating customizing class for process type |
The short text describes the object sufficiently |
|
43 |
122 |
Exception in tool selection |
The short text describes the object sufficiently |
|
44 |
123 |
Tool <&1> has no cumulation logic (check table SSPICOMPD) |
The short text describes the object sufficiently |
|
45 |
125 |
Cumulation of process was incorrect - see log |
Space: object requires documentation |
|
46 |
200 |
&1 - Reorganizing central store |
Space: object requires documentation |
|
47 |
201 |
Deleting data pairs of all inactive process types |
The short text describes the object sufficiently |
|
48 |
202 |
Deleting data pairs that do not belong to any active process type |
The short text describes the object sufficiently |
|
49 |
203 |
Deleting payload data without tracking header |
Space: object requires documentation |
|
50 |
204 |
Deleting data pairs of active process types that are no longer used |
Space: object requires documentation |
|
51 |
209 |
Incomplete administration data |
The short text describes the object sufficiently |
|
52 |
210 |
&1 inactive process types have been selected |
The short text describes the object sufficiently |
|
53 |
211 |
No inactive process types have been selected |
Space: object requires documentation |
|
54 |
212 |
Signatures for the inactive process types were selected |
The short text describes the object sufficiently |
|
55 |
213 |
<&1>: Error while determining signatures |
Space: object requires documentation |
|
56 |
214 |
<&1> |
Space: object requires documentation |
|
57 |
215 |
A total of &1 signatures have been selected (without system signatures) |
The short text describes the object sufficiently |
|
58 |
216 |
Deleting in packages for &1 tracking headers + payload data |
Space: object requires documentation |
|
59 |
217 |
&4 header entries and &3 payload entries were deleted (package &1, &2) |
Space: object requires documentation |
|
60 |
218 |
Error while deleting package &1 (&2) |
Space: object requires documentation |
|
61 |
219 |
No more entries were selected |
The short text describes the object sufficiently |
|
62 |
220 |
Error while selecting package &1 |
The short text describes the object sufficiently |
|
63 |
221 |
Deleting obsolete data from system signatures |
The short text describes the object sufficiently |
|
64 |
222 |
&1 system signatures were selected |
The short text describes the object sufficiently |
|
65 |
223 |
No system signatures were selected |
The short text describes the object sufficiently |
|
66 |
230 |
&1 active process types were selected |
The short text describes the object sufficiently |
|
67 |
231 |
No active process types were selected |
Space: object requires documentation |
|
68 |
232 |
Signatures for the active process types were selected |
The short text describes the object sufficiently |
|
69 |
233 |
A total of &1 signatures were selected |
The short text describes the object sufficiently |
|
70 |
234 |
Structure of range table (exclusion of active signatures) |
The short text describes the object sufficiently |
|
71 |
240 |
Payload entries of the central store are bundled in packages for &1 GUIDs |
Space: object requires documentation |
|
72 |
241 |
Usage check for entries of package &1 ( &2 -- &3 ) |
Space: object requires documentation |
|
73 |
242 |
A total of &1 payload entries were deleted (&2) |
Space: object requires documentation |
|
74 |
250 |
Oldest assembler run: &1 Maximum data age to be considered: &2 |
The short text describes the object sufficiently |
|
75 |
270 |
The selected runtime data will be (asynchronously) deleted |
The short text describes the object sufficiently |
|
76 |
300 |
&1 - Reorganizing process store |
Space: object requires documentation |
|
77 |
301 |
Deleting expired process instances |
The short text describes the object sufficiently |
|
78 |
302 |
&1 process types were selected |
The short text describes the object sufficiently |
|
79 |
303 |
No process types were selected |
The short text describes the object sufficiently |
|
80 |
304 |
Start time: &1 |
The short text describes the object sufficiently |
|
81 |
305 |
Deleting in packages for &1 process instances |
The short text describes the object sufficiently |
|
82 |
306 |
&1 process instances were selected (package &2) |
The short text describes the object sufficiently |
|
83 |
307 |
Header data of the selected instances was deleted (&2) |
Space: object requires documentation |
|
84 |
308 |
An error occurred while deleting the header data |
Space: object requires documentation |
|
85 |
309 |
No more instances were selected |
The short text describes the object sufficiently |
|
86 |
310 |
&1 tracking GUIDs where checked for whether they are in use |
The short text describes the object sufficiently |
|
87 |
311 |
&1 step instance(s) deleted (&2 payload data &3 statistic records) |
Space: object requires documentation |
|
88 |
312 |
Nothing else was selected |
The short text describes the object sufficiently |
|
89 |
313 |
No process instances exist or existed |
The short text describes the object sufficiently |
|
90 |
314 |
Garbage Collector |
The short text describes the object sufficiently |
|
91 |
315 |
Deleting process instances without respective metadata |
The short text describes the object sufficiently |
|
92 |
316 |
&1 process types were found in the meta store |
The short text describes the object sufficiently |
|
93 |
317 |
&2 process instances without valid process type were selected (&1) |
The short text describes the object sufficiently |
|
94 |
318 |
No process instances without valid process type were selected (&1) |
The short text describes the object sufficiently |
|
95 |
319 |
Deleting in packages for &1 process step instances |
The short text describes the object sufficiently |
|
96 |
320 |
Package &3: &2 steps deleted (&4 statistical records, &1) |
Space: object requires documentation |
|
97 |
321 |
No more process steps were selected (&1) |
Space: object requires documentation |
|
98 |
322 |
Header data of the process instances was deleted (&1) |
Space: object requires documentation |
|
99 |
323 |
Delete instance steps without associated process instance |
The short text describes the object sufficiently |
|
100 |
324 |
Deletion in packages for &1 instance steps and payload data |
The short text describes the object sufficiently |
|
101 |
325 |
Locked by another reorganization run |
The short text describes the object sufficiently |
|
102 |
326 |
&1 instance step and &2 payload entries deleted |
The short text describes the object sufficiently |
|
103 |
327 |
Deleting in packages for &1 events |
The short text describes the object sufficiently |
|
104 |
330 |
Deleting cumulation data without related metadata |
The short text describes the object sufficiently |
|
105 |
331 |
No cumulation tools were found |
The short text describes the object sufficiently |
|
106 |
350 |
Reorganization of the event store: &1 |
The short text describes the object sufficiently |
|
107 |
351 |
&1 events of type &2 deleted |
The short text describes the object sufficiently |
|
108 |
352 |
Deleting events without associated process instance |
The short text describes the object sufficiently |
|
109 |
353 |
Deleted expired events |
The short text describes the object sufficiently |
|
110 |
370 |
Process &1 released |
The short text describes the object sufficiently |
|
111 |
371 |
Release of process &1 canceled |
The short text describes the object sufficiently |
|
112 |
372 |
Process &1 activated |
The short text describes the object sufficiently |
|
113 |
373 |
Process &1 deactivated |
The short text describes the object sufficiently |
|
114 |
374 |
Process &1 deleted |
The short text describes the object sufficiently |
|
115 |
375 |
Action performed by: &1 |
The short text describes the object sufficiently |
|
116 |
376 |
Program executed |
The short text describes the object sufficiently |
|
117 |
377 |
Could not fully deactivate process &1 |
Space: object requires documentation |
|
118 |
378 |
The process is not released |
The short text describes the object sufficiently |
|
119 |
403 |
&1&2&3&4 |
The short text describes the object sufficiently |
|
120 |
404 |
&1: Table size and table growth were not monitored for over 24 hours |
Space: object requires documentation |
|
121 |
405 |
Warning if table growth was not monitored for longer than 24 hours |
The short text describes the object sufficiently |
|
122 |
406 |
Size of a PMI application data table at the time of the last check |
Space: object requires documentation |
|
123 |
407 |
Growth of a PMI application data table in the 24 hours before last check |
Space: object requires documentation |
|
124 |
408 |
Active |
Space: object requires documentation |
|
125 |
409 |
Active, however the related assembler job has not been scheduled |
Space: object requires documentation |
|
126 |
410 |
Deactivated, however the related assembler job is active |
Space: object requires documentation |
|
127 |
411 |
Monitoring status or job status cannot be determined |
Space: object requires documentation |
|
128 |
412 |
&1: Table size and growth were regularly monitored |
Space: object requires documentation |
|
129 |
413 |
Agent <&1>: Step <&2> could not be activated for destination <&3> |
Space: object requires documentation |
|
130 |
414 |
Agent <&1>: Step <&2> could not be deactivated for destination <&3> |
Space: object requires documentation |
|
131 |
415 |
Deactivation/activation error of a signature for a process step |
Space: object requires documentation |
|
132 |
416 |
Are the monitoring status and job status of a process consistent? |
Space: object requires documentation |
|
133 |
417 |
Descriptive text of a process type |
The short text describes the object sufficiently |
|
134 |
418 |
Distance between end times of the last two jobs to have run, in minutes |
Space: object requires documentation |
|
135 |
419 |
Agent <&1> is not active for destination &3 |
The short text describes the object sufficiently |
|
136 |
420 |
Step <&2> is not active for destination &3 |
The short text describes the object sufficiently |
|
137 |
421 |
Step <&2> is not completely active for destination &3 |
The short text describes the object sufficiently |
|
138 |
422 |
Field <&4> of step <&2> does not exist on destination &3 |
The short text describes the object sufficiently |
|
139 |
423 |
Field <&4> of step <&2> exists on destination &3 |
The short text describes the object sufficiently |
|
140 |
424 |
A condition for field <&4> of step <&2> does not exist (&3) |
The short text describes the object sufficiently |
|
141 |
425 |
A condition for field <&4> of step <&2> is available but incorrect (&3) |
The short text describes the object sufficiently |
|
142 |
426 |
The condition for field <&4> of step <&2> is correct (&3) |
The short text describes the object sufficiently |
|
143 |
427 |
Field <&4> of step <&2> actively exists for destination &3 for nothing |
The short text describes the object sufficiently |
|
144 |
428 |
A condition for field <&4> of step <&2> exists too many times (&3) |
The short text describes the object sufficiently |
|
145 |
429 |
Agent <&1> cannot be checked for destination &3 |
The short text describes the object sufficiently |
|
146 |
430 |
Destination &3 cannot be checked |
Space: object requires documentation |
|
147 |
431 |
Checking active process <&3> |
The short text describes the object sufficiently |
|
148 |
432 |
Checking agent <&1> for process <&3> |
Space: object requires documentation |
|
149 |
433 |
Destinations that cannot be checked |
The short text describes the object sufficiently |
|
150 |
434 |
Configuration data that should not actually be available |
The short text describes the object sufficiently |
|
151 |
435 |
Destination <&3> |
Space: object requires documentation |
|
152 |
436 |
Agent <&1> |
The short text describes the object sufficiently |
|
153 |
437 |
Inconsistencies & errors in the configuration data of the agents |
Space: object requires documentation |
|
154 |
438 |
Activation error in configuration data of agents |
Space: object requires documentation |
|
155 |
439 |
&1 &2 - Checking local agent configurations |
The short text describes the object sufficiently |
|
156 |
440 |
&2 - Activating agents of process &1 |
The short text describes the object sufficiently |
|
157 |
441 |
Step <&2> was successfully activated for <&3> |
Space: object requires documentation |
|
158 |
442 |
&2 - Deactivating agents of process &1 |
The short text describes the object sufficiently |
|
159 |
443 |
Step <&2> was successfully deactivated for <&3> |
Space: object requires documentation |
|
160 |
444 |
Activating the self monitoring of the data supplier was unsuccessful |
Space: object requires documentation |
|
161 |
445 |
Failed for processes in client <&1> |
Space: object requires documentation |
|
162 |
446 |
&1 - Monitoring of PMI application tables |
Space: object requires documentation |
|
163 |
447 |
Error in the agent configuration of process &1 |
Space: object requires documentation |
|
164 |
448 |
Assembler is running too often (currently every &1 minutes) |
The short text describes the object sufficiently |
|
165 |
449 |
&1: Monitoring of monitoring status and job status of process <&2> |
Space: object requires documentation |
|
166 |
450 |
Agents activated/deactivated successfully |
Space: object requires documentation |
|
167 |
451 |
&1 - Transporting local PMI data to PMI system |
The short text describes the object sufficiently |
|
168 |
452 |
General information on transport |
The short text describes the object sufficiently |
|
169 |
453 |
Transport ran in mode &1 |
The short text describes the object sufficiently |
|
170 |
454 |
Transport started/scheduled by user &1 |
The short text describes the object sufficiently |
|
171 |
455 |
Network load for destination &1: |
The short text describes the object sufficiently |
|
172 |
456 |
Processing terminated due to following: &1 |
Space: object requires documentation |
|
173 |
457 |
Preparing destination: &1 |
The short text describes the object sufficiently |
|
174 |
458 |
&1: Transport of PMI data for process: &3 |
The short text describes the object sufficiently |
|
175 |
459 |
End timestamp for reading PMI data: &1 |
The short text describes the object sufficiently |
|
176 |
460 |
PMI data from destination &1 not available |
The short text describes the object sufficiently |
|
177 |
461 |
Read and transport PMI data from destination &1 |
The short text describes the object sufficiently |
|
178 |
462 |
&1: Instance &2 not available |
The short text describes the object sufficiently |
|
179 |
463 |
&1: Instance &2 available |
The short text describes the object sufficiently |
|
180 |
464 |
RFC error: &1 |
Space: object requires documentation |
|
181 |
465 |
&1 deleted process &2 |
Space: object requires documentation |
|
182 |
466 |
&1 activated monitoring for process &2 |
The short text describes the object sufficiently |
|
183 |
467 |
&1 deactivated monitoring for process &2 |
The short text describes the object sufficiently |
|
184 |
468 |
&1 released process &2 |
The short text describes the object sufficiently |
|
185 |
469 |
&1 canceled the release for process &2 |
The short text describes the object sufficiently |
|
186 |
470 |
Read and transport PMI data for following process steps, |
The short text describes the object sufficiently |
|
187 |
471 |
PMI data not available for process steps specified above |
The short text describes the object sufficiently |
|
188 |
472 |
Preparing to read PMI data for following process steps, |
The short text describes the object sufficiently |
|
189 |
473 |
Number of records read: &1 |
The short text describes the object sufficiently |
|
190 |
474 |
&2 error(s) occurred in target system with destination &1: |
The short text describes the object sufficiently |
|
191 |
475 |
Instance &1, error/warning: &2 |
The short text describes the object sufficiently |
|
192 |
476 |
Number of records copied from destination &1: &2 |
The short text describes the object sufficiently |
|
193 |
477 |
Invalid timestamp (initial) |
The short text describes the object sufficiently |
|
194 |
478 |
Final status of transport from destination &1: |
The short text describes the object sufficiently |
|
195 |
479 |
Overview of all errors in destination &1: |
The short text describes the object sufficiently |
|
196 |
480 |
Transport statistics of agents: |
Space: object requires documentation |
|
197 |
481 |
Number of inserts; agent <&1>, signature <&2>: &3 |
The short text describes the object sufficiently |
|
198 |
482 |
Saving administration data |
The short text describes the object sufficiently |
|
199 |
483 |
End of transport: &1 |
The short text describes the object sufficiently |
|
200 |
484 |
Accessibility of instances for call number &1 |
The short text describes the object sufficiently |
|
201 |
485 |
&1 activated variant &3 for process &2 |
The short text describes the object sufficiently |
|
202 |
486 |
&1 has removed variants from process &2 |
The short text describes the object sufficiently |
|
203 |
487 |
&1 has set the update of process &2 from '&3' to '&4' |
The short text describes the object sufficiently |
|
204 |
488 |
&1 started immediate updates for process &2 |
The short text describes the object sufficiently |
|
205 |
489 |
&1 deactivated logging for process &2 |
The short text describes the object sufficiently |
|
206 |
490 |
&1 activated logging for process &2 |
The short text describes the object sufficiently |
|
207 |
491 |
Could not reschedule assembler job automatically |
Space: object requires documentation |
|
208 |
492 |
Instance &1: |
The short text describes the object sufficiently |
|
209 |
493 |
Current frequency of job, in minutes: |
The short text describes the object sufficiently |
|
210 |
494 |
Transport running very often, currently every &1 minutes |
The short text describes the object sufficiently |
|
211 |
495 |
Job &1 terminated. Last termination: &2; started at: &3 |
Space: object requires documentation |
|
212 |
496 |
Heavy growth in table for internal administration of process data |
Space: object requires documentation |
|
213 |
497 |
Could not save &1 PMI data records to database |
Space: object requires documentation |
|
214 |
498 |
PMI Java Service available |
The short text describes the object sufficiently |
|
215 |
499 |
PMI Java Service started, but HTTP destination 'pmistore' invalid |
Space: object requires documentation |
|
216 |
500 |
Determining destinations and instances |
The short text describes the object sufficiently |
|
217 |
501 |
Destination &1 not accessible; no data for steps: |
The short text describes the object sufficiently |
|
218 |
502 |
Transport triggered job event 'SPI_STORE_UPDATED'. RC = &1 |
Space: object requires documentation |
|
219 |
503 |
PMI Java Service not available, reason unknown |
The short text describes the object sufficiently |
|
220 |
504 |
Number of inserts; step <&4>, agent <&1>, signature <&2>: &3 |
The short text describes the object sufficiently |
|
221 |
505 |
(from destination &1): |
The short text describes the object sufficiently |
|
222 |
506 |
Results of the read for above-named process steps: |
The short text describes the object sufficiently |
|
223 |
507 |
PMI Java Service not available, as HTTP destination 'pmistore' is missing |
The short text describes the object sufficiently |
|
224 |
508 |
Agent configuration of process &1 in order |
The short text describes the object sufficiently |
|
225 |
509 |
The next update is overdue for process &1 |
Space: object requires documentation |
|
226 |
510 |
The job <&1> was started with a long delay (&2 sec.) |
The short text describes the object sufficiently |
|
227 |
511 |
Tracking Records: Number of inserts <&1>, number of failures <&2> |
The short text describes the object sufficiently |
|
228 |
512 |
No destination found for active processes, transport will be terminated |
The short text describes the object sufficiently |
|
229 |
513 |
Error in Counter Event Generation: |
Space: object requires documentation |
|
230 |
514 |
Transport started serially for all destinations |
The short text describes the object sufficiently |
|
231 |
515 |
Transport started in parallel for each destination |
The short text describes the object sufficiently |
|
232 |
516 |
Transport started for process &1 only |
The short text describes the object sufficiently |
|
233 |
517 |
RFC started for transport of destination &1 |
The short text describes the object sufficiently |
|
234 |
518 |
&1 RFC(s) started for transport (one for each destination) |
The short text describes the object sufficiently |
|
235 |
519 |
RFC for transport of destination &1 completed without errors |
The short text describes the object sufficiently |
|
236 |
520 |
Analysis started |
The short text describes the object sufficiently |
|
237 |
521 |
Could not start analysis |
The short text describes the object sufficiently |
|
238 |
522 |
Inserts for Agent &1. |
The short text describes the object sufficiently |
|
239 |
523 |
&3 - step <&1>(&2) |
The short text describes the object sufficiently |
|
240 |
524 |
&1 set for destination &2 server &3 |
The short text describes the object sufficiently |
|
241 |
525 |
Surplus configuration data for inactive process &1 |
The short text describes the object sufficiently |
|
242 |
526 |
Surplus configuration data of inactive processes |
The short text describes the object sufficiently |
|
243 |
527 |
PMI self-monitoring is active |
Space: object requires documentation |
|
244 |
528 |
PMI self-monitoring is not active |
Space: object requires documentation |
|
245 |
529 |
No active processes currently available |
Space: object requires documentation |
|
246 |
530 |
Messages deleted |
The short text describes the object sufficiently |
|
247 |
531 |
Select an entry |
The short text describes the object sufficiently |
|
248 |
532 |
Job scheduling exists |
The short text describes the object sufficiently |
|
249 |
533 |
Job scheduling does not exist; job rescheduled |
The short text describes the object sufficiently |
|
250 |
534 |
Job scheduling does not exist; job not rescheduled |
The short text describes the object sufficiently |
|
251 |
535 |
Job scheduling not required; scheduling canceled |
The short text describes the object sufficiently |
|
252 |
536 |
Job scheduling not required; scheduling not canceled |
The short text describes the object sufficiently |
|
253 |
537 |
PMI fully deactivated |
Space: object requires documentation |
|
254 |
538 |
Predecessor job still active; processing canceled |
The short text describes the object sufficiently |
|
255 |
539 |
&1 - PMI self-monitoring |
Space: object requires documentation |
|
256 |
540 |
Process is active; no changes possible |
The short text describes the object sufficiently |
|
257 |
541 |
Error when checking agents; see agent log |
The short text describes the object sufficiently |
|
258 |
542 |
Checking agent <&1> |
The short text describes the object sufficiently |
|
259 |
543 |
Step <&1> on destination <&2> |
The short text describes the object sufficiently |
|
260 |
544 |
Field <&1> exists |
The short text describes the object sufficiently |
|
261 |
545 |
Condition on field <&1> is correct |
The short text describes the object sufficiently |
|
262 |
546 |
Field <&1> does not exist |
The short text describes the object sufficiently |
|
263 |
547 |
No condition on field <&1> |
The short text describes the object sufficiently |
|
264 |
548 |
Incorrect condition on field <&1> |
The short text describes the object sufficiently |
|
265 |
549 |
Checking the active destinations |
The short text describes the object sufficiently |
|
266 |
550 |
Destination &1 checked successfully |
The short text describes the object sufficiently |
|
267 |
551 |
Used in process: &1 |
The short text describes the object sufficiently |
|
268 |
552 |
No field names available |
The short text describes the object sufficiently |
|
269 |
553 |
Surplus field <&1> exists |
The short text describes the object sufficiently |
|
270 |
554 |
Surplus condition on field <&1> |
The short text describes the object sufficiently |
|
271 |
555 |
Surplus configuration data exists |
The short text describes the object sufficiently |
|
272 |
556 |
&1 - agent configuration: &2 |
The short text describes the object sufficiently |
|
273 |
557 |
&1 - cross-process agent configuration |
The short text describes the object sufficiently |
|
274 |
558 |
Process is active |
The short text describes the object sufficiently |
|
275 |
559 |
Process is not active |
The short text describes the object sufficiently |
|
276 |
560 |
Surplus configuration data deleted |
The short text describes the object sufficiently |
|
277 |
561 |
Deactivation error in configuration data of agents |
Space: object requires documentation |
|
278 |
562 |
&1 RFC(s) still open after &2 second(s); continuing processing |
The short text describes the object sufficiently |
|
279 |
600 |
&1 - Checking administration data |
The short text describes the object sufficiently |
|
280 |
601 |
Entries for obsolete processes deleted in following tables |
The short text describes the object sufficiently |
|
281 |
602 |
No obsolete entries found |
The short text describes the object sufficiently |
|
282 |
603 |
Entries deleted for following obsolete processes |
The short text describes the object sufficiently |
|