CONTROL-M Presentation Introducing CONTROL-M CONTROL-M is an - - PDF document

control m presentation introducing control m
SMART_READER_LITE
LIVE PREVIEW

CONTROL-M Presentation Introducing CONTROL-M CONTROL-M is an - - PDF document

1 Control-M Presenation CONTROL-M Presentation 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


slide-1
SLIDE 1

Control-M Presenation 1

CONTROL-M Presentation

slide-2
SLIDE 2

Control-M Presentation 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

slide-3
SLIDE 3

Control-M Presentation 3

Control-m Architecture

slide-4
SLIDE 4

Control-M Presentation 4 CONTROL-M/Agent

Three-Tier Architecture

Enterprise Management DB GUI GATEWAY Engine

TM

UNIX CONTROL-M Agent WINDOWS NT CONTROL-M Agent

UNIX

DB GATEWAY CONTROL-M Server

CONTROL-M/Server

Gateway

WINDOWS 2000 CONTROL-M Agent

slide-5
SLIDE 5

Control-M Presentation 5

Control-M Agent

CONTROL-M/Agent

Run under Windows NT/200, Unix, etc … Receive order from Control-M Server Submit, monitor, control and manage jobs Send result to Control-M Server

UNIX CONTROL-M Agent WINDOWS NT CONTROL-M Agent

slide-6
SLIDE 6

Control-M Presentation 6

Control-M Server

It’s the engine of Control-M Contain all calendars Contain all job definitions Activate and Control the « up to plan »

UNIX

DB GATEWAY CONTROL-M Server

CONTROL-M/Server

slide-7
SLIDE 7

Control-M Presentation 7

Enterprise Management

Focal point of control Responsible for cross-platform dependencies Standard GUI for all the Production platforms Give graphic tools to develop jobs

Enterprise Management DB GUI GATEWAY

TM

slide-8
SLIDE 8

Control-M Presentation 8

Job Definitions

slide-9
SLIDE 9

Control-M Presentation 9

Control-M Job Definition

What ? Where ? When ? Resource Requirements Flow Control ? Results Control Who ?

slide-10
SLIDE 10

Control-M Presentation 10

What do we schedule

Unix shell scripts

/export/home/hipfeed/interfaces/scripts/ft_process.pl

NT Batch Files (.bat .cmd)

d:\prod\Ctm\Copy_Logs\del_logs.cmd

Executable Operator Commands

W h a t

Execute Command ls -l

slide-11
SLIDE 11

Control-M Presentation 11

Where do we run

Does it have a Control-M Agent Is it a Production or a Uat agent

W h a t

Which server do we use

slide-12
SLIDE 12

Control-M Presentation 12

Who can execute it

Does the user login have access right to run the job.

W h a t

Which user login is needed to run the job

slide-13
SLIDE 13

Control-M Presentation 13

When : Date & time Scheduling Criteria

Specific days of the month/week/period Automatic holiday processing The nth workday Time window The nth last workday

When

Job can be executed in several times in cyclic mode with personnal interval

slide-14
SLIDE 14

Control-M Presentation 14

When : Selecting a Date

When

Run every: 1st, 2nd, 3rd, 4th, 7th and 23rd

  • f the month.

Depend to working days Run every: Monday, Wednesday, Friday

slide-15
SLIDE 15

Control-M Presentation 15

When : Calendars

When

UK Working Days Calendar for Year 2002 No Run : Bank Holidays

slide-16
SLIDE 16

Control-M Presentation 16

When : Complex Dates

When

Run on the 4th of the month, in addition to the day in WD Calendar Last Working Day of the month

slide-17
SLIDE 17

Control-M Presentation 17

What is a condition

F l

  • w

C

  • n

t r

  • l
  • Is a Flag sent in

PREREQUISITE CONDITIONS BOX under Enterprise ControlStation

  • A condition depends to the ODAT

(Control-M Systeme Date)

  • This Flag can be expected

by one or several other jobs.

  • It is not a « goto » command
slide-18
SLIDE 18

Control-M Presentation 18

Condition Process

F l

  • w

C

  • n

t r

  • l

START – JOB-OK START – JOB-NOK JOB-OK - END JOB-NOK - END

Exist ? Yes or No Exist ?

START END JOB-OK JOB-NOK

NOT OK (exit 1) OK (exit 0) Prerequisite Conditions Box

Yes or No

START – JOB-NOK START – JOB-OK JOB-OK - END OR JOB-NOK - END

Yes or No Exist ?

slide-19
SLIDE 19

Control-M Presentation 19

Complex Dependencies

F l

  • w

C

  • n

t r

  • l

Many jobs can depend on one condition One job can depend on many conditions Combination of conditions - AND/OR

slide-20
SLIDE 20

Control-M Presentation 20

Benefits

F l

  • w

C

  • n

t r

  • l
  • Cross-platform automation flow
  • No need for manual intervention
  • Create a Business Process View
  • Create a Focal Point of Control
slide-21
SLIDE 21

Control-M Presentation 21

Resource Requirement

  • Prevents resource contentions between jobs
  • Provides workload balancing
  • Eliminates contention bottlenecks
slide-22
SLIDE 22

Control-M Presentation 22

Results Control

  • Capture Standard OUTPUT in Sysout
  • Shout Message can be sent to User Mail, Distribution

List, Console ...

  • Rerun Facility

Runs same job « n » times Runs another job Stop a Cyclic Job

Results Control

  • Sysout contain and Error Code will be tested
slide-23
SLIDE 23

Control-M Presentation 23

Job Process

slide-24
SLIDE 24

Control-M Presentation 24

Dynamic Scheduling

  • We can accumulate

Conditions Schedule Date and Time Quantitative Resource

JOB-D JOB-C JOB-B JOB-A

slide-25
SLIDE 25

Control-M Presentation 25

00:00 00:00 00:00 12/11/2002 13/11/2002 14/11/2002

SYSTEM DATE

  • The Control-M System Date isn’t a System Date

Schedule PLAN

  • To be executed, a job should be up to plan.

07:00 07:00 07:00

12/11 13/11 14/11 11/11

ODAT – Control-M System Date

  • 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
slide-26
SLIDE 26

Control-M Presentation 26

Dynamic Scheduling

If all goes well ...

JOB-D JOB-C JOB-B JOB-A

slide-27
SLIDE 27

Control-M Presentation 27

Dynamic Scheduling

JOB-D

Problem ...

Exit code 8

JOB-C JOB-A JOB-B

slide-28
SLIDE 28

Control-M Presentation 28

Dynamic Scheduling

JOB-C

Other Problems ...

Exit code 16 “DB Closed” Restart Restart-

  • DB

DB

JOB-D JOB-B JOB-A

slide-29
SLIDE 29

Control-M Presentation 29

Dynamic Scheduling

JOB-C

Many Problems ...

Clear Clear-

  • DB

DB

Exit code 32 Exit code 32 “ “DB Error DB Error” ”

Exit code 16 “DB Closed” Restart Restart-

  • DB

DB

JOB-D JOB-B JOB-A

Exit code 8

slide-30
SLIDE 30

Control-M Presentation 30

Result Analysis

slide-31
SLIDE 31

Control-M Presentation 31

Error Recovery Process

Job Ended

OK Not OK Exit Code Job’s Output

Actions Actions Actions Actions Actions Actions

Result Analysis

slide-32
SLIDE 32

Control-M Presentation 32

Result Analysis

  • 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 is capable of detecting errors and react

to them dynamically

slide-33
SLIDE 33

Control-M Presentation 33

Result Analysis – Control-M Logs

slide-34
SLIDE 34

Control-M Presentation 34

Result Analysis – Job Sysout

slide-35
SLIDE 35

Control-M Presentation 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

slide-36
SLIDE 36

Control-M Presentation 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-tlv2\\tmp" -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*

slide-37
SLIDE 37

Control-M Presentation 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

slide-38
SLIDE 38

Control-M Presentation 38

What do we need

  • For the Control-M Diagram
  • A Organization Chart of the treatments
  • An Application Architecture Diagram
  • For Each Job Definitions
  • 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
  • External parameters and processes