Sie sind auf Seite 1von 18

Confidentiality Statement

Include the confidentiality statement within the box provided. This has to be legally
approved
Confidentiality and Non-Disclosure Notice
The information contained in this document is confidential and proprietary to TATA
Consultancy Services. This information may not be disclosed, duplicated or used for any
other purposes. The information contained in this document may not be released in
whole or in part outside TCS for any purpose without the express written permission of
TATA Consultancy Services.

Tata Code of Conduct


We, in our dealings, are self-regulated by a Code of Conduct as enshrined in the Tata Code
of Conduct. We request your support in helping us adhere to the Code in letter and spirit.
We request that any violation or potential violation of the Code by any person be
promptly brought to the notice of the Local Ethics Counselor or the Principal Ethics
Counselor or the CEO of TCS. All communication received in this regard will be treated
and kept as confidential.

Table of Content
1. Purpose..................................................................................................................................................4
2. Introduction on Control-M....................................................................................................................4
3. Control-M terms...................................................................................................................................4
..................................................................................................................................................5
.........................................................................................................................................................5
3.2 Order date/Order ID....................................................................................................................5
3.3 Control-M server.........................................................................................................................6
3.4 Control Resource......................................................................................................................7
3.5 Job (Prerequisite) Conditions (in/out)........................................................................................7
3.6 Drain ..........................................................................................................................................7
3.7 Sysout.........................................................................................................................................7
3.8 Control-M Log

........................................................................................................................7

..............................................................................................................................................................8
4. Loading the jobs in Control-M.............................................................................................................8
5. Different Status of jobs .....................................................................................................................11
Find the different status of jobs in control-M indicates below................................................................11
Based on the jobs execution status codes, CONTROL-M automatically assigns a completion status below:
..................................................................................................................................................................11
6. Job Properties.....................................................................................................................................12
7. Job Options in EM..............................................................................................................................15
8. Archive Viewpoint..............................................................................................................................16
9. Forecasting..........................................................................................................................................17

1. Purpose
The purpose of this document is to aid the developers to get basic knowledge on Control-M scheduling
tool usage and to accomplish the same effectively while doing development activities.

2. Introduction on Control-M
Control-M is a scheduling software / tool for jobs used in large enterprises. Control-m acts as front end of ETL
batching process. Simply can say Control-M is batch scheduler software. Control-M software initially written for
Mainframe computers but now this is available for distributed computers like UNIX, Windows, and Linux.etc. In the
CONTROL-M job scheduling environment, jobs are tasks that can be performed by a computer. These tasks are
handled according to parameters. The parameters specified for a particular job are collectively referred to as a job
processing definition.
The term job refers to any task that can be performed by a script of command that is handled by CONTROLM/Server.
Job processing parameters only need to be defined once for each job. CONTROL-M uses the job

processing

definition each time a job is ordered. Definitions can be modified at any time using various CONTROL-M/EM
facilities.

2.1 Various Methods of Job processing definitions


Job processing definitions are created using various methods:
CONTROL-M/Desktop: Using the Job Editing form or the Mass Creation facility (the Skeleton Editor
window), can create definitions offline. These jobs are then uploaded to the CONTROL-M/EM database.
CONTROL-M/EM: Using the Job Editing form, can modify parameters for jobs that have already been
scheduled for submission on the current day

3. Control-M terms
These are the list of terms used in Control-M
Job
Order Date

Order ID
Control-M Node

Control-M server
Control Resource
Job Conditions
Drain
Sysout
Control-M Log
Force OK
Delete

3.1 Job
In Control-M, job is highlighted in below diagrammatic representation.

3.2 Order date/Order ID


Order date (Odate):
The date that the job was ordered onto the schedule. This can be found under the ACTIVE tab in the
job properties in the Order date field.
Odate : YYMMDD / MM/DD/YYYYExample:131023 / 10/23/2013(Odate)

Order id:
Its an unique id for all the jobs used to identify the jobs belongs to which odate

3.3 Control-M server


While opening the control-M enterprise Manager/Control-M desktop, it will ask for the server name. Server should
be either Production or stage server.
Production Server Name

Stage Server Name

3.4

Control Resource

Requirements for a job help to prevent resource contention between jobs. Jobs are defined to run exclusive or in a
share mode against a Control Resource.

3.5 Job (Prerequisite) Conditions (in/out)


A user-defined, descriptive name given to a certain situation, or condition. The plus (+) sign adds a condition,
minus (-) removed a condition

3.6 Drain
Quantitative resources are changed to zero prevents the job from starting. The second part of the drain changes
to quantitative resources back to 9999.

3.7 Sysout
Contains output created as the job executes. Primarily used to trouble shoot problems. This will remain empty
until the job actually begins to run. If the job is runs as a Command the Sysout will remain empty or if the job fails
to execute any code.

3.8 Control-M Log


Provides information (including time, date, user, job name) for actions taken since the job was loaded onto
Control-M. This includes job loads, holds, confirmations, deletes, starts, finishing ok etc. The log is cleared at the
new load daily.

3.9 Force OK
To change the status of a job to OK
Support partners may also refer to this as mark complete.

3.10 Delete
To delete a job from the schedule. The job fall off the schedule after the next new day load (noon load) Support
partners may also refer to this as canceling or removing a job. Be sure to clarify their meaning when they make a
request using these terms.

4. Loading the jobs in Control-M


Consider that going to load the jobs of DPR application in Control-M enterprise manager for
production environment.
Follow the below steps for loading the jobs.
Step1: Click on Control-M enterprise manager

Step2: Choose the production environment.

Step3: Open the viewpoint(it depends on the user requirement).


In the below screenshot, I have choosed viewpoint as ODATE

Step4: Click the applications to be loaded in control-M

After successful completion of all the above four steps, DPR application jobs got loaded in Control-M / EM as stated
in the below diagram.

5. Different Status of jobs


Find the different status of jobs in control-M indicates below

Based on the jobs execution status codes, CONTROL-M automatically assigns a completion status below:

Status
OK

NOTOK

Description
Job ended OK. The job finished executing
with a successful operating system
completion status.
Job did not end OK. The job finished
executing with a unsuccessful operating
system completion status or due to a
submission failure (for example, queue
does not exist.

6. Job Properties
General tab: shows the information about the job name, File name, File path, Application, group and tables names
of the job along with owner id

Active tab: shows the order date, order id, run time and statistics of the job

Execution tab: shows the details about the node id node group and maxwait of the job defines the number of
days that the job remains in control-M

Conditions tab: defines the in and out conditions of the job.


In conditions: Before our current job triggers, all in conditions job should completed
Out conditions: After completion of our current job, it should trigger out condition mentioned jobs

Resource tab: indicates the resources used by the job if any


Set tab: defines the parameters used in the job is getting passed through Control- M to UNIX scripts

Steps tab: defines the next action item needs to be done by the job based on the job return code.

PostProc tab: defines the bucket number of the EAM(Enterprise Application Management) team to

where the

event/alert to be generated in case of job failure

7. Job Options in EM
Restricted (DSO) Actions:
To make these below changes to Production jobs create an IWR(Infrastructure Work Request) to DSO(Distributed
System Operations) team
Hold/Free
Delete/Undelete
Confirm
Force OK / Force OK - no Post Processing
Posting conditions
Kill
Rerun

Demanding in Jobs or Tables


Draining jobs (ctmdrain_1 or 2)
Adjusting start time
Recovering CTM Agents (Unix, Windows, etc.)

8. Archive Viewpoint
In order to see the jobs were purged after noon load refresh, open the archive viewpoint by choosing below steps.
In EM, click on File then Open Archived Viewpoint
Choose Control-M Server (ctmagp02, etc.)
Select date
Select Viewpoint (All Jobs, etc.)

9. Forecasting
In order to find the schedule of jobs, open control-M desktop and load the jobs needs to loaded(e.g.: all jobs in
DPR application) and select any job and right click on the same and choose the forecast option as stated below.
Then you come to know the scheduling of the job defined in Control-m desktop.

Forecast option shows the scheduling day of the job. It may be Daily, Monthly, Weekly. Based on scheduling, the
jobs will get loaded after noon load refresh.

Thank You

Contact
For more information, contact thenmozhi.c@tcs.com

About Tata Consultancy Services (TCS)


Tata Consultancy Services is an IT services, consulting and business solutions organization that delivers real results to global business, ensuring
a level of certainty no other firm can match. TCS offers a consulting-led, integrated portfolio of IT and IT-enabled infrastructure, engineering
TM
and assurance services. This is delivered through its unique Global Network Delivery Model , recognized as the benchmark of excellence in
software development. A part of the Tata Group, Indias largest industrial conglomerate, TCS has a global footprint and is listed on the National
Stock Exchange and Bombay Stock Exchange in India.

For more information, visit us at www.tcs.com.

IT Services
Business Solutions
Consulting
All content / information present here is the exclusive property of Tata Consultancy Services Limited (TCS). The content / information contained here is correct at the time of publishing. No material from
here may be copied, modified, reproduced, republished, uploaded, transmitted, posted or distributed in any form without prior written permission from TCS. Unauthorized use of the content /
information appearing here may violate copyright, trademark and other applicable laws, and could result in criminal or civil penalties. Copyright 2011 Tata Consultancy Services Limited

Das könnte Ihnen auch gefallen