Query management
Use this function to list and track the tasks (requests) sent to the batch server, either from a request submission or request files placed in a dedicated directory.
You can use it to relaunch and stop tasks, and for starting recurring batch tasks.
You can check the status of the batch server. Each task executed by the batch server is assigned an individual process ID.
Prerequisite
Refer to documentation Implementation
Screen management
The Query management function displays the list of tasks submitted to the server (released or not released) and their statuses.
Entry screen
Presentation
Each line in the Query results grid (table) is a task submitted to the batch server (released or not released). Each task has a status and is displayed using a color. The color reflects the status of the task. The standard colors are as follows:
- Green. Task currently being executed.
- Black. Task finished without error.
- Red. Task interrupted or terminated with errors.
- Blue. Task pending execution.
Close
Fields
The following fields are present on this tab :
Grid Queries
| This single number identifies the request. It is assigned starting from an initial number defined in the parameters of the batch server. |
| It defines the folder in which the task execution has been requested. |
| Code identifying the launched task |
|
|
| It defines the code of the user who launched the task. |
| It defines the planned start date and time for the task |
|
|
| If this field is set to Yes, the task can only be executed in the single user mode for the folder. |
| This status flag of the requests in process can take the values defined by the local menu 21 : Standby : the request has not yet been started
|
| It defines the end date and time for the execution of the task. This information is entered only if the task has already been launched and it is completed. |
|
|
| This field, that is defined by the local menu 20, specifies whether the task launched is an adonix process or a script (shellscript or command file) executed on the process server. |
| It defines the code of the process or the script, when the launched task does not correspond to a basic software function. |
|
|
|
|
|
|
| Each request is executed by an adonix process given on the application server. This field identifies the process number (usually called process id, or pid). |
| When this field is not null, it defines a timeout duration, that is to say, a time limit above which the task is automatically stopped if it is still running. |
| When the task belongs to a launched group of tasks, the grid mentions a number common to all the tasks of the group, and a sequence number in the group (these fields are empty if the request does not belong to a group). |
|
|
|
|
| When the batch task is launched at a specified frequency every N minutes, this column defines the value of N. |
| When a task has been subscribed to be executed with a frequency, a single line appears to notify its execution, but each time that it is relaunched, 1 is added to this column. Thus, it is possible to know how many times it has been executed. |
| When the task has been launched via a job file (see the corresponding technical appendix), the name of the file that has been submitted (without the extension) can be found here. |
Block number 2
| Ir displays the number of the current page, along with the total number of pages. |
Close
Action icon
Parameter entry
Click Parameter entry from the Actions icon to change the request parameters (whether pending launch or already finished) for this task.
Interruption
Click Interruption from the Actions icon to interrupt the execution of this task. You will be prompted to confirm your reason for interrupting this task.
Modification
Click Modification from the Actions icon to modify prior to launch, the date and time of launch, and the execution priority of this task.
Log
Click Log from the Actions icon to display the trace file for this executed task. The trace file is prefixed 'RQT' followed by the request number. It can be found in the TRA directory of the SERVX3 directory (which is located in the Runtime directory).
Relaunch query
Click Relaunch query from the Actions icon to create a new task with the same launch parameters as this (original) task.
By default, execution of the new task is requested for the same day, a few minutes after selecting this action. Use the Modification action to modify the date/time of launch of the new task.
The original task must have been launched in the current folder. It could have been launched by a different user but its relaunch will be performed on the current user's account, after verifying the user's access rights.
Restart recur. task
Click Restart recur. task from the Actions icon to restart this task as a recurring task.
Close
Specific Buttons
The following fields are included on the window opened through this button : Block number 1
Block number 2
Block number 3
Block number 4
Close Click the Query action to submit a new task request. |
Click the Update action to refresh the task list and corresponding statuses. Alternatively, use the Refresh (F5) key. |
Click the Purge action to purge the table lines. All requests completed on a given date (as defined in a separate window) are deleted from the task list. |
Click the Information action to display the current Batch server details. |
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
The request is no longer waiting to be executed
Cancellation impossible.
This message is displayed when an attempt is made to delete a task that has been executed.
No request in progress
The request to execute, or the executed request table, is empty. This might occur after a purge or if the batch server has not been started.
Full grid
There are more lines than the Query manager can display in the table. Only the first n lines are visible.
This task should be activated from the XXXX folder.
An attempt has been made to launch a task in a folder other than the current folder.
The server status is displayed (Abled/Disabled), as well as the number of the corresponding process, if it is abled. The submission of tasks is not stopped if the server is not abled (however, they are not executed immediately even if the trigger time has arrived).