Control M – Technical Manual

Qualcomm BI Team
Hyderabad

1
Overview of Scheduling Tools

¾ Scheduling all business processes is the biggest challenge in the enterprise

environment where in every process is dependent on one or more business
components from different business applications.

¾ Controlling such big enterprise data and streamlining multiple processes

parallelly with efficient failure/error and recovery mechanisms and avoiding
with out redundancy is the most challenging tasks.

¾ Although every other enterprise software has its own scheduling mechanism
available as part of it release, functionality provided is not addressing all the
business needs. Hence there is a demand for an efficient tool which
intelligently handles failure/error and recovery mechanisms.

2
Advantages of Control M
¾ Meet deadlines and business goals efficiently
¾ Integrate scheduling across all platforms and applications
¾ Reduce manual errors
¾ Enables complete management and control over the entire business process
via centralized monitoring
¾ Ensures service levels are met by providing automated and early problem
notification
¾ Increases productivity and throughput and reduces learning curves through
an intuitive single definition screen with fill-in-the-blank technology
¾ Minimizes manual intervention, eliminates human error and maximizes
computer resource use by using an Auto-Edit facility
¾ Efficient Failure / Error handling mechanism
¾ Maximizes hardware and software investments by effectively integrating new
environments
¾ Saves administrator time through complete automation, immediate problem
detection and a scalable open architecture

3
Control M - Desktop
Introduction

4
Introduction
¾ Control M-desktop is one of the tool from Control M, which enables individuals
to create Applications/ Groups / Jobs/ Tables etc…

¾ You can execute all the commands e.g. UNIX / Windows basic commands to
shell scripts/ batch scripts, including other .exe files.

¾ Everything you define in control M Desktop will not appear until you write /
upload / order the jobs. After ordering in, they appear in Control M Enterprise
manager.

5
Login Details
Choose Start => Programs => CONTROL-M/Enterprise Manager 6.1.00 =>CONTROL-
M/CONTROL-M Desktop.
When Control M desktop opens you need to either Load the jobs from Control –M/EM or open
a draft on which you want to work.

Input your user name and password.

Logging in to a GUI Server with a different Naming Service
In the Login Dialog Box, click Advanced. The Login dialog box is redisplayed with
additional controls

6
Group Creation
¾Groups are holders for jobs and most of Control M jobs are set up with Groups.
Groups/Jobs are defined in the Control-M Desktop by the Enterprise Scheduling Team.
Most of the information is general and the more specific parms are on the job level.

7
Job Creation

8
 Control M – Desktop
(Job Creation Process)

9
Job Editing Form

10
Job Editing Form - Layout
This form is used to define certain type of parameter. Job editing form
panels are:
¾ General - What the job does and where its script is located.
¾ Scheduling - When and/or how often the job should be scheduled for
submission.
¾ Execution - Parameters related to job execution and
accompanying processes.
¾ Conditions - Prerequisite conditions which must be satisfied before
job submission, and conditions to be added/deleted
when the job is successfully completed.
¾ Resource - Quantitative and Control resources required
for job submission.
¾ Set - Auto Edit variables to be set when the job is
submitted.
¾ Steps - Conditional post-processing instructions.
¾ Postprocs - “Shout when” and Sysout-handling post-
processing instructions

Client Confidential
11
Job Editing Form - General Panel
The parameters that needs to be defined in General panel are :

¾ Job name
¾ File name
¾ Path
¾ Owner
¾ Author
¾ Application
¾ Group
¾ Control-M
¾ Command

12
 Job Editing Form - General Panel

This represents
the name of the
job (Text)
Name of the file
that contains
the job (Text)

Name of the
Path of the file
application to which
that contains the
job group belongs
job

Login User Id of
Name of the group to
the person who
which the job belongs
logs in

Name of the Control-

Control-M to
Is the one who which the job belongs
creates the job e.g:
e.g: CTM_Usse for TST
CTM_Chamboard for PROD

The path of the

command to be
submitted for the
job

13
Job Editing Form - Scheduling Panel
This indicates when and how often the job should run.

The parameters that needs to be Scheduling are :

¾ Month days
¾ Week days

14
 Job Editing Form - Scheduling Panel
¾ This indicates when and how often the job should run.
To schedule the
job for a particular
day like Monday
for all the dates
click on this
button

Scheduling
A calendar and text the job for
box used to indicate selected
the days of each week days
month for which the Usage
job to be scheduled buttons

To schedule for
all the dates
click on this
button

To schedule
complete week
of a month click
on this button

15
Job Editing Form - Scheduling Panel
Month Days:

¾ Calendar:
¾ Click the date once to select it for scheduling
¾ Click on all ready selected date to de-select the date
¾ To select complete week click on left side button of the calendar for specific
week.
¾ To schedule the job on particular day like Monday for all the months select the
button above that day.

¾ Usage Buttons:
¾ +n : Select this to add the date in addition to working days
¾ -n : Select this to remove the day if it is a working day
¾ >n : Select this to order the job on the indicated day if it is a
working day else order the job on the next working day.
¾ <n : Select this to order the job on the indicated day if it is a
working day else order the job on the closest
preceding working day.
¾ Dn : Select this to order the job on the nth working day from
the beginning of the month

16
Job Editing Form - Scheduling Panel
-Dn : Select this to order the job on all the working days
except on nth working day from the beginning of the
month
-Ln : Select this to order jobs on the nth calendar day from
end of the month
-Ln : Select this to order jobs on all the days except the
nth calendar day from end of the month

Week Days:

This parameter is selected to Schedule the job for selected weekdays.

¾ eg: if the job should run only on week days but not for week ends then
Check in the checkboxes from Monday to Friday

17
 Job Editing Form - Execution Panel
This is used to define the parameters that are related to execution of the job .

This is
selected to
run the job Indicates that the
multiple job is not run until
times the administrator
confirms that it
should be
submitted.

Host name of the

Agent platform on
Amount of which the job is
wait time running..
b/w re-runs
Checking the check Specifies that job
box a critical-path submission details
job in CONTROL-M. be broadcast to all
Agents within
The no of a defined Node
days that the Group.
job can wait
to be
executed
after its
executed
date has
passed

18
Job Editing Form - Execution Panel
This execution panel has different parameters and the parameters that should be
defined in execution of a job are :
¾ Re-Run
¾ Maximum
¾ Time
¾ Node ID/Group

Re-Run
Indicates that the job is rerun at an interval defined by the INTERVAL and MAXMIUM
parameters.

INTERVAL
Amount of time to wait between reruns or between cycle of cyclic jobs. By default this is
set to ZERO. The amount of waiting time may be Hours or Minutes or Days and this is
defined by the parameter UNITS.

UNITS
This specifies the unit of time for value specified by Interval parameter.
Valid values are:
HOURS : (1-1080)
MINUTES : (1-64800)
DAYS : (1-45)

19
Job Editing Form - Execution Panel
Maximum
Maximum number of reruns allowed in the case of job failing.
eg: if Maximum is defined as 4.
so the execution of job will be failed if the job fails for 4 times.

Time
This indicates the time limit for the lob submission
This has two parameter FROM and UNTIL which needs to be defined for
job execution

FROM : This is the start time for job submission and should be in HHMM format
UNTIL : This is the end time of the job submission and should be in HHMM format

Generally the job is submitted between this time range i.e. between start and until time
eg: if job needs to be run everyday between 9:00 PM and 11:00 PM then
FROM = 2100
UNTIL = 2300

Node ID/Group
This represents the Host name on which the job should run. This parameter should be defined
properly in order to schedule the job.

20
Job Editing Form - Conditions Panel
This is used to specify the conditions based on which the job should run.
e.g.: consider two jobs job1 and job2.the job2 should run only after job1.

This has two condition sets :

¾ IN Conditions
¾ OUT Conditions

21
 Job Editing Form - Conditions Panel

Select these to
Select this to
change the order
add a new
of list.
condition.

Name of the
prerequisite
condition. (Text)

Click this to save

the new or edited
condition

This is used to edit

already existing
conditions or to
add new
conditions.

22
Job Editing Form - Conditions Panel

23
 Job Editing Form - Resources Panel
¾ The Resources panel is used to define Quantitative and Control resources.
¾ Quantitative resources are defined in the left side of this panel. Control resources are
defined in the right side.

Type of control that the job

must have over the resource.
(Option buttons)

Name of the
resource
required by
the job.(text)

24
Job Editing Form - Set Panel
Set Variables:

Parms defined to a job

Name = PARM1, PARM2, etc

Value=parm sent
*LIBMEMSYM required to set Global
variables for Control M

25
Job Editing Form - Steps Panel
This is used to perform actions based on the status of the job

Displays ON
statement
definition line
Character string that is compared with
the job’s log statement records. Displays DO
statement
definition line

Deletes the
selected statement
Character string that is compared with
the job’s log error codes.

26
Job Editing Form - Steps Panel
¾ Each item in this panel indicates either an ON statement, or a DO statement.
ON statements indicate conditions under which specified actions should be
performed. DO statements indicate actions to be performed when the
preceding ON statements are satisfied.

¾ Statement (Text box): This is a character string which is compared with the
job’s log statement records

¾ Code(Text Box): This is a character string which is compared with the job’s
log error codes

27
Job Editing Form - Postproc Panel
This is used to specify actions to be performed upon job completion.

The parameters that needs to be defined are :

¾ Shout
¾ Sysout

Shout
This describes the message to be sent to the specified destinations based on the
job status .

28
Job Editing Form - Postproc Panel
The PostProc panel is used to specify actions to be performed upon job
completion.

Destination These option buttons

to which indicate the urgency
the level of the shout.
message
should be
sent.

Describes how
the output of
the job should
be handled.

29
 Job Editing Form - Postproc Panel
z These Post Process definitions need to be in place to generate standard format alerts when any of
these conditions occur. Using the standard format alerts, the Event Management system will be
able to forward alerts to Clarify to open cases appropriately. Normally, all job definitions should
have a NOTOK condition defined, as this will generate the alert and subsequent Clarify case if the
job aborts.

z The "To" field should always be set to "ECS" to send the shout message to the Control-M Alert
Server.

z To alert for job running too long:

When: Exectime Urgency: Urgent Shout Text: %%OWNER Exectime
Exceeded

z To alert for job running not long enough:

When: Exectime Urgency: Urgent Shout Text: %%OWNER Exectime Too Low

z To alert for job submitting (start) too late:

When: Late Sub Urgency: Urgent Shout Text: %%OWNER Missed Late Sub

z To alert for job completing too late:

When: Late Time Urgency: Urgent Shout Text: %%OWNER Missed Late Time

z To alert for job abort/ended not ok:

When: NOTOK Urgency: Very Urgent Shout Text: %%OWNER Ended Not OK
RC=%%COMPSTAT

30
Exiting the Job Editing form
Exiting the Job Editing form depends on how the form was originally opened.

¾ If the Job Editing form was opened in Flow Diagram view, in List view, from the New
Job button, or from the Job New menu option, the Job Editing form appeared as a
dialog box.

This dialog box may need to be closed before you perform certain processes.

9 Click Save to Draft (or Save to Database if working in online load

mode) to apply the changes you have made in the Job Editing form.
9 Click Cancel, to cancel the changes you have made in the Job
Editing form. If the Job Editing form was opened in List/Job Editing View by
selecting the job

From the tree in the left pane, the Job Editing form appeared in the right pane.

Additional processing can be performed in the draft when using this format.

9 Click Save to Draft (or Save to Database if working in online load

mode) to apply the changes you have made in the Job Editing form.
9 Click Cancel, to cancel the changes you have made in the Job Editing form.

31
 Control M – Desktop
(Job Writing/Uploading/Ordering Process)

32
Writing Table to Control-EM
¾ When working in local mode, changes made to a definition are saved locally in
the draft, and are not automatically saved in the CONTROL-M/EM database.
Therefore you must perform the Write to CONTROL-M/EM operation to save
the changes in the CONTROL M/EM database.
¾ To write definitions to the CONTROL-M/EM database:
ƒ Open the draft containing the job processing definitions for the scheduling table
ƒ Choose Edit => Scheduling Tables => Write to CONTROL-M/EM,

33
Writing Table to Control-EM
¾ WRITE TO CONTROL-M/EM WINDOW IS DISPLAYED.
¾ After you have created the draft of your job, you have to write it to Control M
EM.
¾ Select the job and opt Edit>Scheduling Tables > Write to Control-M/EM.
¾ If you are writing it from draft and not working online you have to connect to the
server

34
Writing Table to Control-EM
¾ Select the scheduling tables that you want to write to the CONTROL-M/EM
database. Click Write. The scheduling tables are written to the CONTROL-
M/EM database

35
Writing Multiple Tables to Control-EM
z Writing multiple scheduling tables
z The procedure for writing multiple scheduling tables is the same as for writing a
single scheduling table, although two or more tables are selected for writing. If you
are writing multiple scheduling tables and one or more of them already exist in the
CONTROL-M/EM database, the Confirm Write Scheduling Tables dialog box is
displayed. In this dialog box, you must indicate whether you want these scheduling
tables overwritten.

36
Ordering Jobs
z To open the Scheduling Table Manager window,
z 1 In the CONTROL-M/Desktop window menu, either select Edit => Scheduling
Tables => Scheduling Table Manager .

37
Ordering Jobs
¾ The fields at the top of this window can be used to filter the scheduling tables
that are displayed.
¾ Buttons on the right side of this window offer a wide variety of actions that can
be
¾ Performed on scheduling tables selected in this window.

38
Ordering Jobs - Other Commands

39
Ordering Jobs - Other Commands

40
Ordering Jobs - Other Commands

41
Using SYSTEM variable
z User Daily (Optional) Identifier used to assign the scheduling table to a
specific User Daily Job (1-10 characters, case sensitive). If “SYSTEM“(upper
case only) is specified, the scheduling table is ordered by the New Day
procedure.

42
Unlock Table
z To unlock a table you should choose the table and select unlock.

43
Ordering
z To order or force scheduling tables from within CONTROL-M/Desktop:
z 1 In the CONTROL-M/Desktop window menu, either select Edit => Scheduling
z Tables => Scheduling Table Manager or click . The Scheduling Manager
z window is displayed.
z 2 Select the line(s) for the scheduling tables that you want to order or force.
z 3 Click either Order or Force.
z 4 If a confirmation dialog box displays, click Yes. The following dialog box is
displayed
z 5 To assign a different date than the default date, click the button by the date
z selection field, and select the desired date.
z 6 For a job running under CONTROL-M for z/OS version 6.2.00 or later, to ensure
z that it does not run before the Odate, check the Wait for Odate to run check box.
z (If this check box is not checked, the job runs as soon as the execution criteria are
z satisfied.)

44
Frequently Asked Questions

z When does the next day begin?

The new day scan is at 12 PM PST. All jobs that are in green status or that
have a max wait of 0 will be removed and the new jobs for the day will be
scanned in.

z How does a job within a group get removed from the scan temporarily?
Request the job to be expired in the group. The Tag Relationship will be
changed from Or to And which will allow all the other jobs in the group to be
scanned in. Once the job is ready to be scanned back in change the Tag
relationship back to And.

z How does a group get reran?

If an entire group needs to be reran then the out conditions for the group (if
any) and the jobs must be removed from the Prerequisite Table so the jobs
in the group will run in the correct order. Request the conditions to be
removed and a rerun to the jobs.

45
Control M – Enterprise Manager

46
Different products of Control M
CONTROL-M/Enterprise Manager :
¾ Enables you to control business processes for entire enterprise from a single workstation
¾ Allows to view process flow and dependencies so that one can optimize business
processes easily and efficiently

Control M Products:

We cover this
topic in the
presentation

47
CONTROL-M/EM components

48
Login Details
Choose Start => Programs => CONTROL-M/Enterprise Manager 6.1.00 =>CONTROL-
M/Enterprise Manager GUI.
The following dialog box is displayed when CONTROL-M/EM is started:
CONTROL-M/Enterprise Manager Login dialog Box

Input your user name and password.

Logging in to a GUI Server with a different Naming Service
In the Login Dialog Box, click Advanced. The Login dialog box is redisplayed with
additional controls

49
Login Details
You can Log in to a different GUI Server with a different Naming Service using
Advanced command button.

50
Login Details – Command Line
¾ Choose Start => Run.
¾ Enter the following command in the Open text box:
emgui -u <user_name> -p <password> -m <hostname> [-vp <ViewPoint>]

¾Press Enter. The CONTROL-M/EM window is displayed

51
View Point
¾ Jobs that have been ordered for submission are viewed from the main
CONTROL-M/Enterprise Manager window.
¾ Jobs that are visible in this window can be limited and sorted according to
various fields. Each resulting combination based on the specified criteria is
referred to as a Viewpoint
¾ Viewpoints are defined using either the Viewpoint Manager or Viewpoint
Wizard.
To open an existing ViewPoint:
¾ 1. Choose File => Open Viewpoint, or click . The Open Viewpoint
dialog box is displayed.
¾ 2.Select the view point to be open.

52
 View Point
¾ Click on ok Button
¾ View point window can be appear in the Enterprise Manager.

Hierarchical
view
of jobs in the
current
environment Graphic
representation
of job
production
Navigational Tree
Flow Diagram
Miniature
version
of the Flow
Diagram

Net Overview

53
Archived view Point
¾The Archived Viewpoint features enable you to see the job information from a previous day in
CONTROL-M. In this context, a “day” means the timeframe within which all jobs in an Active
Job file are run.
¾An Archived Viewpoint is a static display of all the information on jobs that ran on a data
center in one day. Jobs are displayed as they were at the end of that day.
¾This feature help the user to review, track, and analyze problems of previous days. This
information will be saved automatically by CONTROL-M/EM.

Selecting and displaying Archived Viewpoints:

¾You can use the Open Archived Viewpoint option to select and display Archived
Viewpoints.
¾The Viewpoint Wizard window can be opened at any time during a CONTROL-M/EM session.

¾In the CONTROL-M/EM, select File => Open Archived Viewpoint.... The Open Archived
Viewpoint Wizard is displayed.

54
Archived view Point
¾Select a data center from the CONTROL-M drop-down list.
¾Select a Net from the Nets list, and click Next. The following window is displayed
¾Select the Viewpoint definition you wish to display
¾Click Dynamic Filter to set filtering criteria in order to display the jobs as you
¾ require, in the Archived Viewpoint.
¾Click on Finish

55
Node Types
Node types :
¾Several types of nodes (entities) are displayed in the Flow Diagram.
¾Each entity is represented by a unique icon in the upper left corner of the node.
¾Additional icons and text also appear in the job node to identify the type of job.

Sample node types Node type:

56
Job Node Status
¾The status of a job is indicated by the color of the title bar of its node.
¾The statuses are described in the below diagram.

57
Job Node Operational Status
¾A job node is displayed with the title bar colored according to its status.
¾In addition to the node status, each job node is assigned a state that provides more
information about the node, as indicated in the following table

58
Active Window
There are several options available for jobs in the Enterprise Manager.
Right click on the job or group and a list of available options will show
up in bold print.
¾ Status Summary-a list of statuses and meanings and stats on how
many jobs are in a specific status.
¾ (see previous page)
¾ Properties-job/group detail information.
¾ Hold – Place job on hold
¾ Confirm-satisfy a user confirmation status
¾ Free-Release from hold
¾ Rerun-Restart a job
¾ Delete-Delete job from AJF. Deleted jobs will not permanently be
deleted until the next scan.
¾ Undelete-if job is deleted can be placed back in schedule with
Undelete
¾ Kill-stop a job that is currently running.
¾ Force OK-mark the job ok, continue with stream
¾ Sysout-
¾ Statistics –view last run info on job
¾ Documentation
¾ Log
¾ Why?- look at what job is waiting on
¾ Neighborhood- identifies jobs that are predecessors or dependents of
a selected job or Group Scheduling table and highlights the nodes of
those jobs in the Flow Diagram
¾ Branch menus- preds and successors of job selected.
¾ Find in Flowdiagram-find it in the flow diagram view.

59
Log
Allows viewing of the jobs log records.
View Log :
¾Right click on the job in the Navigational window.

60
Sysout
CONTROL-M can print or delete a job’s log, or move or copy the log to a specified library or
directory.
Based on specifications in the job processing definition, CONTROL-M can dynamically
determine how to handle the job’s log.

View Sysout:
Right Click on Job Node or job.
Select Sysout from the Action Menu.
This option opens a window that displays a list of the job’s Sysout (output) information.

Sysout Display :

Select the output element to view and click OK.

61
Hold
¾Right Click on Job Node or job.
¾Select Hold from the Action Menu changes the state of the job.

¾In the CONTROL-M/Enterprise Manager window, a padlock is added to the job node (shown
below).

¾If the job has not started to execute, it is prevented from executing even after all submission
criteria are satisfied. The job remains in this state until released using the Free option
(described below).

¾Any job that is executing when held will remain with Executing status until it is freed.

¾If the job has completed executing, it cannot be manually rerun until released by you via the
Free option.

62
Free & Kill
Free:
¾ This option removes the padlock from the job node of held job in the CONTROL-
M/Enterprise Manager window
¾ Right Click on Job Node.
¾ Select Free from the Action Menu.
¾ When freed by the user, the job resumes processing at whatever point it was stopped by the
Hold option.
¾ Before updating the details of any job, you must Hold the job. After updating, you should
Free the job so that it can continue processing.

Kill:
¾ This option terminates a job that is currently running and its processes.
¾ Right Click on Job Node or job.
¾ Select Kill from the Action Menu.
¾ The action is recorded in the job log
¾ Killing a specific instance of a cyclic job does not affect subsequent runs of that job.

63
Failure Analysis
When ever the job gets failed job status turns to Red.

Then we have to do the following

¾Rerun

¾Force OK – no Post Processing

¾Rerun :
Right Click on Job Node or job.
Select Rerun from the Action menu or job node popup
menu, or click the Rerun button.
This option reruns the job.

64
Failure Analysis

Force OK :

¾ Force OK – no Post Processing option changes the status of the job to Ended OK and
changes the color of the job node to green.

¾ Job post processing actions, however, are not performed. This option can be used for jobs
with a status of Ended Not OK or for jobs in a Wait status (such as Wait Time, Wait Cond).

¾ You can activate the option from the Action menu, or from the job node popup menu of jobs
that Ended Not OK.

65
Questions?

66