Control M Gui PDF

Control M
Control M is a Workload Automation Software obtained by BMC Software. It is designed for

automation of various functions in the enterprise including traditional IBM mainframe OS/MVS
(z/OS today) JCL, batch files and shell scripts, as well as routine functions such as invoking
database stored procedures, invoking and using Web services and handling file transfers inside
and outside the organization. Control-M can schedule workloads on a daily, weekly or monthly
interval.
In our Nordstrom Account, we are using Control M GUI version 9.
JOBS:
A job is a unit of work that a computer operator or job scheduler (a program) that runs in the
operating system.
Batch processing:
Executing a series of jobs or programs on the system without user interaction.
New day process:

Mainframe refresh is known as New day process. During 7 pm IST (based on account), all the
completed jobs, deleted jobs , jobs which exceeded Max wait and the used conditions are going
out of active environment .Then the current date jobs will come in to active and start running as
per schedule .Control M will be inactive during refresh.
Job Status:
Green : Ended ok
Yellow : Executing
Blue : waiting for resources
Sky-blue : waiting for Host machine
Grey : waiting for predecessor and time conditions
Pink : waiting for user confirmation
White : Unknown status
Login procedure:
Run mstsc  computer: remotesd(RDS) username: NORD/Lanid.
• Select the Environment in Drop down and select PROD for production and Test for testing
environment.
• Give login credentials then ok .
Control Monitoring
Select monitoring and then All active jobs to enter in to active environment.
Active panel
View point:
Here you can customize the active environment as per your requirement such as all jobs, all active
jobs, abended jobs, held jobs ect…
Expand All:
This is expand and see the jobs inside the application.
Rearrange:
This is to refresh and rearrange the jobs in active.
Hierarchy:
We can set the jobs visibility of environment such as control M , Application wise, Sub application
wise, smart folder wise and jobs wise.
Map:
We can see the jobs running inside particular application in the graphical format with all
predecessor and successor details.
List :
We will get to see the details of the jobs inside particular application.
Gantt:
This will give you the time details of the flow in the line graph format.
Rerun:
We can restart the already completed and failed jobs based on requirement.
Hold:
We can hold the jobs which are waiting only.
(Note: holding the executing job wont workout).
Free:
We can release the held jobs using this option.
Kill:
We can stop the executing job using this option.
Set to ok:
This option enables us to mark the job as complete without running its script and also enables the
post processing conditions.
Confirm:
If the job is waiting for user confirmation we can start execution by this action only.
Run Now:
This is used to bypass the scheduling criteria of the jobs such as resources, Time and predecessor
conditions.
Delete:
If you don’t want the job to run for the day, hold it and delete it.
Undelete:
You can undelete the deleted jobs and the job will be in Hold state after wards, you can release it.
Find:
This is to search the jobs inside the active(Control + F)
Restart:
We can restart the job from the failed step or any other particular steps using this option.
• This will give one pop up.
• There select the particular step
• Keep it in specific step mode
• Give ok
Order:
We can bring the job or folder manually irrespective of scheduling criteria using this option.
Select the Control M server name, folder (in which the job belongs to) and then library
Jobs:
Selected : you can expand the folder to select the jobs over here
Mask: we can bring a particular job in to active
All jobs: entire folder will come into active.
Parameter:
Ignore the scheduling criteria: we are running jobs irrespective of its run conditions.
Hold: the job will come in to active with hold only(it is mandatory to put the job in hold)
Order as independent flow: a standalone flow will come in to active.
Then give order
Order date:
We can choose the order date for the jobs which we are bringing inside active.
JOB DETAILS
Select one job to see the details in the side panel:

Synopsis: this will give the biodata date of the job.
Waiting info: it will show for what the job is waiting for.
Script : you can edit the jcl by clicking the pencil icon over here.
Log: this will give the full running details of the job
Belongs to & documentation:
Here we will get the support team details, restart and recovery procedures.
Output:
Sysout of the jobs will be here.
Statistics:
Job’s average running time, start time , end time and all will be here.
Neighbors:
Right click the jobs to see the predecessors and successors jobs list. A single click on the job name
will navigate you to that particular job.
Predecessor:
The previous job which triggers the post processing conditions for the jobs in flow.
Successor:
The immediate next job which will take in conditions from its previous job.
ABC
A is the predecessor job for the current job B
C is the successor job for the current job B
Jobs modification
General:
To modify the job in the active environment, we need to hold the job or click the modify icon on
the right top of the panel which we will get it by double clicking the job.
We can make changes in the owner , command line, priority of the jobs.
We can make the job as Dummy also using this option.
Scheduling:
Here we can set Time for the jobs to run.
Rerun setting:
We can make a job to run in a cyclic manner.(Note: we need to set the no of maximum rerun ,if we
give 0,the jobs will run infinite times within that current date.
Maxwait:
Keep active for table decides the number of days the job should be inside the active environment
before its completion.
Run information:
The run time criteria can be described over here.

Prerequisites:
This field describes the conditions which are needed for jobs to run.
In Condition:
These are the conditions the job is getting from its previous job to run. This can enables the jobs
to run in a organized flow.
The conditions should be specific with order date.
If its mentioned as Nodate, the job can take any old same conditions from the condition table and
will get triggered.
Static conditions:
These conditions cannot be modified, this will be in conditions tables for ever.
Resoures:
Conditional resources:
In order to avoid conjunction between the environment, we are setting the resources for the jobs
to run.
Control resources are the resources in which the job is having the whole control during its
execution.it can be defined as share or exclusive resources.
Example.
Job A and Job B needs to access a Database,
DB is described as Exclusive, If Job A starts first, it will access the DB when the Job B will be
waiting for resource till Job A completes. Once the Job A completes it releases the control to the
Job B, then job B will start.
DB is described as Shared, Both Job A and Job B can run at the same time.
Quantitative Resources:
We can define the quantity of the resources during the jobs execution.
Example:
We declare that the Initiator X can be used by 5 jobs at a time, but 15 jobs are waiting for X
initiator to start. Then first 5 jobs will start running by taking the initiator. If any of those 5 jobs
completes, that will release the initiator X and then 6th job will start executing and so on.
Actions:
This field enables us to decide the post processing conditions of the jobs.
We can set the out conditions of the jobs over here.
Conditions table:
Once the conditions are triggered by the jobs.it will get saved in condition table for 5 days (based
on account). after that it will go out of active.
When ordering the on-demand job, we need to be careful about the prerequisite conditions.jobs
may take the conditions directly from the table and will start running.so always have the habit of
deleting the conditions of job and run it.
Customizable filter(Control +D):
In view point, select customizable filter to get the required view of jobs based on our requirements.
History :
You can see be last 5 days which have gone out of active here.
Alerts:
Alerts panel is playing a important rule in monitoring. For all discrepancies will get alerts in the
panel. Right click the alert and get navigated to the failed job through alert panel only.
Thank You
By,
Anu Mathavan
9894143432

Control M Gui PDF

Uploaded by

Copyright:

Available Formats

Control M Gui PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Control M Gui PDF

Uploaded by

Copyright:

Available Formats

What is Control M used for?

What are the different job statuses in Control M?

Control M

Control M is a Workload Automation Software obtained by BMC Software. It is designed for

New day process:

Select one job to see the details in the side panel:

The run time criteria can be described over here.

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.