Server Deactivation
The Adonix software includes a batch server allowing the execution of tasks (including printing) and task groups in a differed fashion. These tasks can be launched directly or as recurring activities.
This batch server is implemented via the intermediary of a SERVX3 application, in which is located a process which periodically scrutinises a table of requests which is found in the supervisor folder. When the tasks must be released, they are launched under the form of a separate Adonix process in the launch folder.
The batch server process is responsible for the launch and stopping of a task, and the control of the number of tasks simultaneously active by limiting their number.
This function is used to stop the batch server if it is already active. This stop is not immediate because the server "wakes up" periodically to examine pending tasks, and it is only at this time that it will stop. The following message is displayed when the function has been executed :
| Stop command sent to the server |
The request management function is used to identify, at all times, the status of the request server, which can have the following statuses.
active (the process number is displayed)
in the process of stopping (intermediate period, when the order to stop has been given, but the server has not yet stopped).
inactive
Prerequisite
Refer to documentation Implementation
Other conditions
Submission of requests via files.
Defined by the EXTBATCH parameter, which authorises by user, the mode of functioning of the batch server following on from the process described in detail in a dedicated technical annex.
General functioning of the batch server
In addition, it is advisable to read the technical documentation explaining the general functioning of the batch server in order to understand the incidences of the different parameterisations.