You are on page 1of 31

OVERVIEW OF

CONTROL-M / EM 6.3
FOR APPLICATION
SUPPORT

TOPICS COVERED
What is CONTROL-M?
Architecture of CONTROL-M/Enterprise Manager
Basic components
CONTROL-M Terminology
How to log-on to QAccess
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

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

BASIC COMPONENTS

Control-M/Enterprise Manager
Control M EM is used for monitoring of job or applications.
It has set of control properties which is used to perform certain actions like
HOLD, DELETE, FORCE OK, LOG, SYSOUT etc. useful for monitoring
prospective.

Control-M Desktop
Control M desktop is used to design, develop and schedule jobs or
applications. It has set of properties like GENERAL, SCHEDULING,
CONDITION etc.

Control M Database:
Control M database is responsible for storing the tables and scheduling
details of jobs or applications created

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

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 QAccess
From internet browser, go to QAccess

Logging on to QAccess (continued)

To use Desktop Client, download of QAccess Desktop Client from website


below is required.
https://web.qaccess.qwest.com/Download/index.html

Logging on to Control-M/Enterprise Manager


Under Qwest Apps click on Control-M Enterprise Manager GUI

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


Login window for Control-M/Enterprise Manager appears
Login using the userid and password

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

Data Center

Double clicking on each


category also works

Application
Group

Job

table

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, 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

Grey

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

Yellow

Executing

Executing

Green

Ended OK

Processing finished successfully

Red

Ended Not OK or
Disappeared

Processing finished unsuccessfully or Agent


platform where job was running was changed to
Disabled by a user

White

Unknown

Communication with the Agent platform was


interrupted

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.

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 future


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 job 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 Scheduling Table Manager

Viewing application job definitions in Enterprise Manager


(continued)
Click on the desired table and then click on Jobs List button

Viewing application job definitions in Enterprise Manager


(continued)
Double click on the desired job or click on the Update 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

Now have an option to Order/Force with a Hold. . . New with 6.3

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 IDs
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

User Daily Jobs


User Daily

Run Time

Description

(All times are


Mountain Time)

ARMS_UDLY

01:00

Scans and Schedules ARMS jobs

CDW_UDLY

00:15

Scans and Schedules CDW jobs

CURT_UDLY

03:00

Scans and Schedules CURT jobs

DIRB_UDLY

15:00

Scans and Schedules DIRB jobs

FLEET_UDLY

00:20

Scans and Schedules FLEET jobs

T0045_UDLY

00:45

Scans and Schedules any Application job

T0115_UDLY

01:15

Scans and Schedules any Application job

T0315_UDLY

03:15

Scans and Schedules any Application job

T0645_UDLY

06:45

Scans and Schedules any Application job

T1115_UDLY

11:15

Scans and Schedules any Application job

T1545_UDLY

15:45

Scans and Schedules any Application job

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

Page

Email

Sun-Sat, Holiday

0000 - 2359

Within 60 minutes

Yes

Yes

Sun-Sat, Holiday

0000 2359

Same day,
before newday or
specific user daily

Yes

Yes

Sun-Sat, Holiday

0000 - 2359

Within 3 business days

No

Yes

Sun-Sat, Holiday

0000 - 2359

3 to 5 business days

No

Yes

Submit Time

Due

(MST/MDT )

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.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.

Create, maintain, and modify job definitions according AIPs or developer's specifications.
Verify accuracy and content of newly created and /or modified job definitions prior to implementation.
Provide consultation to developers and AIP to improve production job efficiency.
Provide consultation to developers in the creation of test job definitions on the test and development
machines
Meet timeframes for new/modified job definitions according to negotiated schedule.
Pre-Production Setup
Eliminate manual interventions by automation whenever possible.
Review subsequent job streams changes.
Measure manual interventions and scheduling errors.
Communicate impacting Control-M changes to development and/or AIP within 24 hours of application
impact.
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

QUESTIONS?
Contact the Regional Control-M Scheduling & Support Team via
an email to sreques@qwest.com,
a Remedy Work Order assignment group DCO-NONMVS-SCHEDULING
or
Page the oncall NET PIN 12825

THANK YOU!

You might also like