Академический Документы
Профессиональный Документы
Культура Документы
Activity Coordinator
Version 1.0
2.0
3.0
4.0
9 How to find Control-M Server & Table name in Control-M Desktop- ............................................... 17
12.2 To change the focus (navigate among multiple selected nodes) ............................................. 23
1 Control-M Architecture
Control-M/ EM
Control-M/Server
Control-M/Agent
This part is primarily responsible for the GUI part. The prime functionality of this EM server is
to display you the output in GUI format of information regarding the processing of jobs. So all
the information that we want to see regarding alerts, jobs condition, job processing are done
by this part. EM doesn’t process jobs. It only shows or display you the processed output jobs
are executed at control-M server level only. Also a EM server can connect to many control-M
server but not vice versa. The second utility that this part has is that it is used to connect two
This is the main central point of whole system. It is the part which fetched job from the
database checks their scheduling criteria that their time, conditions etc are matched and then
schedule the jobs and sends them to agent for execution while keeping track of the status of
job on agent continuously. The database is obviously needed here to store the permanent
definitions of the jobs
This is where the jobs actually execute when scheduled by control-M server. The server checks
the agent regularly and communicates via fixed port number. Often we here about term
“agentless” it means there is only one agent machine connected to control-M server and all
other agents connect to that machine to get in touch with server.
DECTRLM1
ESCTRLM
ESCTRLMIAT
ITCTRLM1
UKCTRLM1
10th Server
11th Server
Start => Programs =>BMC Control-M => CONTROL-M Enterprise Manager => Control-M Enterprise
Manager
Start => Programs =>BMC Control-M => CONTROL-M Enterprise Manager => Control-M Desktop
For Control-M in Galileo SOC containing jobs of Spain and TeleTu , UK & DE .
DCWVA006.dc.sedc.internal.vodafone.com
DCWVA007.dc.sedc.internal.vodafone.com
DCWVA008.dc.sedc.internal.vodafone.com
eswha099.es.sedc.internal.vodafone.com
eswha100.es.sedc.internal.vodafone.com
Flow Diagram
Navigation
Tree
Network Overview
3.3Net 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.
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
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:
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.
Click on File/Open Viewpoint in the Control-M/Enterprise Manager window to load the list of
viewpoints.
This option is available only in Galileo Control-M . This is very useful while
finding the history of job like chain & status.
We can access this via, File => Open Archived ViewPoint
We can view NDP history of last 4 days in Archived ViewPoint. We have to select Control-M
server name & NDP date in order to view the NDP of jobs.
At a set time each day (defined during installation as the start of day at the site),
CONTROL-M performs New Day processing, during which:
CONTROL-M performs a number of maintenance and clean-up functions that the
operator would otherwise have to perform manually.
Job scheduling definitions are selected from the scheduling tables (based on
their basic scheduling criteria) and are placed in the Active Jobs file. These
jobs can then be submitted and tracked by the CONTROL-M monitor.
During New Day processing, jobs that have ended OK or whose retention period
has expired according to job scheduling definition parameters are deleted from
the Active Jobs file.
In simple terms "this loads all of the jobs that Control-M knows should run that day.
Control-M does not necessarily know all of the jobs to run. it only knows the ones
scheduled to run that day. In process of cleanup Control-M will clear all the jobs
(ended OK, Deleted Jobs, Maxwait expired jobs, Eligible Failed jobs) except the jobs
which are in Hold and Jobs which are having MAXWAIT".
Note: The jobs which were ended OK will be retained for one day.
In Control-M EM GUI, where you can see the currently running jobs for today is called AJF
(Active Job File).
In our environment, we have different timings for ordering jobs [New Day
Plan] for different instances.
At 8:00 am [CET]
For DE istance:
At 11:00 am [CET]
For UK instance:
At 12:00 PM [CET]
Sometimes due to NDP or changes in Active Job File , we can not take any action on jobs until
we refresh the GUI window.
Always keep a practice to refresh the GUI after logging into Control-M.
Refresh GUI
Conditions Colour
Wait Condition
Wait User
Wait Resource
Executing
Ended Ok
Ended Not Ok
Unknown
Wait Condition:
This status indicated that the job is waiting for some conditions to be satisfied like
job dependencies, timings, hold etc.
Wait User:
This status indicates that the job is waiting for user confirmation to run.
Wait Resource:
This indicates that the job is waiting for resources like Control & Quantitative.
Executing:
Ended Ok:
This indicates that the job has been completed/Finished successfully & currently in Success
status.
This indicates that the job has not been completed/Finished successfully & currently in
Failed status.
Unknown:
Sometimes due to problem in network or in control-m agent, Control-M server unable to
retrieve the current status of that job. Due to this the job status becomes Unknown. As soon as the
problem gets resolved, the job comes into its original status.
Confirm –
This action is used to confirm the job. The job which is in ‘user wait’ condition
can only be confirmed. After confirmation, the job will execute when all requirements
are met.
Delete -
This action is used to delete the job. To delete the job, we have to put it on
hold first.
Documentation-
This action is used to check job’s documentation.
Edit JCL/Script-
This action is used to edit the job's JCL or job script statements.
Enhanced Why-
This action is used to 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-
This action is used to change the status of job to Success/Ok.
Hold-
This action is used to hold the job.
Free-
This action is used to free the job. We can free the job which is only on hold.
Kill-
This action is used to terminate the job and its associated processes. We can kill
the job which is running status only.
Log-
This action is used to view the job’s log. This log contains an audit trail of job
related events occurring in the Control-M production environment.
Rerun-
This action is used to re-run the job. Re-running a job starts execution from the
beginning. You can re-run a job that is completed Ok or NOT Ok.
Statistics-
The statistics option allows you to view statistical information related to the
execution time of a job, such as the Start time & CPU time.
View JCL/Script-
The View JCL/Script action opens the view JCL dialog, displaying programming code
for a job from a file.
The Sysout of a job is a record of the execution of that job, which includes operating
system messages captured by Control-M processes.
Why-
This action is used to determine why the job has not yet been executed.
Enhanced Why-
This option enables you to identify any jobs that have not yet completed with an OK
status that are predecessor jobs of a specified job. This feature can help you to
determine why a selected job or SMART table failed to run as expected.
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.
Step 2: Enter the job name in the ‘Job Name’ option & click on apply.
This is useful while handling activities to manage jobs. Also we can use this option to
decide whether there is need to order a job or need to force it.
1. If the Dynamic Filter Definition dialog box is not currently displayed, display it
by performing one of the following tasks (whichever is appropriate):
o 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.
o If the ViewPoint is currently displayed, select <Dynamic Filter> in the Filter
list box.
o 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.
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).
12.1 To find jobs in the flow diagram that confirm to specific criteria
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.
Check the order date [ODAT] of job for which job has to be ordered
Find the job in Control-M if it is already present of same ODAT
If job is already present in Control-M of same ODAT, then confirm with the requester
about the execution timings.
If job is not found in Control-M , then we have to Order/Force it.
Find the Control-M Server name & Table name in Control-M Desktop.
Enter all the details in Control-M Order/Force window.
Please do not forge to select the option ‘Order/Force with hold’. This is useful to avoid
mistakes of ordering unwanted job or unwanted run time.
SMART Tables are a special kind of table; they are indicated graphically in Control-M/EM by a
clock symbol below the group level. They are used by Schedulers to achieve specific
behaviours.
SMART tables have properties that are similar to individual jobs. Included in these parameters
is the capability to define In & Out conditions for jobs in SMART table collectively.
If job is in running status, then we have to kill it first & then force ok the job.
Request to re-run the job & found more than 1 instance of job –
Sol - In such case, if job Odate is given, then we can re-run that particular job. But if
Odate is not provided, then route back the request to requester for correct Odate.
If this is an incident, then we can get Odate details of job in ‘Notes’ field of ticket
in remedy. Check the Odate & perform the action respectively.
For PSRs , request to hold the job & job not found –
Sol - In such case, find the job execution calendar & timing. If job is not scheduled on
that day, then there is no need to order/Force the job & put it on hold. We can write in
remedy as, Task partially done as mentioned job is not scheduled for the day.
For PSRs , request to hold the chain or all the jobs of same name –
Sol- The jobs which are need to be hold, find in ‘Find’ option as shown below.
For example, the chain is ESCTRLM => SAP => * … This means that we need to hold
all the jobs present in chain SAP.
We can use this option to submit & run the table by ‘Bypassing’ the condition.
For PSR, we have a task to put job on hold & we found more than one
instance of job in control-m like more than 20. Out of these instances,
few instances are already on hold.
Sol – In such situation, don’t worry about already held jobs, as it is very difficult to filter
these jobs & put remaining jobs on hold & again put these jobs off hold at the end of PSR.
We have to select all the jobs & put them on hold & put off hold at the end of PSR. There
are ways to put certain instance on hold & put them off hold. But if we have Top Service
PSRs like Canvass, then directly perform actions as mentioned previously.
First thing we have to do is, find the respective Control-M Server for that job, to which the
job belongs. Then check for the NDP timing. We cannot schedule a job for future date. If
want to schedule/execute the job on particular future date , then keep that request in
pending status & load the job on that particular day after NDP. However, we can
schedule/execute the job for past dates anytime.