User monitor

You can use this function to view the different Adonix tasks in progress on the server. The current process server tasks are displayed by default, but any server accessible via the network that has a software connection process with the same service number can be accessed.

Prerequisites

SEEREFERTTO Refer to the implementation documentation.

Screen management

This function displays as a single screen without a left list.

Entry screen

This function displays the connection characteristics for the default server. If you want to view the connections on another server, it is necessary to give its name. It is possible to view it if the service number is the same as the remote server.

The three following sections are on this screen.

Open sessions

This first section contains a grid named Open sessions which displays the characteristics of the Adonix tasks in progress:

  • The identification of the connection in terms of the operating system. Four elements define this identification:
    • The login
    • The service connection number (characteristic of the adxd task to which the workstation is attached for the connection request)
    • The IP address for the connection
    • The name of the client workstation. It is either:
      • The network name of the client workstation to which the task is attached
      • The ADAPI (connection to an Adonix API, for example, via ADONIX XTEND™)
      • BATCH (batch task)
      If the connection is via a web server (it is the case when using a web client), the web server's name displays here.
  • The folder, login for the software, module, and function: This information identifies the context of the session itself. You can see both the connection folder and the user code (AUTILIS table), plus the function currently being executed (AFONCTION table) and the corresponding module. If the user is in a menu rather than a function, the function code is empty.
    The batch server itself is present as a task called SERVEUR, functioning in the folder SERVX3.
  • The date and time of the connection start
  • 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 with the result of the evaluation of the adxuid(1) function. The APLLCK file (this is the LCKPID field) also uses it.
    The second is unique for a given server and service number. It corresponds with the result of the evaluation of the adxuid(2) function.
  • The connection type:
    • Batch
    • Primary
    • Secondary
    • ADAPI

Active processes

The grid present in the second section displays, when the user selects a specific line in the upper grid (Open sessions), the active processes managed for the session. These processes are:

  • sadora: access the database according to the Oracle database
  • sadoss: access the database according to the SQLServer database
  • sadudb: access the database according to the DB2 UDB database

These processes can have the following types:

  • adonix: process execution
  • sadfsq: access to the application objects
  • sadsys: system order execution

In addition to the process number (UNIX or NT depending on the case), the server name on which the process is running is also visible.
It can be:

  • The client
  • The server
  • A third-party machine if there are tables open in another folder on another machine

By right-click, there is access from each table row, to the Process stop function. You can use this function to stop the corresponding process (by kill under UNIX or using the killadx function under NT). From a database angle, stopping a process involves the actual stopping of the transaction in progress but also losing data in the process of being entered. Be very careful when using this function. Use it for the resolution of operational incidents. The user's rights to carry out this type of function depend on the characteristics of the user connection. If users want to stop tasks that they have not launched themselves, they must connect as a super user (root in the case of UNIX).

Total sessions

This section displays the number of active sessions by session types (primary, secondary, batch, ADAPI) with a global total. In addition, after each session type, the total number of connections authorized by type is displayed.

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)

This field defines the license number assigned by Sage for the installation. This license number is unique. It is associated with:

  • A group of authorizations (number of sessions, options, etc.)
  • Two series of texts identifying:
    • The user client for the license
    • The partner that has implemented the solution

The license display function allows you to view all this information.

Total sessions (field NBTOTSES)

This field indicates the number of open sessions.

CPU time (field CPUFLG)

Select this check box to display the CPU time used by the Adonix process in the Open sessions grid.

Open sessions grid

Client (field CLIENT)

This field defines the network name of the workstation used to establish the connection for the session. This network name can be:

  • The client workstation connected to the client-server
  • The web server that makes the connection between the web browser and the server
  • The BATCH keyword, in the case where the process is a batch task and has no associated client
  • The web server on which the terminal or web server operates

Type (field TYP)

This field defines the connection type:

  • Batch
  • Primary
  • Secondary
  • ADAPI

Web client (field IPCLI)

This field displays the IP address of the web client.

Login (field USER)

This field defines the user code (in the software sense) under which the session has been opened.

Folder (field DOSSIER)

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 with the result of the evaluation of the adxuid(1) function. The APLLCK file (this is the LCKPID field) also uses it.

The second is unique for a given server and service number. It corresponds with the result of the evaluation of the adxuid(2) function.

Module (field MODULE)

This field defines the module to which the function that is being executed is attached. The list of modules varies according to the software. It corresponds to the local menu number 14.

Function (field FONCTION)

This field defines 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 (for example, he is in a menu), this field is empty.

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 starts in principle with the letters SERV.

System login (field LOGIN)

This field defines the user code (in the system login sense) in which the connected user is known.

Service (field PORT)

This field defines the connection service number. It is the characteristic of the adxd task to which the workstation is attached at the connection request.

Date (field DATCON)

This field defines the date of the start of the connection to the workstation.

UTC time (field HRECON)

This field defines the time of the start of the connection to the workstation.

Date + UTC time (field DATTIME)

This field defines the date and time of the start of the connection to the workstation. This timestamp is in the UTC format.

CPU (field CPU)

This field displays the CPU time used by the Adonix process from its startup. This time is expressed in minutes:seconds.

You need to select the CPU check box in the header of the table.

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 with the result of the evaluation of the adxuid(1) function. The APLLCK file (this is the LCKPID field) also uses it.

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)

This field defines the nature of the connection of the current session. It can be internal or external.

Active processes grid

Process no. (field NUMERO)

For each process associated with the current line session in the upper grid, a unique process number displays here. This number is linked to the server on which this process is executed. It is a process id in the operating system sense, whether UNIX, Linux, or Windows.

Processes (field PROCESS)

This field defines the name of the processes executed on the process server corresponding to the current session in the upper grid. You can find the following information:

  • adonix, which corresponds to the execution engine for the processes
  • sadora, which corresponds to the pilot for the Oracle database session
  • sadoss, which corresponds to the pilot for the SQL database session
  • sadudb, which corresponds to the pilot for the  DB2 UDB 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)

This field identifies the computers on which each process operates associated with the current session in the upper grid.

It can be one of the network servers. It is often the process server or the application server.

It can also be the client workstation. For example, when writing on the local workstation, a sadfsq process is then open.

Total sessions grid

Session type (field TYPSES)

This section displays the number of active sessions by session types (primary, secondary, batch, ADAPI) with a global total. In addition, after each session type, the total number of connections authorized by type is displayed.

Type (field TYPINTSES)

Total (field TOTSES)

Process stop

By right-click, there is access from each table row, to the Process stop function. You can use this function to stop the corresponding process (by kill under UNIX or using the killadx function under NT). From a database angle, stopping a process involves the actual stopping of the transaction in progress but also losing data in the process of being entered.

Be very careful when using this function. Use it for the resolution of operational incidents. The user's rights to carry out this type of function depend on the characteristics of the user connection. If users want to stop tasks that they have not launched themselves, they must connect as a super user (root in the case of UNIX).

Specific buttons

  • This button, also accessible using the F5 key, is used to refresh the display of the open sessions.

  • Click this button to search the session using a process where a 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.

  • Click this button to delete any inactive sessions from the open sessions grid. A session is inactive when it is no longer connected to the database.

Sort / Folder

This function is used to sort the lines by folder.

Sort / Client

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

Sort / Login

This function is used to sort the lines by connection code.

Sort / System login

This function is used to sort the lines by system connection code.

Sort / Date

This function is used to sort the lines by date.

Error messages

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

xxxx: Server not accessible.

This message can mean that:

  • The server whose name is given does not exist
  • The server is not connected to the network
  • No adxd connection service is pending for the current service number.

This message can display after a long wait time.

Tables used

SEEREFERTTO Refer to the implementation documentation.