OVERVIEW OF

CONTROL-M / EM 7.0
FOR APPLICATION
SUPPORT
• Click to add text

Updated: July 2013

TOPICS COVERED
 What is CONTROL-M?
 Architecture of CONTROL-M/Enterprise Manager
 Basic components
 CONTROL-M Terminology
 How to log-on to CTLAccess
 How to log-on to CONTROL-M/Enterprise Manager
 Getting around in CONTROL-M/Enterprise Manager
 Operator Functions in Active Jobs File
 Accessing CONTROL-M/Desktop
 User Daily Process
Scheduling Requests Severity Levels
Roles and Responsibilities
Want to use Control-M to Schedule your Application?
WHAT IS CONTROL-M?

 Business integrated scheduling product that focuses on the production

environment's business applications and platforms
 Provides advanced production-scheduling capabilities across the
enterprise from a single point of control
 Solution to manage and integrate dissimilar applications into one
business flow, assuring service levels are met
 CONTROL-M Environment
Control-M Control-M DB

D
U
O
P
W
L
N
Global O
L
Conditions A
O
D
Server A
D
Enterprise
Global Enterprise
Manager
Alerts Manager
Server DB
W R
R
E
Administration I
A
Facility T
D
E
Control-M/Desktop
(Scheduling Table
Manager)
BASIC COMPONENTS
 Control-M/Enterprise Manager
 Enterprise Manager GUI
 Enterprise Manager GUI Server
 Enterprise Manager Database
 Control-M Desktop

 Control-M Components
 Control-M Server
 Control-M Database
 Control-M Monitor

 Gateways

 Global Conditions Server

 Global Alerts Server

 Administration Facility

 Reporting Facility
Control-M Enterprise Manager
 Enterprise Manager GUI
Centralized GUI-based control center used to manage scheduling functions and
monitor workflow activities

 Enterprise Manager GUI Server

Handles communication between each CONTROL-M/EM GUI and the other
components of CONTROL-M/EM

 Enterprise Manager Database

Repository for all CONTROL-M/EM information

 Control-M Desktop
Used to define and manage job processing definitions, scheduling tables and
calendars

Control-M Components
 Control-M Server
Exchanges operations data with CONTROL-M/EM and maintains CONTROL-M
database

 Control-M Agent
Executes job-handling requests received from CONTROL-M/Server
Control-M Monitor
Heart of the CONTROL-M Production Control System and responsible for many
functions, including submitting jobs in the Active Jobs file for execution, tracking
jobs, and analyzing execution results

Gateway
Communication between CONTROL-M and CONTROL-M/EM

Global Condition Server

Distributes global conditions for job dependencies between Data Centers

Global Alerts Server

Uses CONTROL-M/EM gateways to distribute alert messages to the appropriate
CONTROL-M installations

Administration Facility Agent

Starts and stops the CONTROL-M/EM components and maintains contact with the
CONTROL-M/EM database

Reporting Facility
Facility for generating reports about CONTROL-M/EM functioning
BASIC TERMINOLOGY
 Job
Script, Started Task, Daemon, Detached process, Cyclic Job, Process, Job
 Scheduling Table
Group of jobs based on certain criteria
 Condition
Flag representing a user-specified situation or set of circumstances
 Schedule Criteria
Terms and conditions required to run a specific job or a job stream (E.g. Time, Day,
Condition)
 Calendar
Used to specify what days of the year a job needs to be run
 Active Jobs File
Consists of a copy of all job definitions “eligible to run” on a given day
 ViewPoint
Collection of objects logically grouped in a graphical display
Logging on to CTLAccess
 From internet browser, go to CLTAccess
https://ddc.ctlaccess.centurylink.com/QAccess/loginAction!input

To log on to CTLAccess, type your CUID in the User ID field, and your CUID
Password in the Password field, then click Log In
Logging on to Control-M/Enterprise Manager

 In the CTLAccess screen locate the Control-M 7 Icons:

CTL-M 7 Enterprise Manager

CTL-M 7 Desktop

CTL-M 7 Reporting Facility

Logging on to Control-M/Enterprise Manager (continued)

 Login window for Control-M/Enterprise Manager appears

 Login using the userid and password
Logging on to Control-M/Enterprise Manager (continued)
 To change SERVER to ctmdnt or ctmprd
Click on ADVANCED
In HOSTNAME enter ctmdnp for production or ctmdnt for test
Click APPLY SETTINGS
 Login using the userid and password
Note:
The Control-M login screen will differ between Domain AD_CTL users
converted to using LDAP password and EM user not converted
Control-M/Enterprise Manager – Main window

 After successful login to Control-M/Enterprise Manager, primary window to

access different parts of Enterprise Manager appears
Active Jobs File
 From Enterprise Manager click on
File -> Open ViewPoint
 “Open ViewPoint” window appears
 Jobs can be monitored /
manipulated by selecting specific
criteria (ViewPoints)
 Select a ViewPoint and click OK
To view job activity from the selected ViewPoint
 Display of Active Jobs File based on ViewPoint criteria
Drilling down to the job

Double clicking on each category

Data Center
also works

Application
table

Group

Job
Operator Functions in AJF
 Right-clicking on the job will provide a list of operations that can be performed
on the job (can also be selected under action)
 Operators can perform manual operations on the jobs like hold, confirm,
delete, re-run or view job details
Operator Functions in AJF (continued)
Job Colors in ‘Active Jobs File’ and what they mean

COLOR STATUS MEANING

GRAY Wait Status or Waiting for Time or
Wait Agent Platform Pre-requisite Condition
PINK Wait User Waiting for Confirmation
BLUE Wait Resource  Waiting for control or quantitative resource
 Waiting for nodes resources to become
available for job submission
 Waiting due to restrictions enforced by
workload policy rules

YELLOW Executing Executing

GREEN Ended OK Processing Finished Successfully

RED Ended Not OK or Processing finished unsuccessfully or Agent

Disappeared platform where job was running was changed to
DISABLED by an user
WHITE Unknown Communication with the Agent platform was
interrupted

PURPLE Not in AJF Job is not in the Active Job File. This status is only
displayed in the archived View Points
To order / force a job to run
 Place job in AJF via Order or
Force (from Enterprise Manager)
 Order adds job only if scheduling
criteria is satisfied
 Force always adds job - ignores
scheduling criteria
 Tables or Individual jobs can be
Ordered or Forced

 To order / force a table or job,

click on “Tools”  ”Order/Force”
 “Order/Force Jobs” window
appears
 Fill-in the Table/Job details and
click on order/force.
To order / force a job with a ‘Hold’ or to ‘Wait for a
future ODate’ to run.

 Select the job, click the ‘Advanced <<‘

button and the Order/Force with Hold
section will appear.

 To view the scheduling definition

properties for a specific job

 Check the ‘Order/Force with Hold’ box and

the job will be in Held status when added
to the AJF.

 To add a job to the AJF with a specific

ODate, mark the date box and select the
desired date. If job is to not run until the
selected date, check the ‘Wait for ODate
to run’ box.
 Viewing application tables / jobs definitions in Enterprise
Manager
 Under Tools choose
“CONTROL-M/Desktop…”

 “CONTROL-M/Desktop”
window appears
Viewing application job definitions in Enterprise Manager
(continued)

 Under Tools click on Table Manager

Viewing application job definitions in Enterprise Manager
(continued)
 Select the appropriate Control-M
Click on the desired table, then click on “Jobs List” button or
double click on the desired table.
Viewing application job definitions in Enterprise Manager
(continued)
 Double click on the desired job or click on the “View/Edit Properties”
button
Viewing application job definitions in Enterprise Manager
(continued)
 This displays the “Job Editing Form” (detailed information about job)
 Includes name of job, server it runs on, day and time it is scheduled
to run, etc.
 Order/Force a Table/Job from Control-M Desktop
Select a table in Scheduling Table Manager and click on ‘Order’

Options are Upload table before ordering, Force, or Order/Force with a ‘Hold’.
New Day Process and User Daily

New Day Process

 Runs everyday at 00:10 AM (Mountain Time)
 Scans the scheduling tables assigned to it (Userdaily name of SYSTEM)
 Places potential job orders in the Active Jobs file & assigns unique order ID’s
 Orders User Daily jobs

User Daily Job

 Reviews job tables with a specific User Daily name
 Resolves scheduling criteria
 Adds all jobs scheduled to run today to the Active Jobs file
 More than 20 user dailies (For every Application, Time based) execute at
different times to bring-in new jobs into AJF throughout the day
Production User Daily Jobs

User Daily Run Time Description

(Mountain Time)
ARMS_UDLY 01:00 Scans and Schedules ARMS jobs CTMOMP
CDW_UDLY 00:15 Scans and Schedules CDW jobs CTMDNP
CURT_UDLY 03:00 Scans and Schedules CURT jobs CTMDNP

DIRB_UDLY 15:00 Scans and Schedules DIRB jobs CTMDNP / CTMOMP

RAS_UDLY 02:45 Scans and Schedules RAS jobs CTMDNP / CTMOMP

RUP0-UDLY-0015 00:15 Scans and scheduled RUP jobs CTMDNP

RUP2-UDLY-0030 00:30 Scans and scheduled RUP jobs CTMDNP

RUP4-UDLY-0100 01:00 Scans and scheduled RUP jobs CTMDNP

T0015_UDLY 00:15 Scans and Schedules any Application job CTMDNP / CTMOMP

T0020_UDLY 00:20 Scans and Schedules any Application job CTMDNP / CTMOMP

T0025_UDLY 00:25 Scans and Schedules any Application job CTMDNP

T0030_UDLY 00:30 Scans and Schedules any Application job CTMDNP / CTMOMP

T0045_UDLY 00:45 Scans and Schedules any Application job CTMDNP / CTMOMP

T0115_UDLY 01:15 Scans and Schedules any Application job CTMDNP / CTMOMP

T0315_UDLY 03:15 Scans and Schedules any Application job CTMDNP / CTMOMP

T0645_UDLY 06:45 Scans and Schedules any Application job CTMDNP / CTMOMP

T1115_UDLY 11:15 Scans and Schedules any Application job CTMDNP / CTMOMP

T1545_UDLY 15:45 Scans and Schedules any Application job CTMDNP / CTMOMP
Scheduling Requests Severity Levels
Hours of Operation:

Normal Business hours: Mon – Fri (07:00 – 15:00 MDT/MST)

Non-business hours: Mon - Fri (15:00 - 07:00 MDT/MST), Saturday, Sunday and Holidays

Severity Submit Date Submit Time Due Page Email

(MST/MDT )

0 Sun-Sat, Holiday 0000 - 2359 Within 60 minutes Yes  Yes

1 Sun-Sat, Holiday 0000 – 2359 Same day, Yes Yes

before newday or
specific user daily

2 Sun-Sat, Holiday 0000 - 2359 Within 3 business days  No Yes

3 Sun-Sat, Holiday 0000 - 2359 3 to 5 business days No Yes

Scheduling requests
1) for new applications,
2) containing more than 30 changes require a minimum lead time of 5-7 business days.
 Roles and Responsibilities
Scheduling:
1. Create, maintain, and modify job definitions according AIP’s or developer's specifications.
2. Verify accuracy and content of newly created and /or modified job definitions prior to implementation.
3. Provide consultation to developers and AIP to improve production job efficiency.
4. Provide consultation to developers in the creation of test job definitions on the test and development
machines
5. Meet time frames for new/modified job definitions according to negotiated schedule.
6. Pre-Production Setup
7. Eliminate manual interventions by automation whenever possible.
8. Review subsequent job streams changes.
9. Measure manual interventions and scheduling errors.
10. Communicate impacting Control-M changes to development and/or AIP within 24 hours of application
impact.
11. Test new revisions of Control-M and EM for functionality of improvements and fixes.

Control-M Tool Support:

1. Tier 1 support for Control-M and EM.
2. Control-M, EM, and agent software upgrade installations.
3. Monitor Control-M, EM, and production and test server availability.
4. Develop and maintain Scheduling team support scripts
5. Automation
Want to use Control-M to schedule your application?

The website below contains documents related to UNIX Control-M

http://collaboration.ad.qintra.com/BU/IT/scph/UnixCTM/Shared%20Documents/Forms/AllItems.aspx
- How to Request Control-M Service
- Scheduling Calendars
- User Daily
- Calendars
- Auto edit files
- Escalation Procedures
- -etc...

Control-M FAQ information and Standards for Control-M job definitions can be found at website:

http://controlm.uswc.uswest.com/midrange/index.html

w
DOCUMENTATION

 More documentation is available on Control-M cshare site

http://collaboration.ad.qintra.com/BU/IT/scph/UnixCTM/SitePages/Home.aspx
in the Shared Documents Library
or
http://collaboration.ad.qintra.com/BU/IT/scph/UnixCTM/Shared
%20Documents/Forms/AllItems.aspx


SESSION I – OVERVIEW OF CONTROL-M EM7.0

SESSION II – SCHEDULING USING CONTROL-M EM
7.0
QUESTIONS?
For Midrange Control-M questions or problems contact the Regional
Control-M Scheduling & Support Team via:
 An email to [email protected]
 A Remedy Work Order – assignment group DCO-NONMVS-SCHEDULING
 Page the oncall – NET PIN: 12825
NET PIN GROUP: UNIX CONTROL-M

NOTE:
Control-M Job adds, changes, deletes;User ID password resets;
and request for access to the Control-M Enterprise Manger GUI
must be requested via website

http://controlm.uswc.uswest.com/midrange/index.html

Click on FORMS, select the required form, complete and submit.

THANK YOU!

• Click to add text