Setting up the ENS Components › Using the Command Line Interface to the Configuration Editor › Add Actions

Add Actions

See the chapter Understanding ENS for information about actions.

To add an action

1. Start the configuration editor:

   $ CONSOLE EDIT /INTERFACE=character_cell
   

2. Enter:

   CM Edit> add action
   

3. Enter the name of the action. For example, your action:

   Action name: your action
   

4. Enter a description of what the action does. For example, your description:

   Information: your description
   

5. Enter the command name:

   Command: your_action.com
   

   Note: You must include the appropriate file extension on the corresponding action routine, for example YOUR_ACTION.COM for a command file.

6. You are asked to choose an action type to determine how the action will be executed, and the way in which ENS will communicate events to it:

   Action types may be one of the following :-
    1 = Activate once for EACH event and EACH userdata item
    2 = Activate once for ALL events and ALL userdata items
    3 = Activate once for ALL events and EACH userdata item
   Action Type ? (1:) 1
   

7. You are asked if you want to pass all arguments to the action:

   Pass all Arguments? [Y/N] (Y:) N
   

8. You are asked if you want to pass an event name:

   Pass Event Name? [Y/N] (Y:) Y
   

9. You are asked if you want to pass an event time:

   Pass Event Time? [Y/N] (Y:) N
   

10. You are asked if you want to pass an event class:

    Pass Event Class? [Y/N] (Y:) N
    

11. You are asked if you want to pass the event information:

    Pass Event Information? [Y/N] (Y:) Y
    

12. You are asked if you want to pass event text:

    Pass Event Text? [Y/N] (Y:) N
    

13. You are asked if you want to pass an event priority:

    Pass Event Priority? [Y/N] (Y:) N
    

14. You are asked if you want to pass the system that generated the event:

    Pass system that generated event? [Y/N] (Y:) N
    

15. You are asked if you want to pass the subsystem that generated the event:

    Pass subsystem that generated event? [Y/N] (Y:) N
    

16. You are asked if you want to pass the source of the event:

    Pass source of event (application? [Y/N] (Y):) N
    

17. You are asked if you want to pass user-defined data:

    Pass User-defined data? [Y/N] (Y:) N
    

18. You are asked if it is all right to add the action:

    OK to add? [Y/N] (Y:) Y
    

The following is an example of what you see on your screen:

Database contains NO verification errors
CM Edit> add action
Action name: your action
Information: your description
Command: your_action.com
Action types may be one of the following :-
 1 = Activate once for EACH event and EACH userdata item
 2 = Activate once for ALL events and ALL userdata items
 3 = Activate once for ALL events and EACH userdata item
Action Type ? (1:) 1 
Pass all Arguments? [Y/N] (Y:) N
Pass Event Name? [Y/N] (Y:) Y
Pass Event Time? [Y/N] (Y:) N
Pass Event Class? [Y/N] (Y:) N
Pass Event Information? [Y/N] (Y:) Y
Pass Event Text? [Y/N] (Y:) Y
Pass Event Priority? [Y/N] (Y:) N
Pass system which generated event? [Y/N] (Y:) N
Pass subsystem which generated event? [Y/N] (Y:) N 
Pass source of event (application? [Y/N] (Y):) N
Pass User-defined data? [Y/N] (n:) N

OK to add? [Y/N] (Y:) Y