Professional Documents
Culture Documents
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
ViewPoint
Collection of objects logically grouped in a graphical display
Logging on to QAccess
From internet browser, go to QAccess
Data Center
Application
Group
Job
table
STATUS
MEANING
Grey
Pink
Wait user
Blue
Wait Resource
Yellow
Executing
Executing
Green
Ended OK
Red
Ended Not OK or
Disappeared
White
Unknown
CONTROL-M/Desktop
window appears
Run Time
Description
ARMS_UDLY
01:00
CDW_UDLY
00:15
CURT_UDLY
03:00
DIRB_UDLY
15:00
FLEET_UDLY
00:20
T0045_UDLY
00:45
T0115_UDLY
01:15
T0315_UDLY
03:15
T0645_UDLY
06:45
T1115_UDLY
11:15
T1545_UDLY
15:45
Severity
Submit Date
Page
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
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.
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.
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!