Job Management

The following table lists actions that you can perform on a job in the Monitoring domain.

Job Action	Description
Finding a Job	Enables you to search for a job.
Finding a Job Within a Viewpoint	Enables you to search for a job in a Viewpoint.
Holding a Job	Stops the job from processing, which enables you to update the job.
Releasing a Job	Releases a job from a Hold state, which enables the job to execute.
Rerunning a Job	Reruns a job.
Running Multiple Jobs	Executes foldersA container of jobs and sub-folders that passes its definitions to the included jobs and sub-folders, sub-foldersA container of jobs and sub-folders that inherits its scheduling definitions from the folder that it is within, and passes its scheduling definitions to the included jobs and sub-folders, and jobs.
Executing a Job Now	Overrides the job's submission criteria and executes the job.
Restarting a Job	Describes how to restart a Control-M for z/OS job from a specific step. You can also specify a range of steps to restart a job from. When you restart a job, files from a previous run of the job are deleted.
Reactivating a Job	Describes how to reactivate a Control-M for z/OS job or task that was started and has a status of either disappeared or failed reason unknown.
Confirming a Job	Confirms a job that is waiting for user confirmation, which allows the job to continue executing.
Setting a Job to OK	Sets a job to end OK by overriding any defined scheduling criteria or other job prerequisitesThe part of the job definition that controls the flow of your jobs, such as an event that controls sequence or a resource that controls load.
Setting a Job to OK (No PP)	Describes how to set a Control-M for z/OS job to end OK. This job action overrides any scheduling criteria and post processing job actions are not performed.
Skipping a Job	Skips over a job and continues the job flow. The job that you skip does not execute.
Bypassing Options in a Job	Enables you to ignore specific options such as a resource, event, or time limit when you submit a job.
Applying Events to a Waiting Job	Applies eventsAn entity that creates a sequence relationship between jobs by enabling the successor job to execute after the predecessor job has executed to a waiting job so that the job can begin executing.
Deleting a Job	Enables you to delete a job that is in a Hold state.
Killing a Job	Terminates a job during execution.
Editing a Job	Enables you to edit the job settings.
Searching for a File Transfer	Searches for a file that was transferred with Control-M MFT (Managed File TransferAn FTP client and server solution that enables you to watch and transfer files from a local host to a remote host, a remote host to a local host, or a remote host to another remote host) and displays it's job properties and transfer status.
Viewing File Transfers from a Job	Displays the status of all file transfers from a specific job.
Finding Neighborhood Jobs	Finds the jobs that are in the neighborhoodThe jobs in a workflow that are predecessors or successors to a job of the selected job. You can analyze your job flow based on jobs related to the selected job, such as searching for prerequisite jobs, which are the predecessors of the selected job.
Job Details	Describes the details of each job tab.

Finding a Job

This procedure describes how to search for jobs. If you have a Viewpoint that contains the job that you want to search, see Finding a Job Within a Viewpoint.

Begin

1. From the Monitoring domain, click and then click Job Search.

   The Job Search tab appears.

2. From the Today drop-down list, select the relevant date.

   The date of the search is changed.

3. In the job search field, type the name of the job, file name, or job run IDThe ID code of the run of a folder, sub-folder, or job.

4. Click .

   A list of jobs appear.

   You can edit the attribute columns by clicking .

Finding a Job Within a Viewpoint

This procedure describes how to search for jobs within a Viewpoint.

Begin

1. From the Monitoring domain, click Add Viewpoint

2. In the Job name field, type the name of the job you want to search.

3. Click Open.

4. The selected job appears.

Holding a Job

This procedure describes how to hold a job, which prevents the job from executing, or pauses the execution of a job that has already started.

Begin

• From the Monitoring domain, right-click on the job and select Hold.

  The job is on hold and you can now update the job.

Releasing a Job

This procedure describes how to release a job from a Hold state, which enables the job to continue executing according to it's defined attributes.

Begin

• From the Monitoring domain, right-click on the job and select Release.

  The job is released and can now continue executing.

Rerunning a Job

This procedure describes how to execute a job again.

Begin

• From the Monitoring domain, right-click on the job and click Rerun.

  You can only rerun a job after it has finished executing.

Running Multiple Jobs

This procedure describes how to execute folders, sub-folders, and jobs whether according to the scheduling criteria or not.

Begin

1. From the Monitoring domain, click and select Run Jobs/Folders.

   

   The Run tab appears, showing 3 steps.

2. In Step 1 Search and select jobs and folders to run, select the jobs that you want to execute as follows:

   1. From the Server drop-down list, select the required Control-M/Server.

   2. In the Select Folder field, select the folder containing the jobs you want to execute.

   3. In the Search Job/Sub Folder Name field, type the job names, separated by commas.

3. In Step 2 Configure Run Settings, set the Run attributes, as described in Run Attributes.

4. In Step 3 Review and Run, verify the settings are as required, and the click Run.

   You can check the status of the execution in the Run Report tab, as described in Viewing the Run Report.

Run Attributes

The following table describes the run attributes you can use when executing folders, sub-folders, and jobs from the Monitoring domain:

Attribute	Description
Use Scheduling Criteria	Determines whether the job runs according to the scheduling criteria.
Run as independent flow	Determines whether the job flow in the folder executes independently from other instances of the same flow using the same events. This is achieved by adding a unique suffix to the events used in each flow instance. Run as independent flow is supported in SMART folders and sub-folders.
Hold - Put the folder/job on hold	The job is in a Hold state when it enters the run queue. This enables you to make changes to the job before it starts executing.
Date Selection	Determines the date that the job executes, as follows: Current working date: The job executes on the current date. The date includes the year. Run now with a different run date: The job executes on the date that you select instead of the original run date. Wait for selected run date to run: The job must wait to execute on the scheduled run date Select Wait for selected run date to run for time zone jobs to execute before their scheduled run date.
Place in Folder	Determines the type of folder that contains sub-folders or jobs, as follows: New: Creates a new execution of the original folder that contains only the selected job or sub-folder. Standalone: Run the job into a regular folder. Recent: Executes the job into the folder that executed last, according to the folder's Run ID. Selected: Enables you to execute the job into a folder that executed previously, according to the folder's Run ID. If the job or sub-folder is inserted into an existing folder or sub-folder that has already completed, the status of all parent folders is set to Executing. If it is not possible due to scheduling criteria, then the job remains in a WAIT_SCHEDULING status. This parameter is ignored if the folder that runs is not a SMART folder.
Create Duplicate	Determines that for jobs or sub-folders that belong to a folder, when you select Run into > Recent or Run into > Selected, jobs or sub-folders that already exist with the same name are duplicated instead of overwritten in the folder. This option is selected by default.
Variables	Defines the user-defined variablesA type of variable whose name and value you manually set in a job, which you can reference in subsequent jobs or in the same job of the job or sub-folder, in addition to any variables that already exist in the job definitionThe set of parameters that defines what the job does, when it must run, its prerequisites to run, and post-processing actions for Control-M to perform after its completion (also called a job processing definition). For more information, see Variables.

Viewing the Run Report

This procedure describes how to view folders, sub-folders, and jobs that you executed in the Monitoring domain. You can only view a report of the jobs that you executed from your current Control-M login session.

Begin

• From the Monitoring domain, click and select View Run Report.

  The Run Report tab opens and the jobs that you executed appear.

  You can view jobs in a folder by clicking to expand the folder.

Executing a Job Now

This procedure describes how to execute a job immediately, overriding all the prerequisite and submission criteria of the job.

Begin

• From the Monitoring domain, right-click the job you want to execute and select Run.

  The job executes, overriding any submission criteria.

Restarting a Job

This procedure describes how to restart a Control-M for z/OS job from a specific step. You can also specify a range of steps to restart a job from. If you restart a job, files from a previous run of the job are deleted.

Begin

1. Select the Control-M/for z/OS job you want to restart.

2. From the Actions drop-down list, select Restart.

   The Restart Job dialog box appears.

3. For each field, type or select the required value, as described in Restart Job Attributes.

4. Click Restart.

   The Control-M/for z/OS job restarts. The Viewpoints and Services are automatically refreshed at defined intervals.

5. To view the job details, click one of the tabs in the right pane, as described in Job Details.

Restart Job Attributes

The following table describes Restart Job attributes for Control-M for z/OS jobs. To define Restart Job attributes, see Restarting a Job.

Attribute	Description
From Step/Proc	Determines the job restart point of the pgmstep and procstep steps.
To Step/Proc	Determines the job restart end point of the pgmstep and procstep steps. If a from step/proc value is defined, and the To step/proc field is blank, the job reruns up to and including the last step.
Recapture Abend Codes	Determines whether to save the Abend codes from the original job execution.
Recapture Cond Codes	Determines whether to save the event codes from the original job execution.
Step Adjustment	Determines whether to enable automatic Step Adjustment. For more details about Step Adjustment, see the Control-M/Restart User Guide.
Restart Parm Member Name	Defines the name of the member that contains control attributes for the job to restart (1-8 characters only). The default value is the member that contains the JCL of the job.

Reactivating a Job

This procedure describes how to reactivate a Control-M for z/OS job or task that was started and has a status of either disappeared or failed reason unknown.

Begin

1. From the Home page, right-click the relevant job and select Reactivate.

   The job is reactivated.

2. To view the job details, click one of the tabs in the right pane, as described in Job Details.

Confirming a Job

This procedure describes how to confirm a job that is waiting for user confirmation to enable the job to continue executing. This is relevant only for jobs that are defined to request user confirmation.

Begin

• From the Monitoring domain, right-click the job with a Wait User status that you want to confirm, and select Confirm.

  The job is confirmed and continues to execute.

Setting a Job to OK

This procedure describes how to set a job to end OK by overriding any defined scheduling criteria or other job prerequisites.

Begin

• From the Monitoring domain, right-click the job and select Set to OK.

  The job ends OK.

Setting a Job to OK (No PP)

This procedure describes how to set a Control-M for z/OS job to end OK. This job action overrides any scheduling criteria and post processing job actions are not performed.

Begin

1. From the Monitoring domain, right-click the relevant job and select Set to OK (No PP)

   The job ends OK.

2. To view the job details, click one of the tabs in the right pane, as described in Job Details.

Skipping a Job

This procedure describes how to skip over a job within a job flow. The job that you skip is not executed.

Begin

• From the Monitoring domain, right-click the job and select Skip.

  The skipped job does not execute.

Bypassing Options in a Job

This procedure describes how to bypass or ignore job options such as a resource, event, or time limit when you submit a job.

Begin

1. From the Monitoring domain, right-click the job and select Bypass Options.

   The Select Options to Bypass pane appears.

2. Select the relevant options, and then click Apply, as described in Run Now Bypass Options

Run Now Bypass Options

The following table describes the Run Now Bypass options that appear when you select the Bypass Options option:

Option	Description
Time Limits	Determines whether to execute the job regardless of the Time From, Time Until and Next Time parameter values. The Time Limits bypass does not include the Time Zone parameter, which means jobs that are waiting for a specific date still wait for that date, even if the Time Limit bypass is checked.
Wait For Events	Determines whether to execute the job even if the events that the job is waiting for did not happen.
Resources from a Pool	Determines whether to execute the job regardless of whether resources are available from the Resource PoolA type of quantifiable resource, which represents the total amount of resources from a physical or logical device that a job can access. The Resource Pool bypass also ignores the Resource Pool in the workload entities that the job belongs to.
Lock Resources	Determines whether to execute the job regardless of whether the Lock ResourcesA type of resource that controls the flow of the workflow, which represents a physical or logical device that a folder, sub-folder, or job can access exclusively or share specified in the job are available in the active list.
Scheduling Environment (z/OS only)	Runs the job regardless of the job’s SCHENV statement.
Pipes (z/OS only)	Runs the job regardless of whether other jobs using the same Pipe as that specified in the definition of this job, are ready to run.
Pause (Quiesce z/OS only)	Runs the job even if Control-M is in Quiesce mode, either as a result of QUIESTIME or QUIESQRES commands.
Run job as Dummy	Determines whether to execute the job as a Dummy jobA type of job that enables you to perform job actions, but not execute anything on the Agent host when the pre-submission criteria of the job are satisfied and you want the job status to change to Ended OK, and you only want the job post-processing actions in the job to be peformed.
Run job without post processing	Determines whether to execute the job without performing any of the job post-processing actions, including the following: If-ActionsA post-processing action that you define for Control-M to perform after a job executes, if a condition is met Add/Delete events Notifications OK/Not OK Output handling If running without the Use Scheduling Criteria option selected, a job that is set with Post Processing Bypass the job ends OK and does not perform the post processing actions.

Applying Events to a Waiting Job

This procedure describes how to apply events to a waiting job which enables you to force a job to start executing.

Begin

1. From the Monitoring domain, click the job that you want to view.

   The Job Properties pane appears.

2. Click the Waiting Info tab.

   The Waiting InfoA tab in the job properties pane in the Monitoring domain, that lists the events, resources, and job predecessors that a job in the Run Queue is currently waiting for before it can execute data appears.

3. In the Job Events area, do one of the following:

   • To apply all missing events, click Apply all.

   • To apply an individual event, click .

   The events are added to the Active Events list.

Deleting a Job

This procedure describes how to delete a job.

Begin

1. From the Monitoring domain, right-click a job in a Hold state and select Delete.

   The job is deleted.

2. Click OK.

Killing a Job

This procedure describes how to kill a job, which cancels a job from executing in the middle of its execution.

Begin

• From the Monitoring domain, right-click the job in a Hold state, and select Kill.

  The job is terminated and no longer continues to execute.

Editing a Job

This procedure describes how to edit a job.

Begin

1. From the Monitoring domain, select the job you want to edit.

2. From the Job Details pane, click Edit.

   The Job Settings tab opens.

3. Edit one or more of the following:

   • General tab: Edit the job attributes according to the job type as described in Job Types.

   • Scheduling

   • Prerequisites

   • Actions

   • If you edit a job in the Monitoring domain, only the definitions of the job in the Run queue are updated and the job definitions in the Planning domain are not modified.

   • As an Administrator you can disable the editing of specific job field values in the Monitoring domain using the ModifyJobFieldsBlock parameter. These fields cannot be updated and are read only.

4. Click Save.

   The job is updated.

   The status of the job is unaffected by these changes.

   If the job was originally in a Wait status, after making the changes, the job continues in a Wait status. If the job Ended OK the job is held to update the changes and then released.

Searching for Archive Data

This procedure describes how to search for Job log and output archived data stored in the Control-M Workload Archiving server from the Services and Viewpoints tabs.

Begin

1. Do one of the following:

   • (Services tab only) To search for archive data from multiple Jobs, click Archive Search.

     The Archive Search tab appears.

   • To search for archive data from a single Job, select the Job that you want to search, and right-click Archive Search.

   The Archive Search tab appears.

2. Do one of the following:

   • To perform a quick search, do the following:

     1. In the Search field, type the name or part of the name of the Control-M entities that contain the Jobs in your search.

     2. From the drop-down list, select the Control-M entities that contain the Jobs in your search.

     3. Click .

        The archived Jobs appear.

     You want to search for all Jobs where Job Name and Application contain the number 5. In the Search field, type 5 and from the drop-down list, select Application and Job Name.

   • To perform an advanced search, do the following:

     1. Click Advanced.

        The Advanced Search window opens.

     2. For each field, type the required value, as described in .

        You can use * and ? wild characters.

     3. Click Search.

     The archived Jobs appear.

Searching for a File Transfer

This procedure describes how to search for a file that was transferred with Control-M MFT and view its job properties and transfer status.

Begin

1. From the Managed File Transfer domain, do one of the following:

   • To perform a quick search:

     1. In the Search field, type the filename, applicationA job attribute that provides a logical name for sorting groups of jobs, which you can use to search and update jobs, or job name.

        The asterisk character is not supported for a quick search. However, you can type a partial string that contains characters from the filename.

     2. Click .

   • To perform an advanced search:

     1. Click Advanced Search.

     2. For each field, type or select the required value, as described in MFT Connection Profile Additional Parameters and then click Search.

        You can use the * wildcard character for advanced searches. You can only place the wildcard after the string.

        ab*.

     3. To view the previous ten advanced searches, click Recent & Favorites.

        The search results appear. You can pin a search so that it remains in a list of up to 10. The list is saved per client.

        The yellow bar indicates the search parameters, the number of results found, and the time the search occurred. You can view the transfer details in the General and Job Output tabs in the right pane.

        The data does not refresh automatically. To view the latest status, perform the search again.

2. Do one or more of the following:

   • To filter and sort each column, click the column header and select the required values.

   • To see more search details:

     1. In the top right-hand corner of the search results, click Show Column Chooser.

     2. Drag and drop the columns you want to see in the search results from the Available Columns to Visible Columns.

     3. Group the search results by dragging and dropping the columns into the Group by area.

   • To locate the job of each file transfer, in the General tab, click the job name.

     A neighborhood tab appears that shows the context of the job. This enables you to perform actions on the job, such as rerunning the job or viewing the output or logThe activity log of a job, which lists every status change to a job, such as job execution start and completion time, and whether the job succeeded.

Viewing File Transfers from a Job

This procedure describes how to view the status of all file transfers from a specific job.

Begin

From the Home page, right-click a Managed File Transfer Job and select Show File Transfers.

The associated file transfers from the job appear in the MFT Search window filtered by Run ID and Run Count.

MFT Advanced Search Attributes

The following table describes MFT Advanced search attributes:

Attribute	Description
File Name	Defines the filename of the transfer
Status	Determines the status of the transfer: Any In Progress Completed Failed Completed with Errors In queue Canceled
Transfer Type	Determines whether the file was transferred internally within the organization or externally to a trading partner.
Job Name	Defines the File Transfer Job name that is executing the transfer
Application	Defines the application of the File Transfer Job
Sub Application	Defines the sub-applicationA job attribute that provides a logical name for sorting groups of jobs within an application, which you can use to search and update jobs of the File Transfer Job
Folder	Defines the folder of the File Transfer Job
Source	Determines the source host of the file transfer
Destination	Determines the destination host of the file transfer
Source Path	Defines the location of the file transfer on the source host
DestinationPath	Defines the location of the file transfer on the destination host
Run ID	Defines the unique execution instance of the job
Job Run Count	Defines the number of executions of the job
Time Frame	Defines when the files were transferred.

Finding Neighborhood Jobs

This procedure describes how to find the successor and predecessor jobs of the selected job, which enables you to analyze your job flow based on the jobs related to the selected job. For example, you can search for prerequisite jobs, which are the predecessors of the selected job.

Begin

1. From the Monitoring domain, right-click the job, and select Neighborhood.

   The Open neighborhood window appears.

2. Set the fields described in Neighborhood Search Fields.

3. Click OK.

   The results of the search appear in the Neighborhood results tab.

Neighborhood Search Fields

The following table describes the Neighborhood search fields:

Neighborhood	Description
Directions	Determines the relationship of the search jobs to the selected jobs. Successor: Defines the jobs that are dependent on the selected job (below the job). Predecessor and Successor: Defines the prerequisite jobs of the selected job, and the jobs that are dependent on the selected job (above and below the job). Predecessor: Defines the prerequisite jobs of the selected job (above the job). All connections: Defines the jobs branching in all directions from the selected job.
Radius	Defines the number of jobs that branch out from the selected job. Valid values: 1-99999

Job Details

The following table describes the job details of each tab.

For information about SMART folder settings, see Folder General Attributes.

Tab	Description
Summary	Shows fields such as, start time and end time, run ID, run date, status, attributes of the selected job, as described in Job Summary Tab.
Job Settings	Shows the job properties, as described in Creating a Job.
Log	Shows the activity log of the selected job.
Waiting Info	Shows the reasons why the job did not execute.
Output	Shows the different outputs of the selected job. To view, see Viewing Job Output.
Statistics	Shows the statistics of the selected job, as described in Statistics Tab.
Script	Shows the script of the selected job. In the Script tab, you can search for a specific word in the Find field.
Application Plug-in	Shows the fields and values of the specific application plug-inA Control-M component that extends functionality to third-party applications like Hadoop or SAP and integrates plug-in jobs with other jobs into a single workflow. Some application plug-ins allow you to refresh, pause, restart and delete a process.
Documentation	Shows a description related to the job, and is saved in a defined location. The Documentation area includes information about where to find the Documentation. In a z/OS job, the Documentation is in a Doc Member located in a Doc Library. The Documentation depends on whether the type is File or URL: For a file, the description is located in a file located in a file path. For a URL, the Documentation is located in a URL address.
Services	Shows the following: The service these jobs belong to The service that this job is dependent upon The services that depend on this job
SLA	Shows the SLA ManagementA service that enables you to monitor critical job flows for potential delays and failures attributes, as follows: Service Name: Defines the logical name from a user or business perspective. Service Must Complete At: Defines the time the critical service must be completed to be considered on time. Server Priority: Defines the priority level of this service, from a user or business perspective.

Job Summary Tab

The following table describes the basic attributes for the selected job:

Attribute	Description
Run As	Shows the name of a user with authorized to execute the job.
Run Where	Shows the host ID and host group of the job.
Status	Shows one of the following possible statuses: Failure/Error Ended OK Executing Unknown Wait Event Wait Resource Wait User Wait Workload Wait Host Pre execution (z/OS only)
Start	Shows the timestamp when the job started to execute. If SLA Management is installed, and the job has not executed yet, this parameter displays an estimation of when the job execution starts. For more information, see Run Time Estimations.
End	Shows the timestamp when the job stopped executing. If SLA Management is installed, and the job has not executed yet, this parameter displays an estimation of when the job run ends. For more information, see Run Time Estimations.
Execution Times	Shows the estimated future execution time for a cyclicA folder or job that executes multiple times in one run, at a specific interval or specific times, or according to a specific sequence of intervals job if SLA Management is installed.
Submission Window	Shows the time span during when the job is allowed to execute.
Execution Time	Shows the number of seconds that it takes to execute the job.
Run ID	Shows the Run ID number.
Run Date	Shows the date that the job executed.
Description	Shows a description of the job.
Job Type	Shows the job type, such as AWS, Databases or Hadoop. OS z/OS SLA Management Applications (SAP, Oracle E-Business Suite, AFT, Databases, Web Services, Java and Messaging, PeopleSoft)
Sub Application	Shows the Sub Application that the job is associated with at the third level in the host hierarchy.
Application	Shows the application that the job is associated with at the second level in the host hierarchy.
Parent Folder	Shows the folder container that the job is associated with at the fourth level in the host hierarchy.
Execution Timezone	Shows the time zone according to the job's schedule.
Cyclic	Shows whether the job executes at defined cyclic intervals.
Rerun Every	Shows the time to wait between reruns of a job or between cyclic executions of a job.

Run Time Estimations

You can install SLA Management on your system and view run time estimations for all jobs, not only jobs in an SLA service. SLA uses average run time statistics to calculate the run time estimation. You can view the estimation times in the job tile or in the Summary tab, which is displayed in italics. This is an estimation and not actual run times.

If a job is a cyclic job, future run times are calculated by the SLA Manager and displayed in the Execution Times field.

Viewing Job Output

This procedure describes how to view the output of a job, which enables you to review the actions of a job to determine if and where the job did not process correctly.

Begin

1. Select a job and click the Output tab.

2. From the drop-down list, select the output file you want to view.

3. Do one or more of the following:

   • To view the latest version of the output, from the drop-down list select the latest output.

   • To view specific characters or words in the output, in the Find field, type the words or characters that you want to view.

   • To view job output in a separate window, click .

   • (z/OS only) View the output in Control-D/WebAccess Server by clicking .

     Control-D/Web Access Server Report List window appears. For more information, see the Control-D/WebAccess Server Administrator guide.

     Enable access to Control-D/Web Access Server. For more information, see Control-D/WebAccess Server output in Control-M in Control-M Administration.

Statistics Tab

The following table describes the start time, end time, and projection attributes for the selected job:

Attribute	Description
Start Time	Shows the start time of the job.
End Time	Shows the end time of the job.
Projection	Shows the estimated start and end time of the job.