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

See also 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

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.

Grid 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.
Folder (field DOSSIER)

It defines the folder in which the task execution has been requested.

Task code (field TACHE)

Code identifying the launched task
Language (field LAN)
Usr (field USER)

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

Server (field SERVER)
Port (field PORT)
Session ID (field SESSIONID)
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.
Group (field GRP)

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)
Series (field SEQGRP)
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.

Block number 2

field PAGCUR

Ir displays the number of the current page, along with the total number of pages.
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.

 
Restart recur. task

Click Restart recur. task from the Actions icon to restart this task as a recurring task.

Specific Buttons

Delete

Click the Delete action to delete the current task.

 This action is only available for tasks pending execution. Use the Stop action if the task is in progress; use the Purge