Control-M/Server
The Control-M/Server is the heart of
Control-M Workload Automation. In the
background, it submits jobs onto job
execution hosts according to their dependencies
and priorities and tracks their status until
the execution completes. Just the same as
Control-M/Enterprise Manager,
Control-M/Server for distributed systems stores
information in its own database. (The reason
we specifically stated distributed
systems here, is because Control-M for
mainframe stores information in data files
rather than a database.) The stored
information includes static job definitions, active
jobs (AJF), job execution statistics, job
logs, and so on.
Control-M/Server for distributed systems can
be installed on Windows, Unix, or
Linux machines. Control-M/Enterprise Manager
and Control-M/Server can share
the same machine and same database, but users
normally separate the two for
production environment to get better
performance and in case of increase in load in
the future.
Control-M/Server processes
Control-M/Server is a collection of 9 core
background processes, plus 1 configuration
agent process (introduced since version
6.3.01). Each process has its own role, such
as being in charge of internal communication,
communication with Control-M/
Enterprise Manager, communication with
Control-M/Agents, or handling job
submission, tracking, and logging. Each
process also generates its own log file for
error diagnosis and monitoring. These
processes are:
• SU:
Supervisor
• SL: Job
Selector
• TR: Job
Tracker
• NS: Network
Services
• CE: New Day
and EM Communication Process
• CS: Client
Service Process
• LG: Logger
• WD: Watch
DogRT – Internal Communication Router
• CA: Control-M/Server Configuration
Agent (Additional).
Processes Status
R Running
S Suspended
T
or Z Terminated
No comments:
Post a Comment