Database Jobs › Defining Database Trigger Jobs

Defining Database Trigger Jobs

You can define a Database Trigger (DB_TRIG) job to monitor a database table for added, deleted, or updated rows. To monitor the database table for specific changes, you can add a condition to the job definition. When the condition is met, the job completes. You can set up continuous monitoring so that each time a database change occurs, an alert is triggered. For continuous monitoring, the job state changes to a monitoring state and remains in that state until it is forced complete or cancelled.

Note: To run these jobs, your system requires CA WA Agent for UNIX, Linux, or Windows and CA WA Agent for Databases.

Required Statements

To define a Database Trigger job, you must specify the following statements:

• AGENT
• TABLE_NAME
• TRIG_TYPE

Note: All database jobs require a database user ID and the database resource location. You can use the defaults defined on the agent in the agentparm.txt file or specify the USER and DB_URL statements in the job definition.

Optional Statements

You can specify the following optional statements for a Database Trigger job:

• DB_URL
• JOBCLASS
• TRIG_COND
• USER
• USER_TYPE