Job definition

In Control-M for Databases, you can define one or more of the following database jobs:

Stored Procedure: Defines a database job with a program that is stored on the database, as described in Defining a Stored Procedure job.
SQL Script: Defines a database job with a script that is stored on a file system, as described in Defining an SQL Script job.
SQL Server Integration Services (SSIS): Defines an SSIS Package job, as described in Defining an SSIS Package job.
Embedded Query: Defines a database job by creating an SQL query statement, as described in Defining an Embedded Query database job. You can also create an SQL statement with the Query Designer, which acts as a wizard to build an SQL statement, as described in Defining a database job with the Query Designer.
MSSQL Agent Job: Describes how to run an MSSQL Agent job, which is defined in the SQL server and managed by Control-M, as described in Running an MSSQL Agent job. Control-M for Databases only supports Standard ANSI SQL syntax for SQL scripts or Embeddied Queries. If you need to run native SQL commands, such as PL/SQL, BMC recommends using a Stored Procedure job.

After you have defined a database job, you can enhance it by doing the following:

Integrate database jobs with other Control-M jobs into a single scheduling environment, as described in Control-M Workload Automation User Guide.
Introduce all Control-M capabilities to databases, including advanced scheduling criteria, complex dependencies, quantitative and control resources, and AutoEdit variables, as described in the Control-M Workload Automation User Guide.