CONTROL-M is a solution that provides interoperable production control across diverse environments through a centralized management point. It uses a three-tier architecture with enterprise management, CONTROL-M servers, and CONTROL-M agents. Jobs are defined with details on what the job is, where it runs, who runs it, when it runs based on schedules and calendars, flow control using conditions, resource requirements, and results control.

1. CONTROL-M
Presentation
Control-M Presenation 1

2. Introducing CONTROL-M
CONTROL-M is an interoperable solution for
the integration of production control from a focal
point of management across diverse
environments
Challenges
Managing the enterprise vs. Platforms
Controlling the Business Process
Alert reactivity
Control-M Presentation 2

3. Control-m Architecture
Control-M Presentation 3

4. Three-Tier Architecture
TM
Enterprise Management
DB GUI
GATEWAY Engine
CONTROL-M/Server
GATEWAY DB
CONTROL-M Gateway
Server
UNIX
CONTROL-M/Agent
CONTROL-M CONTROL-M CONTROL-M
Agent Agent Agent
WINDOWS NT WINDOWS 2000 UNIX
Control-M Presentation 4

5. CONTROL-M/Agent
Control-M Agent CONTROL-M CONTROL-M
Agent Agent
WINDOWS NT UNIX
Run under Windows NT/200, Unix, etc …
Submit, monitor, control and manage jobs
Receive order from Control-M Server
Send result to Control-M Server
Control-M Presentation 5

6. CONTROL-M/Server
Control-M Server GATEWAY DB
CONTROL-M
Server
UNIX
It’s the engine of Control-M
Contain all job definitions
Contain all calendars
Activate and Control the « up to plan »
Control-M Presentation 6

7. TM
Enterprise Management
Enterprise Management
DB GUI
GATEWAY
Focal point of control
Standard GUI for all the Production platforms
Responsible for cross-platform dependencies
Give graphic tools to develop jobs
Control-M Presentation 7

8. Job Definitions
Control-M Presentation 8

9. Control-M Job Definition
What ?
Where ?
Who ?
When ?
Flow Control ?
Resource Requirements
Results Control
Control-M Presentation 9

10. What do we schedule
Unix shell scripts
/export/home/hipfeed/interfaces/scripts/ft_process.pl
NT Batch Files (.bat .cmd)
Wha
t
d:prodCtmCopy_Logsdel_logs.cmd
Executable
Operator Commands
Execute Command
ls -l
Control-M Presentation 10

11. Where do we run
Wha
t
Which server do we use
Does it have a Control-M Agent
Is it a Production or a Uat agent
Control-M Presentation 11

12. Who can execute it
Wha
t
Which user login is needed to run the job
Does the user login have access right to run the job.
Control-M Presentation 12

13. When : Date & time Scheduling Criteria
Specific days of the month/week/period
When
Automatic holiday processing
The nth workday
The nth last workday
Time window
Job can be executed in several times in cyclic mode
with personnal interval
Control-M Presentation 13

14. When : Selecting a Date
Run every: 1st, 2nd,
When
3rd, 4th, 7th and 23rd
of the month.
Run every: Monday,
Wednesday, Friday
Depend to
working days
Control-M Presentation 14

15. When : Calendars
UK Working Days
Calendar for Year 2002
When
No Run :
Bank Holidays
Control-M Presentation 15

16. When : Complex Dates
Run on the 4th of the
When
month, in addition to
the day in WD
Calendar
Last Working
Day of the
month
Control-M Presentation 16

17. What is a condition
Is a Flag sent in
PREREQUISITE
CONDITIONS BOX under
Enterprise ControlStation
Flow
This Flag can be expected
Cont
rol by one or several other jobs.
It is not a « goto » command
A condition depends to the ODAT
(Control-M Systeme Date)
Control-M Presentation 17

18. Condition Process
START – JOB-OK
START
START – JOB-NOK
NOT OK OK
(exit 1) (exit 0)
START – JOB-NOK Exist ? START – JOB-OK Exist ?
Yes or No Yes or No
Flow
Cont
rol
JOB-OK - END
JOB-NOK JOB-OK
JOB-NOK - END
Prerequisite
Conditions
Box
JOB-NOK - END JOB-OK - END Exist ?
OR Yes or No
END
Control-M Presentation 18

19. Complex Dependencies
Flow
Cont
rol
Many jobs can depend on one
condition
One job can depend on many
conditions
Combination of conditions -
AND/OR
Control-M Presentation 19

20. Benefits
Cross-platform automation flow
No need for manual intervention
Create a Business Process View
Flow
Create a Focal Point of Control
Cont
rol
Control-M Presentation 20

21. Resource Requirement
Prevents resource contentions between jobs
Provides workload balancing
Eliminates contention bottlenecks
Control-M Presentation 21

22. Results Control
Capture Standard OUTPUT in Sysout
Sysout contain and Error Code will be tested
Resu
Shout Message can be sent to User Mail, Distribution
lts Co
ntrol
List, Console ...
Rerun Facility
Runs same job « n » times
Runs another job
Stop a Cyclic Job
Control-M Presentation 22

23. Job Process
Control-M Presentation 23

24. Dynamic Scheduling
JOB-B
JOB-A
JOB-C
We can accumulate
Conditions JOB-D
Schedule Date and Time
Quantitative Resource
Control-M Presentation 24

25. Schedule PLAN
To be executed, a job should be up to plan.
A plan is a period of 24 hours
The plan begins at 7:00 AM (for that example)
The plan stops at 6h59 AM the following day
The Control-M System Date isn’t a System Date
ODAT – Control-M System Date
11/11 12/11 13/11 14/11
00:00 07:00 00:00 07:00 00:00 07:00
12/11/2002 13/11/2002 14/11/2002
SYSTEM DATE
Control-M Presentation 25

26. Dynamic Scheduling
If all goes well ...
JOB-B
JOB-A
JOB-C
JOB-D
Control-M Presentation 26

27. Dynamic Scheduling
Problem ...
JOB-B
JOB-A
JOB-C
Exit code 8
JOB-D
Control-M Presentation 27

28. Dynamic Scheduling
Other Problems ...
JOB-B
JOB-A
Restart-DB
JOB-C
JOB-D
Exit code 16
“DB Closed”
Control-M Presentation 28

29. Dynamic Scheduling
Many Problems ...
JOB-B
JOB-A
Restart-DB Clear-DB
JOB-C
Exit code 8
JOB-D
Exit code 16
“DB Closed” Exit code 32
“DB Error”
Control-M Presentation 29

30. Result Analysis
Control-M Presentation 30

31. Error Recovery Process
Job
Ended
Exit Code Job’s Output
Result Analysis
OK Not OK
Actions Actions
Actions Actions
Actions Actions
Control-M Presentation 31

32. Result Analysis
CONTROL-M is capable of detecting errors and react
to them dynamically
Analyze contents of the Job Log
Match Line of statement with statement ouput and
errors (contain of sysout)
Actions :
Set completion status to Ok or NOTOK
Set a parameter value (counter)
Create or delete a condition
Force a job to run
Notify a user or console message
Rerun the job
Stop Cyclic
Control-M Presentation 32

33. Result Analysis – Control-M Logs
Control-M Presentation 33

34. Result Analysis – Job Sysout
Control-M Presentation 34

35. Result Analysis - Unix
Unix
$ cp /etc/passwd /tmp
$ cp /etc/passwdx /tmp
cp /etc/passwdx: No such file or directory
$ cp /etc/passwd /usr/kvm/xyzzy
cp: /usr/kvm/xyzzy: Permission denied
$ exit 12
On Statement/Code examples for this job:
On Stmt cp /etc/passwdx/tmp
Code No such file or directory (the string 'no*file‘
will also work - see wild card characters above)
On Stmt cp /etc/passwd/usr/kvm/xyzzy
Code cp *: Permission denied
Control-M Presentation 35

36. Result Analysis - NT/2000
NT
E:fcopy -recover -context_file="fccf_00007"
FCOPY-I-CMD_LINE - Original command was :
fcopy "E:fastcopy*.doc" "nt-tlv2tmp" -report -user="fctest" -
password=PASSWORD -replace -context_file="fccf_00007"
FCOPY-E-CONNECTREF, could not connect to node nt-tlv2
-SYS-E-ERRMSG, Connection refused
On Statement/Code examples for this job:
On Stmt fcopy*
Code *could not connect to node nt-tlv2*
Control-M Presentation 36

37. Error Message
Regular (Green)
Message for information
Use to keep log information
No Pilote Action
Urgent (Orange)
Warning Message
Need Pilote acknowledgement
Not a Critical Problem
Very Urgent (Red)
Critical Message
Need Pilote acknowledgement
Critical Problem, need immediate action
Control-M Presentation 37

38. What do we need
For the Control-M Diagram
A Organization Chart of the treatments
An Application Architecture Diagram
For Each Job Definitions
External parameters and processes
Command Line or Executable
User Login
Scheduling Criteria (Date, Time, Calendar...)
Error code and Error Message Received and To be
Sent
Actions List, Order for each error
Control-M Presentation 38