control-m training doc

7/24/2019 Control-M Training Doc

1/27

294804987.doc

Control-M Training Document

Document Type: Training


Page 1


2/27

294804987.doc

Training

Introduction

CONTROL M automates job processing in our data center.

It performs virtually all the job handling tass of computer

operators.

It provides a user interface !hich enables the user to intervene inthe process of production management.

It provides continual data and status information regarding jobprocessing.

CONTROL M contains many facilities and components. "oring together#they all serve to automate your data center. This section introduces thesefacilities and components from a functional perspective# beginning !ith themajor components !hich comprise the heart of CONTROL M and

progressing to the more minor components !hich enhance the functionalityof CONTROL M.

Main Components

The follo!ing components are essential to CONTROL M$

%ob scheduling de&nitions

'ctive %obs &le

CONTROL M monitor

Objective:

The purpose of this document is to describe the speci&c %ob handlingsubmitted via CONTROL(M.

This document !ill provide the frame!or and functional overvie! of the)MC CONTROL(M


Page 2


3/27

294804987.doc

Logging into BMC Control-MTo log into Control(M double clic on the Control(M *nterprise Managericon on the destop.

CONTROL-M Enterprise Manager GUI 6.2.01.lnk

The follo!ing logon screen !ill appear.

To login to the di+erent environments select the 'dvanced button$

,or -rod $ ost Name$ //Host Name>>

-ort Number$

,or 0' $ ost Name$ //Host Name>>

-ort Number$

,or T1T$ ost Name$ //Host Name>>

-ort Number$ Once the connection settings are entered clic 'pply settings.1erver should be ost Name.

2ser Id3 cavie! -ass!ord$ 4initial is Temp556 /cliclogin7

' ne! session !ill need to be opened for each -rod# 0'# and T1T.


Page 3


4/27

294804987.doc

"hen logging in the follo!ing screen !ill appear$

All Active Jobs$ 'll jobs !aiting8completed for the current scan

day

All Jobs$ 'll jobs scanned in for day including jobs that havebeen deleted. 9eleted jobs !ill be removed at the ne:t daysscan.

Dynamic Filter$ the dynamic &lter can be used to &lter formore speci&c information

'll 'ctive %obs is mostly used. Clic O;. This also can be added as adefault so it !ill login to the same place every time.

*nterprise Manager


5/27

294804987.doc

Current 'ctive ,ile 4ActiveJob File =AJF6

Ctm>prod 3 Control M *nvironment

'pplication


6/27

294804987.doc

Nodes

Change Title to %O)>N'M* /O;7


Page 6


7/27

11/14/2015 11/14/2015 294804987.doc

1 NODES & NODE GRO!S

Node"' node is a place for !or to be performed. It could be a 2NI? node# a NTnode or it could be a printer. ' node must be de&ned to the !orload serverso that the server no!s that is has a !orload client and no!s the name

of that client. ' client must also de&ne a node name for the !orload serverto be de&ned to the client.

Node: Node name !ill be the server name

Node Grou#"The node group pro&le de&nes a group of nodes !here !or can beperformed so that you can schedule !or to multiple nodes or the bestavailable node in a group. 2sing this approach re@uires that you have all

needed resources for the job on every server that is de&ned to this nodegroup.

$ C%LEND%RS

%obs are scanned in to the job tracing system# using de&ned calendars !ithdates and8or times de&ned to the job.


Page 7


8/27

11/14/2015 11/14/2015 294804987.doc

RESORCES !RO'ILES

Resource pro&les are used for !orload balancing. To de&ne a resourcepro&le# go to Control(M *nterprise Manager 4if not currently logged in thenlog in to desired environment6. 1elect Resources.

There are four types of resources in Control M

Prerequisite Conditions$ The out conditions sent out by jobsthat have completed successfully. These can be removed

manually if a job stream8job needs to be rerun.

Control Resource$ Not currently used. Resources that arede&ned as e:clusive or shared.

Quantitative Resource$ Resources de&ned by @uantity.1tandards$ all jobs re@uire anASI>'LL and C-2Anodename@uantitative resource. 2sed to stop speci&c jobs from runningdue to scheduled outages.

lobal Conditions$ Not currently used. a special case ofprere@uisite conditions that create job dependencies bet!eenCONTROL(M installations.


Page 8


9/27

11/14/2015 11/14/2015 294804987.doc

( 'ILE )%*C+

,ile "atch constantly !atches for a speci&ed &le on a node. Once the &lede&ned is seen the &le !atch job !ill !atch the &le for :: amount of time to!atch it gro!. Once the number of iterations to !atch the speci&ed &le hasbeen met the &le !atch job !ill post a condition so the job !aiting for the&le !ill run.

If a &le comes in multiple times a day the job and the &le !atch job must mede&ned as a cyclic process.

't the ne! day scan the previous day &le !atch job !ill end and the ne:tdays if any !ill be scanned into the 'ctive ,ile.

Control M &le !atch loos for!ard and !ill not loo bac for a &le.


Page 9


10/27

11/14/2015 11/14/2015 294804987.doc

, GRO!S & OBS

Setting u# ne. Grou#"

Grou#" /re 0older" or job" /nd 2o"t o Control M job" /re "et u# .it0Grou#"Grou#"3ob" /re de4ned in t0e Control-M De"5to# b6 t0e

Enter#ri"e Sc0eduling *e/27 Mo"t o t0e inor2/tion i" gener/l /nd t0e2ore "#eci4c #/r2" /re on t0e job level78

Go to Edit

Sc0eduling Grou#" Ne.

5.1.1

eneral !ab

Job Name"'t group level should be named same as group8table.

#$ner "user that the job is running under%

Aut&or "!ho set up the job 4default if not changed is emuser6

!as'ty(e: 1cheduling prod# ctm>@a# or ctm>tst

*c&edulin+ !able Name: )ust start $it& A((lication *ystem,denti-er de-ned .or t&e +rou( /A*,0 limit to B5 characters

A((lication : A*,

rou(: should be same as scheduling table name


Page 10


11/27

11/14/2015 11/14/2015 294804987.doc

!ime From: time group should start( no time speci&ed# group !illstart !ith scan. %obs in group !ill not run until preds or time issatis&ed at the job level

1ntil: last possible time group can run

Descri(tion: a description about the group limited to 5 characters.

2*c&edulin+ !a+s /N#!3: used only on 4obs $it& +rou(s0

!a+ Name: Name of calendar 4some have the group name6. Cande&ne multiple

calendars# no calendars on job level.

)ont& Days Calendar: 'ctual calendar name that the tag namerefers to.

"hen setting this up mae sure all months are checed andonce the Month

9ays calendar is &lled in used the greenchec mar to completethe calendar%

)a5 6ait: Number of days group should stay in the active &le# mustbe completed

for each calendar de&ned. green check when complete

Active Date: From: date that group can start to run


Page 11


12/27

11/14/2015 11/14/2015 294804987.doc

1ntil: last date group !ill run


Page 12


13/27

11/14/2015 11/14/2015 294804987.doc

DConditions

78delete

Pencil8add ne! condition

,n Conditions" predecessors

Name: group8job name pred

Date: *!A! " !aiting for condition# does not loo at date

#DA! 9 loos for condition from current order date

PR3 9 loos for condition from previous date.

once complete !ith pred information

#ut Conditions 9 successors. Condition sent out to prere@uisitetable to satisfy other in conditions


Page 13


14/27

11/14/2015 11/14/2015 294804987.doc

2*et : used to specify 'uto*dit variables to be resolved before groupsubmission.

Not used at group level


Page 14


15/27

11/14/2015 11/14/2015 294804987.doc

2*&outs"This panel is used to specify shout messages to be sent upon groupcompletion 4Not used at group level6

PostProc: The panel indicates conditional post processing actions to be performed hen the last !ob in

the gro"p finishes processing# depending on the s"ccessf"l or "ns"ccessf"l completion of all the !obs in

the gro"p.


Page 15


16/27

11/14/2015 11/14/2015 294804987.doc

Setting u# ne. ob"

%ob Name $ Name of job# M21T start !ith '1I. Limited to EF characters

,ile Name$ script job is running. Limited to B5 characters

-ath Name$ path !here script is located

O!ner$ 2ser id that runs the job

'uthor$ job created by . . .

Tastype$ %ob

Table8


17/27

11/14/2015 11/14/2015 294804987.doc

,or group scheduling this panel is not used in the job level e:cept for the TagRelationship &eld.

'nd3job !ill not load at scan time

Or 3 job !ill scan


Page 17


18/27

11/14/2015 11/14/2015 294804987.doc

Cyclic$ chec if job is to run multiple times a day

Interval$ number of minutes bet!een cycles

Ma:imum$ Ma: number of times to run the job

Ma:!ait$ number of days job !ill !ait in the active &le# group level ma:!aitoverrides job level.

Time

,rom$ 1tart time of job

2ntil$ end time of job( usually used to place an end time on a cyclic process

Con&rm $ 3 scanning job into the 'ctive %ob ,ile 4'%,6 in con&rmation status. %ob!ill not run until con&rmed

Node I98


19/27

11/14/2015 11/14/2015 294804987.doc

IN conditions$ predecessors for job

Name ( (name of pred job

9ate ( ( O9'T $ current date

1T'T$ doesnGt loo at date

-R*H$ prior date

Can use 4 6 to do 'nd8Or statements bet!een predecessors.

O2T conditions$ condition posted to the prere@uisite table in Control M so otherjobs can run.


Page 19


20/27

11/14/2015 11/14/2015 294804987.doc

0uantative Resources$ resources de&ned that the job !ill !ait for before running

Re@uired ( C-2A

'1I>'LL

Control Resources$ not used at this time. 'n *?CL21IH*81'R* type of resource.


Page 20


21/27

11/14/2015 11/14/2015 294804987.doc

1et Hariables$ -arms de&ned to a job

Name 3 -'RM# -'RMB# etc

Halue3parm sent

JLI)M*M1KM re@uired to set


22/27

11/14/2015 11/14/2015 294804987.doc

The 1teps panel indicates conditional post processing actions to be performed#depending on the outcome of speci&ed statements.

This panel is used to de&ne On 1tatements and 9o 1tatements.


Page 22


23/27

11/14/2015 11/14/2015 294804987.doc

These Post Process definitions need to be in place to generate standard format alerts when any of theseconditions occur. Using the standard format alerts, the Event Management system will be able to forward alerts tolarify to open cases appropriately. !ormally, all "ob definitions should have a !#T#$ condition defined, as thiswill generate the alert and subse%uent larify case if the "ob aborts.

The &To& field should always be set to &E'& to send the shout message to the ontrol(M )lert 'erver. To alert for "ob running too long* +hen* Eectime Urgency* Urgent 'hout Tet*

--#+!E Eectime Eceeded To alert for "ob running not long enough* +hen* Eectime Urgency* Urgent 'hout Tet*

--#+!E Eectime Too /ow

To alert for "ob submitting0start1 too late* +hen* /ate 'ub Urgency* Urgent 'hout Tet*--#+!E Missed /ate 'ub

To alert for "ob completing too late* +hen* /ate Time Urgency* Urgent 'hout Tet* --#+!E Missed /ate Time

To alert for "ob abort2ended not ok* +hen* !#T#$ Urgency* 3ery Urgent 'hout Tet* --#+!E Ended !ot #$ 4--#MP'T)T


Page 23


24/27

11/14/2015 11/14/2015 294804987.doc

Tags 1election$ tag from group to de&ne calendar for the job.

(multiple calendars can be de&ned to one job by selecting the appropriate tags fromthe tag list.

(the tag must be de&ned at the group level in order for the job to use it.

9 MONI*ORING CON*ROL-M OBS *+ROG+ EN*ER!RISEM%N%GER

%obs !ill be able to be monitored as they process through Control(M *nterpriseManager. There are several status codes8colors# follo!ing is a list of those codes and

there meanings. This can be seen by right clicing on the group and selecting 1tatus1ummary.


Page 24


25/27

11/14/2015 11/14/2015 294804987.doc


Page 25

There are several options available for jobs in theEnterprise Manager. Right click on the job or groupand a list of available options will show up in bold

print.

Status Summary-a list of statuses and meaningsand stats on how many jobs are in a specific status. (see previous page)

Properties-jobgroup detail information.

Hold! "lace job on holdConfirm-satisfy a user confirmation status

Free-Release from holdRerun-Restart a job

Delete-Delete job from AJF. Deleted jobs will notpermanently be deleted until the next san.Undelete-if job is deleted an be plaed ba! inshedule with "ndelete

Kill-stop a job that is urrently running.Force OK-mar! the job o!# ontinue with stream

Sysout-Statistics view last run info on jobDocumentation

Log!y"- loo! at what job is waiting on

#eig!$or!ood-identifies jobs that arepredeessors or dependents of a seleted job or$roup %heduling table and highlights the nodes ofthose jobs in the Flow Diagram

%ranc! menus-preds and suessors of jobseleted.

Find in Flo&diagram-find it in the flow diagram

view.


26/27

11/14/2015 11/14/2015 294804987.doc

9717171 'lo. Di/gr/2 ie.: 'lo. di/gr/2 2ode di"#l/6" /dr/t cont/ining t0e job #roduction ;o. in / gr/#0ic or2/t7*0e job ;o. re;ect" job de#endencie" indic/ted b6#rere


27/27

11/14/2015 11/14/2015 294804987.doc

Frequently Asked Questions

$hen does the ne%t da& begin'

The ne da& scan is at 11 am ()T. *ll !obs that are in green stat"s or that ha+e a ma% aitof 0 ill be remo+ed and the ne !obs for the da& ill be scanned in.

,o does a !ob ithin a gro"p get remo+ed from the scan temporaril&'

-e"est the !ob to be e%pired in the gro"p. The Tag -elationship ill be changed from rto *nd hich ill allo all the other !obs in the gro"p to be scanned in. nce the !ob is read& to be

scanned bac in change the Tag relationship bac to *nd.

,o does a gro"p get reran'

f an entire gro"p needs to be reran then the o"t conditions for the gro"p if an&3 and the

!obs m"st be remo+ed from the Prere"isite Table so the !obs in the gro"p ill r"n in the correctorder. -e"est the conditions to be remo+ed and a rer"n to the !obs.

control-m training doc

Documents