Previous Topic: How the BEGIN Event Works

Next Topic: DELETE Event Example

Using SSM Global Events

The SSMGLOBALEXITS parameter controls whether the global action is enabled. This parameter defaults to NO, the global action is not enabled.

You must also create a global action RDF table, which contains the following four required columns:

EXIT_EVENT              CHAR(8)              PK UC      NULL
EXIT_RES_TABLE          CHAR(18)             PK UC
EXIT_RES_NAME           CHAR(18)             PK UC
EXIT_ACTION             VARCHAR(450)                    NULL

Additional columns are allowed.

If the global action is enabled by setting the SSMGLOBALEXITS parameter to YES and the global action RDF table does not exist, then the SSM global action process does the following:

There can be multiple actions that match a global event in the global table. The SSM engine assigns a numerical score to each action that matches, so that it can choose the action that most closely matches the event. Actions can be generic, meaning they only specify the event type (ADD, DELETE, or UPDATE), or they can be specific, meaning they specify the generic information and also more specific information, such as the table name being updated. The numerical score increases for each column of the action that matches the corresponding event type. The highest score is the closest match.

The RDF-triggered global events share the global action table that is used by the global BEGIN action. These actions also share the parameters for setting the action table name and enabling the action.

There are a number of variables available to global actions.

More information:

Process Events

BEGIN Event

Built-in Variables