This function is used to view the different Adonix tasks in process on the server. By default, the current process server tasks are displayed, but any server accessible via the network that has a software connection process with the same service number can be accessed.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

This function is presented as a single screen without a left list.

Entry screen

Presentation

On entering this function, the connection characteristics for the default server are displayed. If the user wants to view the connections on another server, it is necessary to give its name. It will be possible to view it provided the service number is the same as the remote server.

In this screen, three data sections are displayed:

  • the first one, called Open Sessions, gives the list of connections with the server in a grid;
  • the second one, called Active processes,  is used to list the processes related to a session (i.e. the session defined by the current line on which the cursor is set in the first section);
  • the last one, called Total sessions, gives cumulated information.

Close

 

Fields

The following fields are present on this tab :

Block number 1

  • Machine (field SERVEUR)

Define the process server on which the processes are viewed. By default, the server that is proposed when starting the function is the current application server.

  • License (field LICENCE)

Define the license number assigned by Sage for the installation. This license number is unique. It is associated with a group of authorizations (umber of sessions, options...) as well as two series of texts identifying the user client for the license and the partner that has implemented the solution.

A dedicated function to view all this information.

  • Total sessions (field NBTOTSES)

 

  • CPU time (field CPUFLG)

 

Grid Open sessions

  • Client (field CLIENT)

Define the network name of the workstation used to establish the connection for the session. It should be noted that this network name can be :

  • either the client workstation that is connected to the client-server.
  • or the Web server that makes the connection between the Web browser and the server.
  • or the key-word BATCH, in he case where the process is a batch task and has no associated client.
  • or the Web server on which the terminal or Web server operates.
  • Type (field TYP)

Defines the connection type of the current session It corresponds to one of the choices defined in local menu 924.

  • Web client (field IPCLI)

 

  • Login (field USER)

Defines the user code (in the software sense) under which the session has been opened.

Define the folder in which the current session is executed.

  • Module (field MODULE)

Define the module to which the function that is being executed is attached. The list of modules vary according to the software. It corresponds to local menu number 14.

  • Function (field FONCTION)

Define the code for the function executed by the connected user. This code corresponds to the value of the GFONCTION variable on the workstation itself.

If the user is connected without being in this function (if they are positioned in a menu), this field is empty.

It should be noted that the batch server itself is present as a task called SERVEUR, functioning in BATCH mode on the folder where the name depends on the software, but which start in principle with the letters "SERV".

  • System login (field LOGIN)

Define the user code (in the system login sense) in which the connected user is known.

  • Service (field PORT)

Define the connection service number (characteristic of the adxd task to which the workstation is attached at the connection request).

  • Date (field DATCON)

Define the date and time of the start of the connection to the workstation.

  • UTC time (field HRECON)

 

  • Date + UTC time (field DATTIME)

 

  • CPU (field CPU)

Display the CPU time used by the adonix process from its startup. This time is expressed in minutes:seconds

  • Session ID (field ID)

The Ident1 and Ident2 fields are unique identifiers managed by the Adonix engine for the user connection. The first is unique for a given folder, it corresponds to the result of the evaluation of the adxuid(1) function and is used in the APLLCK file (this is the LCKPID field). The second is unique for a given server and service number, it corresponds with the result of the evaluation of the adxuid(2) function.

  • Type (field NATURE)

 

Grid Active processes

  • Process no. (field NUMERO)

For each process associated with the current line session in the upper grid, a unique process number is found here linked to the server on which this process is executed (it is aprocess idoperating system sense, whether UNIX, Linux or Windows).

  • Processes (field PROCESS)

Defines the name of the processes being executed on the process server corresponding to the current session in the upper grid. Amongst the names frequently present on line are the following :

  • adonix, which corresponds to the execution engine for the processes.
  • sadora, which corresponds to the pilot for the Oracle database session.
  • sadora, which corresponds to the pilot for the SQL database session.
  • sadfsq, which corresponds to the process that manages the access to the sequential files.
  • sadsys, which corresponds to the process executing the system commands on the server.
  • Machine (field MACHINE)

Identify the computers on which each process operates associated with the current session in the upper grid. It can be one of the network servers (notably the process server, the application server, but also the client workstation, in the case for example when writing on the local workstation : a sadfsq process is then open on the workstation).

Grid Total sessions

  • Session type (field TYPSES)

 

  • Type (field TYPINTSES)

 

  • Total (field TOTSES)

 

Close

 

Action icon

Process Stop

This function is used to stop the corresponding process (via the kill function on UNIX, and killadx function on NT). From the point of view of the database, the stopping of a process not only signifies the actual stopping of the transaction in process but also the loss of data in the process of being entered. It is therefore important to be very careful with the use of this function, which is reserved for the resolution of operational incidents.

In fact, the rights of the user to carryout this type of function depend on the characteristics of the user connection. If a user wants to stop tasks that they have not themselves launched, they must be connected as a super-user (root in the case of UNIX).

 

Close

 

Menu Bar

This button, also accessible using the short cut, is used to refresh the display of the open sessions.

This button is used to search the session using a processes where number is entered. If this process can be attached to a session, the user is positioned on the line in question at the end of the search.

Menu Bar

Sort / Folder

This function is used to sort the lines in the order of the folders.

Sort / Client

This function is used to sort the lines by order of client workstation.

Sort / Login

This function is used to sort the lines in order of the connection code.

Sort / System Login

This function is used to sort the lines in order of the connection code in the system sense.

Sort / Date

This function is used to sort the lines in order of the date.

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

xxxx: server not accessible

This message signifies either that the server whose name is given does not exist or that it is not connected to the network or that no adxd connection service is pending for the current service number. Warning, this message can be displayed after a long wait time (the time that the wait times give to the network functions needs to elapse).

Tables used

SEEREFERTTO Refer to documentation Implementation