Running Global Projects
Transaction Audit Trail
:
Following the Audit Trail
: As seen from the TRINCO
As seen from the TRINCO
A TRINCO is created when an input command is received. It has a creation date (DATECR) an initial state (INCSTA) of ‘Received’, and a command type TRCNUM.
If the command came from the user, (or from TIMEDUPDATES) then the command UID (COMUID) is set to a null reference. Otherwise it will be the reference of the output command (TROUCO) that sent the command. If this is from another location it is an unknown reference as it is in another transaction database that is not in the current MDB and so cannot be navigated to.
The originating location of the command (where a user first issued it) is ORILOC. The location that sent the command to this location is PRVLOC. And the destination location to which it is eventually heading is DESLOC. Normally, commands are passed from location to location until the destination is reached where operations take place. For some commands, the operations take place at the ORILOC and DESLOC is used as a location to which to pass on some other commands. It is not obvious which commands are exceptions to the normal rule.
If INCSTA = ‘Acknowledged” then an acknowledgement has gone to the sender of the command. This is only relevant if the sender was a TROUCO and not a base product user.
If the state INCSTA = ‘Ready’ then the input command has created its operations successfully and TROPERs and/or TROUCOs will exist.
If there was a failure in the create processes the INCSTA may be ‘Stalled’ and no operations will exist. After waiting for the standard time the command will try again. Alternatively this failure can terminate the TRINCO. Its TRPASS will be set to FALSE, its state will be “Complete” or a later state, and it may own a TRMLST/TRMESS and perhaps a TRFAIL but no TROPERs or TROUCOs. Input commands can be given a delayed start time (EXTIME) after which operations will be generated. It will wait in the “Waiting” state until this time has passed. This stay of execution will persist until EXTIME has expired, even if this is a longer period than the Time out.
The TRINCO stays in ‘Ready’ state for as long as all its operation and output commands take to complete. Once the TRINCO has been set to ready the command cannot time out until all operations have also timed out.
When all member operations and output commands have completed INCSTA is set to “Complete”. All failures and successes generated by them are collected together and handed on to the sending TROUCO (which stores them). The success state of the command (TRPASS) is set to true if all operations have succeeded. INCSTA is now at “Replied”.
Once a reply acknowledgement has been received back from the previous location, INCSTA is set to ”Processed” and no more actions will take place.
There are other terminating conditions of a TRINCO; “Timed Out” means that the command did not manage to start before either its end time was reached, or the number of retries allowed was exceeded. It will not own any TROUCOs or TROPERs.
The state is set to “Cancelled” if the command is cancelled before any significant action took place. Owned TROUCOs and TROPERs may be set to cancelled if they have not yet started work: subsequent operations that depend on them will be set to “Redundant”.
1974 to current year.
AVEVA Solutions Limited and its subsidiaries. All rights reserved.
