AVEVA Global User Guide
Monitoring Command Progress : Viewing Command Transactions
Viewing Command Transactions
The Command Transactions window can be used to view a list of the current transactions for the Global commands that have been issued.
This window can be launched from the MODEL, DRAW or ADMIN modules via the menu bar Utilities > Transactions.
When viewing this window in the Admin module an additional tab will be available “Purge/Merge transaction DB” for more information refer to Merging and Purging from ADMIN, this tab will not appear when viewing this window from Design.
Note:
The Global Scheduler takes time to initiate the call to the Global Daemon, before the issued command appears in the scrollable list. Refer to Global Scheduler for further information.
The Command Transactions scrollable list displays the Issue Date, Status, and other information about each Command issued. This combination of details for a command is known as a command transaction. As a command progresses, the information displayed in the Command Transactions list is updated. If required, the user can view details of all the transaction messages for a specific command, as explained in Viewing Transaction Messages.
The user can use the Filters on the left hand side of the window to control exactly which transactions are displayed in the Commands Transactions list. An Administrator can choose some additional values for filters that are not available to general users.
Click Initialise Filters if you want to reset all filters to their default state.
You can use the following filters:
•
Use User to specify which user’s commands will be displayed. General users can only view their own commands. An Administrator can view commands for All Users, and also commands from the ‘users’ Local Daemon, Remote Daemon and Timed Updates. For example, by selecting Remote Daemon, the Administrator can view the remote commands passing through the location.
•
Use Module to display commands issued from that module only.
•
Use Command to specify which type of commands will be displayed. The default is All commands. The option list contains the most commonly used Global commands. If you want to display a different Global command, set this option to All commands and use the Text filter to make sure that only the required commands are displayed.
The display can be filtered so that only Local commands are listed. Local commands are defined as those commands that take place entirely locally, For example, an Extract claim made when an owning extract database is at the same location.
The display can also be filtered so that only Satellite commands are listed. Satellite commands are defined as those commands that take place via the Global daemon (i.e. not locally), For example, an Extract claim made when an owning extract database is NOT at the same location.
It is possible to switch local command recording on or off. Refer to Transaction Audit Trail in Running Global Projects. for further information
•
Use Status to specify which status the displayed commands should have. For example, you may decide to display Waiting commands only. The default is All status. See below for descriptions of the different statuses.
•
Use Pass/Fail to set the list of commands to display only those commands that passed (were successful), or only those that failed, or all commands regardless of whether they passed or failed. A "1" in the Passed column of the commands list indicates that the command has completed successfully. A "0" indicates that it has not.
Switch on Display flagged commands only to filter the commands so that you view flagged commands only. You can flag certain commands with your own text, to make it easier for you to follow them up.
Checkmark the Text checkbox if you want to filter the commands based on specific text appearing within them. Enter the required text in the text box. For example, you might enter /PIPE7.
•
Use Start Date to specify the start date from which commands should be displayed. The default is yesterday.
•
Use End Date to specify the end date up to which commands should be displayed. The default is today.
Click Apply Filters to apply the filters to the Command Transactions list and update the display, so that only transactions that meet the filter criteria are shown.
As there may be too many command transactions to display at once in the list, you can specify the number of Commands per page. You can also select to show transactions either in Date Order or Reverse Order. If there are several pages of commands, use the left and right buttons to display the different pages, or enter the number of the required page directly in the Page text box.
If the window is displayed for several minutes, click Update Transactions to update the Command Transactions list from the transaction database, re-applying the filter criteria.
The Status of a command in the Command Transactions list can be any of the following:
Waiting
the command is waiting to be executed.
Stalled
the command cannot be executed currently.
In Progress - the command is being executed currently. A command that does not succeed initially and then retries, goes from the status In Progress to the status Stalled, with a message describing why the command did not succeed.
Complete
the command has been executed successfully.
Cancelled
the command failed and, while it was being retried, the user cancelled it successfully.
Redundant
the command had dependencies that were not met, (for example, it may have depended on a previous command that has been cancelled), and so the command is now redundant.
Timed Out
the command did not manage to start before either its end time was reached, or the number of retries allowed was exceeded.
1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
AVEVA Logo