1.What is Control M ?

Control-M is a workload automation (traditionally called batch scheduling) software obtained

by BMC Software via its 1999 acquisition of Israel's New Dimension Software. It was
originally developed for IBM mainframe computers (OS/MVS operating system), but has
since expanded and is also available for distributed computing platforms including Unix,
Windows, Linux and OpenVMS environments.

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. It can also be used
to respond to trigger events such as the appearance of a file, being called by a third party
application through an API, or invocation on demand through Java or Web services.

Control-M can be integrated with applications such as SAP and Oracle's PeopleSoft, to act as
a scheduling organizer in these computing platforms.

With the addition of BMC Batch Discovery in 2007, it integrates with the configuration
management database ("CMDB") of BMC Remedy Action Request System. This is intended
to help identify the relationships between batch processes and other business and information
technology ("IT") infrastructure component

Control-M is a software application product developed by a team of software

engineers in Israel to provide enterprise-level job scheduling and management.
According to BMC’s literature “CONTROL-M for Distributed Systems is a business
integrated scheduling product that focuses on the production environment's business
applications and platforms”. Simply put, Control-M is an application able to execute
programs on many different types of servers, manage the timing of them and report
the results to a central point.

Control M Components-->

CONTROL-M/Enterprise Manager (CONTROL-M/EM): This application provides a

single, centralized point of access and control of your batch processing environment. Through
EM we can connect to multiple control-m servers.

CONTROL-M/Servers: At the heart of CONTROL-M processing are

CONTROL-M/Servers. These are the scheduling engines that schedule jobs, manage job
processing flows, and provide notification of job flow status. Each CONTROL-M/Server is
resident on a particular computer and is specific to its operating system.

CONTROL-M/Agents and Remote hosts: Though CONTROL-M/Servers are

responsible for job scheduling and processing, they do not have to limit their activity to the
computer on which they reside; they can schedule jobs on other computers that come under
their control. CONTROL-M/Agents are commonly used to place computers under the control
 of a CONTROL-M/Server. CONTROL-M/Agents submit jobs on behalf of the
CONTROL-M/Server, track the jobs’ processing, and provide status information back
to the CONTROL-M/Server.

As an alternative to having a dedicated CONTROL-M/Agent installed on each computer

under the control of a CONTROL-M/Server, CONTROL-M/Server can also submit jobs
to agentless computers known as remote hosts.

CONTROL-M/Agents and remote hosts are identified by their node IDs. Jobs are assigned to
specific node IDs.

You can balance processing loads by grouping a number of CONTROL-M/Agents

together into a node group, and then assigning jobs to the node group, instead of to a
specific CONTROL-M/Agent. The job will be processed on any agent in the group,
according to the processing load at that particular moment. You can also submit a single job
to all the nodes in a Node Group. This is all depends on the scenario.

Control Modules: To bring CONTROL-M functionality to your external, packaged

application environment (for example SAP and Oracle E-Business Suite), CONTROL-M
provides Control Modules (CMs) that enable CONTROL-M/Agents to interface with the
external applications

The Control-M “Accessories” are:--->

• Control-M/Enterprise Manager GUI (EM/GUI or ECS GUI)

• Gateways
• Global Alert Server (GAS)
• Global Condition Server (GCS)

It is important to understand what each of these components does and its place in
the Control-M architecture.

GUI’s:--->

The main 3 GUI’s are listed below.

1. Control-M / EM GUI
2. Control-M Desktop
3. Control-M Configuration Manager

Gateways: These are used for communication between Control-M/EM and Control-
M Server. If these gateways are down then Control-M/EM GUI won’t get any status
updates from the Control-M Server.

Global Alert Server (GAS): GAS will contain all the alerts sent from jobs which are
active in Control-M. You can connect to GAS using ‘Alert window’ and can view all
the alerts. Usually operations will monitor these alerts and take appropriate actions.
Global Condition Server (GCS): GCS will keep track of all Prerequisite and Global
conditions added by jobs which are in AJF. Once a condition added to GCS, control-
M will satisfies the condition for all the waiting jobs.

The Control-M/Data Center is the true core of the Control-M system. The Data
Center is comprised of a Control-M/Server, Database and Control M/Agents.

The Control-M/Server

The Control-M/Server is the central component of the Data Center. It controls

interaction with the Enterprise Manager, Control-M/Agents and the database
backend. The Control-M/Server (CTM/SERVER) is the component that maintains the
schedule, job definitions, calendars, resources and conditions. CTM SERVER is the
only component that can load or order jobs.

The Database

The database serves as a backend data repository for Control-M (Sybase, PGSQL,
Oracle or MS SQL server can be used). The CTM/SERVER has its own data-space
within an Oracle instance. This data-space contains the Master versions of all of the
job-related data: job-definitions, scheduling tables, resources, calendars active jobs
tables and shout tables, to name a few. It also houses runtime specific data for the
CTM/SERVER such as process flags, user access profiles and agent status.

The Database is critical to the operation of CTM/SERVER & Control-M. If the

database is not available, Control-M will not operate.

The Control-M/Agent---->

The Control-M/Agent (CTM AGENT) is a small-footprint application that is installed

on each target server for jobs, as well as the CTM SERVER. It runs as a service on
Windows-based systems and has a “hook” into “inetd” on UNIX systems. It is
dormant until a request comes from the CTM SERVER or until a job-related
message needs to be sent to CTM SERVER.

CONTROL-M/Agents are commonly used to place computers under the control of a

CONTROL-M/Server. CONTROL-M/Agents submit jobs on behalf of the CONTROL-
M/Server, track the jobs’ processing, and provide status information back to the
CONTROL-M/Server.

As an alternative to having a dedicated CONTROL-M/Agent installed on each

computer under the control of a CONTROL-M/Server, CONTROL-M/Server can also
submit jobs to agentless computers known as Remote Hosts.

CONTROL-M/Agents and remote hosts are identified by their node IDs. Jobs are
assigned to specific node IDs. You can balance processing loads by grouping a
number of CONTROL-M/Agents together into a node group, and then assigning jobs
to the node group, instead of to a specific CONTROL-M/Agent. The job will be
processed on any agent in the group, according to the processing load at that
particular moment.

· CONTROL-M/Enterprise Manager GUI (CM/EM-GUI) & CONTROL-M/Desktop

The CONTROL-M/ENTERPRISE MANAGER software product is used by Operations as a focal point

to monitor jobs, scripts/ or commands that are scheduled by all the CONTROL-M/Servers in the network.

It is used to pass conditions created on one system to any other systems so they may trigger jobs on
platforms other than their own.

It also managed all alerts generated by job processes from all CONTROL-M/Servers

The CONTROL-M/Desktop software product is used as a focal point to define jobs online or off-line
on all the CONTROL-Ms that run on all distributed systems and on z/OS

· CONTROL-M/Servers

The CONTROL-M/Server software product is used to submit (schedule) jobs, scripts or commands
based on events such as time or conditions.

The server also passes on the statuses of the jobs to the CM/EM from the CONTROL-M agents that
run the jobs.

· CONTROL-M/Agents

The agent software actually executes the task submitted by the CONTROL-M/Server under which the
agent is controlled by.
It also notifies the Server as to the status of the job; Waiting/Ready to run, Running, Ended-OK or
Not-OK

i) Enhanced Services
Automated Job Scheduling.

Various criteria can be specified to determine when a job should be scheduled. Jobs
can be scheduled
by calendar and clock (days, dates, time of day, etc.), job priority, predecessor job
completion,
availability of input, and dependencies upon other events. These user-defined
specifications are
recorded in Job Processing definitions. Jobs can also be scheduled according to special
calendars,
which are created using the Calendar facility. Calendars can define workdays,
weekends, holidays, etc.
for each data center. Once a job is scheduled, it is not submitted for execution until its
runtime
 requirements (e.g., availability of a tape drive) are satisfied.
Load Balancing.
When the Agent Technology implementation is used, CONTROL-M is capable of monitoring
resource availability on Agent platforms distributed across the network. Using a load-balancing
algorithm, CONTROL-M determines which Agent platform has sufficient available resources
to handle execution of a job at any given moment and submits the job to that platform.
In this manner, CONTROL-M assures efficient utilization of available resources and helps achieve
maximum production throughput.

Allocation and Monitoring of Resources.

CONTROL-M monitors resources via logical names, which are specified in the data center then
dynamically submits jobs according to resource availability. A job is not submitted as long as any
of the resources required for its execution are not available. Once the resources are available,
CONTROL-M
allocates those resources and submits the job. This mechanism prevents bottlenecks where
concurrently
processed jobs are waiting for a particular resource. Consequently, overall system throughput is
maximized
and performance degradation does not occur.

CONTROL-M dynamically resolves contention for all data center resources while taking into account
a job’s requirement for exclusive or shared control of each Resource. Contention problems are resolved
prior to submitting jobs. CONTROL-M also allows logical definition of resources which are otherwise not
usually controlled (e.g., CPU utilization). By logically defining how much of a resource is available and
how much of that resource is required by each job, utilization of the resource can be controlled.

Automated Job Submission.

Automatic Job submission allows execution of scheduled jobs to begin without operator intervention.
CONTROL-M submits a job when all submission criteria (e.g., availability of resources) specified in the
Job Processing definition are satisfied.
Tracking and monitoring of Job Execution.
CONTROL-M automatically follows the progress of scheduled jobs through all stages
(in queue, executing, completed).

Immediate Detection and Notification of Problems.

As soon as a problem or an unexpected situation occurs, CONTROL-M notifies the appropriate
personnel. These situations/problems are detected by analysis of job control statement error
messages
, operating system prompts, etc. Notification is issued via the “Shout” facility, which can send messages
to a variety of destinations including the CM/EM workstation, the CONTROL-M log, user mail, a logical
or specific user, or any terminal. CONTROL-M can also be instructed to issue a Shout message
in the event an exception occurs at the time of submission and/or execution of a job
(e.g., a job completes well before, or in excess of, its anticipated execution time).

For a job ABEND:

Providing automated PMS record creation
and/or
Providing automated 3rd level support paging
and/or
Providing automated e-mail to selected user/group/userid
For a job not started by specified time
Providing automated PMS record creation
and/or
Providing automated 3rd level support paging
and/or
Providing automated e-mail to selected user/group/userid
For a job run time exceeded by specified minutes
Providing automated PMS record creation
and/or
Providing automated 3rd level support paging
and/or
Providing automated e-mail to selected user/group/userid
For a job run time exceeded by specified % of average of last 20 runs
Providing automated PMS record creation
and/or
Providing automated 3rd level support paging
and/or
Providing automated e-mail to selected user/group/userid
Sysout (Job Log) Control.
CONTROL-M can print or delete a job’s log, or move or copy the log to a different library/directory.

Sysout analysis for specified error code or message

Based on specifications in the Job Processing definition, CONTROL-M can dynamically determine
how to handle the job’s log, depending on the job’s execution results.

Shout Messages.
A Shout message is a message sent to one or more destinations when certain conditions exist
at the time a job is executed or completes execution. The targeted destinations may include the
CM/EM Alerts window, the CONTROL-M log (described below), the system console, certain terminals
, users or users’ mail. Potential recipients of Shout messages are defined in a table
called the “Shout Destination table” in the CONTROL-M data center. By switching the table
(either manually or automatically), the user can alter the recipients of messages targeted for
specific logical addresses.

Utilities
Utilities provided with CONTROL-M are used to perform a variety of management functions.
Some utilities also generate reports, which assist in the efficient use of CONTROL-M
(e.g., CTMRPLN that indicates when selected jobs in a Scheduling table are scheduled to run).

Report facilities
Job Report:
Lists jobs and their attributes.
Link Report:
Lists job dependencies and their attributes.
Prerequisite Conditions Report
Lists prerequisite conditions and their attributes.
Control Resources Report
Lists Control resources and their attributes.
Quantitative Resources Report
Lists Quantitative resources and their attributes.
Detect Logical Errors Report
Performs validity checks on the current network and lists errors, which have,
been detected.
Manual Report
Lists any IN condition which is not defined as an OUT condition of another
job.
Alerts Report
Lists alerts generated by CM/EM
Download History
Provides a history of downloads with related data.
Graphical Job Report
Lists jobs and their attributes, and includes graphics. This report only refers
to jobs displayed in
the current CM/EM GUI View window.
Poster
Presents the job schedule in graphic poster form. This report only refers to
jobs displayed in
the current CM/EM GUI View window.

Printing facilities
Based on a report created as indicated above, said report can be send to:

Any printer defined to the Windows XP PRO PC

To a file to be sent to a user via e-mail

Network monitoring facility

All CONTROL-M servers and agents are constantly monitored and any platform or network failure is
detected and reported.

ii) Automated PMS records

When a job ends NOT-OK, either due to script failure or based on the ON STATEMENT
parameters, the CONTROL-M/Server responsible for the agent that executed the script,
sends or "SHOUTS" an alert message to the CM/EM

This message contains the following parameters:

The JOBNAME (as defined in the job definition using Sears Canada Inc. standard jobname convention)

The MemName (usually the name of the script being executed)

The NodeID (the platform's I.P. address where the script was executed)

The COMPSTAT (The completion status of the script as code by the programmer)

This information once received by the CM/EM application is routed to the mainframe system
HOST166 where CONTROL-O, the mainframe automation application, creates a PMS record that is
passed to the TOROPS INFO-PMS queue (PS) for handling
B) CONTROL-M Server

The central software component of CONTROL-M. CONTROL-M/Server runs on a UNIX platform

(referred to as the Server platform). From this location, CONTROL-M/Server exchanges operations
data with CM/EM with multiple production platforms, and maintains the CONTROL-M database.

CONTROL-M includes an option for accumulating and collating runtime statistics for each defined job.
These statistics are used for the following purposes:

i. Runtime statistics

CONTROL-M includes an option for accumulating and collating runtime statistics for each defined job.
These statistics are used for the following purposes:

· The Job Processing parameter Shout can be specified to issue a message if the execution time
required by a job varies from its average runtime by more than a stated interval. This can help highlight
possible errors. (The Shout parameter is described in Chapter 5, working with the Job editing form, in
the CONROL-M/Desktop User guide.)

· When a simulation is run using the CM/EM Simulation facility, job statistics are used by the
facility to determine how much time to allow for the execution of each job.

· When viewing information regarding a scheduled job (i.e., a job in the Active Jobs file) in CM/EM
GUI, you are provided with the average runtime and the standard deviation in the Job Details window.
In addition, you can view the job statistics recorded in the Statistical Details table by selecting the
Statistics option from the job node menu.

All Shout messages are recorded in the CONTROL-M log. You would select the log as a destination
only when you do not wish to send the message to any additional destination.

· The Job Processing parameter Shout can be specified to issue a message if the execution time
required by a job varies

2) CONTROL-M/AGENT

This is the component of CONTROL-M which runs on each production platform

(referred to as the Agent platform) and which executes job-handling requests received from
CONTROL-M/Server. Any number of Agent platforms with different operating systems can be
handled by a single Server platform.

In the above configuration, each instance of CONTROL-M/Server and its associated

CONTROL-M/Agents is viewed as a single data center in Enterprise Control station.
All schedule definitions reside in a database managed by CONTROL-M/Server.
The active scheduling environment is also managed by CONTROL-M/Server, including all scheduling
logic.
A typical job execution proceeds as follows:

A job waiting to be submitted “waits or is eligible” on the Server platform.

Once all its prerequisite conditions, resource requirements and all other scheduling
constraints are satisfied, CONTROL-M/Server instructs CONTROL-M/Agent to submit the job.

Upon receiving a request for submission, CONTROL-M/Agent submits the job for execution locally
according to the job definition.

CONTROL-M/Agent monitors the job and reports any exceptional situation to CONTROL-M/Server.

Upon completion of the job, CONTROL-M/Agent performs the post-processing analysis.

No job sysout needs to be transmitted over the network, thus keeping network resource consumption
at an absolute minimum.

Post-Processing parameters specify what actions should be performed by the CONTROL-M Monitor
at completion of job execution.

Post-Processing parameters are used to describe:

· Actions to be performed if the job is not submitted.

· Actions to be performed after the job has finished executing.
· Handling of the job’s log.
· Notification messages to different users.
· Rerun conditions.

CONTROL-M/Agent handles requests from CONTROL-M/Server.

A request may consist of:

· Instructions to submit a job on the Agent platform.

· Requests for information regarding jobs on the Agent platform which are currently executing
or recently completed.
· Request to view/edit job script statements.
· Request to view job sysout or job documentation.

In addition, CONTROL-M/Agent may perform the following functions as instructed by "Job processing"
parameters supplied with the job submission request:

· Handling of job sysout.

· Issuing Shout messages.

Each Agent platform requires a “listener” process to accept requests from CONTROL-M/Server.
UNIX platforms can provide this service using operating system services. On other types of platforms,
CONTROL-M/Agent, started at boot-time, includes this listener process.
Each Agent platform is known to CONTROL-M/Server by its node ID. This is generally the
Agent platform’s host name. The Job Processing definition for each job should include the node ID of the

Agent platform on which the job should be submitted by CONTROL-M/Server.

In the event of a communication interruption between CONTROL-M/Server and one or more

Agent platforms, CONTROL-M/Server sends a special Shout message to ENTERPRISE/CS.
All jobs that were running on the affected Agent platform(s) are reclassified in the Active Jobs file as
Unknown. The status of the Agent platform is changed to Unavailable.

If processing on the Agent platform was not interrupted, any job which had been submitted to a
platform prior to the interruption continues executing.

When communication between CONTROL-M/Server and an Agent platform is restored,

CONTROL-M checks the status of any jobs that were running on the Agent platform and
updates the status in the Active Jobs file. If a job completed execution during the period of interrupted
communication, CONTROL-M/Server retrieves its completion status from the Agent platform

i) Sysout handling

Specifies how the job’s log should be maintained/ handled after the job completes with a
completion status of OK. Sysout handling is specified using the parameters Option and Parm.

Option Specifies whether the job’s Sysout should be copied/moved to another location, printed or
deleted.
Parm Provides supplementary information for the action specified by the Option parameter.

ii) New features

· CONTROL-M/Control Module for FTP

CONTROL-M/CM for FTP implements File Transfer Protocol (FTP) as defined in RFC 959.
It serves as an interface between the CONTROL-M environment and FTP servers. CONTROL-M/CM
for FTP enables you to define, schedule and monitor file transfer jobs.

· CONTROL-M/Control Module for PeopleSoft

The CONTROL-M/CM for PeopleSoft is a Java-based server that serves CONTROL-M/Agent requests.
It uses TCP/IP to communicate with CONTROL-M/Agent on one side and with a PeopleSoft Component
Interface on the other. Configuration parameters control the number of concurrent connections to
PeopleSoft. CONTROL-M/CM for PeopleSoft is automatically activated by the first request that arrives
from CONTROL-M/Agent. It remains active to serve CONTROL-M/Agent requests. You can
use a utility to shut down CONTROL-M/CM for PeopleSoft.

· CONTROL-M/Control Module for Oracle

CONTROL-M/CM for Oracle Applications enables CONTROL-M to perform the following actions:

• Schedule existing Oracle Applications jobs

• Define and schedule new Oracle Applications jobs
• Monitor jobs already running in Oracle Applications
• Run Oracle Applications concurrent requests as if they were CTL-M
batch jobs.

Control-M 7 EM Client Installation Steps

1. Win XP
Locate the hosts file on Win XP under the file location
“C:\WINDOWS\system32\drivers\etc”.
Open the host file with Notepad and add the following line
to the last in the file
142.93.7.59 r5981psp59.inside.sears.ca r5981psp59
Save the file
Win 7
Go to Control Panel –>User setting -> click on Change
User Account control
settings -> then move the selection to never notify as below
and click ok.
Reboot your machine to make the change settings active.
Locate the hosts file on Win XP under the file location
“C:\WINDOWS\system32\drivers\etc”.
Right click and the Properties of the host file and uncheck
the read only option
click Apply and click Ok to close the properties window.
Open the host file with Notepad and add the following line
to the last in the file
142.93.7.59 r5981psp59.inside.sears.ca r5981psp59
Save the file
Installation Procedure on Win XP & Win 7
1. DROST.7.0.00.windows.zip
2. Kindly extract this on ZIP/RAR under the local directory
3. Click on setup.exe (any OS version it can automatically
check and update)
Click I Accept option and click Next.
Click on Control-M Specific Component & select Control-
M Enterprise Manager
Client 7.0.00
Click Next
Specify the text box as below:
Naming Server hostname: r5981psp59
Naming Services port number: 23075
Click Next
Click Install
Once Installation complete the above screen is received.
After installation, kindly reboot the workstation and install
the fixpack
Installation of Fix Pack
Click on respective exe files & run the same
Win XP - PANFT.7.0.00.500_windows.exe
Win 7 - PANFT.7.0.00.500_windows_x86_64.exe

Once Installation completes click Finish

Post installation verify the Control-M client logon window

BMC Control-M Workload Automation Services

A business-integrated scheduler must be able to
integrate additional applications into the environment
quickly and smoothly, as well as enable
communication with applications from external
organizations. Only a business-integrated scheduling
solution can tackle such versatile and critical business
requirements

By utilizing BMC Control-M V8 for your job flow

environment, you'll experience the increased power
and simplified interface designed to make
management easier, and your BMC workload
automation environment as efficient as possible.
Reduce IT and business operations costs
Improve quality and availability of business
services
Decrease production workload disruption and
speed recovery times
Enable business growth, agility and flexibility

Control-M 7 Basics
This is currently a Work In Progress. Ignore any spelling
errors or anything else really. Consider it a draft.
Thanks.
The goal of this guide is to provide a jump in point for
Control-M. It is going to cover only the basic
understanding of Control-M to allow someone with very
little scheduling knowledge to jump into creating and
uploading test jobs and learn on the fly.
Disclaimer: When in doubt read the manual. BMC provides
very easy to read manuals (compared to other applications)
they are full of details and tidbits you just wont find
anywhere else. I would have to say Control-M is very user
intuitive and you can use the manuals as a great reference
for any issues that arise.
What is covered?
How Control-M works
Parts of Control-M
How to create a job
How to upload a table
How Control-M works:

A basic overview of Control-M requires you to only know

3 parts. The Control-M Data Center, The Agent, and Your
server.

Basically the Data Center is the Servers that Control-M

itself resides on. There are several parts to these servers but
it is not necessary for you to know this. Just understand the
data center is where your jobs are contained.
The Agent is a Control-M component that resides on your
server. (there is agent less ability in Control-M 7+) The
agent gives you many of the features Control-M offers and
acts as a translator between the Data Center and your
server.
Your Server is where all the actual processing is done.
Your scripts reside there that Control-M will trigger and
monitor, or it is where commands are issue to from
Control-M.

Aging this is a very basic understanding of the way control-

M works. There are several Servers combined housing
various parts of Control-M its database and attached
storage.

Parts of Control-M.
By parts I am referring to the interfaces you will use, GUI's
or applications. Average users will use only two of these,
Desktop and Enterprise Manager. There are however other
interfaces like Configuration manager, Reporting facility
and BIM. For the purpose of this we will cover Desktop
and Enterprise Manager (EM).
Desktop
Desktop is used to create Tables and jobs. You will do all
of you actual manipulation of the jobs in Desktop. If you
were building a chair it would be the workshop you would
cut and assemble the pieces.
Enterprise Manager (EM)
EM is where you follow your job and manipulate it daily. It
is where if a job was scheduled to run and you wanted to
hold it you would do so. If you wanted to see why the job
hasn't run yet, Delete the job, rerun it etcetera you would do
this all in EM. With our chair example this is the house you
would sit in it at.
How to create a job.
Now lets get to the best part creating the job. There are
several Job types, we are going to cover the following
types; Job Type OS : Command, Job & Dummy. We will
assume that most jobs are on a Linux platform but will also
include a windows job as an example.

We will go Tab by Tab in the job creation starting from the

General Tab. ,the one used in the examples below. Right
click on the link and do a Save Target as otherwise it will
open as xml in your browser. Follow the steps below and\or
use the sample as well.

1. Open Control-M Desktop

Sign in using your Control-M ID and password.

Sign into the the test server.

2. Click on File | New| Local Workspace - This will open

your work area.

3. (Shortcut Step) Click on Edit| New| Job - This is going to

create a new job into a blank table. It is a shortcut step
because you are not creating a table first. The average
group (in CompanyXYZ) does not use Smart tables so if
you do refer to the manual. This will create a basic job and
give you an error stating that No Control-M has been
defined. Just acknowledge the error.

4. Create your Job - The most important items to start out

with are Control-M, Parent Table, Application, Group.
These tend to remain the same throughout all of your jobs
and are the strictest when it comes to following standards.
Refer to the screenshot for our test Jobs information.

5. General Tab - General Job information

Job Name - Unique Identifier for the job - Follow job
naming standards (Required for all Types)
Task Type - Allows you to select the type of task (job)
it is - Job, Command, Dummy, Detached (Required for all
Types)
File Name - This would be the file you are referencing
on the server. (Required for Job & Detached only)
File Path - If you have a file name you need a path.
(Required for Job & Detached only)
Over Lib - Override library this is mostly used for
mainframe jobs. Refer to manual for other uses.
Command - If your running a command job you need a
command. This is where it would go. (Required for
Command only)
Hierarchy - This includes the Parent Table, Application
and Group that should be standard for all jobs in a group.
Owner - This is a very important field. It is the ID that
the command or Job you are running requires on the server.
Without this your jobs will not run (Required for all Types)
Author - This is the person who created or last updated
the job. (Required for all Types)
Documentation - The URL of where your
documentation (Call out procedure\ Run book) is stored. In
CompanyXYZ Control-M is monitored 24/7/365 if your
job fails someone will see it and check this location for call
out requirements. (Required by CompanyXYZ for all
Types)
Description - Details on what the job does. This helps
the team (yours and ours) to know what the purpose of this
job is. (Required by CompanyXYZ for all Types

6. Scheduling Tab - Define when the job should run

You can also use a calendar see Using predefined calendars
to schedule jobs Chapter 8 in the Control-M User Guide for
information on this. (I will not cover it here)
This section will allow you to pick the days and times a job
is allowed or wanted to run. In Control-M job only come in
when they are scheduled or demanded to run by another
job. Here you will define when they can run as long as all
other requirements on the job are satisfied. We will cover
only the following field here:
Month Days
Week Days
Months
Month Days - These are the actual days you want the job to
run. Highlight every day the job will run. If you want it to
run with additional restrictions for example you want the
job to run 5 days before the last day of the month you will
use the Rules Box in the Days: section.
Week Days - These are set up exactly the same as Month
days except use the Days of the week. Using the And\Or
option between the two fields will allow you to select if
you want it to run on the 5 only if its a Wednesday or
always on Wednesday's. There is also a Rules box for
specific Day of the week rules you may need. Example:
Need a job to run the First Tuesday of the month.
Moths - Like above can be used in combination with Days
and Weeks information or on its own. Example - Allow
jobs to run All months or on January March and April.
Image below - Show's jobs running on the
1,7,9,13,17,19,25,29 all months and ignores the Week
Days.

Image below - Shows the schedule as 8 days from the last

day of the month and any Sunday or Saturday, but only in
the months Jan, Mar, Jun, Aug, Oct and Dec. So this job
would run only once if the 8th day from the last day was a
Sunday or a Saturday but if it was not it would also run
regardless of the day.

Note: For any calendar information see the Manual. Smart

Tables also operate differently. Please refer to the manual.

7. Execution Tab - Define where and how the job should

run on dates scheduled