DB2

DB2 solutions are designed to establish a link between DB2 and Control-M jobs. This link is established using IOA prerequisite conditions that reflect DB2's status (up or down) and Quantitative resources that indicate on which computer DB2 is running (for follow-me support). This connection enables Control-M to schedule certain jobs only when DB2 is active. Optionally, in a multi-CPU data center, jobs requiring DB2 services (follow-me jobs) can be submitted by Control-M to the same CPU (that is, MVS system) where DB2 is operated. DB2 solutions also "shout" messages notifying the database administrator (DBA) of problems in the DB2 environment.

Note: All messages (DO SHOUT actions) in DB2 rules are sent to an INCONTROL user named U-SYSDBA. A user with this name must be defined in the IOA Dynamic Destination table (CTMDEST). For more information, see the Dynamic Destination Table chapter of the INCONTROL for z/OS Administrator Guide.

Note: All messages (DO SHOUT actions) in DB2 rules are sent to an INCONTROL user named U-SYSDBA. A user with this name must be defined in the IOA Dynamic Destination table (CTMDEST). For more information, see the Dynamic Destination Table chapter of the INCONTROL for z/OS Administrator Guide.

In many cases, rule definitions make use of the inverse IN condition feature. This feature activates rules only if the specified IN conditions are not set. (For more information about using inverse IN conditions, see SolveWare Implementation Considerations.