Dynamic Filter in Control-M EM GUI

A dynamic filter is a filter that you define locally as you need it. You can then discard it or save it for reuse.

To define a dynamic filter:

1. If the Dynamic Filter Definition dialog box is not currently displayed, display it by performing one of the following tasks (whichever is appropriate):
• If the Select ViewPoint dialog box is currently displayed (that is, you are in the process of opening a ViewPoint), after you select the ViewPoint, click Dynamic Filter.
• If the ViewPoint is currently displayed, select <Dynamic Filter> in the Filter list box.
• The Dynamic Filter Definition dialog box displays the last-used dynamic filtering criteria.
2. To edit an existing filter, select it in the Filter Presets field and click OK. To create a new filter, specify a name for it in the Filter Presets field.
3. Fill in filtering criteria.
4. To save this definition for later reuse, click SAVE Button.

Consider the following when filling in filtering criteria:

• Most fields are self-explanatory. If you need a description of the fields that correspond to fields in the job editing form,
• You can use the LIKE operator for all text fields except the Odate and Time parameters. For Odate From and Time From, use the >= operator. For the Odate To and Time To fields, use the <= operator.
• For Odate From and Odate To, use the yymmdd format. For Time From and Time To, use the hh:mm format.
• Fields can contain several criteria separated by commas (for example, CONTROLM = A*,B*).
• If you specify values for Time From and To fields in the filter, the filter processes values in the Start Time and End Time fields in the Job Detail screen (not the From and Until fields in the Job Detail screen).
• The Job Status and TaskType fields each have a button, when clicked, opens an appropriate dialog box (with relevant check boxes):
• For BMC Batch Impact Manager users: Check the Included in Business Service checkbox to filter on jobs belong to a critical batch service.

Read more »

Find jobs in Control-M

To find jobs in the flow diagram that conform to specific criteria

1. In CONTROL-M/Desktop or CONTROL-M/EM, select Edit => Find Jobs.
2. In the Find Job dialog box, fill in the criteria (you can specify pattern-matching strings in certain fields).
3. In CONTROL-M/EM only, to save the specified Find criteria for future use, assign a name in the Find Presets field, and click Save.
4. Click Find, which selects all nodes matching the criteria, and displays the first node that fits the criteria.

To change the focus (navigate among multiple selected nodes)

Click the appropriate navigation button (First)  , (Previous) , (Next) , or (Last) ,  or use the View => Toggle Selection menu.

Read more »

Prerequisite Conditions

"Prerequisite Condition is a flag representing a user-specified situation or condition. Submission of a job for execution can be made dependent upon the existence of one or more conditions. Conditions are recorded in the Conditions table in Control-M EM Server database"

Job dependencies in the flow diagram are represented by lines and arrows connecting

job nodes, for example.These lines can even indicate dependencies between jobs in different CONTROL-Ms. The direction of arrows at the ends of the lines indicates the flow direction (predecessor and successor relationship) of the connected nodes.

Dotted lines between two jobs indicates a conditional link between the two jobs (for example, optional In conditions defined using OR logic).

An arrow without a connecting line at the top or bottom of a node indicates one of the following condition types:

Arrow at the top of the Job — a manual In prerequisite condition. This is a condition that does not get added automatically by another job, but rather must be manually added.

Arrow at the bottom of the Job — The Out prerequisite condition has no corresponding In condition or job dependent upon the condition.

In CONTROL-M/EM, the connecting lines between conditions are

■ Green —condition exists (active)
■ Black — condition does not exist yet (inactive)

Read more »

Control-M Job Actions

Actions that can be performed on jobs:

Action	Description
Confirm	Confirm the job.
Delete	Delete the job.
Documentation	View the job's documentation.
Edit JCL/Script	Edit the job's JCL or job script statements.
Enhanced Why	View the predecessor’s jobs and Group Scheduling table for a selected job or Group Scheduling table. It is selectable only from Flow Diagram.
Force OK	Set the job status to OK.
Free	Free the job.
Hold	Hold the job.
Kill	Terminate the job and its associated processes.
Log	View log messages for the job.
Reactivate	[OS/390] Reactivate post-processing for the selected job.
Rerun	Rerun the job.
Restart	[OS/390] Restart the job using CONTROL-R.
Statistics	View statistics of the job's latest runs.
Undelete	Undelete the deleted job.
View JCL/Script	View the job's JCL or job script statements.
Sysout	View the job's Sysouts.
Why	Determine why the job has not yet been executed.

Menu options can be disabled in specific situations.

For example:

•  The Why option is disabled when the job is executing or has completed.
•  The Hold option is disabled when the job is already held.
•  All options (excluding the Properties option) are disabled when communication is temporarily not synchronized.
•  When any one of these actions is selected, CONTROL-M/EM accesses and/or updates the relevant CONTROL-M installation's database.

Before updating a job's details, you must HOLD the job. After updating, you can FREE the job.

Read more »

Order / Force using Control-M / EM GUI

Order/Force a Job:

Click the Icon on the Toolbar or select Tools -> Order/Force a Job (Cntrl+R is the shortcut key)

You will get Order/Force dialog box. You have to select Control-M (Data center) and Table from the dropdown list to display all the jobs in that table. Then you can select the job which you want to order/force job.

Difference between Order and Force:

• Order: will bring the in to AJF if the job is in schedule.
• Force: will bring the job into AJF irrespective of the schedule.

Note: If you would like to bring the job with HOLD then you need to select ‘Order/Force with Hold’ option.

Read more »

Control-M Viewpoints

Viewpoints

Batch flows at most sites exist in a distributed environment spanning many computers of different types. CONTROL-M provides a powerful graphic user interface that allows you to view, monitor, and control all enterprise-wide batch flows from a single console, called the CONTROL-M/Enterprise Manager console (sometimes referred to as CONTROL-M/EM GUI or CONTROL-M/EM).

Using CONTROL-M/EM, you can see the progress of your batch flows, and identify problems and potential problems. CONTROL-M/EM provides a customizable, dynamic tool called ViewPoints to allow you to display only those jobs and job flows of interest. For example, you can view and monitor:

• Jobs on a particular CONTROL-M
• Jobs belonging to a specific user
• Jobs having a particular status, such as failed jobs

ViewPoints are constantly updated and show in real-time the execution status of the batch production. CONTROL-M provides a set of predefined ViewPoints. You can define other ViewPoints according to need.

Opening a Viewpoint:

Click on File/Open Viewpoint in the Control-M/Enterprise Manager window to load the list of viewpoints. You can have more then one viewpoint open at a time.

Each window can use a different Viewpoint to display the environment.

• Click on “All Active Jobs”/your desired viewpoint and then click the OK button.
• Click on “NOTOK Only”/Your desired viewpoint and then click the OK button

In this example two viewpoints have been opened. One viewpoint shows “All Active Jobs”. The other viewpoint shows “Ended NOTOK” jobs only.

You can open as many viewpoints as you wish and click on the Window/Tile and the Window/Cascade menu options to rearrange the view. You can simply click and drag the viewpoint windows around to the desired place. All viewpoints will default to show at the datacenter level.

The CONTROL-M/Enterprise Manager window consists of the following parts:

1. Navigation Tree – Hierarchical view of jobs in the current environment.


2. Flow Diagram – Graphic representation of job production flow, based on job dependencies established by prerequisite conditions specified in job processing definitions. Components of the active environment are represented by boxes called nodes. The information displayed in a node varies depending on the type of node and on how certain customization options.


3. Net Overview – Miniature version of the flow diagram, indicating the part of the network currently displayed in the Flow Diagram view. By ragging the selected area in this view to a different part of the network, you can quickly navigate in a complex environment.

Understanding the flow diagram:

In the flow diagram, components of the environment (definition environment or active environment) are represented by node boxes. The information displayed in a node varies depending on the type of node and on customization options.

Read more »

CONTROL-M/Agents:

CONTROL-M/Agents are commonly used to place computers under the control of a CONTROL-M/Server. CONTROL-M/Agents submit jobs on behalf of the CONTROL-M/Server, track the jobs’ processing, and provide status information back to the CONTROL-M/Server.

As an alternative to having a dedicated CONTROL-M/Agent installed on each computer under the control of a CONTROL-M/Server, CONTROL-M/Server can also submit jobs to agentless computers known as Remote Hosts.

CONTROL-M/Agents and remote hosts are identified by their node IDs. Jobs are assigned to specific node IDs. You can balance processing loads by grouping a number of CONTROL-M/Agents together into a node group, and then assigning jobs to the node group, instead of to a specific CONTROL-M/Agent. The job will be processed on any agent in the group, according to the processing load at that particular moment.

Read more »

Control-M GUI's

GUI’s:

          The main 3 GUI’s are listed below.

ü  Control-M / EM

ü  Control-M Desktop

ü  Control-M Configuration Manager

Control-M / EM:

This is a GUI where we can view all the jobs which are running for today. The jobs which are active for today is called ‘Active Job File (AJF)’.

Control-M Desktop

Using this GUI you can make all permanent changes to scheduling tables and calendars. You can create new jobs, tables and calendars using Control-M desktop. The changes which you are performing through this will be permanently stored in control-M server database.

Control-M Configuration Manager

Through this GUI you can monitor all control-m components (Control-M server, agents, remote hosts… etc) health status. You can also implement additional security using this GUI. We can define agents, Remote Hosts through this GUI.  

Read more »

The Control-M Data Center

The Control-M/Data Center is the true core of the Control-M system. The Data Center is comprised of a Control-M/Server, Database and Control M/Agents.

The Control-M/Server

The Control-M/Server is the central component of the Data Center. It controls interaction with the Enterprise Manager, Control-M/Agents and the database backend. The Control-M/Server (CTM/SERVER) is the component that maintains the schedule, job definitions, calendars, resources and conditions. CTM SERVER is the only component that can load or order jobs.

The Database

The database serves as a backend data repository for Control-M (Sybase, PGSQL, Oracle or MS SQL server can be used). The CTM/SERVER has its own data-space within an Oracle instance. This data-space contains the Master versions of all of the job-related data: job-definitions, scheduling tables, resources, calendars active jobs tables and shout tables, to name a few. It also houses runtime specific data for the CTM/SERVER such as process flags, user access profiles and agent status.

The Database is critical to the operation of CTM/SERVER & Control-M. If the database is not available, Control-M will not operate.

The Control-M/Agent

The Control-M/Agent (CTM AGENT) is a small-footprint application that is installed on each target server for jobs, as well as the CTM SERVER. It runs as a service on Windows-based systems and has a “hook” into “inetd” on UNIX systems. It is dormant until a request comes from the CTM SERVER or until a job-related message needs to be sent to CTM SERVER.

Read more »

The Control-M Accessories

The Control-M “Accessories” are:

• Control-M/Enterprise Manager GUI (EM/GUI or ECS GUI)

• Gateways

• Global Alert Server (GAS)

• Global Condition Server (GCS)

It is important to understand what each of these components does and its place in the Control-M architecture.

GUI’s:

The main 3 GUI’s are listed below.

1. Control-M / EM GUI
2. Control-M Desktop
3. Control-M Configuration Manager

Gateways: These are used for communication between Control-M/EM and Control-M Server. If these gateways are down then Control-M/EM GUI won’t get any status updates from the Control-M Server.

Global Alert Server (GAS): GAS will contain all the alerts sent from jobs which are active in Control-M. You can connect to GAS using ‘Alert window’ and can view all the alerts. Usually operations will monitor these alerts and take appropriate actions.

Global Condition Server (GCS): GCS will keep track of all Prerequisite and Global conditions added by jobs which are in AJF. Once a condition added to GCS, control-M will satisfies the condition for all the waiting jobs.

Read more »