Job Type

Defines the type of job that determines which fields are exposed in a job definition. The value of the job type is usually based on the platform for the job run. Jobs defined as Dummy provide instructions for Control-M such as post-processing actions.

The appropriate job template with Job Type must be selected from the job palette, or you can change the Job Type if you have not yet saved the job. The following Job Types identify the relevant job fields for jobs that run on particular platforms or for jobs that perform Control-M actions:

Table Header	Table Header
OS	Defines job fields for Control-M/Server Distributed jobs that run on the UNIX or Windows platform. For more information on OS fields, see OS.
z/OS	Defines job fields for Control-M for z/OS jobs that run on the Mainframe platform. For more information on z/OS fields, see z/OS.
BIM (Batch Impact Manager)	Defines job fields for defining a batch service. You can define and order a BIM job to represent batch tasks that can seriously impact critical business services if delayed, so BMC Batch Impact Manager can provide early warning. For more information on BIM fields, see BIM.
Dummy	Defines Dummy job parameters which provide instructions to Control-M, but do not run any script or command. For more information on Dummy fields, see Dummy.
Dummy (z/OS)	Defines Dummy job parameters which provide instructions to Control, but do not run any script or command. For more information on z/OS Dummy fields, see z/OS Dummy.
File Watcher	The File Watcher job type defines the ctmfw (Control-M File Watcher) utility job to monitor file status and detect file processes, as described in ctmfw File Watcher utility. For more information on File Watcher fields, see File Watcher.
Control-M Report	Defines Control‑M Report job fields which enables you to view jobs that execute the emreportcli utility to generate a report based on a format using a template you define in Control-M Reports. This enables you to schedule the generation of reports according to scheduling criteria in batch mode. NOTE: From Control-M version 9.0.18, you cannot run Control-M Report jobs but instead you need to define a job in Control-M Automation API and then run an O/S job in Control-M client using the command defined in Automation API.
OS2200	Supports running jobs on other platforms, and enables you to submit jobs for execution on the agent platform, monitor the jobs, and perform post-processing analysis of output files. The completion status of jobs and the results of post-processing analysis are transmitted to the Control-M/Server.For more information on Other Control-M/Agents, see Control-M/Agent and remote hosts.
Mapper	Supports running jobs on other platforms, and enable you to submit jobs for execution on the agent platform, monitor the jobs, and perform post-processing analysis of output files. The completion status of jobs and the results of post-processing analysis are transmitted to the Control-M/Server.
OS/400 <type>	Enables you to submit jobs for execution on the agent platform, monitor the jobs, and perform post-processing analysis of output files. The completion status of jobs and the result of post-processing analysis are transmitted back to the Control-M/Server. You can view and modify the following OS/400 type of jobs: External, Full, Multiple Commands, Program, VT.
Tandem Full	Supports running jobs on other platforms, and enables you to define jobs, retrieve job parameters, and control jobs running on the Guardian operating system.
<Application Plug-in jobs>	Defines job fields for Application Plug-ins such as SAP, Oracle E-Business Suite, or IBM Cognos.

Parent Topic

General parameters