Managing actions

Use supplemental SQL statements (actions) to be executed at selected phases of an archive, delete, insert, extract, or restore process. For example, you might use an action to audit deleted rows by executing an appropriate SQL statement before the start of the delete process, or after the deletion of each row. You can also create an SQL statement to call a stored procedure. You can define actions for all phases, including insert or restore phases, in the access definition, which is copied to the archive or extract file during processing. Any insert actions in the access definition become the default actions when data is inserted but can be overridden in the table map that is used in the insert, load, or restore process. For load processing, however, actions for many phases are disregarded.

Process actions occur at the beginning or end of a process. For example, you might use a process action to record the time at which a process begins or to record the name of a file generated by the process. Table actions, however, are specific to a table and can occur before or after the first or last row in a table is processed or before or after each row in the table is processed. For insert and restore, all process and table actions can be executed during processing. For load processing, however, only actions for the beginning and end of the process or before or after processing the first or last row in a table can be executed; actions for other phases are ignored.