Usage > Batch server > Query management 

This function is used to list and track the requests sent to the batch server, either by means of the request submission or by placing the request files in a dedicated directory.


SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen


The request management function is used to display, in a single screen, the list of requests submitted to the server (released or not released) and their statuses.

According to the request status, the line appears in black (request finished without error), in red (request interrupted or terminated with errors), in green (request being executed) or in blue (request pending execution).




The following fields are present on this tab :

Table Queries

  • Number (field NUMREQ)

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.

  • Date (field DAT)

It defines the planned start date and time for the task

  • Time (field HEURE)


  • Prio (field PRIO)

It defines the launch priority (at system level) of the process launched to execute the task.

  • Single (field MONO)

If this field is set to Yes, the task can only be executed in the single user mode for the folder.

  • Status (field FLAG)

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

  • In progress : the request is in the process of being executed
  • Finished : the request has finished without errors.
  • Aborted : the request was interrupted
  • Error : the task has terminated on an error.
  • Held : the request is part of a group in the process of execution or it is blocked manually by an interruption.
  • Kill : A user has requested the termination of the request.
  • Immediate the task has been submitted for immediate processing (via the intermediary of a file)
  • Warning : the task ended on a non-blocking error code (GERRBATCH variable<100).
  • End time (field HFIN)

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.

  • End date (field DFIN)


  • Task type (field TYPTAC)

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.

  • Script (field ETAT)

It defines the code of the process or the script, when the launched task does not correspond to a basic software function.

  • Process no. (field PROCESS)

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).

  • Time-out (field TIMOUT)

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.

  • Service (field SERVICE)

It defines the service number used for connection to adonix. When it is not specified, the current service number is used.

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).

  • Order no. (field NUMGRP)


  • 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)

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.

  • Batch file (field JOB)

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.


  • Status (field ACTIF)

This flag, whose values are defined by the local menu 8, is used to know the status of the batch server, and it can take the following values :

  • Active : the batch server is being executed
  • Inactive : the batch server is bot being executed
  • In the process of being started : the start of the batch server has been requested, but it still is in an initialization phase and it does not process the requests yet.
  • In the process of being stopped : the termination of the batch server has been requested, but it is not effective yet.
  • Process no. (field PID)

It identifies the process number of the batch server itself (usually called process id or pid).

  • field PAGCUR

Ir displays the number of the current page, along with the total number of pages.



Functions accessed by right click on the grid

Parameter Entry

it is used to modify the request parameters (whether pending launch or already finished).


it is used to request that the batch server interrupts the execution of a task.


it is used to modify the date and time of launch and the execution priority for a request that has not already been launched.


it is used to display the trace file of the execution of a request already executed (it is found in the TRA directory of the SERVX3 directory, itself located in the Runtime directory, and its name is RQT followed by the request number).


it is used to create a new task, with the same launch parameters as the previous task. By default, the execution is requested for the same day, in 5 minutes (which leaves enough time to modify the date/time of launch thanks to the Modification action). The task to be re-launched must have been launched in the current folder. It could have been launched by another user, but its re-launch will be performed on the current user's account, after verifying the user's access rights.

Relaunch group
Restart recur. task




Specific Buttons

This button is used to delete the request upon which the cursor is positioned. This can only be carried out for requests pending execution : if the they are in progress, the stop function is used and if they are already finished, the purge function is used.

The following fields are present on the window opened through this button :

Block number 1

It defines the code for the folder in which the request must be launched.

It defines the code (and any password) of the user who has launched the request.

  • Password (field PASSE)


Block number 2

It defines a group of tasks to be launched.

  • field ZGRP


It defines the code of the task that will be launched automatically by the batch server.

  • field ZTACHE


  • Date (field DAT)

It defines the triggering day and time required for the request.

  • Time (field HEURE)


  • Template (field JOBMOD)

If thIS field is checked, a file containing the entered parameters for the request will be generated in the template file directory (batch server parameters) and the request will not be submitted to the server. The name of this file is composed of the task code followed by .mod. The file serves as a template for the creation of the .job files that permit the creation of the batch requests.


it allows the submission of a new request.

it is used to refresh the request list and their corresponding statuses. This function is also available via the shortcut key

it is used to display the general trace file for the server (start time, request launching, end of requests....). This file is called server.tra, and it can be found in the TRA directory of the SERVX3 directory, itself located in the Runtime directory.

it triggers the purging of the table lines. The requests completed on a given date (entered in a window which opens then) are deleted from the task list.

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 request where the execution has already taken place.

No request in progress

The request to execute or executed request table is empty (this may occur after a purge, or if the batch server has not been started).

Full grid

There are more lines than the request manager can display in the table : only the first 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.

At the bottom of the screen, the server status appears (Abled/Disabled), as well as the number of the corresponding process, if it is abled. The fact that the server is not abled does not stop the submission of requests (however, they are not executed immediately even if the trigger time has arrived).

Tables used

SEEREFERTTO Refer to documentation Implementation