Appendix A: Messages

Code	Text
SCHEDULER-104	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> .
SCHEDULER-105	Unknown command: <(1)> See XML commands.
SCHEDULER-106	Unknown command for task: (1)
SCHEDULER-107	Missing script
SCHEDULER-110	Unknown task state: (1)
SCHEDULER-113	Unexpected XML tag: (1)
SCHEDULER-115	Missing XML configuration file, option -config=FILENAME.XML
SCHEDULER-116	XML configuration contains no <config spooler_id=(1)> element
SCHEDULER-117	Cannot use different scripting languages in the same scripting engine
SCHEDULER-119	There is no security level "(1)"
SCHEDULER-120	Script has reported an error: (1)
SCHEDULER-121	The security settings do not allow this operation
SCHEDULER-122	Task terminated
SCHEDULER-125	task.wait_until_terminated() cannot be called in its own thread. Deadlock.
SCHEDULER-130	Job (1) has already been defined
SCHEDULER-136	No history
SCHEDULER-139	Operation is not possible when using a plain text file for history
SCHEDULER-140	Task logged error: (1)
SCHEDULER-141	History has been suppressed for job (1) (history=no)
SCHEDULER-142	Relative database file path cannot be used with need_db=yes and log_dir=*stderr
SCHEDULER-143	Task cannot start because it has no start time and no valid <run_time>
SCHEDULER-145	<script> com_class= and language= cannot be combined
SCHEDULER-146	Missing script
SCHEDULER-147	(1) cannot accept orders because it has not been declared with <job order="yes">
SCHEDULER-148	'(1)' has been initialized already and cannot be modified
SCHEDULER-149	There is no job in job chain "(1)" for the state "(2)"
SCHEDULER-150	The state "(1)" has already assigned a job in job chain (2)
SCHEDULER-151	Job chain is not in use (missing add_job_chain() or job chain is to be removed)
SCHEDULER-152	Job "(1)" is not in job chain "(2)"
SCHEDULER-153	'(1)' is not in state '(2)'
SCHEDULER-155	A temporary job cannot accept orders
SCHEDULER-156	(1) is not in (2)
SCHEDULER-157	(1) is not in a job chain
SCHEDULER-159	Id and priority of an order placed in an order queue cannot be changed
SCHEDULER-160	There is already a (1) '(2)'
SCHEDULER-161	There is no (1) '(2)'
SCHEDULER-162	There is no order (1) in job chain "(2)"
SCHEDULER-163	(1) is not in an order queue
SCHEDULER-164	<show_... what="(1)">: invalid value for attribute what=
SCHEDULER-166	<script> java_class= and language= cannot be combined
SCHEDULER-167	A program source cannot be set with <script> com_class= or java_class=
SCHEDULER-168	com_class= and java_class= cannot be combined in <script>
SCHEDULER-172	This kind of script (scripting engine, Perl, COM or Java) is not possible here
SCHEDULER-173	Missing script
SCHEDULER-174	Method "(1)" is missing in class "(2)"
SCHEDULER-177	Java is not available (see error message when Scheduler started)
SCHEDULER-179	<process> task did not terminate. pid=(1)
SCHEDULER-182	Unexpected XML element <(1)>
SCHEDULER-183	Scheduler cannot start because spooler_init() in '(1)' returned false
SCHEDULER-184	Scheduler database cannot be accessed due to a database problem
SCHEDULER-186	(1) is already in job chain (2)
SCHEDULER-187	Order.setback(): An order can only be set back when it is being executed by a task
SCHEDULER-188	Order.setback() and Order.state= cannot be combined
SCHEDULER-191	separate_process: Unexpected state (2) in (1)
SCHEDULER-192	A separate process is only possible with use_engine="task"
SCHEDULER-194	process_class and separate_process cannot be combined
SCHEDULER-196	use_engine="(1)" is deprecated
SCHEDULER-197	Module::java_method_id((1)): unknown Java class
SCHEDULER-198	Missing variable name
SCHEDULER-199	Module instance has been closed
SCHEDULER-200	Remote instance has been closed
SCHEDULER-201	Missing working directory when calling Java compiler
SCHEDULER-202	Connection to task has been lost, state=(1): (2)
SCHEDULER-203	Module instance in the server has been closed
SCHEDULER-204	Job "(1)" is in error state. (2)
SCHEDULER-205	No database given (entry db= in factory.ini)
SCHEDULER-206	With need_db=(1), only "yes", "no" and "strict" are allowed
SCHEDULER-207	Task (1) is unknown (and not noted in the history)
SCHEDULER-208	Only a date without a time is allowed
SCHEDULER-209	Too many objects for Microsoft Windows MsgWaitForMultipleObjects(). MAXIMUM_WAIT_OBJECTS-1=(1) has been reached. Operation is not executable
SCHEDULER-210	Too many processes. The number of processes is limited to (1)
SCHEDULER-212	Missing entry [spooler] html_dir= in file factory.ini
SCHEDULER-213	Error in HTTP header: expecting (1)
SCHEDULER-214	Forbidden path in HTTP request
SCHEDULER-215	Unknown or terminated task (1)
SCHEDULER-217	(1) is being processed by (2)
SCHEDULER-218	Subprocess pid=(2) has been terminated with exit code=(1). Command=(3)
SCHEDULER-219	Subprocess pid=(2) has been terminated with signal (1). Command=(3)
SCHEDULER-220	<run_time (1)> cannot be carried out for an order
SCHEDULER-221	<day day="(1)">: only the days from (2) to (3) are possible
SCHEDULER-222	This command <(1)> is only executable by way of a TCP connection
SCHEDULER-223	Supervisor has reported an error: (1)
SCHEDULER-224	Supervisor has closed the connection
SCHEDULER-225	start_new_file() is only applicable for the main protocol
SCHEDULER-226	Order has not been processed because the task has been terminated before the processing step (spooler_process())
SCHEDULER-227	Scheduler script has logged an error: (1)
SCHEDULER-230	Job "(1)" is to be removed - it is not longer usable
SCHEDULER-231	Missing attribute (2) in XML element <(1)>
SCHEDULER-232	Attribute <(1) (2)="(3)"> is not allowed here
SCHEDULER-234	The <job (1)="..."> attribute cannot be overwritten
SCHEDULER-235	Unknown web service: "(1)"
SCHEDULER-236	Web service "(1)" has already been declared
SCHEDULER-237	XSLT stylesheet "(1)" does not deliver a result
SCHEDULER-238	Web service or alias for url_path="(1)" has already been declared
SCHEDULER-239	XML root element <(1)> expected
SCHEDULER-240	Order has not been assigned to a web service
SCHEDULER-241	Task has not been assigned to a web service
SCHEDULER-242	forward_xslt_stylesheet (1) does not deliver <service_request>
SCHEDULER-243	Property (1) is fixed and is no longer modifiable
SCHEDULER-244	Element <content> is missing or empty
SCHEDULER-245	Element <content> has more than one child element
SCHEDULER-246	Order does not belong to a web service operation
SCHEDULER-247	HTTP response has already been sent Web_service_response cannot be changed after Web_service_response.send() .
SCHEDULER-248	web_service_operation has finished and is not longer valid
SCHEDULER-249	Order id cannot be represented as a character string: (1)
SCHEDULER-250	Order state cannot be represented as a character string: (1)
SCHEDULER-251	Order payload cannot be represented as character string: (1)
SCHEDULER-252	Invalid url path - it has to begin with '/': (1)
SCHEDULER-254	(1) tasks did not terminate in spite of kill (2) seconds ago. Extending deadline for (3)s
SCHEDULER-255	(1) tasks did not terminate in spite of kill (2) seconds ago. Scheduler is aborting
SCHEDULER-256	Deadline for terminating Scheduler has been reached, but (1) tasks are still running
SCHEDULER-257	Job is being removed now
SCHEDULER-258	Job will be removed after all its tasks have terminated
SCHEDULER-259	Java did not start. Scheduler is starting without Java
SCHEDULER-260	Error in Scheduler Skript, spooler_exit(): (1) Error in Scheduler script, spooler_exit(): (1)
SCHEDULER-261	Nothing done, event=(1), operations=(2)
SCHEDULER-262	Kill signal ((1)) received. Scheduler is terminating
SCHEDULER-263	Kill signal ((1)) #(2) received. (3)
SCHEDULER-264	SCHEDULER IS TERMINATING AFTER SERIOUS ERROR
SCHEDULER-265	SCHEDULER IS ABORTING DUE TO A PROBLEM WITH THE DATABASE: (1)
SCHEDULER-266	Error when writing the history: (1)
SCHEDULER-267	Error when storing the log in table (1): (2)
SCHEDULER-268	Log of task (1) is not readable from database: (2)
SCHEDULER-269	Error when closing the job history: (1)
SCHEDULER-270	Cannot open history: (1)
SCHEDULER-271	Task is being terminated in favour of job (1)
SCHEDULER-272	Terminating task after reaching deadline <job timeout="(1)">
SCHEDULER-273	Killing subprocess (1)
SCHEDULER-274	Error when killing subprocess (1): (2)
SCHEDULER-275	Deadline reached, killing subprocess (1)
SCHEDULER-276	Could not kill task
SCHEDULER-278	<period> ended, terminating task
SCHEDULER-279	Process terminated with signal (1) ((2))
SCHEDULER-280	Process terminated with exit code (1) (0x(2))
SCHEDULER-281	Killing process
SCHEDULER-283	Error when loading task (1) from database: (2)
SCHEDULER-284	Ignoring cmd='(1)' because job is to be removed
SCHEDULER-285	Max. (1) history records are being read
SCHEDULER-286	More than (1) communication channels. Connection denied
SCHEDULER-287	TCP connection not allowed
SCHEDULER-288	-reuse-port (SO_REUSEADDR): using (1), but another application can use it too
SCHEDULER-289	(1) is blocked. Trying a further (2) seconds before giving up
SCHEDULER-290	Timeout: No job started to execute (1), cancelling order and HTTP operation See <web_service timeout="…">
SCHEDULER-291	Error when removing protocol file: (1)
SCHEDULER-292	Missing from, to, subject or body. Suppressing email
SCHEDULER-293	Waiting for closing module instance ...
SCHEDULER-294	Java class (1) could not be loaded. Java source is being recompiled before retrying
SCHEDULER-295	Error when loading order (1) from database: (2)
SCHEDULER-296	Order's <run_time> does not have a next start time
SCHEDULER-297	Order has been carried out without web_service_operation.send(), operation cancelled
SCHEDULER-298	Ignoring job=(1) because order is removed from job chain
SCHEDULER-299	Removing process (1) after error
SCHEDULER-300	Monitoring of directory (1) has ended after error: (2)
SCHEDULER-301	UDP message from (1) is not allowed
SCHEDULER-302	Error sending e-mail: (1)
SCHEDULER-303	Problem with database: (1)
SCHEDULER-304	Error when reading next id (column "(2)"): (1)
SCHEDULER-305	Error when inserting into table (1): (2)
SCHEDULER-306	Error when updating table (1): (2)
SCHEDULER-307	Not writing history record because of already existing database problem
SCHEDULER-308	Ignoring cancel() because response has already been sent
SCHEDULER-309	Error when opening database: (1)
SCHEDULER-310	Error when closing the database: (1)
SCHEDULER-311	Error when processing HTTP request (1): (2)
SCHEDULER-312	Variable "(1)" (vt=(2)) cannot be converted to Text: (3)
SCHEDULER-313	Cannot store order in database: (1)
SCHEDULER-314	Cannot open database. Scheduler is aborting immediately because of need_db=(1)
SCHEDULER-316	<web_service name="(1)"/>: attributes job_chain=/timeout= and request/response/forward_xslt_stylesheet= cannot be combined
SCHEDULER-318	Option -env=NAME=VALUE: missing '=' between name and value: -env="(1)"
SCHEDULER-319	XML-Element <(1)> is not possible here
SCHEDULER-320	Could not send mail
SCHEDULER-321	Mail has been sent, but an error occurred when processing the mail queue: (1)
SCHEDULER-322	min_tasks=(1) is greater than max_tasks=(2) See <job min_tasks="…"> .
SCHEDULER-323	exit_code is available only when task module is loaded See Task.exit_code .
SCHEDULER-324	Invalid value for attribute exit_code="" in <commands> See <job><commands> .
SCHEDULER-325	Attribute exit_code is not applicable here See <commands> .
SCHEDULER-326	<commands on_exit_code="">: <commands> for exit code (2) is already defined See <job><commands> .
SCHEDULER-327	Last error occurred when executing command: (1) See <job><commands> .
SCHEDULER-328	Executing <commands on_exit_code="(1)">: See <job><commands> .
SCHEDULER-329	<copy_params from=""/>: requested parameters are not available See <copy_params from="order"> .
SCHEDULER-330	(1) could not be initialized:(2)
SCHEDULER-331	Scheduler is terminating after error (see last error line)
SCHEDULER-332	Error in (1) while switching to state=(2): (3)
SCHEDULER-333	"now+SECONDS" expected in "(1)"
SCHEDULER-334	Error when building mail: (1)
SCHEDULER-335	Only "yes", "no" and a number are allowed with (1)="(2)": (3)
SCHEDULER-336	Only "yes", "no" and a list of signal names are allowed with (1)="(2)": (3)
SCHEDULER-337	Signal (1) is unknown on this operating system and is ignored
SCHEDULER-338	Order.payload is not a Variable_set
SCHEDULER-339	File does not exist and can therefore neither be moved nor removed: (1)
SCHEDULER-340	File still exists. Order has been set on the blacklist
SCHEDULER-342	There is no job between order source and order sink in (1)
SCHEDULER-343	This is no file order: (1)
SCHEDULER-344	order.id has more than (2) characters: (1)
SCHEDULER-345	order.id has more than (2) characters, the limit of your database column (3) is: (1)
SCHEDULER-346	Due to previous error the path will be ignored: (1)
SCHEDULER-347	Path has been removed from the blacklist: (1)
SCHEDULER-348	Database doesn't deliver width of column (1).(2)
SCHEDULER-349	Database column (1).(2) could not be expanded
SCHEDULER-350	Width of database column (1).(2) is unknown. We assume (3)
SCHEDULER-351	<modify_order_... setback="(1)">: Invalid value for attribute setback=
SCHEDULER-353	No immediate response from command <(1)>
SCHEDULER-354	Scheduler Java classes (sos.spooler.jar (1) expected) are not up to date: (2)
SCHEDULER-355	SQL update statement changed more than one record, (1): (2)
SCHEDULER-357	This is a member of a cluster (option -exclusive or -distributed-orders), and therefore needs a database
SCHEDULER-358	This is a member of a cluster (option -exclusive or -distributed-orders), and therefore needs a database. need_db=(1) is not allowed
SCHEDULER-359	For an exclusive or distributed Scheduler, the database (1) is not supported
SCHEDULER-360	Error when accessing database table (1)
SCHEDULER-361	No database
SCHEDULER-362	Scheduler is aborting because it has become inactive
SCHEDULER-363	Error when creating SQL table (1): (2)
SCHEDULER-365	Illegal character in -id=(1)
SCHEDULER-367	Scheduler is aborting because it has lost its exclusivity
SCHEDULER-368	Option (1) needs (2)
SCHEDULER-369	Option (1) conflicts with (2)
SCHEDULER-370	Operation can only be performed on a distributed orders Scheduler
SCHEDULER-371	DATABASE INTEGRITY IS BROKEN
SCHEDULER-372	Exclusivity has been stolen by Scheduler member '(1)'
SCHEDULER-373	UNEXPECTED DEACTIVATION BY SCHEDULER MEMBER (1)
SCHEDULER-374	In (1), state '(2)' has no job
SCHEDULER-375	Order is distributed and therefore does not support operation '(1)'
SCHEDULER-377	After own late heart beat, Scheduler member '(1)' has taken exclusiveness
SCHEDULER-378	After own late heart beat, this Scheduler has been deactivated and the occupied orders have been freed by Scheduler member '(1)'
SCHEDULER-379	(1) is occupied by Scheduler member '(2)'
SCHEDULER-380	job_chain orders_recoverable="no" cannot be combined with distributed="yes", in (1)
SCHEDULER-381	Scheduler is not yet active and cannot execute the operation
SCHEDULER-384	(1) is distributed and therefore does not support operation '(2)'
SCHEDULER-385	Deletion of order in database has failed
SCHEDULER-386	Last heart beat was (1), (2) seconds ago. Something is delaying Scheduler execution, the Scheduler is aborted immediately
SCHEDULER-389	This order stored in database is distributed and cannot be used in a non-distributed job chain
SCHEDULER-390	More than (1) nested includes in (2)
SCHEDULER-391	Invalid value '(2)' for setting '(1)'. Allowed values are: (3)
SCHEDULER-392	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	Error when calling <run_time> function '(1)': (2)
SCHEDULER-394	<run_time>-Function '(1)' returned start time (2) which is earlier than the requested beginning (3)
SCHEDULER-396	Job has not yet reached state '(1)' for operation (2)
SCHEDULER-397	A distributed order does not support (1)
SCHEDULER-398	After last error, next_start_function='(1)' will no longer be executed for this <run_time>
SCHEDULER-399	Error in (1):(2)
SCHEDULER-401	Unknown '(1)'
SCHEDULER-403	There is no valid state for job chain node state='(1)', action='next_state' (circular next_state)
SCHEDULER-404	action='(1)' is not possible on a distributed job chain
SCHEDULER-405	Setting state='(1)' is not possible while job chain has state '(2)'
SCHEDULER-406	Error in job chain node state='(1)': (2)
SCHEDULER-407	Attribute (1) is empty
SCHEDULER-408	<(1) (2)=...> cannot be changed
SCHEDULER-409	XML tag <(1)> expected, instead of <(2)>
SCHEDULER-412	Job chains can only be nested once
SCHEDULER-413	Nested job chains cannot be combined with distributed orders
SCHEDULER-414	There is a circular nesting of job chains: (1)
SCHEDULER-415	Error when trying to continue in next job chain: (1)
SCHEDULER-416	'(1)' is already known
SCHEDULER-417	Invalid name: '(1)'
SCHEDULER-419	New Process_class.max_processes=(1) is below current number of processes=(2)
SCHEDULER-420	Negative value is not allowed for (1)
SCHEDULER-422	'(1)' has already been added
SCHEDULER-423	There is no supervisor
SCHEDULER-424	'(1)' is being removed before '(2)'
SCHEDULER-426	'(2)' and '(3)' cannot be combined, because of duplicate order id '(1)'
SCHEDULER-427	Invalid MD5 hexadecimal coded password for HTTP user '(1)'
SCHEDULER-428	Error when reading base file '(1)' ((2)):(3)
SCHEDULER-429	Current name of '(1)' is fixed and cannot be changed to '(2)'
SCHEDULER-430	'(1) (2)' is unknown
SCHEDULER-431	Error when processing configuration directory:(1)
SCHEDULER-432	(1) has no name
SCHEDULER-433	'(1)' is not in any folder and cannot be replaced or removed
SCHEDULER-434	Error when closing '(1)':(2)
SCHEDULER-435	Standing order filename has not expected syntax jobchain,orderid.order.xml: (1)
SCHEDULER-436	Order id in <order> is different from order id in configuration filename
SCHEDULER-437	Attribute job_chain="(1)" is not empty and differs from Job_chain '(2)' in configuration filename
SCHEDULER-438	Invalid Job_chain_node for add_order() with state='(1)'
SCHEDULER-439	Error when removing after base file '(1)' has been removed:(3)
SCHEDULER-440	Definition of (1) is incomplete
SCHEDULER-441	Invalid value in <(1) (2)="(3)">
SCHEDULER-442	Attribute (1) cannot be combined with (2)
SCHEDULER-443	<month month="(1)"> has been defined already
SCHEDULER-445	Invalid weekday '(1)'
SCHEDULER-446	<weekday day="(1)" which="(2)" has been defined already
SCHEDULER-447	Error in (1): (2)
SCHEDULER-448	File '(1)' cannot be read, because it is bigger than (2)MB
SCHEDULER-449	Syntax error in order parameters file (1): Missing '=' after variable name
SCHEDULER-450	Java file '(1)' could not be deleted
SCHEDULER-451	Database check failed, database is not useable. (1)
SCHEDULER-452	Database does not correctly store test values:(1) (written value)(2) (read value)
SCHEDULER-453	Database does not respect rollback command
SCHEDULER-454	Remote configuration directories '(1)' and '(2)' refer to the same IP number
SCHEDULER-455	No configuration directory for '(1)'
SCHEDULER-456	Invalid response from supervisor
SCHEDULER-457	Remote scheduler '(1)' has not been registered
SCHEDULER-459	Error in dependant after '(1)' has been loaded:(2)
SCHEDULER-460	(1) is centrally defined and cannot be locally overwritten
SCHEDULER-461	Path reaches beyond root (too many '..'): (1)
SCHEDULER-462	Attribute live_file= is not possible here. Use attribute file=
SCHEDULER-463	(1): substituted '(2)' is a substitute
SCHEDULER-464	(1): valid_from=""> is not before valid_to=""
SCHEDULER-465	'(1)' overlaps (2)
SCHEDULER-466	'(1)' is a substitute for another schedule and cannot be used directly
SCHEDULER-467	Attribute '(1)' is only valid with attribute '(2)'
SCHEDULER-468	Using this call is not possible in this context
SCHEDULER-469	try_hold_lock() or try_hold_lock_non_exclusive() has failed and call_me_again_when_locks_available() has not been called
SCHEDULER-470	Path is not absolute: (1)
SCHEDULER-471	Not supported character for encoding '(1)'
SCHEDULER-900	Scheduler (1) is starting with (2), pid=(3)
SCHEDULER-902	state=(1)
SCHEDULER-904	Tasks have (1) seconds to terminate
SCHEDULER-906	Restarting Scheduler: (1)
SCHEDULER-907	Opening database: (1)
SCHEDULER-908	Column (2) is being added to database table (1): (3)
SCHEDULER-909	Creating database table (1)
SCHEDULER-910	New history file opened: (1)
SCHEDULER-912	add_pid((1)), process deadline is (2)
SCHEDULER-913	Previous history has been archived under (1)
SCHEDULER-914	end() called, task will terminate
SCHEDULER-915	Process event
SCHEDULER-916	idle_timeout is over, terminating task
SCHEDULER-917	Enqueued task has been loaded from database: id=(1) start_at=(2)
SCHEDULER-918	state=(1) (2)
SCHEDULER-919	Task (1) enqueued
SCHEDULER-920	Reading script again (processing again <include>)
SCHEDULER-921	Next period is (1), Schedule '(2)'
SCHEDULER-922	No further period
SCHEDULER-923	Repeating at (1) due to delay_after_error
SCHEDULER-924	First start at the start of the period: (1)
SCHEDULER-925	Next start at (2) due to spooler_job.repeat=(1)
SCHEDULER-926	Next start at (2) due to <period repeat="(1)">
SCHEDULER-927	Next start time will be determined at beginning of the next period. This is at (1)
SCHEDULER-928	Next single_start at (1)
SCHEDULER-930	Task (1) started - cause: (2)
SCHEDULER-931	state=(1)
SCHEDULER-933	TCP connection accepted
SCHEDULER-934	Compiling Java source: (1)
SCHEDULER-935	(1) orders read from database
SCHEDULER-936	Replacing (1) now
SCHEDULER-937	Removing (1) now
SCHEDULER-938	Order will be processed at (1)
SCHEDULER-939	Replacing order with same id: (1)
SCHEDULER-940	Removing order from job chain
SCHEDULER-941	Removing order from job chain. Order is still being executed by (1)
SCHEDULER-942	add_or_replace_order(): order delayed until (1) has executed (2)
SCHEDULER-943	setback() called (1) times. Setting order to error state
SCHEDULER-944	End state reached - order will be repeated at (2) with state=(1)
SCHEDULER-945	No further job in job chain - order has been carried out
SCHEDULER-946	setback(): order has been set back (1) times, until (2)
SCHEDULER-947	setback(): order has been set back (1) times. This is more than (2) - the maximum for this job
SCHEDULER-948	Process (1) started
SCHEDULER-949	Job will be executed when a process of process class '(1)' becomes available
SCHEDULER-950	Scheduler has been registered
SCHEDULER-951	Daylight saving time has begun
SCHEDULER-952	Daylight saving time has ended, now it's standard time
SCHEDULER-953	Still sleeping (1) seconds ...
SCHEDULER-954	XSLT stylesheet (1)="(2)" returns:
SCHEDULER-955	UDP message from (1): (2)
SCHEDULER-956	Scheduler expects commands from (1) port (2)
SCHEDULER-957	Closing database
SCHEDULER-958	Waiting (1) seconds before reopening the database
SCHEDULER-959	Switching history from database to plain files
SCHEDULER-960	Windows service handler: control=(1) event=(2)
SCHEDULER-961	Protocol starts in (1)
SCHEDULER-962	Protocol ends in (1)
SCHEDULER-963	Copying protocol file to (1)
SCHEDULER-964	New (1) The web service has created a new order and handed it over to the job chain.
SCHEDULER-965	Executing command (1)
SCHEDULER-966	Command answer: (1)
SCHEDULER-967	start_new_file(): protocol file is being closed now
SCHEDULER-968	start_new_file(): intermediate protocol file is: (1)
SCHEDULER-969	Less than min_tasks=(1) are running. New tasks will be started. Reason: (2)
SCHEDULER-970	(1) ended immediately after start, so min_tasks=(2) doesn't lead to new tasks
SCHEDULER-972	Still waiting until (1) ((2)) ...
SCHEDULER-973	Killed task does not stop the job because of ignore_signals="..."
SCHEDULER-974	Last error does not stop the job if the task aborts (after kill or crash) with any signal listed in ignore_signals="". In this case, expect warning SCHEDULER-279
SCHEDULER-975	This file path with ';' will not be included in changed_directory: (1)
SCHEDULER-976	This directory path with ';' will not be included in triggered_files: (1)
SCHEDULER-977	Job is not stopping because of <job stop_on_error="no">. Task error was: (1)
SCHEDULER-978	Job is stopping because of <job stop_on_error="yes">. Task error was: (1)
SCHEDULER-979	Removing file (1)
SCHEDULER-980	Moving file (1) to (2)
SCHEDULER-981	File on blacklist has been removed
SCHEDULER-982	File has been removed, so the file order is being removed too
SCHEDULER-983	New file, (2): Added (1)
SCHEDULER-984	Recovered from previous error in directory (1)
SCHEDULER-985	(1) more file orders will be added later, after previous orders have been processed
SCHEDULER-986	Continuing reading buffered directory (as of (1))
SCHEDULER-987	Starting process: (1)
SCHEDULER-989	(1) cannot be removed now, it will be done later
SCHEDULER-990	Adding (1)
SCHEDULER-991	Order has been suspended
SCHEDULER-992	Order ist not longer suspended, next start (1)
SCHEDULER-994	No heart beat for (2) seconds ((1)), expecting heart beat within (3) seconds
SCHEDULER-995	No heart beat for (2) seconds ((1)), ignored for (3) seconds because of recent database reconnect
SCHEDULER-996	No heart beat for (2) seconds ((1)) - Scheduler seems to be dead
SCHEDULER-997	Making up an extra heart beat
SCHEDULER-999	Scheduler has been terminated properly
SCHEDULER-805	No Scheduler is active
SCHEDULER-806	This Scheduler is active and exclusive now
SCHEDULER-807	Using database product (1)
SCHEDULER-809	Dead scheduler record has been removed
SCHEDULER-811	Executing command read from database: (1)
SCHEDULER-812	Just before processing, order record in database has been occupied or removed
SCHEDULER-813	Order is occupied by Scheduler '(1)'
SCHEDULER-814	Inactive Scheduler '(2)' has the higher backup precedence (1) ((3))
SCHEDULER-815	Task should end but it has just been started with an order attached, so one step will be done
SCHEDULER-816	Unable to release occupation in database
SCHEDULER-817	Missing order record in database
SCHEDULER-819	Scheduler becomes active
SCHEDULER-820	Watching heart beat of that Scheduler
SCHEDULER-821	Scheduler member '(1)' seems to be active, claiming its last heart beat was (2)s ago (pid=(4), (3))
SCHEDULER-822	Scheduler member '(1)' seems to be exclusive, claiming its last heart beat was (2)s ago (pid=(4), (3))
SCHEDULER-823	Dead Scheduler member '(1)' has resurrected
SCHEDULER-825	No exclusive Scheduler is running
SCHEDULER-826	That Scheduler has terminated
SCHEDULER-827	Own heart beat is late: next_heart_beat has been announced for (1) (this is (2) seconds late)
SCHEDULER-829	Releasing occupied order (1):(2)
SCHEDULER-830	Because all Scheduler tasks have been killed, the order in database has not been updated. Only the occupation has been released
SCHEDULER-831	Waiting (1)s for start of non-backup Scheduler
SCHEDULER-832	This is a backup Scheduler, waiting for a non-backup Scheduler
SCHEDULER-833	Watching heart beat of that exclusive Scheduler, standing by to take over operation
SCHEDULER-834	Active Scheduler has terminated properly
SCHEDULER-835	This Scheduler is becoming exclusive now
SCHEDULER-836	Deactivating that dead Scheduler
SCHEDULER-837	Taking exclusiveness from that Scheduler
SCHEDULER-838	(1). heart beat detected
SCHEDULER-839	This order has been replaced
SCHEDULER-841	It has been requested that the exclusive operation will not be continued
SCHEDULER-842	Task is going to process (1), state=(2), on Scheduler (3)
SCHEDULER-843	Task has ended processing of (1), state=(2), on Scheduler (3)
SCHEDULER-844	Scheduler script is not yet active. Operation is executed without the call of function '(1)'
SCHEDULER-845	Task ended without processing the order. The order remains in job's order queue in the same state
SCHEDULER-846	After task exception and due to stop_on_error='no', the order has been moved to error_state='(1)'
SCHEDULER-847	Please use new name '(1)' instead of old '(2)'
SCHEDULER-848	Task pid=(1) started for remote scheduler
SCHEDULER-849	Timeout is not possible for a subprocess running on a remote host (it cannot be killed), pid=(1)
SCHEDULER-850	After lost connection to remote scheduler, process (1) is going to be killed
SCHEDULER-851	After possibly volatile error (number (1)), the statement which caused the error will be repeated: (2)
SCHEDULER-852	Order not found in database
SCHEDULER-853	Order in database could not be updated or deleted.
SCHEDULER-854	Closing lock (1) while held by (2)
SCHEDULER-855	Task is now holding (1) (2)
SCHEDULER-856	(1) has been released
SCHEDULER-857	(1) has been released, (2) non-exclusive holders remaining
SCHEDULER-858	Not longer waiting for lock (1)
SCHEDULER-859	Due to action='next_state' the state '(2)' has been skipped. Next state is '(1)'
SCHEDULER-860	Waiting for '(1)', (2), on place (3) ((4))
SCHEDULER-861	'(1)' has been removed
SCHEDULER-862	Continuing in '(1)'
SCHEDULER-863	Continuing from '(1)'
SCHEDULER-871	Closing process class before (1)
SCHEDULER-872	New '(1)' shares order IDs with (2)
SCHEDULER-873	Job_chains (2) share order IDs because '(1)' has been removed
SCHEDULER-874	Order_id_space has been closed
SCHEDULER-875	Order_id_space has been closed because '(1)' has been removed
SCHEDULER-876	Temporary files cannot be deleted. Still trying ..., (1)
SCHEDULER-877	Temporary files have been deleted now
SCHEDULER-878	Temporary files cannot be deleted: (1)
SCHEDULER-879	Deactivating old cluster member with same ID
SCHEDULER-880	Error when creating database index is ignored
SCHEDULER-881	Error when reading stdout file is ignored: (1), (2)
SCHEDULER-882	Configuration directory '(1)' has been removed:(2)
SCHEDULER-884	Configuration directory has been deleted
SCHEDULER-885	Task ends because '(1)' is being removed
SCHEDULER-886	Lock will be removed later, it is held by '(1)'
SCHEDULER-887	More lock holders than new max_non_exclusive=(1): (2)
SCHEDULER-888	(1) cannot be replaced now, it will be done later
SCHEDULER-889	These filenames yield the same object name: '(1)' and '(2)'. The second is ignored
SCHEDULER-890	(2) is going to be removed because its configuration file '(1)' has been removed
SCHEDULER-891	Configuration file '(1)' ((2)) is going to be be loaded into this new (3)
SCHEDULER-892	This (3) is going to be replaced due to changed configuration file '(1)' ((2))
SCHEDULER-893	(1) is '(2)' now
SCHEDULER-894	'(1)' will be removed later, it is used by (2)
SCHEDULER-895	Configuration directory '(1)' does not exist, it will be ignored
SCHEDULER-897	Error in replacement ignored::(2)
SCHEDULER-898	Folder is going to be removed because its configuration directory has been removed
SCHEDULER-899	Scheduler has no UDP port, so updated configuration files on supervisor will not be noticed
SCHEDULER-701	Replicating '(1)'
SCHEDULER-702	Removing '(1)'
SCHEDULER-703	Local configuration file is ignored, the central configuration file is used instead
SCHEDULER-704	Order has reached its end_state='(1)'
SCHEDULER-705	Substitute '(1)' is valid now
SCHEDULER-706	Standard '(1)' is valid now
SCHEDULER-707	Creating configuration directory '(1)'
SCHEDULER-708	Adding '(1)'
SCHEDULER-709	Killing descendant pid=(1) ((2))
SCHEDULER-710	Delayed command <scheduler_log.log_categories.reset> has been executed
SCHEDULER-711	Step has run for (2)s, which is shorter than the expected duration of (1)
SCHEDULER-712	Step runs longer than the expected duration of (1)

Code	Text
Z-REMOTE-100	Separate process: (1)
Z-REMOTE-101	Separate process: pid=(1): Connection lost
Z-REMOTE-102	Separate process: Unknown proxy id (1)
Z-REMOTE-103	Separate process: Not a registered object: (1)
Z-REMOTE-104	Separate process: Invalid session id (1)
Z-REMOTE-105	Separate process: Unknown session command, failure in communication
Z-REMOTE-106	Separate process: Unknown session class, failure in communication
Z-REMOTE-107	Separate process pid=(1): Invalid response
Z-REMOTE-108	Separate process: Variant type (1) is not transmittable
Z-REMOTE-109	Separate process: Failure in communication (message is too short)
Z-REMOTE-111	Separate process: Thread (1) tries to use connection owned by thread (2)
Z-REMOTE-112	Separate process: Program did not fetch operation's result: (1)
Z-REMOTE-113	Separate process: pop_operation with different method "(2)" ("(1)" expected) or different object
Z-REMOTE-114	Separate process: Program did not fetch result of an finished operation, method=(1)
Z-REMOTE-115	Separate process pid=(1): Message length (2) too big or invalid
Z-REMOTE-118	Separate process pid=(1): No response from new process within (2)s
Z-REMOTE-119	Separate process: Two operations on the same connection. First: (1), second: (2)
Z-REMOTE-120	Separate process: Unknown object id (1)
Z-REMOTE-121	Separate process: pop_operation() on empty stack, method=(1)
Z-REMOTE-122	Separate process pid=(1): Caller has killed process
Z-REMOTE-123	Separate process pid=(1): Process lost
Z-REMOTE-124	Separate process: Named arguments not implemented
Z-REMOTE-125	Separate process: DISPID (1) unknown
Z-REMOTE-126	Separate process: Default proxy for (1) has no properties
Z-REMOTE-127	Separate process: More data as announced received. Failure in communication
Z-REMOTE-128	Separate process: v.vt is not the value of SafeArrayGetVartype()
Z-REMOTE-129	Separate process: Blocking invocation on asynchronous connection rejected. Object=(1), dispid=(2)

Code	Text
Z-CHARSET-001	Unknown character encoding: (1)
Z-CHARSET-002	Missing character encoding