User Tools

Site Tools


novo_motion_trigger_generator

This is an old revision of the document!


**NovoMotion Trigger Generator**

The NovoMotion deployment package includes a process to enable and disable triggers. This process is executed in the U2 environment and is called NOVO.E.T

Its syntax is:

NOVO.E.T filename UPDATE/DELETE ENABLE/DISABLE

  • Filename is the file to be acted upon.
  • Either UPDATE or DELETE can be specified - both can be specified if needed

Example: NOVO.E.T IM UPDATE DELETE ENABLE

  • Either ENABLE or DISABLE can be executed
  • The additional keyword AFTER can be used to change the execution order of the existing trigger in conjunction with the new NovoMotion trigger. The default ENABLE command will execute the NovoMotion trigger and then check for the existence of a Manage 2000 trigger. Specifically the order of events are
  1. request the write of data to a file
  2. execute the NovoMotion trigger
  3. execute the Manage 2000 trigger
  4. write the base file record to disk.

If the AFTER keyword is used the order of the triggers is reversed. The order then becomes

  1. request the write of data to a file
  2. execute the Manage 2000 trigger
  3. execute the NovoMotion trigger
  4. write the base file record to disk.

THIS IS USEFUL IF THE MANAGE 2000 TRIGGER IS CHANGING DATA ON THE BASE FILE THAT SHOULD BE RESPECTED BY THE NOVOMOTION TRIGGER.

Here is an example where the update trigger was enabled on the PT file:

:NOVO.E.T PT UPDATE ENABLE

           

Verify current trigger status...          
Create Update Trigger...                  
:LIST.TRIGGER PT                          
BEFORE UPDATE TRIGGER: NOVO.UPDATE.TRIGGER

BEFORE DELETE TRIGGER: not defined

novo_motion_trigger_generator.1300752764.txt.gz · Last modified: 2011/03/22 00:12 by novowiki

DokuWiki Appliance - Powered by TurnKey Linux