Running Global Projects
Transaction Audit Trail
:
Following the Audit Trail
: As seen from the TROPER
As seen from the TROPER
Operations are created during the create operations process and possibly again when post operations are generated. Operation information is stored in TROPER elements. This is used to execute an operation at a location, to progress the operation and store any results, errors, messages it may generate.
It is only operations that actually do anything in the daemon, input and output commands (TRINCOs and TROUCOs) are just the means of marshalling instructions between users and locations, and between locations. Extra commands may be generated, but in the end it is the operations that are created at locations that do the work.
The operation type is the TRONUM attribute.
Operations start in state OPSTAT “Waiting” until it is no longer dependent on any prior operation or command and can be executed. It then goes to “Ready” and put into a list ready for execution. Execution takes place in a separate thread and the state is then “Running”.
During the running state Failures and Successes may be generated as well as messages. But these are not stored in the database immediately.
When the operation finishes (TRPASS set to true or false) the OPSTAT is set to “Complete” and successes and failures stored in the database under the TROPER (and not before this). The finishing may also set a string in MSTEXT, but this is not passed on.
The execution of an operation can stall due to inability to access data for example. In this case the OPSTAT is set to “Stalled” and will be reset back to Ready after time WAITIM. The number of retries after stalling is stored in NRETRY. Operations will time out if still stalled at date ENDTIM or the number of retries exceeds MAXTRY. In this case OPSTAT goes to “Complete” and finally “TimedOut”.
When an operation is complete it may need to generate extra operations and commands the form of which are dependent on the results of the operation. If this create operation is stalled then the operation goes to OPSTAT “Stalled Post Operation” and will go back to “Complete” after WAITIM. When post operations are successfully created, or none are needed, then the operation goes to a final state that is “Processed” or “Timed Out”.
TROPERs may never be needed if dependencies are not met in which case they terminate in state “Redundant”. This may happen if a command is cancelled.
1974 to current year.
AVEVA Solutions Limited and its subsidiaries. All rights reserved.
