Viewpoints

Viewpoints in the Monitoring domain enables you to display your job flows, view, and monitor jobs that are for a specific user, or jobs that have ended Not OK.

Viewpoints show in real-time the execution status of the batch production. Viewpoints can only be viewed by the user that created them and cannot be shared.

Using SLA Management you can monitor actual and estimated job executions and obtain an understanding of the jobs execution time information that enables you to control your active environment more efficiently. The monitoring Viewpoint can show you the jobs in a flow that have started or ended executing, or jobs that are scheduled to execute in a specific time frame.

In the CCM, the Administrator can set the number of viewpoints that can be created by changing the Maximum viewpoints a user can define parameter. If you exceed the limit, the oldest saved viewpoint is deleted. For more information about Control-M system parameters, see Control-M Web parameters.

Creating a Viewpoint

This procedure describes how to create a Viewpoint and filter and group job attributes.

Begin

1. From the Viewpoints tool bar, click Add Viewpoint.

   A Viewpoint pane appears.

2. Add filters:

   1. Click Add/remove fields.

      The Add Fields section appears.

   2. Select the fields as required, as described in Viewpoint Fields.

   3. Click Done.

3. Define the hierarchy in which the jobs appear by doing the following:

   1. Click Grouping to expand the hierarchical levels.

      By default, the hierarchy is set for Control-M/Server, Application, and Sub-Application.

   2. Click Add level and select an option from the Select drop-down list.

4. Click Open.

   The Viewpoint is created.

5. Click Save.

6. In the Save Viewpoint dialog box, type a name and description of the viewpoint and click Save.

Viewpoint Fields

The following table describes the viewpoint fields when creating or editing a viewpoint.

Field	Description
Folder Name	Defines the name of the folder A container of jobs and sub-folders that passes its definitions to the included jobs and sub-folders. that holds the job.
Application	Defines the Application A job attribute that provides a logical name for sorting groups of jobs, which enables you to search for and update jobs. defined for the job.
Sub Application	Defines the sub-application A job attribute that provides a logical name for sorting groups of jobs in an Application, which enables you to search and update jobs. defined for the job.
Control-M/Server	Defines the name of the Control-M/Server that processes the job.
Folder Library	(z/OS jobs only) Defines the name of the library that contains the job’s folder.
Job Name	Defines the name of the job.
Description	Defines the job description.
Job Type	Defines the job type The type of the job, such as an OS Job that executes at the operating system level or integrations that run on third-party applications, such as AWS, Azure, and Control-M for Databases., such as OS job or SAP job.
Run as	Identifies the user name who is authorized to execute the job.
File Name/Member Name	Indicates the name of a member that contains one of the following in relation to the job to be executed: The JCL of the job The started task procedure Warning messages
File Path/Member library	Defines the location of the file that contains the script.
Host	Defines the computer where the job is executed.
Host Group	Defines a collection of host computers which enables you to define and execute jobs on any of the computers within the host group.
Critical	Determines whether the job is a critical-path job, which ensures priority resource allocation.
Cyclic	Indicates that the job is set to execute cyclically A SMART folder or job that executes multiple times in one run, whether for specific intervals, sequences of intervals, or times..
Emergency	Determines whether the z/OS job is an Emergency job.
Included in an SLA	Includes jobs that belong to an SLA Management Service A service that enables you to monitor critical job flows for potential delays and failures..
Rule-Based Calendar	Determines a Rule-Based Calendar A type of calendar with multiple sets of scheduling criteria, including a confirmation calendar and activity period, which you can base on another calendar.
Workload Policy	Defines the name of the Workload policy that controls, manages, and balances the workload of resources and hosts.
Command	Defines the OS Command line executed by the job.
Keep Folder after ended not ok	Determines the number of days the job remains in the active environment if the job ended not ok. To see Keep Folder after ended not ok results, you need to view the empty folders, by doing the following: Enable system parameter ViewpointPolicy and set to SELECT_JOBS_AND_SG. (Default is set to SELECT_JOBS). Clear the Hide empty SMART Folders checkbox in user Preferences.
Job JCL Name	Defines where the job runs.
NJE Node	Defines where the job runs.
Override Path	Determines the alternative file path for running a job if the specified file path is not found.
Late	Determines the job status.
Keep jobs in folder	Keeps all the jobs in the folder until the folder is removed.
Requested	Determines the job status.
Job Status	Determines whether to search for jobs that Ended OK, Not OK, or both.
Run Date	Shows the date that the job executed.
Execution Time	Shows the number of seconds that it takes to execute the job.
Run ID	Shows the run ID The identification code for a SMART folder, sub-folder, or job execution. number.
Folder Held	Determines which Folder is in a hold A job action that stops the job from executing or pauses a job that is currently executing. status.
Held	Determines which job is in a hold status.
Include deleted jobs	Shows deleted jobs in the viewpoint.
Resource Pools	Specifies the Resource Pool A type of quantifiable resource, which represents the total amount of resources from a physical or logical device that a job can access. and for each job the quantity required/used by that job.
Lock resources	Specifies whether the job requires exclusive or shared access to the Lock Resource A type of prerequisite that controls the flow of the workflow, which represents a physical or logical device that folders, sub-folders, or jobs can exclusively access or share..
Wait For event name	Specifies the name of the Wait For event An conditional entity that creates a sequential relationship between jobs by enabling the successor job to execute after the predecessor job has executed..
Wait For event date	Shows the date of the Wait For event in mmdd format.
Event name	Specifies the name of the Add/Delete event.
Event date	Shows the date of the Add/Delete event in mmdd format.

Creating a Historical Viewpoint

This procedure describes how to create a historical Viewpoint using previously saved Viewpoints, which enables you to review job data from past dates.

Before You Begin

You must create and save at least one Viewpoint to use this tool.

Begin

1. From the table of saved Viewpoints in the Viewpoints tab, click on the Viewpoint that contains the historical job data you want to review.

2. From the Viewpoints toolbar, click History.

   A dialog box with a calendar and a Control-M/Server drop-down list appears.

3. From the Server drop-down list, select the relevant Control-M/Server.

4. From the calendar, click the date you want to review.

   The saved Viewpoint for that date appears.

   • You can edit the Viewpoint fields by clicking Edit.

   • Jobs from earlier dates that remain in the active environment appear in the Run Date column in List View.