FAQ: Information regarding Control-M SMART Tables / Folders

Version 10
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    Control-M/Enterprise Manager


    Control-M/Enterprise Manager


    All versions of Control-M/Enterprise Manager All versions of Control-M/Server for UNIX and Microsoft Windows



    Information collected from various product documentation regarding all aspect of  Control-M/Enterprise Manager and Control-M/Server SMART Tables / Folders



    FAQ for Control-M/Enterprise Manager and Control-M/Server SMART Tables / Folders


    Some Control-M Grammar (Definitions to follow)

       GUI Server
       Prerequisite Condition
       Rules Based Calendar
       Scheduling Group
       SMART Table

    From Control-M version 9.0.00 CTM_TABLE_ADJUST_DUMMY and CTM_TABLE_RECHECK parameters have been renamed to CTM_FOLDER_ADJUST_DUMMY and CTM_FOLDER_RECHECK respectively.

       1. SMART Table displays in ViewPoints  

    - When you define ViewPoint filtering criteria, it can happen that a SMART Table satisfies the criteria but none of the jobs in the SMART Table satisfy the criteria.
    - By default, when a SMART Table, but no jobs in the SMART Table, satisfy the ViewPoint filtering criteria, the GUI Server does not display the SMART Table in the ViewPoint.
    - For example,
       According to the filtering criteria for the ABC ViewPoint, only jobs having an In prerequisite condition called CondA are displayed. 
       The SMART Table XYZ has CondA as an In prerequisite condition, but none of the jobs in that SMART Table have CondA as a prerequisite condition. 
    - By default, the SMART Table is not displayed in the ViewPoint.
    - By modifying the appropriate system parameter, you can display the SMART Table in the ViewPoint, even though no jobs will be displayed in the table.
      (See 3. Displaying empty SMART Tables in ViewPoints)


    2. Tables and jobs
    This topic discusses tables and the scheduling of jobs in tables.


    - A table is a collection of related job processing definitions.
    - Tables are stored in the Control-M database (and duplicated in the Control-M/EM database).
    - Tables are “ordered” by the New Day procedure or User Daily jobs. 

    - SMART tables (prior to version 7.0.00 these were known as Scheduling groups) include an extended set of table definition parameters, having a state and status.
    - All jobs in a SMART table are ordered for scheduling at the same time, unless prevented by their scheduling criteria.
    - In addition, SMART tables may contain sub-tables.

    - A table that is nested inside a SMART table is known as a sub-table. A sub-table inherits the Rules Based Calendar from its parent table.


    3. Displaying empty SMART Tables in ViewPoints
    - By default, when a SMART Table, but no jobs in the SMART Table, satisfies ViewPoint filtering criteria, the GUI server does not display the SMART Table in the ViewPoint.
    - You can override this default for all users or for specific users.
    - To override the default so that “empty” SMART Tables are displayed for all users:
       Set the value of the ViewpointPolicy system parameter to SELECT_JOBS_AND_SG.
       (To filter out the “empty” SMART Tables, reset the ViewpointPolicy system parameter to its default value: SELECT_JOBS.)


       If ViewpointPolicy  is set to SELECT_JOBS_AND_SG, users can still hide any empty SMART Tables displayed in the ViewPoint by choosing the Hide Empty tables option from the View menu in Control-M/EM.
    - To set whether empty tables are displayed for specific users:
       i.   In the Control-M Configuration Manager, choose Tools => System Configuration. 
       ii.  The Control-M/EM System Parameters window is displayed.
       iii.  Locate the ViewPointPolicy system parameter, and click New.
       iv.  In the Component Name field, specify the user name for which different behavior is required.
       v.   Ensure that the Value field is defined as required for this specific user, and click Save.


       For other system parameters, Comp. Name identifies the data center. For the ViewpointPolicy system parameter, Comp. Name indicates the user names of the exceptions.


    4. SMART Tables:
    - Defining SMART Tables, basic procedure (7.0.00 User Guide pp 79-82)  http://documents.bmc.com/supportu/documents/03/35/200335/200335.pdf#Page=79
    - Creating and Editing SMART Tables (7.0.00 User Guide pp 127-139) http://documents.bmc.com/supportu/documents/03/35/200335/200335.pdf#Page=127
    - The node color of a SMART Table is determined by both the status of the jobs in the table and the SMART Table itself.
    - The status is indicated by the color of the clock image in the SMART Table icon ( ).
    - The title bar display color is the color representing the greatest degree of urgency.
    - You can change a table to a SMART Table in the table editing form by selecting the SMART Table checkbox and defining the extended scheduling parameters.
    - SMART Tables may contain Sub-tables which will also be displayed in the list of jobs (Table Manager). The contents of a Sub-table can be viewed by clicking on the Sub-table in the list.
    - You can also define SMART Table templates which can be used not only for creating SMART Tables, but for defining jobs within the SMART Table as well by applying the SMART Table template on a specific job or table. (7.0.00 User Guide pp 171-176) http://documents.bmc.com/supportu/documents/03/35/200335/200335.pdf#Page=171
    - When updating a table to become a SMART Table, a Rule-Based Calendar must be defined or the table entity will be marked as invalid.
    - SMART Tables are ordered only if the scheduling criteria of at least one Rule-Based Calendar in the table is satisfied.
    - Whether individual jobs in the SMART Table are ordered depends on the relationship between the individual job scheduling criteria and the selected Control-M level Rule-Based Calendars, which is set by selecting either And or Or, and on the values of job-specific basic scheduling parameters.
    - Smart Tables and Sub-tables can also be placed in Held status and all jobs belonging to the table will be held.
    - (ORDER/FORCE dialog)
      i.   To select a SMART Table, click Select.
      ii.  Then click the displayed ellipsis (...)
      iii.  And in the displayed Select Active Group dialog box, select the SMART Table to which to add the jobs. (You can use this option only if you are forcing, not ordering, jobs.) 
      iv.  If you chose Recent or Selected, to add jobs and/or Sub-tables to the SMART Table.
            Even if jobs and/or Sub-tables with the same name already exist in the table, click the DUPLICATE check box.


    5. Related Configuration Parameters
    - ViewpointPolicy
    Determines which SMART Tables are passed to the ViewPoint.
    Valid values:
    SELECT_JOBS - Filtering criteria are applied only to the jobs. Only jobs satisfying the filtering criteria, and only SMART Tables containing at least one such job, are passed and displayed. (No empty tables are passed.)
    SELECT_JOBS_AND_SG - Filtering criteria are applied both to jobs and SMART Tables. In addition to passing the same jobs and SMART Tables that are passed for the SELECT_JOBS value, the Server also passes any SMART Tables that match the filtering criteria (and pass the security criteria) even if they are empty.
    Default: SELECT_JOBS


    For jobs in the SMART Table, determines conditions of which unscheduled predecessor jobs to ignore.
    Valid values:
    AJF – Ignore predecessor jobs in the Active Jobs file level. When selected, jobs in the SMART Table ignore conditions set by jobs in the active jobs file that are not scheduled.
    GROUP – Ignore predecessor jobs in the group level. When selected, jobs in the SMART Table ignore conditions set by jobs in the SMART Table that are not scheduled. Default.
    Note: This parameter is relevant only when ADJUST_COND is set to Y. For more information, see ADJUST_COND in the Control-M Parameter Guide.
    Default: GROUP
    How / where to set: config.dat
    Refresh Type: Manual


    - CTM_TABLE_ADJUST_DUMMY (version 9.0.00 and higher CTM_FOLDER_ADJUST_DUMMY)
    Controls creation of dummy jobs that run in place of unscheduled prerequisite jobs.
    Valid values:
    Y—A dummy job waits for the prerequisite conditions expected by the job it is replacing, and performs the post processing of the job. When a SMART Table is ordered, jobs in the table that should not be ordered at this time are ordered as DUMMY jobs. This functionality is useful for data centers that require identical job flow regardless of whether certain jobs in a table are ordered for a specific instance of the table.
    N—Out conditions of the jobs that were not ordered are ignored by the ordered jobs in the SMART Table.
    Note: This parameter is relevant only when ADJUST_COND is set to Y. For more information, see ADJUST_COND in the Control-M Parameter Guide
    Default: N
    How / where to set: config.dat
    Refresh Type: Manual

    - CTM_TABLE_RECHECK (version 9.0.00 and higher CTM_FOLDER_RECHECK)
     Indicates if SMART Table or Sub-table conditions should be checked for each job in a SMART Table or Sub-table after the SMART Table or Sub-table conditions have been satisfied.
    Valid values:
    N— SMART Table or Sub-table conditions are ignored when ordering specific jobs in a table.
    Y— SMART Table or Sub-table conditions are checked for each job in the table (in addition to conditions specified for the job).
    Note: If N is specified for this parameter, SMART Tables or Sub-tables are activated when the necessary conditions exist, and remain active regardless of whether or not any of those conditions are deleted.
    Default: N
    How / where to set: config.dat
    Refresh Type: Manual

     - MaxRecentItemsInList
     Is used to determine the max number of saved items in the recent viewpoints list in the monitoring domain.

    6.Cyclic Folders 
    Cyclic jobs and cyclic folders don’t stop and keep on cycling even if the job/folder has failed.
    The cyclic will be stopped only if the max runs have reached or if “stop cyclic” was issued.
    In V8 we even added an option to do this “stop cyclic” after xx failures in a raw and this is also supported for cyclic folders.
    So cyclic folder behaves the same as cyclic job: it keep on running even if failed unless stopped…
    As for rerun:
    Folders don’t have a “rerun” option (only jobs have such an option) and cyclic folders are not an exception.
    Need to consider if we want to add rerun to Folders in the future
    The reason: rerun for a folder must include the “conditions recycle process” in which we remove the internal conditions in the folder so the dependencies inside will be maintained (similar to how we are doing it when the folder is “recycled” for the next cycle). If we want to add “rerun” it should be for all folders… Not just cyclic ones.
    Additional Information:

       Customers viewing this solution may find value in the following self-help Connect with Control-M video.

    Legacy ID:KA388281


    Article Number:


    Article Type:

    Solutions to a Product Problem

      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles