Monitoring Open Sessions and Processes

Use Users (PSADX) under Verifications > System monitor in the Development > Utilities > block to view the different processes being performed by users on the server and the open sessions. By default, the processes for the current process server are displayed, but any server accessible through the network that has a software connection process with the same service number can be accessed.

• When first launching this utility, the connection information for the default server is displayed.

• Use the Machine field to define the process server on which the processes are viewed.

• The License field displays the license number assigned by Sage for the installation.

• The Function column displays the function code executed by the connected user. This code corresponds to the GFONCTION variable on the workstation.

Open sessions

This section displays the information for the processes, such as the following.

• The identification of the connection in terms of the operating system. This identificationis defined by the following:

• Login

• Service connection number

• IP address

• The name of the client is either the network name of the client workstation to which the task is attached, the ADAPI, or BATCH (batch task).

• The folder, the login for the software, the module, and the function identifies both the connection folder and the user code (AUTILIS table), in addition to the function that is currently being executed (AFONCTION table) and the corresponding module. The batch server is present as a task called SERVEUR, functioning in the SERVX3 folder.

• The ID1 and ID2 fields are unique identifiers managed by the Sage X3 engine for the user connection.

• ID1 is unique for a given folder and corresponds to the result of the evaluation of the adxuid(1) function and is used in the APLLCK file (this is the LCKPID field).

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

Active processes

When you select a specific line in the Open sessions section, the Active processes section displays the active processes.

• These processes are called sadora, sadoss, or sadubd (access the database according to the Oracle or SQL Server database), adonix (process execution), sadfsq (access to the application objects), or sadsys (system order execution).

• In addition to the process number (UNIX or NT according to the case), the server name on which the process is running also displays. This can be the server or a thirdparty machine, if for example, there are tables open in another folder on another machine.

• Clicking the Actions icon for a specific line allows you to terminate a process (kill under UNIX or killadx under NT).

• The stopping of a process in the database not only signifies the actual stopping of the transaction in process, but also the loss of data that is in the process of being entered.

• You should use caution when using this function, which is reserved for the resolution of operational incidents.

• The rights of the user carrying out this type of function depends on the user connection. If a user wants to stop tasks that have not launched, they must be connected as a super user (root for UNIX).

Total sessions

This section displays the number of active sessions by session types along with a general total. In addition, after each session type, the total number of authorized connections display in parentheses.



-

Sage X3 and Sage Software are trademarks of Sage Software, Inc. Microsoft SQL Server, Microsoft SQL Enterprise Manager and SQL Server Management Studio are registered trademarks of Microsoft Corporation. Oracle is is a registered trademark or Oracle Corporation. All other product names used here are trademarks or registered trademarks of their respective owners.

-