SCHEDULER-104
|
en: |
There is an error such as the start time set in the begin="(1) " attribute is later than the end time set in end="(2) " |
|
|
- Example - An error results from, for example <period begin="23:00" end="01:00"/> as the start and end times must lie within the same day, i.e. between 00:00 und 24:00. See <period>. |
|
de: |
Beginnzeit (1) liegt nach der Endezeit (2) , oder anderer Fehler bei Attributen begin= und end= - Beispiel für eine nähere Beschreibung - Fehlerhaft ist zum Beispiel <period begin="23:00" end="01:00"/>. Eine Periode muss innerhalb eines Kalendertages liegen, zwischen 00:00 und 24:00. Siehe <period>.
|
| |
SCHEDULER-105
|
en: |
Unknown command: <(1) > |
|
|
|
|
de: |
Unbekanntes Kommando: <(1) >
|
| |
SCHEDULER-106
|
en: |
Unknown command for task: (1)
|
|
de: |
Unbekanntes Kommando an eine Task: (1)
|
| |
SCHEDULER-107
|
en: |
Missing script |
|
de: |
Skript fehlt |
| |
SCHEDULER-110
|
en: |
Unknown task state: (1)
|
|
de: |
Unbekannter Zustand einer Task: (1)
|
| |
SCHEDULER-113
|
en: |
Unexpected XML tag: (1)
|
|
de: |
XML-Tag (1) ist hier falsch |
| |
SCHEDULER-115
|
en: |
Missing XML configuration file, option -config=FILENAME.XML |
|
de: |
Die XML-Konfigurationsdatei ist nicht angegeben. Option -config=DATEINAME.XML |
| |
SCHEDULER-116
|
en: |
XML configuration contains no <config spooler_id=(1) > element |
|
de: |
XML-Konfiguration enthält kein Element <config spooler_id=(1) > |
| |
SCHEDULER-117
|
en: |
Cannot use different scripting languages in the same scripting engine |
|
de: |
Verschiedene Skriptsprachen können nicht in derselben Scripting Engine verwendet werden |
| |
SCHEDULER-119
|
en: |
There is no security level "(1) " |
|
de: |
Security level "(1) " gibt es nicht |
| |
SCHEDULER-120
|
en: |
Script has reported an error: (1)
|
|
de: |
Skript meldet Fehler: (1)
|
| |
SCHEDULER-121
|
en: |
The security settings do not allow this operation |
|
de: |
Die Sicherheitseinstellungen lassen die Operation nicht zu |
| |
SCHEDULER-122
|
en: |
Task terminated |
|
de: |
Task ist beendet |
| |
SCHEDULER-125
|
en: |
task.wait_until_terminated() cannot be called in its own thread. Deadlock. |
|
de: |
task.wait_until_terminated() kann nicht im selben Thread verwendet werden. Deadlock. |
| |
SCHEDULER-130
|
en: |
Job (1) has already been defined |
|
de: |
Job (1) ist bereits definiert |
| |
SCHEDULER-136
|
en: |
No history |
|
de: |
Keine Historie |
| |
SCHEDULER-139
|
en: |
Operation is not possible when using a plain text file for history |
|
de: |
Operation bei Historie in Textdatei nicht möglich |
| |
SCHEDULER-140
|
en: |
Task logged error: (1)
|
|
de: |
Task hat Fehler protokolliert: (1)
|
| |
SCHEDULER-141
|
en: |
History has been suppressed for job (1) (history=no) |
|
de: |
Die Historie für Job (1) ist ausgeschaltet (history=no) |
| |
SCHEDULER-142
|
en: |
Relative database file path cannot be used with need_db=yes and log_dir=*stderr |
|
de: |
Relativer Datenbankdateiname kann bei need_db=yes und log_dir=*stderr nicht verwendet werden |
| |
SCHEDULER-143
|
en: |
Task cannot start because it has no start time and no valid <run_time> |
|
de: |
Element <run_time> sieht keine Periode für eine Task ohne Startzeit vor |
| |
SCHEDULER-145
|
en: |
<script> com_class= and language= cannot be combined |
|
de: |
<script> com_class= und language= können nicht zugleich angegeben werden |
| |
SCHEDULER-146
|
en: |
Missing script |
|
de: |
Das Skript fehlt |
| |
SCHEDULER-147
|
en: |
job(1) cannot accept orders because it has not been declared with <job order="yes"> |
| |
SCHEDULER-148
|
en: |
'object(1) ' has been initialized already and cannot be modified |
| |
SCHEDULER-149
|
en: |
There is no job in job chain "(1) " for the state "(2) " |
|
de: |
Für den Zustand "(2) " ist kein Job in der Jobkette (1) definiert |
| |
SCHEDULER-150
|
en: |
The state "(1) " has already assigned a job in job chain (2)
|
|
de: |
Für den Zustand "(1) " ist bereits ein Job in der Jobkette (2) definiert |
| |
SCHEDULER-151
|
en: |
Job chain is not in use (missing add_job_chain() or job chain is to be removed) |
|
de: |
Jobkette ist außer Betrieb (add_job_chain() fehlt oder Jobkette wird entfernt) |
| |
SCHEDULER-152
|
en: |
Job "(1) " is not in job chain "(2) " |
|
de: |
Job "(1) " ist nicht in der Jobkette "(2) " |
| |
SCHEDULER-153
|
en: |
'object(1) ' is not in state '(2) ' |
| |
SCHEDULER-155
|
en: |
A temporary job cannot accept orders |
|
de: |
Ein temporärer Job kann keine Aufträge annehmen |
| |
SCHEDULER-156
|
en: |
(1) is not in Order_queue(2)
|
|
de: |
(1) ist nicht in der Auftragswarteschlange des Jobs "(2) " |
| |
SCHEDULER-157
|
en: |
(1) is not in a job chain |
|
de: |
(1) ist nicht in einer Jobkette |
|
→ |
Order |
| |
SCHEDULER-159
|
en: |
Id and priority of an order placed in an order queue cannot be changed |
|
de: |
Id und Priorität eines Auftrags können nicht mehr geändert werden, wenn er in einer Auftragsliste steht |
| |
SCHEDULER-160
|
en: |
There is already a objecttype(1) '(2) ' |
| |
SCHEDULER-161
|
en: |
There is no objecttype(1) '(2) ' |
|
→ |
Job, Lock, Locks, Process_classes, <lock.remove>, <lock.use>
|
| |
SCHEDULER-162
|
en: |
There is no order (1) in job chain "(2) " |
|
de: |
Auftrag (1) ist nicht in der Jobkette (2)
|
|
→ |
<modify_order>
|
| |
SCHEDULER-163
|
en: |
(1) is not in an order queue |
|
de: |
(1) ist nicht einer Auftragswarteschlange |
|
→ |
Order |
| |
SCHEDULER-164
|
en: |
<show_... what="(1) ">: invalid value for attribute what= |
|
de: |
<show_... what="(1) ">: Ungültige Angabe für Attribut what |
| |
SCHEDULER-166
|
en: |
<script> java_class= and language= cannot be combined |
|
de: |
<script> java_class= und language= können nicht zugleich angegeben werden |
| |
SCHEDULER-167
|
en: |
A program source cannot be set with <script> com_class= or java_class= |
|
de: |
Bei <script> com_class= oder java_class= kann die Programmquelle nicht angegeben werden |
| |
SCHEDULER-168
|
en: |
com_class= and java_class= cannot be combined in <script> |
|
de: |
In <script> ist com_class= und java_class= zusammen angegeben |
| |
SCHEDULER-172
|
en: |
This kind of script (scripting engine, Perl, COM or Java) is not possible here |
|
de: |
Die Skriptart (Scripting Engine, Perl, COM oder Java) ist hier nicht möglich |
| |
SCHEDULER-173
|
en: |
Missing script |
|
de: |
Skript fehlt |
| |
SCHEDULER-174
|
en: |
Method "(1) " is missing in class "(2) " |
|
de: |
Methode (1) der Klasse (2) fehlt |
| |
SCHEDULER-177
|
en: |
Java is not available (see error message when Scheduler started) |
|
de: |
Java steht nicht zur Verfügung (siehe Fehler beim Start des Schedulers) |
| |
SCHEDULER-179
|
en: |
<process> task did not terminate. pid=(1)
|
|
de: |
<process>-Task hat sich nicht beendet. pid=(1)
|
| |
SCHEDULER-182
|
en: |
Unexpected XML element <(1) > |
| |
SCHEDULER-183
|
en: |
Scheduler cannot start because spooler_init() in 'scheduler_script(1) ' returned false |
| |
SCHEDULER-184
|
en: |
Scheduler database cannot be accessed due to a database problem |
|
de: |
Die Scheduler-Datenbank ist wegen eines Datenbankproblems gerade nicht geöffnet |
| |
SCHEDULER-186
|
en: |
(1) is already in job chain (2)
|
|
de: |
(1) ist bereits in der Jobkette (2)
|
|
→ |
Job_chain |
| |
SCHEDULER-187
|
en: |
Order.setback(): An order can only be set back when it is being executed by a task |
|
de: |
Order.setback(): Ein Auftrag kann nur zurückgestellt werden, während eine Task ihn ausführt |
|
→ |
Order |
| |
SCHEDULER-188
|
en: |
Order.setback() and Order.state= cannot be combined |
|
de: |
Order.setback() und Order.state= können nicht zusammen gerufen werden, das ist Unsinn |
|
→ |
Order |
| |
SCHEDULER-191
|
en: |
separate_process: Unexpected state (2) in (1)
|
|
de: |
separate_process: Unerwarteter Zustand (2) in (1)
|
| |
SCHEDULER-192
|
en: |
A separate process is only possible with use_engine="task" |
|
de: |
Ein separater Prozess ist nur mit use_engine="task" möglich |
| |
SCHEDULER-194
|
en: |
process_class and separate_process cannot be combined |
|
de: |
process_class und separate_process können nicht kombiniert werden |
| |
SCHEDULER-196
|
en: |
use_engine="(1) " is deprecated |
|
de: |
use_engine="(1) " ist veraltet |
| |
SCHEDULER-197
|
en: |
Module::java_method_id((1) ): unknown Java class |
|
de: |
Module::java_method_id((1) ): Java-Klasse ist unbekannt |
| |
SCHEDULER-198
|
en: |
Missing variable name |
|
de: |
Variablenname fehlt |
| |
SCHEDULER-199
|
en: |
Module instance has been closed |
|
de: |
Die Modulinstanz ist geschlossen |
| |
SCHEDULER-200
|
en: |
Remote instance has been closed |
|
de: |
Die Remoteinstanz ist geschlossen |
| |
SCHEDULER-201
|
en: |
Missing working directory when calling Java compiler |
|
de: |
Das Arbeitsverzeichnis zum Aufruf des Java-Compilers fehlt |
| |
SCHEDULER-202
|
en: |
Connection to task has been lost, state=(1) : (2)
|
|
de: |
Verbindung zur Task verloren, state=(1) : (2)
|
| |
SCHEDULER-203
|
en: |
Module instance in the server has been closed |
|
de: |
Die Modulinstanz im Server ist geschlossen |
| |
SCHEDULER-204
|
en: |
Job "(1) " is in error state. (2)
|
|
de: |
Der Job "(1) " ist im Fehlerzustand. (2)
|
| |
SCHEDULER-205
|
en: |
No database given (entry db= in factory.ini) |
| |
SCHEDULER-206
|
en: |
With need_db=(1) , only "yes", "no" and "strict" are allowed |
|
de: |
need_db=(1) , erlaubt sind aber nur yes, no, strict |
| |
SCHEDULER-207
|
en: |
Task (1) is unknown (and not noted in the history) |
|
de: |
Task (1) unbekannt (auch in der Historie) |
| |
SCHEDULER-208
|
en: |
Only a date without a time is allowed |
|
de: |
Hier ist nur ein Datum ohne Uhrzeit möglich |
| |
SCHEDULER-209
|
en: |
Too many objects for Microsoft Windows MsgWaitForMultipleObjects(). MAXIMUM_WAIT_OBJECTS-1=(1) has been reached. Operation is not executable |
|
de: |
Das Microsoft Windows-Limit der Objekte, auf die gewartet werden kann (TCP-Verbindungen, beobachteten Verzeichnisse etc.) von MAXIMUM_WAIT_OBJECTS-1=(1) ist erreicht. Die Operation ist nicht ausführbar. |
| |
SCHEDULER-210
|
en: |
Too many processes. The number of processes is limited to (1)
|
|
de: |
Zuviele Prozesse. Die Zahl der Prozesse ist auf (1) begrenzt |
| |
SCHEDULER-212
|
en: |
Missing entry [spooler] html_dir= in file factory.ini |
|
de: |
Eintrag [spooler] html_dir= fehlt in der Datei factory.ini |
| |
SCHEDULER-213
|
en: |
Error in HTTP header: expecting (1)
|
|
de: |
Fehler beim Lesen des HTTP-Kopfs: (1) erwartet |
| |
SCHEDULER-214
|
en: |
Forbidden path in HTTP request |
|
de: |
Unzulässiger Pfad in HTTP-Anforderung |
| |
SCHEDULER-215
|
en: |
Unknown or terminated task (1)
|
|
de: |
Task (1) unbekannt oder beendet |
| |
SCHEDULER-217
|
en: |
order(1) is being processed by task(2)
|
|
de: |
auftrag(1) ist in Bearbeitung durch task(2)
|
|
→ |
Order, <modify_order>
|
| |
SCHEDULER-218
|
en: |
Subprocess pid=(2) has been terminated with exit code=(1) . Command=(3)
|
|
de: |
Subprocess pid=(2) hat sich mit exit code=(1) beendet. Command=(3)
|
| |
SCHEDULER-219
|
en: |
Subprocess pid=(2) has been terminated with signal (1) . Command=(3)
|
|
de: |
Subprocess pid=(2) hat sich mit Signal (1) beendet. Command=(3)
|
| |
SCHEDULER-220
|
en: |
<run_time (1) > cannot be carried out for an order |
|
de: |
<run_time (1) > ist für einen Auftrag nicht möglich |
| |
SCHEDULER-221
|
en: |
<day day="(1) ">: only the days from (2) to (3) are possible |
|
de: |
<day day="(1) ">: Nur die Tage (2) bis (3) sind möglich |
| |
SCHEDULER-222
|
en: |
This command <(1) > is only executable by way of a TCP connection |
|
de: |
Das Kommando <(1) > kann nur über eine TCP-Verbindung gegeben werden |
| |
SCHEDULER-223
|
en: |
Supervisor has reported an error: (1)
|
| |
SCHEDULER-224
|
en: |
Supervisor has closed the connection |
|
de: |
Haupt-Scheduler hat Verbindung geschlossen |
| |
SCHEDULER-225
|
en: |
start_new_file() is only applicable for the main protocol |
|
de: |
start_new_file() ist nur fürs Hauptprotokoll möglich |
| |
SCHEDULER-226
|
en: |
Order has not been processed because the task has been terminated before the processing step (spooler_process()) |
|
de: |
Der Auftrag ist nicht verarbeitet worden ist, weil die Task vor dem ersten Jobschritt (spooler_process()) beendet worden ist |
| |
SCHEDULER-227
|
en: |
Scheduler script has logged an error: (1)
|
|
de: |
Scheduler-Skript hat Fehler protokolliert: (1)
|
| |
SCHEDULER-230
|
en: |
Job "(1) " is to be removed - it is not longer usable |
|
de: |
Der Job "(1) " wird entfernt, er kann nicht mehr verwendet werden |
| |
SCHEDULER-231
|
en: |
Missing attribute (2) in XML element <(1) > |
|
de: |
Attribut (2) fehlt im XML-Element <(1) > |
| |
SCHEDULER-232
|
en: |
Attribute <xml_element_name(1) (2) ="(3) "> is not allowed here |
| |
SCHEDULER-234
|
en: |
The <job (1) ="..."> attribute cannot be overwritten |
|
de: |
<job (1) ="..."> Attribut kann nicht überschrieben werden |
| |
SCHEDULER-235
|
en: |
Unknown web service: "(1) " |
|
de: |
Web-Dienst "(1) " ist unbekannt |
| |
SCHEDULER-236
|
en: |
Web service "(1) " has already been declared |
|
de: |
Web-Dienst "(1) " ist bereits bekannt |
| |
SCHEDULER-237
|
en: |
XSLT stylesheet "(1) " does not deliver a result |
|
de: |
XSLT-Stylesheet "(1) " liefert kein Ergebnis |
|
→ |
<web_service>
|
| |
SCHEDULER-238
|
en: |
Web service or alias for url_path="(1) " has already been declared |
|
de: |
Web-Dienst für url_path="(1) " ist bereits bekannt |
| |
SCHEDULER-239
|
en: |
XML root element <(1) > expected |
| |
SCHEDULER-240
|
en: |
Order has not been assigned to a web service |
|
de: |
Auftrag ist keinem Webdienst zugeordnet |
|
→ |
Order |
| |
SCHEDULER-241
|
en: |
Task has not been assigned to a web service |
|
de: |
Task ist keinem Webdienst zugeordnet |
| |
SCHEDULER-242
|
en: |
forward_xslt_stylesheet (1) does not deliver <service_request> |
|
de: |
forward_xslt_stylesheet (1) liefert nicht <service_request> |
| |
SCHEDULER-243
|
en: |
Property (1) is fixed and is no longer modifiable |
|
de: |
Eigenschaft (1) ist fixiert, sie kann nicht mehr geändert werden |
|
→ |
Lock, Process_class
|
| |
SCHEDULER-244
|
en: |
Element <content> is missing or empty |
|
de: |
Element <content> fehlt oder ist leer |
|
→ |
<web_service>
|
| |
SCHEDULER-245
|
en: |
Element <content> has more than one child element |
|
de: |
Element <content> hat mehr als ein Element |
|
→ |
<web_service>
|
| |
SCHEDULER-246
|
en: |
Order does not belong to a web service operation |
|
de: |
Auftrag gehört nicht zu einer Web-Dienst-Operation |
|
→ |
Order |
| |
SCHEDULER-247
|
en: |
HTTP response has already been sent |
|
|
|
|
de: |
HTTP-Antwort wird bereits versendet
|
|
→ |
Web_service_response |
| |
SCHEDULER-248
|
en: |
web_service_operation has finished and is not longer valid |
|
de: |
web_service_operation ist abgeschlossen und nicht mehr gültig |
|
→ |
<web_service>
|
| |
SCHEDULER-249
|
en: |
Order id cannot be represented as a character string: (1)
|
|
de: |
Order-Id lässt sich nicht als Zeichenkette darstellen: (1)
|
| |
SCHEDULER-250
|
en: |
Order state cannot be represented as a character string: (1)
|
|
de: |
Order-State lässt sich nicht als Zeichenkette darstellen: (1)
|
| |
SCHEDULER-251
|
en: |
Order payload cannot be represented as character string: (1)
|
|
de: |
Order-Payload lässt sich nicht als Zeichenkette darstellen: (1)
|
| |
SCHEDULER-252
|
en: |
Invalid url path - it has to begin with '/': (1)
|
|
de: |
Ungültiger Url-Pfad, er muss mit '/' beginnen: (1)
|
|
→ |
<web_service>
|
| |
SCHEDULER-254
|
en: |
(1) tasks did not terminate in spite of kill (2) seconds ago. Extending deadline for (3) s |
|
de: |
(1) Tasks haben sich nicht beendet trotz kill vor (2) s. Die (3) s lange Nachfrist läuft weiter |
| |
SCHEDULER-255
|
en: |
(1) tasks did not terminate in spite of kill (2) seconds ago. Scheduler is aborting |
|
de: |
(1) Tasks haben sich nicht beendet trotz kill vor (2) seconds. Scheduler bricht ab |
| |
SCHEDULER-256
|
en: |
Deadline for terminating Scheduler has been reached, but (1) tasks are still running |
|
de: |
Frist zur Beendigung des Schedulers ist abgelaufen, aber (1) Tasks haben sich nicht beendet |
| |
SCHEDULER-257
|
en: |
Job is being removed now |
|
de: |
Job wird jetzt entfernt |
| |
SCHEDULER-258
|
en: |
Job will be removed after all its tasks have terminated |
|
de: |
Job wird entfernt sobald alle Tasks beendet sind |
| |
SCHEDULER-259
|
en: |
Java did not start. Scheduler is starting without Java |
|
de: |
Java kann nicht gestartet werden. Scheduler startet ohne Java |
| |
SCHEDULER-260
|
en: |
Error in Scheduler Skript, spooler_exit(): (1) Error in Scheduler script, spooler_exit(): (1)
|
| |
SCHEDULER-261
|
en: |
Nothing done, event=(1) , operations=(2)
|
| |
SCHEDULER-262
|
en: |
Kill signal ((1) ) received. Scheduler is terminating |
|
de: |
Abbruch-Signal ((1) ) empfangen. Der Scheduler wird beendet |
| |
SCHEDULER-263
|
en: |
Kill signal ((1) ) #(2) received. what to do(3)
|
| |
SCHEDULER-264
|
en: |
SCHEDULER IS TERMINATING AFTER SERIOUS ERROR |
| |
SCHEDULER-265
|
en: |
SCHEDULER IS ABORTING DUE TO A PROBLEM WITH THE DATABASE: (1)
|
|
de: |
SCHEDULER WIRD BEENDET WEGEN FEHLERS BEIM ZUGRIFF AUF DATENBANK |
| |
SCHEDULER-266
|
en: |
Error when writing the history: (1)
|
|
de: |
Fehler beim Schreiben der Historie: (1)
|
| |
SCHEDULER-267
|
en: |
Error when storing the log in table (1) : (2)
|
|
de: |
Fehler beim Schreiben des Protokolls in die Tabelle (1) : (2)
|
| |
SCHEDULER-268
|
en: |
Log of task (1) is not readable from database: (2)
|
|
de: |
Protokoll der Task (1) lässt sich nicht aus der Datenbank lesen: (2)
|
| |
SCHEDULER-269
|
en: |
Error when closing the job history: (1)
|
|
de: |
Fehler beim Schließen der Job-Historie: (1)
|
| |
SCHEDULER-270
|
en: |
Cannot open history: (1)
|
|
de: |
Historie lässt sich nicht öffnen: (1)
|
| |
SCHEDULER-271
|
en: |
Task is being terminated in favour of job (1)
|
|
de: |
Zugunsten des Jobs (1) wird die Task beendet |
| |
SCHEDULER-272
|
en: |
Terminating task after reaching deadline <job timeout="(1) "> |
|
de: |
Task wird nach nach Fristablauf von <job timeout="(1) "> abgebrochen |
| |
SCHEDULER-273
|
en: |
Killing subprocess (1)
|
|
de: |
Subprozess (1) wird abgebrochen |
| |
SCHEDULER-274
|
en: |
Error when killing subprocess (1) : (2)
|
|
de: |
Subprozess (1) lässt sich nicht abbrechen: (2)
|
| |
SCHEDULER-275
|
en: |
Deadline reached, killing subprocess (1)
|
|
de: |
Subprozess (1) wird abgebrochen, weil seine Frist überschritten ist |
| |
SCHEDULER-276
|
en: |
Could not kill task |
|
de: |
Task konnte nicht abgebrochen werden |
| |
SCHEDULER-278
|
en: |
<period> ended, terminating task |
|
de: |
Laufzeitperiode <period> ist abgelaufen, Task wird beendet |
| |
SCHEDULER-279
|
en: |
Process terminated with signal (1) (name(2) ) |
|
de: |
Prozess hat mit Signal (1) (name(2) ) geendet |
|
→ |
<job>
|
| |
SCHEDULER-280
|
en: |
Process terminated with exit code (1) (0x(2) ) |
|
de: |
Prozess hat mit Exit code (1) (0x(2) ) geendet |
|
→ |
<process>
|
| |
SCHEDULER-281
|
en: |
Killing process |
|
de: |
Prozess wird abgebrochen |
| |
SCHEDULER-283
|
en: |
Error when loading task (1) from database: (2)
|
|
de: |
Task (1) aus der Datenbank ist fehlerhaft: (2)
|
| |
SCHEDULER-284
|
en: |
Ignoring cmd='(1) ' because job is to be removed |
|
de: |
cmd='(1) ' wird ignoriert, weil Job entfernt wird |
| |
SCHEDULER-285
|
en: |
Max. (1) history records are being read |
|
de: |
Max. (1) Historiensätze werden gelesen |
| |
SCHEDULER-286
|
en: |
More than (1) communication channels. Connection denied |
|
de: |
Mehr als (1) Kommunikationskanäle. Verbindung abgelehnt |
| |
SCHEDULER-287
|
en: |
TCP connection not allowed |
|
de: |
TCP-Verbindung nicht zugelassen |
| |
SCHEDULER-288
|
en: |
-reuse-port (SO_REUSEADDR): using (1) , but another application can use it too |
|
de: |
-reuse-port (SO_REUSEADDR): (1) wird verwendet, auch wenn er schon von einer anderen Anwendung belegt ist |
| |
SCHEDULER-289
|
en: |
(1) is blocked. Trying a further (2) seconds before giving up |
|
de: |
(1) ist blockiert. Wir probieren es (2) Sekunden |
| |
SCHEDULER-290
|
en: |
Timeout: No job started to execute (1) , cancelling order and HTTP operation |
|
|
|
|
de: |
Kein Job hat während der Frist begonnen (1) auszuführen, Auftrag und HTTP-Operation werden abgebrochen
|
|
→ |
<web_service>
|
| |
SCHEDULER-291
|
en: |
Error when removing protocol file: (1)
|
|
de: |
Fehler beim Löschen der Protokolldatei: (1)
|
| |
SCHEDULER-292
|
en: |
Missing from, to, subject or body. Suppressing email |
|
de: |
Email unterdrückt, weil From, To, Subject oder der Nachrichtentext fehlt |
| |
SCHEDULER-293
|
en: |
Waiting for closing module instance ... |
|
de: |
Warten auf Schließen der Modulinstanz ... |
| |
SCHEDULER-294
|
en: |
Java class (1) could not be loaded. Java source is being recompiled before retrying |
|
de: |
Die Java-Klasse (1) konnte nicht geladen werden. Die Java-Quelle wird neu übersetzt, mal sehen, ob's dann geht |
| |
SCHEDULER-295
|
en: |
Error when loading order (1) from database: (2)
|
|
de: |
Auftrag (1) aus der Datenbank ist fehlerhaft: (2)
|
| |
SCHEDULER-296
|
en: |
Order's <run_time> does not have a next start time |
|
de: |
Die <run_time> des Auftrags hat keine nächste Startzeit |
| |
SCHEDULER-297
|
en: |
Order has been carried out without web_service_operation.send(), operation cancelled |
|
de: |
Auftrag erledigt ohne web_service_operation.send(), Operation wird abgebrochen |
|
→ |
<web_service>
|
| |
SCHEDULER-298
|
en: |
Ignoring job=(1) because order is removed from job chain |
|
de: |
job=(1) wird ignoriert, weil Auftrag bereits aus der Jobkette entfernt ist |
| |
SCHEDULER-299
|
en: |
Removing process (1) after error |
|
de: |
Prozess (1) wird nach Fehler entfernt |
| |
SCHEDULER-300
|
en: |
Monitoring of directory (1) has ended after error: (2)
|
|
de: |
Überwachung des Verzeichnisses (1) wird nach Fehler beendet: (2)
|
| |
SCHEDULER-301
|
en: |
UDP message from (1) is not allowed |
|
de: |
UDP-Nachricht von (1) nicht zugelassen |
| |
SCHEDULER-302
|
en: |
Error sending e-mail: (1)
|
|
de: |
Fehler beim eMail-Versand: (1)
|
|
→ |
»Änderungsprotokoll« |
| |
SCHEDULER-303
|
en: |
Problem with database: (1)
|
|
de: |
Fehler beim Zugriff auf die Datenbank: (1)
|
| |
SCHEDULER-304
|
en: |
Error when reading next id (column "(2) "): (1)
|
|
de: |
Fehler beim Lesen der nächsten Id (Spalte "(2) "): (1)
|
| |
SCHEDULER-305
|
en: |
Error when inserting into table (1) : (2)
|
|
de: |
Fehler beim Einfügen in die Tabelle (1) : (2)
|
| |
SCHEDULER-306
|
en: |
Error when updating table (1) : (2)
|
|
de: |
Fehler beim Update der Tabelle (1) : (2)
|
| |
SCHEDULER-307
|
en: |
Not writing history record because of already existing database problem |
|
de: |
Historiensatz wird wegen vorausgegangenen Datenbankfehlers nicht geschrieben |
| |
SCHEDULER-308
|
en: |
Ignoring cancel() because response has already been sent |
|
de: |
cancel() ignoriert, weil die Antwort schon übertragen wird |
|
→ |
<web_service>
|
| |
SCHEDULER-309
|
en: |
Error when opening database: (1)
|
|
de: |
Fehler beim Öffnen der Datenbank: (1) |
| |
SCHEDULER-310
|
en: |
Error when closing the database: (1)
|
|
de: |
Fehler beim Schließen der Datenbank: (1)
|
| |
SCHEDULER-311
|
en: |
Error when processing HTTP request (1) : (2)
|
| |
SCHEDULER-312
|
en: |
Variable "(1) " (vt=(2) ) cannot be converted to Text: (3)
|
| |
SCHEDULER-313
|
en: |
Cannot store order in database: (1)
|
| |
SCHEDULER-314
|
en: |
Cannot open database. Scheduler is aborting immediately because of need_db=(1)
|
| |
SCHEDULER-316
|
en: |
<web_service name="(1) "/>: attributes job_chain=/timeout= and request/response/forward_xslt_stylesheet= cannot be combined |
|
→ |
<web_service>
|
| |
SCHEDULER-318
|
en: |
Option -env=NAME=VALUE: missing '=' between name and value: -env="(1) " |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-319
|
en: |
XML-Element <(1) > is not possible here |
| |
SCHEDULER-320
|
en: |
Could not send mail |
| |
SCHEDULER-321
|
en: |
Mail has been sent, but an error occurred when processing the mail queue: (1)
|
| |
SCHEDULER-322
|
en: |
min_tasks=(1) is greater than max_tasks=(2)
|
|
|
|
|
→ |
<job>
|
| |
SCHEDULER-323
|
en: |
exit_code is available only when task module is loaded |
|
|
|
| |
SCHEDULER-324
|
en: |
Invalid value for attribute exit_code="(1) " in <commands> |
|
|
|
|
→ |
<commands>
|
| |
SCHEDULER-325
|
en: |
Attribute exit_code is not applicable here |
|
|
|
|
→ |
<commands>
|
| |
SCHEDULER-326
|
en: |
<commands on_exit_code="(1) ">: <commands> for exit code (2) is already defined |
|
|
|
|
→ |
<commands>
|
| |
SCHEDULER-327
|
en: |
Last error occurred when executing command: xml_command(1)
|
|
|
|
|
→ |
<commands>
|
| |
SCHEDULER-328
|
en: |
Executing <commands on_exit_code="(1) ">: |
|
|
|
|
→ |
<commands>
|
| |
SCHEDULER-329
|
en: |
<copy_params from="(1) "/>: requested parameters are not available |
|
|
|
|
→ |
<copy_params>
|
| |
SCHEDULER-330
|
en: |
job(1) could not be initialized:
error(2)
|
| |
SCHEDULER-331
|
en: |
Scheduler is terminating after error (see last error line) |
| |
SCHEDULER-332
|
en: |
Error in (1) while switching to state=(2) : (3)
|
| |
SCHEDULER-333
|
en: |
"now+SECONDS" expected in "(1) " |
| |
SCHEDULER-334
|
en: |
Error when building mail: (1)
|
| |
SCHEDULER-335
|
en: |
Only "yes", "no" and a number are allowed with (1) ="(2) ": error(3)
|
|
→ |
»Einstellungen« |
| |
SCHEDULER-336
|
en: |
Only "yes", "no" and a list of signal names are allowed with (1) ="(2) ": error(3)
|
| |
SCHEDULER-337
|
en: |
Signal (1) is unknown on this operating system and is ignored |
|
→ |
<commands>, <job>
|
| |
SCHEDULER-338
|
en: |
Order.payload is not a Variable_set |
| |
SCHEDULER-339
|
en: |
File does not exist and can therefore neither be moved nor removed: (1)
|
|
→ |
»Verzeichnisüberwachung mit Dateiaufträgen« |
| |
SCHEDULER-340
|
en: |
File still exists. Order has been set on the blacklist |
|
→ |
»Verzeichnisüberwachung mit Dateiaufträgen« |
| |
SCHEDULER-342
|
en: |
There is no job between order source and order sink in job_chain(1)
|
|
→ |
<file_order_source>
|
| |
SCHEDULER-343
|
en: |
This is no file order: order(1)
|
| |
SCHEDULER-344
|
en: |
order.id has more than (2) characters: (1)
|
| |
SCHEDULER-345
|
en: |
order.id has more than (2) characters, the limit of your database column (3) is: (1)
|
| |
SCHEDULER-346
|
en: |
Due to previous error the path will be ignored: (1)
|
|
→ |
»Verzeichnisüberwachung mit Dateiaufträgen« |
| |
SCHEDULER-347
|
en: |
Path has been removed from the blacklist: (1)
|
| |
SCHEDULER-348
|
en: |
Database doesn't deliver width of column (1) .(2)
|
| |
SCHEDULER-349
|
en: |
Database column (1) .(2) could not be expanded |
| |
SCHEDULER-350
|
en: |
Width of database column (1) .(2) is unknown. We assume (3)
|
| |
SCHEDULER-351
|
en: |
<modify_order_... setback="(1) ">: Invalid value for attribute setback= |
| |
SCHEDULER-353
|
en: |
No immediate response from command <(1) > |
| |
SCHEDULER-354
|
en: |
Scheduler Java classes (sos.spooler.jar version(1) expected) are not up to date: (2)
|
| |
SCHEDULER-355
|
en: |
SQL update statement changed more than one record, count(1) : statement(2)
|
| |
SCHEDULER-357
|
en: |
This is a member of a cluster (option -exclusive or -distributed-orders), and therefore needs a database |
|
→ |
»Änderungsprotokoll«, »Kommandozeilenoptionen« |
| |
SCHEDULER-358
|
en: |
This is a member of a cluster (option -exclusive or -distributed-orders), and therefore needs a database. need_db=(1) is not allowed |
|
→ |
»Kommandozeilenoptionen«, »Einstellungen« |
| |
SCHEDULER-359
|
en: |
For an exclusive or distributed Scheduler, the database (1) is not supported |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-360
|
en: |
Error when accessing database table (1)
|
| |
SCHEDULER-361
|
en: |
No database |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-362
|
en: |
Scheduler is aborting because it has become inactive |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-363
|
en: |
Error when creating SQL table (1) : (2)
|
| |
SCHEDULER-365
|
en: |
Illegal character in -id=(1)
|
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-367
|
en: |
Scheduler is aborting because it has lost its exclusivity |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-368
|
en: |
Option (1) needs (2)
|
| |
SCHEDULER-369
|
en: |
Option (1) conflicts with (2)
|
| |
SCHEDULER-370
|
en: |
Operation can only be performed on a distributed orders Scheduler |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-371
|
en: |
DATABASE INTEGRITY IS BROKEN |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-372
|
en: |
Exclusivity has been stolen by Scheduler member '(1) ' |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-373
|
en: |
UNEXPECTED DEACTIVATION BY SCHEDULER MEMBER (1)
|
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-374
|
en: |
In job_chain(1) , state '(2) ' has no job |
| |
SCHEDULER-375
|
en: |
Order is distributed and therefore does not support operation '(1) ' |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-377
|
en: |
After own late heart beat, Scheduler member '(1) ' has taken exclusiveness |
|
→ |
»Änderungsprotokoll«, »Kommandozeilenoptionen« |
| |
SCHEDULER-378
|
en: |
After own late heart beat, this Scheduler has been deactivated and the occupied orders have been freed by Scheduler member '(1) ' |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-379
|
en: |
order(1) is occupied by Scheduler member '(2) ' |
|
→ |
»Kommandozeilenoptionen«, <modify_order>
|
| |
SCHEDULER-380
|
en: |
job_chain orders_recoverable="no" cannot be combined with distributed="yes", in (1)
|
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-381
|
en: |
Scheduler is not yet active and cannot execute the operation |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-384
|
en: |
job_chain(1) is distributed and therefore does not support operation '(2) ' |
|
→ |
Job_chain_node, »Kommandozeilenoptionen«, <job_chain.modify>
|
| |
SCHEDULER-385
|
en: |
Deletion of order in database has failed |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-386
|
en: |
Last heart beat was time(1) , (2) seconds ago. Something is delaying Scheduler execution, the Scheduler is aborted immediately |
|
→ |
»Änderungsprotokoll«, »Kommandozeilenoptionen«, <cluster>
|
| |
SCHEDULER-389
|
en: |
This order stored in database is distributed and cannot be used in a non-distributed job chain |
| |
SCHEDULER-390
|
en: |
More than (1) nested includes in (2)
|
| |
SCHEDULER-391
|
en: |
Invalid value '(2) ' for setting '(1) '. Allowed values are: (3)
|
| |
SCHEDULER-392
|
en: |
heart_beat_warn_timeout=(1) seconds has to be lower than heart_beat_own_timeout=(2) , which has to be lower than heart_beat_warn_timeout=(3) seconds |
| |
SCHEDULER-393
|
en: |
Error when calling <run_time> function '(1) ': (2)
|
|
→ |
<run_time>
|
| |
SCHEDULER-394
|
en: |
<run_time>-Function '(1) ' returned start time (2) which is earlier than the requested beginning (3)
|
|
→ |
<run_time>
|
| |
SCHEDULER-396
|
en: |
Job has not yet reached state '(1) ' for operation (2)
|
| |
SCHEDULER-397
|
en: |
A distributed order does not support (1)
|
|
→ |
Order |
| |
SCHEDULER-398
|
en: |
After last error, next_start_function='(1) ' will no longer be executed for this <run_time> |
| |
SCHEDULER-399
|
en: |
Error in include_xml_element(1) :
(2)
|
| |
SCHEDULER-401
|
en: |
Unknown 'object(1) ' |
| |
SCHEDULER-403
|
en: |
There is no valid state for job chain node state='(1) ', action='next_state' (circular next_state) |
|
→ |
Job_chain_node |
| |
SCHEDULER-404
|
en: |
action='(1) ' is not possible on a distributed job chain |
|
→ |
Job_chain_node |
| |
SCHEDULER-405
|
en: |
Setting state='(1) ' is not possible while job chain has state '(2) ' |
|
→ |
<job_chain.modify>
|
| |
SCHEDULER-406
|
en: |
Error in job chain node state='(1) ': (2)
|
| |
SCHEDULER-407
|
en: |
Attribute (1) is empty |
|
→ |
<lock.use>
|
| |
SCHEDULER-408
|
en: |
<(1) (2) =...> cannot be changed |
|
→ |
<lock.use>
|
| |
SCHEDULER-409
|
en: |
XML tag <(1) > expected, instead of <(2) > |
|
→ |
<include>
|
| |
SCHEDULER-412
|
en: |
Job chains can only be nested once |
|
→ |
<job_chain_node.job_chain>
|
| |
SCHEDULER-413
|
en: |
Nested job chains cannot be combined with distributed orders |
| |
SCHEDULER-414
|
en: |
There is a circular nesting of job chains: (1)
|
| |
SCHEDULER-415
|
en: |
Error when trying to continue in next job chain: (1)
|
|
→ |
<job_chain_node.job_chain>
|
| |
SCHEDULER-416
|
en: |
'(1) ' is already known |
|
→ |
Locks, Process_classes
|
| |
SCHEDULER-417
|
en: |
Invalid name: '(1) ' |
|
→ |
Lock, Process_class, <include>
|
| |
SCHEDULER-419
|
en: |
New Process_class.max_processes=(1) is below current number of processes=(2)
|
|
→ |
Process_class |
| |
SCHEDULER-420
|
en: |
Negative value is not allowed for (1)
|
|
→ |
Process_class |
| |
SCHEDULER-422
|
en: |
'object(1) ' has already been added |
|
→ |
Locks, Process_classes
|
| |
SCHEDULER-423
|
en: |
There is no supervisor |
|
→ |
Spooler |
| |
SCHEDULER-424
|
en: |
'(1) ' is being removed before '(2) ' |
| |
SCHEDULER-426
|
en: |
'job_chain(2) ' and 'job_chain(3) ' cannot be combined, because of duplicate order id '(1) ' |
|
→ |
»Änderungsprotokoll«, <job_chain_node.job_chain>
|
| |
SCHEDULER-427
|
en: |
Invalid MD5 hexadecimal coded password for HTTP user '(1) ' |
|
→ |
<http.user>
|
| |
SCHEDULER-428
|
en: |
Error when reading base file 'path(1) ' (timestamp(2) ):
error(3)
|
| |
SCHEDULER-429
|
en: |
Current name of '(1) ' is fixed and cannot be changed to '(2) ' |
| |
SCHEDULER-430
|
en: |
'object type(1) name(2) ' is unknown |
| |
SCHEDULER-431
|
en: |
Error when processing configuration directory:
error(1)
|
| |
SCHEDULER-432
|
en: |
object type(1) has no name |
| |
SCHEDULER-433
|
en: |
'object(1) ' is not in any folder and cannot be replaced or removed |
| |
SCHEDULER-434
|
en: |
Error when closing 'object(1) ':
error(2)
|
| |
SCHEDULER-435
|
en: |
Standing order filename has not expected syntax jobchain,orderid.order.xml: filename(1)
|
| |
SCHEDULER-436
|
en: |
Order id in <order> is different from order id in configuration filename |
| |
SCHEDULER-437
|
en: |
Attribute job_chain="(1) " is not empty and differs from Job_chain '(2) ' in configuration filename |
| |
SCHEDULER-438
|
en: |
Invalid Job_chain_node for add_order() with state='(1) ' |
| |
SCHEDULER-439
|
en: |
Error when removing after base file 'path(1) ' has been removed:
error(3)
|
| |
SCHEDULER-440
|
en: |
Definition of object(1) is incomplete |
| |
SCHEDULER-441
|
en: |
Invalid value in <element(1) attribute(2) ="(3) "> |
| |
SCHEDULER-442
|
en: |
Attribute attribute(1) cannot be combined with attribute(2)
|
| |
SCHEDULER-443
|
en: |
<month month="(1) "> has been defined already |
| |
SCHEDULER-445
|
en: |
Invalid weekday '(1) ' |
| |
SCHEDULER-446
|
en: |
<weekday day="(1) " which="(2) " has been defined already |
| |
SCHEDULER-447
|
en: |
Error in job_monitor(1) :
error(2)
|
| |
SCHEDULER-448
|
en: |
File '(1) ' cannot be read, because it is bigger than (2) MB |
| |
SCHEDULER-449
|
en: |
Syntax error in order parameters file environment_variable_name(1) : Missing '=' after variable name |
| |
SCHEDULER-450
|
en: |
Java file '(1) ' could not be deleted |
| |
SCHEDULER-451
|
en: |
Database check failed, database is not useable. error(1)
|
|
→ |
»Änderungsprotokoll« |
| |
SCHEDULER-452
|
en: |
Database does not correctly store test values:
(1) (written value)
(2) (read value) |
|
→ |
»Änderungsprotokoll« |
| |
SCHEDULER-453
|
en: |
Database does not respect rollback command |
|
→ |
»Änderungsprotokoll« |
| |
SCHEDULER-454
|
en: |
Remote configuration directories '(1) ' and '(2) ' refer to the same IP number |
|
→ |
»Änderungsprotokoll«, <config>
|
| |
SCHEDULER-455
|
en: |
No configuration directory for '(1) ' |
|
→ |
»Änderungsprotokoll«, <config>
|
| |
SCHEDULER-456
|
en: |
Invalid response from supervisor |
|
→ |
»Änderungsprotokoll« |
| |
SCHEDULER-457
|
en: |
Remote scheduler '(1) ' has not been registered |
|
→ |
»Änderungsprotokoll«, <config>
|
| |
SCHEDULER-459
|
en: |
Error in dependant after '(1) ' has been loaded:
(2)
|
| |
SCHEDULER-460
|
en: |
object(1) is centrally defined and cannot be locally overwritten |
|
→ |
»Änderungsprotokoll« |
| |
SCHEDULER-461
|
en: |
Path reaches beyond root (too many '..'): (1)
|
|
→ |
<include>
|
| |
SCHEDULER-462
|
en: |
Attribute live_file= is not possible here. Use attribute file= |
| |
SCHEDULER-463
|
en: |
schedule(1) : substituted 'schedule(2) ' is a substitute |
|
→ |
<schedule>
|
| |
SCHEDULER-464
|
en: |
schedule(1) : valid_from="(2) "> is not before valid_to="(3) "
|
|
→ |
<schedule>
|
| |
SCHEDULER-465
|
en: |
'schedule(1) ' overlaps schedule(2)
|
|
→ |
<schedule>
|
| |
SCHEDULER-466
|
en: |
'schedule(1) ' is a substitute for another schedule and cannot be used directly |
|
→ |
<schedule>
|
| |
SCHEDULER-467
|
en: |
Attribute 'attribute(1) ' is only valid with attribute 'attribute(2) ' |
| |
SCHEDULER-468
|
en: |
Using this call is not possible in this context |
|
→ |
Task |
| |
SCHEDULER-469
|
en: |
try_hold_lock() or try_hold_lock_non_exclusive() has failed and call_me_again_when_locks_available() has not been called |
|
→ |
Task |
| |
SCHEDULER-470
|
en: |
Path is not absolute: (1)
|
| |
SCHEDULER-471
|
en: |
Not supported character for encoding '(1) ' |
|
→ |
»Änderungsprotokoll«, <script>
|
| |
SCHEDULER-900
|
en: |
Scheduler (1) is starting with (2) , pid=(3)
|
|
de: |
Scheduler (1) startet mit (2) , pid=(3)
|
| |
SCHEDULER-902
|
en: |
state=(1)
|
| |
SCHEDULER-904
|
en: |
Tasks have (1) seconds to terminate |
|
de: |
Die Tasks haben (1) s sich zu beenden |
| |
SCHEDULER-906
|
en: |
Restarting Scheduler: (1)
|
| |
SCHEDULER-907
|
en: |
Opening database: (1)
|
|
de: |
Datenbank wird geöffnet(1)
|
| |
SCHEDULER-908
|
en: |
Column (2) is being added to database table (1) : (3)
|
|
de: |
Datenbank-Tabelle (1) wird um die Spalte (2) erweitert: (3)
|
| |
SCHEDULER-909
|
en: |
Creating database table (1)
|
|
de: |
Datenbank-Tabelle (1) wird eingerichtet |
| |
SCHEDULER-910
|
en: |
New history file opened: (1)
|
|
de: |
Neue Historiendatei eröffnet: (1)
|
| |
SCHEDULER-912
|
en: |
add_pid((1) ), process deadline is (2)
|
| |
SCHEDULER-913
|
en: |
Previous history has been archived under (1)
|
|
de: |
Bisherige Historie ist archiviert worden unter (1)
|
| |
SCHEDULER-914
|
en: |
end() called, task will terminate |
|
de: |
|
| |
SCHEDULER-915
|
en: |
Process event |
| |
SCHEDULER-916
|
en: |
idle_timeout is over, terminating task |
|
de: |
idle_timeout ist abgelaufen, Task beendet sich |
| |
SCHEDULER-917
|
en: |
Enqueued task has been loaded from database: id=(1) start_at=(2)
|
|
de: |
Zu startende Task aus Datenbank geladen: id=(1) start_at=(2)
|
| |
SCHEDULER-918
|
en: |
state=(1) (2)
|
| |
SCHEDULER-919
|
en: |
Task (1) enqueued |
|
de: |
Task (1) in Warteschlange eingereiht |
| |
SCHEDULER-920
|
en: |
Reading script again (processing again <include>) |
|
de: |
Skript wird erneut gelesen (<include> wird erneut ausgefhrt) |
| |
SCHEDULER-921
|
en: |
Next period is (1) , Schedule '(2) ' |
| |
SCHEDULER-922
|
en: |
No further period |
|
de: |
Keine weitere Periode |
| |
SCHEDULER-923
|
en: |
Repeating at (1) due to delay_after_error |
|
de: |
Wiederholung wegen delay_after_error: (1)
|
| |
SCHEDULER-924
|
en: |
First start at the start of the period: (1)
|
|
de: |
Erster Start zu Beginn der Periode: (1)
|
| |
SCHEDULER-925
|
en: |
Next start at (2) due to spooler_job.repeat=(1)
|
|
de: |
Wiederholung wegen spooler_job.repeat=(1) : (2)
|
| |
SCHEDULER-926
|
en: |
Next start at (2) due to <period repeat="(1) "> |
|
de: |
Nächste Wiederholung wegen <period repeat="(1) ">: (2)
|
| |
SCHEDULER-927
|
en: |
Next start time will be determined at beginning of the next period. This is at (1)
|
|
de: |
Nächste Startzeit wird bestimmt zu Beginn der nächsten Periode: (1)
|
| |
SCHEDULER-928
|
en: |
Next single_start at (1)
|
|
de: |
Nächster single_start (1)
|
| |
SCHEDULER-930
|
en: |
Task (1) started - cause: (2)
|
|
de: |
Task (1) gestartet, Anlass: (2)
|
|
→ |
»Änderungsprotokoll« |
| |
SCHEDULER-931
|
en: |
state=(1)
|
|
de: |
state=(1)
|
| |
SCHEDULER-933
|
en: |
TCP connection accepted |
|
de: |
TCP-Verbindung angenommen |
| |
SCHEDULER-934
|
en: |
Compiling Java source: (1)
|
| |
SCHEDULER-935
|
en: |
(1) orders read from database |
|
de: |
(1) Aufträge aus der Datenbank gelesen |
| |
SCHEDULER-936
|
en: |
Replacing (1) now |
| |
SCHEDULER-937
|
en: |
Removing (1) now |
| |
SCHEDULER-938
|
en: |
Order will be processed at (1)
|
|
de: |
Auftrag wird ausgeführt um (1)
|
| |
SCHEDULER-939
|
en: |
Replacing order with same id: (1)
|
|
de: |
Auftrag mit gleicher Id wird ersetzt: (1)
|
| |
SCHEDULER-940
|
en: |
Removing order from job chain |
|
de: |
Auftrag wird aus der Jobkette entfernt |
| |
SCHEDULER-941
|
en: |
Removing order from job chain. Order is still being executed by (1)
|
|
de: |
Auftrag wird aus der Jobkette entfernt, aber weiterhin von (1) ausgeführt |
| |
SCHEDULER-942
|
en: |
add_or_replace_order(): order delayed until (1) has executed (2)
|
|
de: |
add_or_replace_order(): Auftrag wird verzögert bis (1) (2) ausgeführt hat |
| |
SCHEDULER-943
|
en: |
setback() called (1) times. Setting order to error state |
|
de: |
(1) mal zurückgestellt. Der Auftrag wechselt in den Fehlerzustand |
| |
SCHEDULER-944
|
en: |
End state reached - order will be repeated at (2) with state=(1)
|
|
de: |
Kein weiterer Job in der Jobkette, der Auftrag wird mit state=(1) wiederholt um (2)
|
| |
SCHEDULER-945
|
en: |
No further job in job chain - order has been carried out |
|
de: |
Kein weiterer Job in der Jobkette, der Auftrag ist erledigt |
| |
SCHEDULER-946
|
en: |
setback(): order has been set back (1) times, until (2)
|
|
de: |
setback(): Auftrag zum (1) . Mal zurückgestellt, bis (2)
|
|
→ |
Order |
| |
SCHEDULER-947
|
en: |
setback(): order has been set back (1) times. This is more than (2) - the maximum for this job |
|
de: |
setback(): Auftrag zum (1) . Mal zurückgestellt, das ist über dem Maximum (2) des Jobs |
|
→ |
Order |
| |
SCHEDULER-948
|
en: |
Process (1) started |
|
de: |
Prozess (1) gestartet |
| |
SCHEDULER-949
|
en: |
Job will be executed when a process of process class '(1) ' becomes available |
|
→ |
»Änderungsprotokoll« |
| |
SCHEDULER-950
|
en: |
Scheduler has been registered |
|
de: |
Scheduler ist registriert |
| |
SCHEDULER-951
|
en: |
Daylight saving time has begun |
|
de: |
Sommerzeit beginnt |
| |
SCHEDULER-952
|
en: |
Daylight saving time has ended, now it's standard time |
|
de: |
Winterzeit beginnt |
| |
SCHEDULER-953
|
en: |
Still sleeping (1) seconds ... |
|
de: |
Noch (1) Sekunden schlafen ... |
| |
SCHEDULER-954
|
en: |
XSLT stylesheet (1) ="(2) " returns: |
|
de: |
XSLT-Stylesheet (1) ="(2) " liefert: |
|
→ |
<web_service>
|
| |
SCHEDULER-955
|
en: |
UDP message from (1) : (2)
|
|
de: |
UDP-Nachricht von (1) : (2)
|
| |
SCHEDULER-956
|
en: |
Scheduler expects commands from (1) port (2) |
|
de: |
Scheduler erwartet Kommandos über (1) -Port (2)
|
| |
SCHEDULER-957
|
en: |
Closing database |
|
de: |
Datenbank wird geschlossen |
| |
SCHEDULER-958
|
en: |
Waiting (1) seconds before reopening the database |
|
de: |
(1) Sekunden warten bevor Datenbank erneut geöffnet wird ... |
| |
SCHEDULER-959
|
en: |
Switching history from database to plain files |
|
de: |
Historie wird von Datenbank auf Dateien umgeschaltet |
| |
SCHEDULER-960
|
en: |
Windows service handler: control=(1) event=(2)
|
| |
SCHEDULER-961
|
en: |
Protocol starts in (1)
|
| |
SCHEDULER-962
|
en: |
Protocol ends in (1)
|
| |
SCHEDULER-963
|
en: |
Copying protocol file to (1)
|
| |
SCHEDULER-964
|
en: |
New (1)
|
|
|
The web service has created a new order and handed it over to the job chain. |
|
de: |
Neuer (1) Der Web-Service hat einen Auftrag erzeugt und der Jobkette übergeben.
|
|
→ |
<web_service>
|
| |
SCHEDULER-965
|
en: |
Executing command (1)
|
|
→ |
<commands>
|
| |
SCHEDULER-966
|
en: |
Command answer: (1)
|
|
→ |
<commands>
|
| |
SCHEDULER-967
|
en: |
start_new_file(): protocol file is being closed now |
| |
SCHEDULER-968
|
en: |
start_new_file(): intermediate protocol file is: (1)
|
| |
SCHEDULER-969
|
en: |
Less than min_tasks=(1) are running. New tasks will be started. Reason: (2)
|
|
→ |
<job>
|
| |
SCHEDULER-970
|
en: |
task(1) ended immediately after start, so min_tasks=(2) doesn't lead to new tasks |
|
→ |
<job>
|
| |
SCHEDULER-972
|
en: |
Still waiting until time(1) (object(2) ) ... |
|
→ |
»Änderungsprotokoll« |
| |
SCHEDULER-973
|
en: |
Killed task does not stop the job because of ignore_signals="..."
|
| |
SCHEDULER-974
|
en: |
Last error does not stop the job if the task aborts (after kill or crash) with any signal listed in ignore_signals="(1) ". In this case, expect warning SCHEDULER-279 |
|
→ |
<job>
|
| |
SCHEDULER-975
|
en: |
This file path with ';' will not be included in changed_directory: (1)
|
|
→ |
Task |
| |
SCHEDULER-976
|
en: |
This directory path with ';' will not be included in triggered_files: (1)
|
|
→ |
Task |
| |
SCHEDULER-977
|
en: |
Job is not stopping because of <job stop_on_error="no">. Task error was: (1)
|
|
→ |
»Änderungsprotokoll«, <job>
|
| |
SCHEDULER-978
|
en: |
Job is stopping because of <job stop_on_error="yes">. Task error was: (1)
|
|
→ |
»Änderungsprotokoll«, <job>
|
| |
SCHEDULER-979
|
en: |
Removing file (1)
|
|
→ |
<file_order_sink>
|
| |
SCHEDULER-980
|
en: |
Moving file (1) to (2)
|
|
→ |
<file_order_sink>
|
| |
SCHEDULER-981
|
en: |
File on blacklist has been removed |
|
→ |
»Verzeichnisüberwachung mit Dateiaufträgen«, <file_order_source>
|
| |
SCHEDULER-982
|
en: |
File has been removed, so the file order is being removed too |
|
→ |
»Verzeichnisüberwachung mit Dateiaufträgen«, <file_order_source>
|
| |
SCHEDULER-983
|
en: |
New file, written at ...(2) : Added order(1)
|
|
→ |
<file_order_source>
|
| |
SCHEDULER-984
|
en: |
Recovered from previous error in directory (1)
|
|
→ |
»Verzeichnisüberwachung mit Dateiaufträgen«, <file_order_source>
|
| |
SCHEDULER-985
|
en: |
number(1) more file orders will be added later, after previous orders have been processed |
|
→ |
»Verzeichnisüberwachung mit Dateiaufträgen«, <file_order_source>
|
| |
SCHEDULER-986
|
en: |
Continuing reading buffered directory (as of time(1) ) |
|
→ |
»Verzeichnisüberwachung mit Dateiaufträgen«, <file_order_source>
|
| |
SCHEDULER-987
|
en: |
Starting process: program and arguments(1)
|
|
→ |
»Änderungsprotokoll«, <process>
|
| |
SCHEDULER-989
|
en: |
object_type(1) cannot be removed now, it will be done later |
|
→ |
Process_class |
| |
SCHEDULER-990
|
en: |
Adding order(1)
|
| |
SCHEDULER-991
|
en: |
Order has been suspended |
| |
SCHEDULER-992
|
en: |
Order ist not longer suspended, next start (1)
|
| |
SCHEDULER-994
|
en: |
No heart beat for (2) seconds (time(1) ), expecting heart beat within (3) seconds |
|
→ |
»Kommandozeilenoptionen«, <cluster>
|
| |
SCHEDULER-995
|
en: |
No heart beat for (2) seconds (time(1) ), ignored for (3) seconds because of recent database reconnect |
|
→ |
»Kommandozeilenoptionen«, <cluster>
|
| |
SCHEDULER-996
|
en: |
No heart beat for (2) seconds (time(1) ) - Scheduler seems to be dead |
|
→ |
»Kommandozeilenoptionen«, <cluster>
|
| |
SCHEDULER-997
|
en: |
Making up an extra heart beat |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-999
|
en: |
Scheduler has been terminated properly |
|
de: |
Scheduler ordentlich beendet |
|
→ |
<terminate>
|
| |
SCHEDULER-805
|
en: |
No Scheduler is active |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-806
|
en: |
This Scheduler is active and exclusive now |
| |
SCHEDULER-807
|
en: |
Using database product (1)
|
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-809
|
en: |
Dead scheduler record has been removed |
| |
SCHEDULER-811
|
en: |
Executing command read from database: (1)
|
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-812
|
en: |
Just before processing, order record in database has been occupied or removed |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-813
|
en: |
Order is occupied by Scheduler '(1) ' |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-814
|
en: |
Inactive Scheduler '(2) ' has the higher backup precedence (1) (http_url(3) ) |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-815
|
en: |
Task should end but it has just been started with an order attached, so one step will be done |
|
→ |
Task, »Kommandozeilenoptionen« |
| |
SCHEDULER-816
|
en: |
Unable to release occupation in database |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-817
|
en: |
Missing order record in database |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-819
|
en: |
Scheduler becomes active |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-820
|
en: |
Watching heart beat of that Scheduler |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-821
|
en: |
Scheduler member 'cluster_member_id(1) ' seems to be active, claiming its last heart beat was (2) s ago (pid=(4) , url(3) ) |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-822
|
en: |
Scheduler member 'cluster_member_id(1) ' seems to be exclusive, claiming its last heart beat was (2) s ago (pid=(4) , url(3) ) |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-823
|
en: |
Dead Scheduler member 'cluster_member_id(1) ' has resurrected |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-825
|
en: |
No exclusive Scheduler is running |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-826
|
en: |
That Scheduler has terminated |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-827
|
en: |
Own heart beat is late: next_heart_beat has been announced for (1) (this is (2) seconds late) |
|
→ |
»Änderungsprotokoll«, »Kommandozeilenoptionen« |
| |
SCHEDULER-829
|
en: |
Releasing occupied order job_chain(1) :id(2)
|
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-830
|
en: |
Because all Scheduler tasks have been killed, the order in database has not been updated. Only the occupation has been released |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-831
|
en: |
Waiting (1) s for start of non-backup Scheduler |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-832
|
en: |
This is a backup Scheduler, waiting for a non-backup Scheduler |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-833
|
en: |
Watching heart beat of that exclusive Scheduler, standing by to take over operation |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-834
|
en: |
Active Scheduler has terminated properly |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-835
|
en: |
This Scheduler is becoming exclusive now |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-836
|
en: |
Deactivating that dead Scheduler |
|
→ |
»Kommandozeilenoptionen«, <cluster>
|
| |
SCHEDULER-837
|
en: |
Taking exclusiveness from that Scheduler |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-838
|
en: |
(1) . heart beat detected |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-839
|
en: |
This order has been replaced |
| |
SCHEDULER-841
|
en: |
It has been requested that the exclusive operation will not be continued |
| |
SCHEDULER-842
|
en: |
Task is going to process order(1) , state=(2) , on Scheduler (3)
|
| |
SCHEDULER-843
|
en: |
Task has ended processing of order(1) , state=(2) , on Scheduler (3)
|
| |
SCHEDULER-844
|
en: |
Scheduler script is not yet active. Operation is executed without the call of function '(1) ' |
| |
SCHEDULER-845
|
en: |
Task ended without processing the order. The order remains in job's order queue in the same state |
|
→ |
»Änderungsprotokoll« |
| |
SCHEDULER-846
|
en: |
After task exception and due to stop_on_error='no', the order has been moved to error_state='(1) ' |
|
→ |
»Änderungsprotokoll«, <job>
|
| |
SCHEDULER-847
|
en: |
Please use new name '(1) ' instead of old '(2) ' |
|
→ |
»Änderungsprotokoll« |
| |
SCHEDULER-848
|
en: |
Task pid=(1) started for remote scheduler |
|
→ |
<process_class>
|
| |
SCHEDULER-849
|
en: |
Timeout is not possible for a subprocess running on a remote host (it cannot be killed), pid=(1)
|
|
→ |
Subprocess, Task, <process_class>
|
| |
SCHEDULER-850
|
en: |
After lost connection to remote scheduler, process (1) is going to be killed |
|
→ |
<process_class>
|
| |
SCHEDULER-851
|
en: |
After possibly volatile error (number (1) ), the statement which caused the error will be repeated: (2)
|
| |
SCHEDULER-852
|
en: |
Order not found in database |
| |
SCHEDULER-853
|
en: |
Order in database could not be updated or deleted. |
| |
SCHEDULER-854
|
en: |
Closing lock (1) while held by (2)
|
| |
SCHEDULER-855
|
en: |
Task is now holding Lock(1) exclusively/non-exclusively(2)
|
|
→ |
<lock.use>
|
| |
SCHEDULER-856
|
en: |
Lock(1) has been released |
|
→ |
<lock.use>
|
| |
SCHEDULER-857
|
en: |
Lock(1) has been released, (2) non-exclusive holders remaining |
|
→ |
<lock.use>
|
| |
SCHEDULER-858
|
en: |
Not longer waiting for lock locknames(1)
|
|
→ |
<lock.use>
|
| |
SCHEDULER-859
|
en: |
Due to action='next_state' the state '(2) ' has been skipped. Next state is '(1) ' |
|
→ |
<job_chain_node.modify>
|
| |
SCHEDULER-860
|
en: |
Waiting for 'lock(1) ', exclusive(2) , on place (3) (current holders(4) ) |
|
→ |
<lock.use>
|
| |
SCHEDULER-861
|
en: |
'object(1) ' has been removed |
|
→ |
Lock, Process_class, <lock.remove>, <schedule.remove>
|
| |
SCHEDULER-862
|
en: |
Continuing in 'job chain(1) ' |
|
→ |
<job_chain_node.job_chain>
|
| |
SCHEDULER-863
|
en: |
Continuing from 'job chain(1) ' |
|
→ |
<job_chain_node.job_chain>
|
| |
SCHEDULER-871
|
en: |
Closing process class before process(1)
|
| |
SCHEDULER-872
|
en: |
New 'Job_chain(1) ' shares order IDs with job_chains(2)
|
|
→ |
»Änderungsprotokoll«, <job_chain_node.job_chain>
|
| |
SCHEDULER-873
|
en: |
Job_chains job_chains(2) share order IDs because 'Job_chain(1) ' has been removed |
|
→ |
»Änderungsprotokoll«, Job_chain, <job_chain_node.job_chain>, <remove_job_chain>
|
| |
SCHEDULER-874
|
en: |
Order_id_space has been closed |
|
→ |
»Änderungsprotokoll«, Job_chain, <job_chain_node.job_chain>, <remove_job_chain>
|
| |
SCHEDULER-875
|
en: |
Order_id_space has been closed because 'job_chain(1) ' has been removed |
|
→ |
»Änderungsprotokoll«, <job_chain_node.job_chain>
|
| |
SCHEDULER-876
|
en: |
Temporary files cannot be deleted. Still trying ..., paths(1)
|
|
→ |
»Änderungsprotokoll« |
| |
SCHEDULER-877
|
en: |
Temporary files have been deleted now |
|
→ |
»Änderungsprotokoll« |
| |
SCHEDULER-878
|
en: |
Temporary files cannot be deleted: paths(1)
|
|
→ |
»Änderungsprotokoll« |
| |
SCHEDULER-879
|
en: |
Deactivating old cluster member with same ID |
|
→ |
»Kommandozeilenoptionen« |
| |
SCHEDULER-880
|
en: |
Error when creating database index is ignored |
| |
SCHEDULER-881
|
en: |
Error when reading stdout file is ignored: error(1) , path(2)
|
| |
SCHEDULER-882
|
en: |
Configuration directory '(1) ' has been removed:
error(2)
|
| |
SCHEDULER-884
|
en: |
Configuration directory has been deleted |
| |
SCHEDULER-885
|
en: |
Task ends because 'lock(1) ' is being removed |
| |
SCHEDULER-886
|
en: |
Lock will be removed later, it is held by '(1) ' |
|
→ |
Lock, <lock.remove>
|
| |
SCHEDULER-887
|
en: |
More lock holders than new max_non_exclusive=(1) : holders(2)
|
|
→ |
Lock, <lock>
|
| |
SCHEDULER-888
|
en: |
object_type(1) cannot be replaced now, it will be done later |
| |
SCHEDULER-889
|
en: |
These filenames yield the same object name: '(1) ' and '(2) '. The second is ignored |
| |
SCHEDULER-890
|
en: |
object_type(2) is going to be removed because its configuration file '(1) ' has been removed |
| |
SCHEDULER-891
|
en: |
Configuration file '(1) ' (timestamp(2) ) is going to be be loaded into this new type(3)
|
| |
SCHEDULER-892
|
en: |
This type(3) is going to be replaced due to changed configuration file '(1) ' (timestamp(2) ) |
| |
SCHEDULER-893
|
en: |
objecttype(1) is 'state(2) ' now |
| |
SCHEDULER-894
|
en: |
'(1) ' will be removed later, it is used by job_chains(2)
|
| |
SCHEDULER-895
|
en: |
Configuration directory '(1) ' does not exist, it will be ignored |
| |
SCHEDULER-897
|
en: |
Error in replacement ignored::
error(2)
|
| |
SCHEDULER-898
|
en: |
Folder is going to be removed because its configuration directory has been removed |
| |
SCHEDULER-899
|
en: |
Scheduler has no UDP port, so updated configuration files on supervisor will not be noticed |
|
→ |
»Änderungsprotokoll« |
| |
SCHEDULER-701
|
en: |
Replicating '(1) ' |
|
→ |
»Änderungsprotokoll« |
| |
SCHEDULER-702
|
en: |
Removing '(1) ' |
|
→ |
»Änderungsprotokoll« |
| |
SCHEDULER-703
|
en: |
Local configuration file is ignored, the central configuration file is used instead |
|
→ |
»Änderungsprotokoll« |
| |
SCHEDULER-704
|
en: |
Order has reached its end_state='(1) ' |
| |
SCHEDULER-705
|
en: |
Substitute 'schedule(1) ' is valid now |
|
→ |
<schedule>
|
| |
SCHEDULER-706
|
en: |
Standard 'schedule(1) ' is valid now |
|
→ |
<schedule>
|
| |
SCHEDULER-707
|
en: |
Creating configuration directory '(1) ' |
|
→ |
<modify_hot_folder>
|
| |
SCHEDULER-708
|
en: |
Adding 'job_chain(1) ' |
|
→ |
<job_chain_node.job_chain>
|
| |
SCHEDULER-709
|
en: |
Killing descendant pid=(1) (command line(2) ) |
|
→ |
<kill_task>
|
| |
SCHEDULER-710
|
en: |
Delayed command <scheduler_log.log_categories.reset> has been executed |
|
→ |
<scheduler_log.log_categories.reset>
|
| |
SCHEDULER-711
|
en: |
Step has runned (2) s, which is shorter than the expected duration of (1)
|
|
→ |
<job>
|
| |
SCHEDULER-712
|
en: |
Step runs longer than the expected duration of (1)
|
