Query management
Use this function to list and track the tasks (requests) sent to the batch server, either from a request submission, request files placed in a dedicated directory, or recurring tasks.
You can use it to relaunch and stop tasks, to start recurring batch tasks, and for executing a group of tasks.
You can check the status of the batch server. Each task executed by the batch server is assigned an individual process ID.
Since 2025 R1/V12.0.37, this function was enhanced to include further searching, sorting, and filtering capabilities. The action Classic function allows you to access the classic AREQUETE function representation.
Prerequisite
Refer to the implementation documentation.
Screen management
The query management function displays the list of tasks submitted to the server (released or not released) and their statuses.
Entry screen
Each line in the Query results grid (table) is a task submitted to the batch server (released or not released).
Field descriptions
Queries grid
|
Number (field NUMREQ) |
|
This number identifies this task (request). It is a sequential number assigned automatically from an initial number defined in the batch server parameters. |
|
Folder (field DOSSIER) |
|
This field defines the folder in which execution of this task was requested. |
|
Task code (field TACHE) |
|
This code identifies the launched task. |
| Description (field ZDES) |
|
Language (field LAN) |
|
Defines the language in which this task is expressed. |
|
User (field USER) |
|
This field defines the code of the user who launched this task. |
|
Start date (field DAT) |
|
This field defines the planned start date for this task. |
|
Single (field MONO) |
|
This field is set to 'Yes' or 'No'. If set to 'Yes', this task can only be executed in single user mode for the folder. |
|
Status (field FLAG) |
|
This field displays the current status of the task in process. The values are defined in Local menu 21 - Query progress status, as follows:
|
|
End date (field DFIN) |
|
This field defines the date of execution of this task. This field is only displayed if this task has been launched and execution is complete. |
|
Task type (field TYPTAC) |
|
This field is defined by Local menu 20 - Batch Task Type. It defines whether this task has been launched as a process or a script (shellscript or command file) executed on the batch server. |
|
Script (field ETAT) |
|
This field displays the code of a process or a script if this (launched) task does not correspond to a basic function. |
|
Session ID (field SESSIONID) |
|
This field displays the unique number assigned by the server to the task. |
|
Execution tag (field RTTAG) |
|
Time-out (field TIMOUT) |
|
This field, if populated, defines a timeout duration. A timeout duration is the time limit defined for when this task will be stopped automatically if it is still running. |
|
Group (field GRP) |
|
This field is populated if this task belongs to a (launched) group of tasks. The code, if displayed, is common to all the tasks in the group. |
|
Order no. (field NUMGRP) |
|
This field is populated if this task belongs to a (launched) group of tasks. The number, if displayed, is common to all the tasks in the group. |
|
Sequence (field SEQGRP) |
|
This field is populated if this task belongs to a (launched) group of tasks. The number, if displayed, represents the sequence number of this task in the group. |
|
Frequency (min) field FRQ) |
|
When the batch task is launched at a specified frequency every N minutes, this column defines the value of N. |
|
Reminder (field IMPETX) |
|
This field is populated if this task has been subscribed to be executed with a frequency. Each time this task is relaunched this column is incremented by 1. The number displayed represents the number of times this task has been executed. |
|
Batch file (field JOB) |
|
This field is populated if this task has been launched using a job file (see the corresponding technical appendix). It displays the name of the submitted file (without the extension). |
| Subgroup (field GRPCHILD) |
| This field, if populated, contains the code of the subgroup the task belongs to. |
| Sub-sequence (field SEQGRPCHILD) |
| This field, if populated, contains the sub-sequence of a task belonging to a subgroup. |
| Run after (field RUNAFTERGRP) |
| This field contains the Run after field of a task belonging to a subgroup. |
| Task/Group code (field RUNAFTERVGRP) |
| This field contains the Task/Group code related to the Run after field. |
| Error condition (field ERRCNDGRP) |
| This field contains the Error condition field of a task belonging to a subgroup. |
| Task/Group code (field ERRCNDVGRP) |
| This field contains the Task/Group code related to the Error condition field. |
| Run after (mn) (field RUNAFTTIMGRP) |
| This field contains the Run after (mn) field of a task belonging to a sub group. |
| Parent run after (RUNAFTERPAR) |
| This field contains the Run after field of the parent group code of the task. |
| Parent task/group code (RUNAFTERVPAR) |
| This field contains the Task/Group code related to the Parent run after field. |
| Parent error condition (ERRCNDPAR) |
| This field contains the Error condition of the parent group code of the task. |
| Parent task/group code (ERRCNDVPAR) |
| This field contains the Task/Group code related to the Parent error condition fie. |
| Parent run after (mn) (RUNAFTTIMPAR) |
| This field contains the Run after (mn) field of the parent group code of the task. |
Block number 2
|
field PAGCUR |
|
This field displays the number of the current page, along with the total number of pages. |
| Delete |
| Click Delete from the Actions icon to delete a record if its status is set as Standby or Held. If the record is a group, check the status of the first query in the group before deleting it. |
| Display |
| Click Display from the Actions icon to display the record's entire information in a new window. |
|
Parameter entry |
|
Click Parameter entry from the Actions icon to change the request parameters (whether pending launch or already finished) for this task. |
|
Log |
|
Click Log from the Actions icon to display the trace file for the 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). |
|
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. Modifications are only permitted if the task is set as Standby. |
|
Interrupt |
|
Click Interrupt from the Actions icon to interrupt the execution of this task. You will be prompted to confirm your reason for interrupting the task. |
|
Relaunch query |
|
Click Relaunch query from the Actions icon to create a new task with the same launch parameters as the 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. Note: 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 right |
| Relaunch group |
|
Click Relaunch group from the Actions icon to create a new group with the same launch parameters as the original group. 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. Note: The original task must not include any inactive tasks or group for its relaunch to be performed. |
|
Restart recur. task |
|
Click Restart recur. task from the Actions icon to restart this task as a recurring task. |
Specific Buttons
| Classic function | Click the Classic function action to access the old AREQUETE display. |
|
Query |
Click the Query action to submit a new task request. |
|
Log |
Click the Log action to display the general trace file for the server (start time, request launch, end of request). The trace file is called server.tra. It can be found in the TRA directory of the SERVX3 directory (which is located in the runtime directory). |
|
Purge |
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. |
|
Information |
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 (Enabled/Disabled), as well as the number of the corresponding process, if it is enabled. The submission of tasks is not stopped if the server is not enabled (however, they are not executed immediately even if the trigger time has arrived).
Tables used
Refer to the implementation documentation.