Viewpoints

A Viewpoint is a filtered view of folders and jobs in your environment that enables you to monitor the real-time execution status of your workflows across multiple Control-M/Servers and Agents. You can create simple or sophisticated Viewpoints based on the hierarchies and filters that you define, as described below:

Hierarchies: Enable you to determine the organizational appearance of a Viewpoint.
Filters: Enable you to filter and refine Viewpoints by Control-M attributes and Boolean operators, as described in Viewpoints.

Viewpoints are accessible only to the user who creates them—they cannot be shared.

In the CCM, Administrators can determine the number of private Viewpoints that users can create with the Maximum Viewpoints a User Can Define system parameter, as described in Control-M Web Parameters. If you exceed this limit, the oldest saved Viewpoint is deleted.

You can view up to 20,000 jobs in a Viewpoint. If the number of jobs that appear in a public Viewpoint exceed this limit, you can open a public Viewpoint with filters or presets. Admin-level users can increase this limit, if required.

Creating a Private Viewpoint

This procedure describes how to create a private Viewpoint, which enables you to monitor the structure, scheduling, and real time execution status of workflows on one or more Control-M/Servers.

Begin

From the Monitoring domain, click Viewpoints.

The Viewpoints tab appears.
From the Viewpoints toolbar, click Add Viewpoint.

The Viewpoint creation pane appears.
Do the following to define the hierarchical order of the Viewpoint:
1. Click Grouping.
  
  The Grouping section expands and the current hierarchy appears. By default, the hierarchy is set to Control-M/Server > Application > Sub-application.
2. Do one or more of the following to add or delete grouping attributes from the hierarchy:
  - Add: Select an attribute from the drop-down list.
    
    The grouping attribute appears at the lowest level of the hierarchy.
  - Delete: Mouse over a grouping attribute and click ✕.
    The attribute disappears from the hierarchy.
3. To add to the current hierarchy, click Add Level and, from the Select drop-down, select an attribute.
Do the following to define Viewpoint filters:
1. Click Filter.
  
  The Filter section appears.
2. Complete the filter fields as required.
  
  You can use wildcards to define more than one entry in many of the fields when a named attribute matches an existing attribute in your environment. For more information, see Pattern-Matching Strings.
Click Open.

The Viewpoint is created.
From the Viewpoints toolbar Save.

The Save Viewpoint dialog box appears.
In the Save Viewpoint dialog box, type a name and description of the Viewpoint and click Save.

The Viewpoint is saved to the Viewpoints pane.

Viewpoint Fields

The following table describes the Viewpoint fields that you can complete when you create or edit a Viewpoint.

Field	Description
Folder Name	Defines the names of the folders A container of jobs and sub-folders that passes its definitions to the included jobs and sub-folders. that are included in the Viewpoint.
Application	Defines the names of the Application A job attribute that provides a logical name for sorting groups of jobs, which enables you to search for and update jobs. names that are included in the Viewpoint.
Sub-application	Defines the names of 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. names that are included in the Viewpoint.
Control-M/Server	Defines the names of the Control-M/Server names that are included in the Viewpoint.
Folder Library (z/OS only)	Defines the names of the libraries that are included in the Viewpoint.
Job Name	Defines the job name that is included in the Viewpoint.
Description	Defines the job description that is included in the Viewpoint.
Job Type	Defines the job types 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 jobs or SAP jobs, that included in the Viewpoint.
Run As	Defines the name of the Run As User An OS account name that is used to execute jobs on the host. that is included in the Viewpoint.
File Name/Member Name	Indicates the filename or member name that contains one of the following for the job that is executed: The JCL of the job. The started task procedure. Warning messages.
File Path/Member Library	Defines the location of the file, which contains the script, that is included in the Viewpoint.
Host	Defines the computer where the job is executed that is included in the Viewpoint.
Host Group	Defines the host group, which is a collection of Agents or Agentless Hosts, that is included in the Viewpoint. For more information, see Host Groups.
Critical	Determines whether critical-path jobs are included in the Viewpoint. For more information, see Job General Attributes.
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 (z/OS only)	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 (z/OS only)	Defines where the job runs.
NJE Node (z/OS only)	Defines where the job runs.
Override Library/Path	Determines the alternative file path or member library for running a job if the specified file path or member library is not found.
Late (z/OS only)	Determines the job status.
Keep jobs in folder	Keeps all the jobs in the folder until the folder is removed.
Requested (z/OS only)	Determines the job status.
Job Status	Determines whether jobs that Ended OK, Not OK, or both are included in the Viewopint.
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 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.

Opening a Viewpoint on Historical Data

This procedure describes how to open private Viewpoints that enable you to review past environment data and track workflow execution. Viewpoints with historical data are limited to the Control-M/Server that you select. To view workflows that span multiple Control-M/Servers, you must open a separate Viewpoint for each Control-M/Server.

Before You Begin

You must create and save at least one private Viewpoint.

Begin

From the table of saved Viewpoints in the Viewpoints tab, select a private Viewpoint.
From the Viewpoints toolbar, click History.

A dialog box with a calendar and a Control-M/Server drop-down list appears.
From the Server drop-down list, select the required Control-M/Server.
From the calendar, click the required date.

The filtered workflows on this date and Control-M/Server appear in your selected Viewpoint.