MEM620100UG50525

CONTROL-M/Enterprise Manager
User Guide
Supporting
CONTROL-M/Enterprise Manager version 6.2.01
May 1, 2005
Contacting BMC Software

You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information about the company, its products, corporate offices, special events, and career opportunities.
United States and Canada

Address BMC SOFTWARE INC 2101 CITYWEST BLVD HOUSTON TX 77042-2827 USA Telephone 713 918 8800 or 800 841 2031 Fax 713 918 8000
Outside United States and Canada

Telephone (01) 713 918 8800 Fax (01) 713 918 8000
Copyright 2005 BMC Software, Inc. All rights reserved. BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered trademarks or trademarks of BMC Software, Inc. Oracle is a registered trademark, and the Oracle product names are registered trademarks or trademarks of Oracle Corporation. All other trademarks belong to their respective companies. BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices included in this documentation.
Restricted rights legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC SOFTWARE INC, 2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA. Any contract notices should be sent to this address.
Customer support
You can obtain technical support by using the Support page on the BMC Software website or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, please see Before Contacting BMC Software.
Support website
You can obtain technical support from BMC Software 24 hours a day, 7 days a week at http://www.bmc.com/support_home. From this website, you can

read overviews about support services and programs that BMC Software offers find the most current information about BMC Software products search a database for problems similar to yours and possible solutions order or download product documentation report a problem or ask a question subscribe to receive e-mail notices when new product versions are released find worldwide BMC Software support center locations and contact information, including e-mail addresses, fax numbers, and telephone numbers
Support by telephone or e-mail

In the United States and Canada, if you need technical support and do not have access to the web, call 800 537 1813 or send an e-mail message to support@bmc.com. Outside the United States and Canada, contact your local support center for assistance.
Before contacting BMC Software

Before you contact BMC Software, have the following information available so that Customer Support can begin working on your problem immediately:
product information product name product version (release number) license number and password (trial or permanent)
operating system and environment information machine type operating system type, version, and service pack or other maintenance level such as PUT or PTF system hardware configuration serial numbers related software (database, application, and communication) including type, version, and service pack or maintenance level
sequence of events leading to the problem commands and options that you used messages received (and the time and date that you received them) product error messages messages from the operating system, such as file system full messages from related software
CONTROL-M/Enterprise Manager User Guide
Contents
About this book Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 1 CONTROL-M/EM basics 19 20 21 22 23 23 27 30 35 39 43 51 54 64 65 65 69 73 77 77 79 80 81 90 91 92 92 92 93 94 94 95 96 98 98 99
Basic concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing your scheduling environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M/EM administration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M/Server concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . New Day processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M job flow and handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load balancing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Language capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Working with list displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying pattern-matching strings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 2 Viewing the production environment
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding the Navigation Tree and its components . . . . . . . . . . . . . . . . . . . . Understanding the Net Overview and its components . . . . . . . . . . . . . . . . . . . . . . Understanding the FlowDiagram and its components . . . . . . . . . . . . . . . . . . . . . . Viewing the production environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening existing ViewPoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switching filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switching collections and hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying condition nodes In the FlowDiagram . . . . . . . . . . . . . . . . . . . . . . . . . . Refreshing the display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Navigating in the production environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Locating a node in a FlowDiagram using the Navigation Tree . . . . . . . . . . . . . . . Finding nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stepping In and Stepping Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Expanding and collapsing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Zooming in/out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identifying dependent job nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
Navigating: a summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Controlling the production environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Selecting nodes manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Navigating within a set of selected nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Performing actions on selected nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Viewing selected nodes in a new ViewPoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Creating ViewPoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Creating ViewPoints using the ViewPoint Wizard. . . . . . . . . . . . . . . . . . . . . . . . . 121 Creating and editing ViewPoints using ViewPoint Manager . . . . . . . . . . . . . . . . 129 Creating and modifying collections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Creating and modifying filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Creating and modifying hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Printing the production environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Previewing a FlowDiagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Working with the Print Preview window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Adjusting print settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Printing the FlowDiagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Chapter 3 Defining a production environment: Introduction to CONTROL-M/Desktop
161
Defining job processing definitions in CONTROL-M/Desktop . . . . . . . . . . . . . . . . . 162 Creating many jobs using a job template in CONTROL-M/Desktop . . . . . . . . . . . . 163 Synchronizing the tables in CONTROL-M/EM and CONTROL-M/Server databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Uploading and downloading scheduling tables to/from the CONTROL-M/Server database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Other handling of scheduling tables in CONTROL-M/Desktop . . . . . . . . . . . . . . . . 166 Ordering and forcing jobs or scheduling tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Defining calendars in CONTROL-M/Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Calendar Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Calendar Definition window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Chapter 4 Managing job processing definitions 177
High-level node details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 General panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 CONTROL-M panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Job node details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 General panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 General panel (for MVS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Active panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Execution panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Conditions panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Resources Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Set panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Steps panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Steps panel (for MVS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 PostProc panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Undo and Redo in the Job Editing form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
6 CONTROL-M/Enterprise Manager User Guide
Job actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bypass (MVS only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Confirm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delete. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Edit JCL/Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced Why . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Force OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Force OK no Post Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Free . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . React (MVS only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rerun . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restart (MVS only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Undelete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . View JCL/Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . View Sysout List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Why . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Application Activation Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running an application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Group scheduling tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Active panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conditions panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shouts panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PostProc panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 5 Monitoring alerts and errors
204 205 206 206 206 207 208 208 208 208 209 209 210 210 210 210 211 212 212 213 213 215 215 219 220 222 224 225 227 228 229 231
Handling alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Alert Details window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Local View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Chapter 6 Displaying and defining resources and conditions 241 242 245 246 251 255 260 261 261 263
7
Control resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing the Control Resource job list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Quantitative resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Global conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding an anticipated CONTROL-M to a global condition. . . . . . . . . . . . . . . . . Viewing (global) conditions for job nodes in the CONTROL-M/Enterprise Manager window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Global condition logic and examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Best practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
Chapter 7
Communication status
271
Communication with CONTROL-M installations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 Communication between CONTROL-M/EM components . . . . . . . . . . . . . . . . . . . . . 274 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 Using the CONTROL-M/EM GUI Reconnect dialog box . . . . . . . . . . . . . . . . . 274 Chapter 8 Reporting Facility 277
Reporting Facility Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Starting the Reporting Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 Generating a report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Alternative methods for selecting a report template . . . . . . . . . . . . . . . . . . . . . . . 281 Displaying and working with reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Defining Report Definitions and Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 Defining a New Report Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 Specifying Report Definition Criteria in the Report Wizard . . . . . . . . . . . . . . . . . 286 Editing an existing report template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 Defining a one-time report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 Working with Report Templates in the Report Template Manager . . . . . . . . . . . . . . 303 Setting Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 Generating and exporting reports in batch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 Available Report Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 Active Report Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 Definition Report Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 General Report Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 Sample Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 Converting Old Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 Chapter 9 Archived ViewPoints and Playback 315
Archived Nets and Archived ViewPoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 Selecting and displaying Archived ViewPoints . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 Playback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Playing back archived events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Chapter 10 Customization 323
Available branches and corresponding panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 Environment General panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 Environment Display panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 Flowdiagram General panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 Flowdiagram Nodes panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 Flowdiagram Links Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 Flowdiagram Colors panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 Alerts panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Reconnection panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 Diagnostics panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 Confirmations panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Appendix A
CONTROL-M (MVS) and CONTROL-M/EM cross-reference
343 343 346 346 347 347 348 351 353
Job tracking and control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Job documentation and JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IOA conditions/resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IOA manual conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Utilities under ISPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Job processing parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generating alerts on a CONTROL-M for MVS platform. . . . . . . . . . . . . . . . . . . . Appendix B Messages and codes
Mainframe (MVS) CONTROL-M messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 CONTROL-M Messages from Other Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 Appendix C Glossary Index Menu options 385 393 401
Contents
10
Figures
CONTROL-M product family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Group scheduling flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Job Dependency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 CONTROL-M workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 CONTROL-M/Enterprise Manager Login dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . 65 CONTROL-M/Enterprise Manager window (truncated) . . . . . . . . . . . . . . . . . . . . . . 68 Change Password dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Column header pop-up menu for list displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 List display pop-up menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Extract of an empty CONTROL-M/Enterprise Manager window . . . . . . . . . . . . . . . 77 CONTROL-M/Enterprise Manager window with one ViewPoint window . . . . . . . 78 Net Overview display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Node-specific conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Condition node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Condition node in the FlowDiagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Open ViewPoint dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Flowdiagram-Links panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Find/Select Jobs dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Navigating with Step In and Step Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Critical Path dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Enhanced Why dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Network Neighborhood dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 ViewPoint Wizard First window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 ViewPoint Wizard Hierarchy window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 ViewPoint Wizard Collection window Existing Collection pane . . . . . . . . . . . . 124 ViewPoint Wizard Collection window Collection pane . . . . . . . . . . . . . . . . . . . . 126 ViewPoint Wizard Filter window Existing Filter pane . . . . . . . . . . . . . . . . . . . . . 126 ViewPoint Wizard Filter window New Filter pane . . . . . . . . . . . . . . . . . . . . . . . . 128 ViewPoint Wizard Finish window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 ViewPoint Manager Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 ViewPoint Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Collection Definition window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Collection Definition edit operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Collection Definition window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Dynamic Filter dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Filter Definition window for defining global filters . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Filter Definition window Detailed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Hierarchy Definition window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Print Preview window example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Sample Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Figures 11
The Scheduling Table Manager window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Order/Force Jobs dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Advanced Order/Force Jobs dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Calendar Manager window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Calendar Definition Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Status Summary window General panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 CONTROL-M Status Summary panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Job Editing form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Job Editing form General panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Job Editing form General panel (for MVS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Job Editing form Active panel for MVS jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Job Editing form Execution panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Job Editing form Execution panel for MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Job Editing form Conditions panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Job Editing form Resources panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Job Editing form Set panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Job Editing form Steps panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Job Editing form Steps panel (for MVS jobs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 On Stmt fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Job Editing form PostProc panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Deleted Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Job Documentation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Job Script window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Job Log window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Job Restart dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Job Script window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Sysout Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Why Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Group Scheduling Table node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Group Editing form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Group Editing form General panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Group Editing form Active panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Group Editing form Conditions panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Group Editing form Set panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Group Editing form Shouts panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Group Editing form PostProc panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Alerts window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Alert Details window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Alerts panel of the Options dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Resources Filter dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 Control Resources window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Control Resource dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 View Jobs window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Resources Filter dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Quantitative Resources window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 Quantitative Resources Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Prerequisite Conditions Filter dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 Prerequisite Conditions window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 Prerequisite Condition dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
12
Global Conditions window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Global Condition Definition dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . New CONTROL-M Name dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Condition List for a job node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example of global conditions in CONTROL-M installations . . . . . . . . . . . . . . . . . . . Communication Status window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M/EM GUI Reconnect dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M/EM GUI - Reconnect Advanced dialog box . . . . . . . . . . . . . . . . . . . . Reporting Facility Start Page window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enter Parameter Values dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . New Report dialog box Generate Report From a Template . . . . . . . . . . . . . . . . . . Report Preview window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . New Template dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Wizard Title Bar and Panel Name For Report Template Definition . . . . . . . . . . Report Wizard General panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Report Wizard Data Source panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Add Mask dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Report Wizard Filter panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Report Wizard Fields panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Report Wizard Group By panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Report Wizard Sort panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Report Wizard Style panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Report Wizard Summary panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Report Wizard Data Source panel for the Active Links report . . . . . . . . . . . . . . . . . Report Wizard Filter panel for the Links Definition report . . . . . . . . . . . . . . . . . . . . Report Wizard Filter panel for the Audit report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . New Report Dialog Box Create Report Using the Report Wizard . . . . . . . . . . . . . Report Wizard Title Bar and Panel Name For Report Definition . . . . . . . . . . . . . Report Wizard Summary panel for a Report Definition . . . . . . . . . . . . . . . . . . . . . Report Template Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reporting facility Environment panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reporting facility Viewer panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reporting facility Confirmations panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Job Definition report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audit report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Active Jobs report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alerts Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Import Old Reports dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Open Archived ViewPoint Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Open Archived ViewPoint Wizard second window . . . . . . . . . . . . . . . . . . . . . . . . Playback toolbar displayed in the CONTROL-M/EM GUI . . . . . . . . . . . . . . . . . . . . Options dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Environment General panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Environment Display panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flowdiagram General panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flowdiagram Nodes panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flowdiagram Links Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flowdiagram Colors panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alerts panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
256 258 260 261 262 272 274 275 279 280 281 282 285 286 287 288 289 290 292 293 294 295 296 297 298 299 301 301 302 303 305 306 307 312 312 313 313 314 317 318 321 323 325 327 329 331 332 333 334
Figures
13
Reconnection panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 Diagnostics panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 Confirmations panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
14
Tables
CONTROL-M products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 CONTROL-M/EM components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Elements for user authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Group scheduling parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Quantitative resource information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Reaction of Quantitative resources to system events . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Log in command parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Symbols used to compose pattern-matching strings . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Examples of expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Sample node types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Node type icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Node state icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Job statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 High-level node status colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Job node states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Connector line colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Connector line menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Critical Path dialog box fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Enhanced Why dialog box fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Network Neighborhood dialog box fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Data fields of the All Jobs ViewPoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Collection selection criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Valid operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Status bar information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Print Preview actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Index columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 FlowDiagram-specific print settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Overview of defining and tracking jobs and scheduling tables . . . . . . . . . . . . . . . . . 161 Fields of the Order/Force Jobs dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Buttons of the Order/Force Jobs dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Advanced fields of the Order/Force Jobs dialog box . . . . . . . . . . . . . . . . . . . . . . . . . 172 Calendar types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Fields of the General panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Node properties CONTROL-M panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Panels of the Job Editing form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Job Editing form General panel fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Job Editing form General panel fields (for MVS) . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Job Editing form fields of the Active Panel for MVS jobs . . . . . . . . . . . . . . . . . . . . 186 Job Editing form Execution panel fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Job Editing form Execution panel for MVS fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Tables 15
In Condition parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 On Statement Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 On Statement parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 On Stmt parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Job actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Bypass options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Fields in the Activate Applications Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Buttons in the Activate Applications Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Group scheduling tables Action menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Group Editing Form panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 General panel fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Active Panel Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Alerts Window menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Alert Status Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Alert Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Alerts window Filter criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Alert Details window fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Open Into Local View section of the Alerts panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Filtering criteria for Control resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 Control Resources window columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Control Resources Window Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Filtering Criteria for Quantitative Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Quantitative Resources window columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 Quantitative Resources window buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Filtering criteria for Prerequisite conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 Prerequisite Conditions window columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 Prerequisite Conditions window buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 Global Conditions window Filter fields and Columns . . . . . . . . . . . . . . . . . . . . . . . 256 Global Conditions window buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Communication Status window components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 Communication Status fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 Reconnect operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Environment panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Viewer Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 emreportcli utility parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 Columns in the Open Archived ViewPoint Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 Playback toolbar functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 Default settings accessed by branches in the tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 Environment General panel default settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Environment Display panel default settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 Flowdiagram General panel default settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 Flowdiagram Nodes panel default settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 Flowdiagram Links panel default settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 Flowdiagram Colors panel default settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 Alerts panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Reconnection panel default settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 Diagnostic Panel fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339 Job tracking and control terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 Job Documentation Terms (MVS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
16
IOA conditions/resources terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IOA manual conditions - term cross-reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ISPF utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MVS job processing parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MVS Shout message destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . File Menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Edit Menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Action Menu options Legend: M: Menu bar, N: Navigation tree, F: FlowDiagram . . . . . . . . . . . . . . . . . View Menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resources Menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tools Menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Window Menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Help Menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Options of the FlowDiagram pop-up menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
346 347 347 348 351 385 385 386 389 390 391 392 392 392
Tables
17
18
About this book

This book describes how to use CONTROL-M/Enterprise Manager (CONTROL-M/EM) to manage production for your data center. This book describes all CONTROL-M/EM concepts, features, facilities, and operating instructions in detail. It also describes CONTROL-M job processing concepts and how they are applied using CONTROL-M/EM. This book is comprised of the following chapters:
Chapter /Appendix Chapter 1 Chapter 2
Description CONTROL-M/EM basics Introduces key features and concepts of CONTROL-M/EM. Viewing the production environment Describes CONTROL-M/EM windows for tracking and controlling the production environment, monitoring events, reviewing details of the environment, and determining which information should be displayed about the job production environment. Defining a production environment: Introduction to CONTROL-M/Desktop Describes how to force and order jobs. Managing job processing definitions Describes the CONTROL-M/EM mechanism for handling messages. Monitoring alerts and errors Describes how to view and modify details about jobs in the production environment. Displaying and defining resources and conditions Describes how to view and modify information about available resources and prerequisite conditions. Communication status Describes how to view information about communication between CONTROL-M/EM and the various CONTROL-M installations at your site. Reporting Facility Describes CONTROL-M/EM reports and how to request, tailor, and print these reports. Archived ViewPoints and Playback Describes options that can be used to modify the appearance of CONTROL-M/EM. Customization Describes how to set CONTROL-M/EM defaults.
Chapter 3 Chapter 4 Chapter 5
Chapter 6
Chapter 7
Chapter 8
Chapter 9
Chapter 10
About this book
19
Where to go from here
Chapter /Appendix Appendix A
Description CONTROL-M (MVS) and CONTROL-M/EM cross-reference Lists functions and parameters of CONTROL-M for OS/390 and z/OS and the equivalent terms in CONTROL-M/EM. Messages and codes Describes CONTROL-M messages that can be issued to the CONTROL-M/EM GUI. Menu options Provides a comprehensive list of all menu options, including descriptions and references to alternate methods for accessing the same option
Appendix B
Appendix C
Where to go from here
Users of CONTROL-M on an MVS platform: Before reading this book, refer to Chapters 1 and 2 in the CONTROL-M for OS/390 and z/OS User Guide for a description of basic CONTROL-M concepts and facilities. Users of CONTROL-M on distributed systems: It is recommended that you read Chapter 1, CONTROL-M/EM basics, for a basic description of CONTROL-M, and then, read Chapters 3 through 6 for a description of how to schedule, submit, monitor, and follow up execution of jobs in CONTROL-M data centers using the CONTROL-M/EM interface. If you are familiar with CONTROL-M: It is recommended that you read Chapter 1, and then proceed to the detailed descriptions of CONTROL-M/EM features later in this guide. If you have CONTROL-M installed on an MVS platform, it is also recommended that you review Appendix A, CONTROL-M (MVS) and CONTROL-M/EM cross-reference.
20
Related publications
Related publications
CONTROL-M/Enterprise Manager Installation Guide describes the installation processes for implementing CONTROL-M/EM and CONTROL-M/Server environments on Microsoft Windows and Unix platforms. CONTROL-M/Enterprise Manager Administrator Guide describes administrator responsibilities, customization, maintenance and security of CONTROL-M/EM. CONTROL-M/Desktop User Guide describes components used to define and manage CONTROL-M job processing definitions, Scheduling tables, and Calendars in CONTROL-M/Enterprise Manager. CONTROL-M Job Parameter and Variable Reference Guide describes the parameters of job processing definitions, and variables that can be included as values for these parameters. CONTROL-M/Enterprise Manager Utility Guide describes the utilities used for creating and managing the business integrated scheduling environment and maintaining various components of CONTROL-M/Enterprise Manager. CONTROL-M/Agent Administrator Guides each describe installation and maintenance of CONTROL-M/Agent on a supported platform. CONTROL-M/Control Module Administrator Guides each describe installation, maintenance, and implementation of a CONTROL-M/Control Module for a supported application (for example SAP or Oracle Applications). CONTROL-M for OS/390 and z/OS User Guide is a guide to the functions and facilities of CONTROL-M for OS/390 and z/OS. CONTROL-M/Enterprise Manager API Developers Guide describes how to enable your applications to submit requests to CONTROL-M/EM.
About this book
21
Conventions
Conventions
The following abbreviations are used in this guide:
Abbreviation CONTROL-M/EM Net home-directory Description CONTROL-M/Enterprise Manager CONTROL-M/EM Network Directory in which CONTROL-M/EM is installed
The following conventions are used in this guide:

key When describing keystrokes, the name of a key (for example, F1) is in boldface type. When two keys are joined with + as in Shift+F1, hold down Shift while pressing F1. This represents an option selection sequence. For example, Users and Groups => Groups => Add means that you first select Users and Groups from the menu bar. Select the Groups option from the submenu. Finally, select the Add option from the Groups submenu. {Option A|Option B} The vertical bar is used to separate choices. For example: {AND|OR} means that you specify either AND or OR. [Option] Command Script Boldface Square brackets are used to enclose parameters that are optional. All syntax, operating system terms, and literal examples are presented in this typeface. In instructions, boldface type highlights information that you enter. File names, directory names and paths, parameters, and Web addresses also appear in boldface type. Messages are presented in this font.
Menu => Option
Messages
22
Chapter
CONTROL-M/EM basics
Basic concepts
BMC Softwares CONTROL-M/Enterprise Manager (CONTROL-M/EM) enables you to control the business processes for your entire enterprise from a single workstation. CONTROL-M/EM also allows you to view process flow and dependencies so that you can optimize business processes easily and efficiently, even in a data center that includes multiple platform types (for example, Unix, Microsoft Windows, and MVS). CONTROL-M/EM is part of the CONTROL-M Business Integrated Scheduling solution. It works together with CONTROL-M on all supported platforms. Table 1 lists the products that are part of the CONTROL-M scheduling solution. Table 1
Product CONTROL-M/ Enterprise Manager CONTROL-M/Server
CONTROL-M products
Description The central GUI-based control center from which you can manage all scheduling and workflow activities. The engine (on a Unix or Microsoft Windows computer) used to schedule jobs in a data center. Each CONTROL-M/Server can manage multiple CONTROL-M/Agents on various platforms. Software for job submission and execution. An Agent must exist on each computer that executes CONTROL-M jobs. A web-based product that enables you to use input from a web page to create and run jobs under CONTROL-M. Control Modules enable CONTROL-M/Agents to interface with other applications (for example, SAP and Oracle Applications). A web-based interface for performing job handling tasks via the internet.
CONTROL-M/Agent CONTROL-M/eTrigger CONTROL-M/Control Modules CONTROL-M/ WebAccess
PATROL Knowledge Used by BMC PATROL software to monitor CONTROL-M Module for CONTROL-M status.
Chapter 1
CONTROL-M/EM basics
23
Basic concepts
Figure 1
CONTROL-M product family
CONTROL-M/EM consists of several components. The CONTROL-M/EM GUI component runs as an application on Microsoft Windows. Other components of CONTROL-M/EM can run on either a Microsoft Windows computer, or a Unix computer. The various components are described briefly in Table 2. For detailed descriptions of these components, see the CONTROL-M/Enterprise Manager Administrator Guide.
24
Basic concepts
Table 2
Component
CONTROL-M/EM components
Description
CONTROL-M/EM Installed on one or more computers running Microsoft Windows. GUI This component is used to monitor the active scheduling environment. You can configure the GUI to display only selected information. The CONTROL-M/EM GUI is one of the basic client components that are required on every CONTROL-M/EM Windows user workstation. You can also modify the active environment (for example, to rerun or delete a job) using the CONTROL-M/EM GUI. For more information, see Chapter 2, Viewing the production environment. CONTROL-M/EM Handles communication between each CONTROL-M/EM GUI and the GUI Server other components of CONTROL-M/EM. The GUI Server streamlines productivity by enabling data-sharing between the various CONTROL-M/EM GUIs. Multiple CONTROL-M/EM GUI Servers can be installed on various computers in a CONTROL-M/EM environment. However only one GUI Server can be active per computer at a given time. CONTROL-M/ Desktop Used to define and manage job processing definitions, scheduling tables and calendars. CONTROL-M/Desktop is one of the basic client components that are required on every CONTROL-M/EM Windows user workstation. For more information, see the CONTROL-M/Desktop User Guide. CONTROL-M/EM The repository for all CONTROL-M/EM information, including: Database Job processing definitions copied from CONTROL-M/Server databases in the various CONTROL-M installations.
Information about active jobs and available resources in all CONTROL-M installations connected to CONTROL-M/EM. Communication status of all CONTROL-M installations and CONTROL-M/EM components. ViewPoints, collections, hierarchies and global filters, defined for all CONTROL-M/EM GUIs. CONTROL-M/EM security definitions for workstations and for specific users. The operational status of CONTROL-M/EM components (reported by the Administration Facility agents).
Chapter 1
CONTROL-M/EM basics
25
Basic concepts
Table 2
Component
CONTROL-M/EM components
Description
Global Conditions Global conditions enable you to make jobs in one CONTROL-M Server installation dependent on the completion of jobs in a different installation. The Global Conditions server uses the CONTROL-M/EM gateways to distribute Global conditions to the appropriate CONTROL-M installations. For more information, see Global conditions on page 255. Global Alerts Server Alerts are generated by CONTROL-M and by CONTROL-M/EM to describe problems related to a job or a communications problem. The Global Alerts server uses CONTROL-M/EM gateways to distribute alert messages to the appropriate CONTROL-M installations or to the CONTROL-M/EM workstation from CONTROL-M. For more information, see Chapter 5, Monitoring alerts and errors. Processes that handle communication between CONTROL-M and CONTROL-M/EM. There are gateways on each CONTROL-M platform and on the CONTROL-M/EM workstation. For more information, see the CONTROL-M/Enterprise Manager Installation Guide. Programs that can be used to perform job definition, scheduling, and maintenance functions from a command line or using the Command parameter in a job processing definition. The Command Line Interface is one of the basic client components that are required on every CONTROL-M/EM Windows user workstation.
Gateways
Command Line Interface Utilities
Utilities for CONTROL-M/Server are described in the CONTROL-M/Server Administrator Guide. Utilities for CONTROL-M/EM are described in the CONTROL-M/Enterprise Manager Utility Guide.
Administration Facility Agent
An Administration agent is installed on every computer containing a CONTROL-M/EM component. The Administration Agent is used to start and stop the CONTROL-M/EM components and maintains contact with the CONTROL-M/EM database. The Administration Facility is one of the administrator client components that can optionally be installed. For more information about Administration Agents, see the CONTROL-M/Enterprise Manager Administrator Guide.
Reporting Facility A facility for generating reports about CONTROL-M/EM functioning. The Reporting Facility is one of the administrator client components that can optionally be installed. For more information about the available reports, see Producing reports on page 30 and Chapter 8, Reporting Facility.
26
Managing your scheduling environment

The CONTROL-M/EM environment consists of all jobs scheduled for submission by CONTROL-M. Jobs can be linked to each other by scheduling instructions and dependencies, specified in user-defined job processing parameters. The Active environment consists of the Active Jobs file (which contains jobs that have been ordered for submission), the conditions table, and the resources table. Changes made in the current Active environment using CONTROL-M/EM affect the relevant CONTROL-M installations. The Active environment is created and updated when CONTROL-M/EM downloads information from connected CONTROL-M installations. Downloads are described in Network communication on page 32.
Viewing the production environment of the enterprise

Jobs that have been ordered for submission are viewed from the main CONTROL-M/Enterprise Manager window. The jobs that are visible in this window can be limited and sorted according to various fields. Each resulting combination based on the specified criteria is referred to as a ViewPoint. ViewPoints are defined using either the ViewPoint Manager or ViewPoint Wizard. Multiple ViewPoints can be loaded and viewed simultaneously, each in its own window. If a ViewPoint is displayed in the CONTROL-M/EM window, documentation refers to the window as the CONTROL-M/EM ViewPoint window. For more information about the CONTROL-M/EM window, the CONTROL-M/EM ViewPoint window, and the ViewPoint Wizard, see Chapter 2, Viewing the production environment.
Archive network environment Defining jobs and groups

Each job in your production environment is represented in CONTROL-M/EM by a job processing definition. The job processing definition is a collection of parameters that

describe the job control scheduling describe dependencies between jobs specify tasks for CONTROL-M to perform on job completion
Creating good job processing definitions is the key to getting the most out of CONTROL-M/EM. For more information about defining job processing definitions, see the CONTROL-M/Desktop User Guide.
Chapter 1 CONTROL-M/EM basics 27
NOTE
CONTROL-M/Desktop can be used to define jobs for specific applications (for example, Oracle Applications and SAP). These jobs are passed to the CONTROL-M Control Module for the specific application. For more information about specific applications, see the Administrator Guide for the appropriate CONTROL-M Control Module.
Job processing definitions can be scheduled together using a Group Scheduling table. Parameters specified in the Group definition are applied to all the jobs in the table. For example, you can have CONTROL-M/EM send a Shout message to the CONTROL-M/EM administrator after all the jobs in the Group Scheduling table have finished running. For more information about Group Scheduling tables, see Group scheduling tables on page 40.
Specifying variables
For Unix scripts and JCL scripts on an MVS platform, special variables (called AutoEdit variables) offer an automated alternative to manual script modification. AutoEdit variables, functions, and expressions are used in place of values that change from job submission to job submission. At time of job submission, these terms are resolved to their actual values. AutoEdit variables can also be used to

access information about the system under which the job is running pass information to a job or change working parameters for a job pass information using a Shout message to a user when the job ends
AutoEdit variables cannot refer to application-specific parameters. For more information, see the CONTROL-M/EM Job Parameter and Variable Reference Guide.
Scheduling
The New Day procedure and User Daily jobs are used for automatic scheduling of jobs. Each time the CONTROL-M New Day procedure is run or a User Daily job is run, it reviews a list of specified scheduling tables. Each scheduling table contains a collection of job processing definitions. When a Scheduling table is ordered or forced, (for example, by the New Day procedure) the jobs in the table are submitted to CONTROL-M and are run when appropriate according to their individual scheduling criteria.
28
Scheduling tables can be used to group jobs for submission in a logical way (for example, a scheduling table containing jobs related to accounting). For more information, see New Day processing on page 43.
Handling conditions
A condition is a flag representing a user-specified situation or set of circumstances. Submission of a job for execution can be made dependent on the existence of one or more prerequisite conditions. Prerequisite conditions are listed in the Prerequisite Conditions window in the CONTROL-M/EM GUI. Conditions can be created by dragging a line between two job nodes in the CONTROL-M/EM flow diagram or by specifying In or Out conditions in a job processing definition. For more information, see Chapter 6, Displaying and defining resources and conditions.
Global conditions
Global conditions are prerequisite conditions that can affect jobs in data centers other than the one in which the condition was created. For more information, see Global conditions on page 255.
Handling system resources

Certain types of jobs often require system resources. Examples of resources include hard disk space, RAM, and CD-ROM drives. CONTROL-M/EM enables you control over sharing or delegating resources on a job-by-job basis. Resource availability is a condition for running a job. If the specified quantity of a resource is not available, the job is not run. Planning resource distribution ensures efficient business processes and prevents system deadlocks. Each resource is defined as a user variable called a Quantitative or a Control resource:
Control resources. Judge resource availability according to the state of the resource (shared or exclusive). For each job you can specify whether the job requires exclusive or shared access to the resource. CONTROL-M ensures that a job is not submitted for execution unless the Control resources required by the job are available and that they are in the required state. Quantitative resources. The user defines the total quantity of a resource in the CONTROL-M and, for each job, the quantity required by that job. CONTROL-M ensures that a job is not submitted for execution unless the Quantitative resources required by the job are available.
For more information, see Submission criteria on page 45 and Chapter 6, Displaying and defining resources and conditions.
Chapter 1 CONTROL-M/EM basics 29
CONTROL-M/EM administration tasks
Calculating critical path

A critical path is the maximum amount of runtime for a series of jobs. You can calculate the critical path for a series of jobs by selecting the first and last job of the series in the FlowDiagram view of the active ViewPoint in CONTROL-M/EM. Calculating critical paths can help you make decisions about when and under what conditions to run complicated procedures that may involve different combinations of interdependent jobs. For more information, see Critical path on page 99.
Producing reports
You can produce reports based on many aspects of the job production environment using the Reporting facility. Reports help you to

compile job production data for presentations create a historical record of your sites operations identify problems in the active environment prevent problems in job processing definitions by identifying them before they are entered into the active environment
The Reporting facility includes a variety of templates that can be used to examine vital areas of the job production process. These templates can be modified to limit the information provided about each job in the report. For example, you can use the Alerts report template to generate a summary of all jobs that prompted alerts on a given data center. Use this information to analyze the cause of errors in your system. Reports can be based on data in either the active environment or the job definition environment. For more information, see Chapter 8, Reporting Facility.

The following pages focus on various tasks and facilities that are used to manage and monitor CONTROL-M/EM components.
Monitoring CONTROL-M/EM components

You can monitor the performance and status of CONTROL-M/EM components using the Administration facility. You can also print or export to a file the list of CONTROL-M/EM components and system parameters (for details, see Performing other tasks in the list display on page 72). This facility also includes options for modifying many of the components.
30
NOTE
The Administration facility should be used only by CONTROL-M/EM administration personnel. For more information about this facility, see the CONTROL-M/Enterprise Manager Administrator Guide.
Defining user authorizations

CONTROL-M/EM User Authorizations can be used to limit what each user is authorized to view or change in the active environment and in the CONTROL-M/EM database. For example, a user can be limited to viewing only alerts, resources, or jobs for a specific CONTROL-M. CONTROL-M/EM security can be defined for specific users and for groups of users. Authorizations defined for a specific user override group authorizations for that user. Table 3 list elements of CONTROL-M/EM that can be controlled using User Authorizations. For more information, see the CONTROL-M/Enterprise Manager Administrator Guide. Table 3
Jobs
Elements for user authorization

All aspects of job creation, modification, and deletion are subject to authorization. For example, you can allow a given user to view jobs from only the specified CONTROL-M in the CONTROL-M/EM ViewPoint window. In this case, the Alerts window displays only alerts originating from the specified CONTROL-M installation.
Resources and conditions
User Authorizations can limit what the user can view or modify in the resource or conditions window. This does not relate to resources and conditions displayed in the Job Editing form. For example, in the Job Editing form, the user may see that a job requires a specific prerequisite condition, but may not be authorized to create this condition using the Prerequisite Conditions window.
Calendars and Scheduling tables ViewPoints Administrative responsibilities
What you can view or modify is subject to authorization. Limiting access to Scheduling tables also determines which Scheduling tables/jobs you can order or force. What you can modify in the ViewPoint Wizard and the Viewpoint Manager window is subject to authorization. CONTROL-M definitions and security authorizations that you can access, and Command Line Interface (cli) utility privileges are subject to authorization.
Chapter 1
CONTROL-M/EM basics
31
Network communication
All CONTROL-M installations in your enterprise must be connected to CONTROL-M/EM using communication hardware and software. Connectivity hardware and software requirements and installation information are described in the CONTROL-M/Enterprise Manager Installation Guide. Each CONTROL-M is connected to a CONTROL-M/EM GUI using a separate gateway. Separate gateways ensure that data transmission from each CONTROL-M to CONTROL-M/EM is not affected or interrupted by communication with other CONTROL-M installations.
NOTE
In CONTROL-M/EM, the term Download describes the transfer of information from the database in a CONTROL-M to the CONTROL-M/EM database.
Data from the CONTROL-M is downloaded to CONTROL-M/EM in the following ways.
Global download CONTROL-M/EM automatically downloads the Active environment of each CONTROL-M at the beginning of each working day. For more information, see Global download on page 33. Specific download When you perform an action (such as Hold, Delete, or Rerun), the information is transferred from the workstation to the relevant CONTROL-M. You can also request specific CONTROL-M information, such as a jobs Sysout or script file. For more information, see Specific download on page 34.
Gateway synchronization
When a CONTROL-M/EM gateway and a specific CONTROL-M installations gateway are up and the link is available, communication is synchronized and data from the CONTROL-M can be downloaded to CONTROL-M/EM. Communication may temporarily not be synchronized in either of the following cases:

Communication has failed (the physical link has broken). A New Day procedure is updating the Active Jobs file in a CONTROL-M installation.
In both cases, CONTROL-M/EM prevents you from making any changes related to the affected CONTROL-M. You can continue to access and update all other parts of the active environment that are synchronized.
When the physical link is reconnected or the New Day procedure is completed, synchronization automatically resumes. You can refresh the display to reflect the resynchronized environment using the refresh button. (For more information, see Refreshing the display on page 93.)
NOTE
If communication from a CONTROL-M is temporarily halted, other CONTROL-M installations are not affected. Each CONTROL-M maintains its own connection to the CONTROL-M/EM environment using a separate gateway.
Global download
Each day, after the New Day procedure has been run in a CONTROL-M, CONTROL-M/EM automatically initiates a Download process for that CONTROL-M. The following information is downloaded from each CONTROL-M:

Active Jobs file Runtime statistics Quantitative resources, Control resources and prerequisite conditions
The time for download from each CONTROL-M is the time specified for the New Day procedure to run in that CONTROL-M. CONTROL-M/EM can communicate with all connected CONTROL-M installations with the exception of the CONTROL-M that is currently downloading. Information from all the CONTROL-M installations is automatically combined into the Active environment. During communication failure, each disconnected CONTROL-M accumulates scheduling events (such as job status changes or additions of new prerequisite conditions) that occur while it is disconnected. When communication is resumed, the CONTROL-M transfers to CONTROL-M/EM only the accumulated events required to update the Active environment. In certain cases a full download is performed when a CONTROL-M is reconnected. This occurs if one or more of the following conditions exist:
Disconnect time is very long, and the number of accumulated events exceeds memory capacity. Communication failed due to IPL, boot, or CONTROL-M gateway problems. A New Day procedure or Active Job Table Compress procedure executes in a CONTROL-M while it is disconnected. (This procedure is used only with CONTROL-M for MVS platforms.)
Chapter 1
CONTROL-M/EM basics
33
Specific download
Certain types of actions require specific information to be downloaded from CONTROL-M to CONTROL-M/EM. You can view or modify this information. If information is modified, it is returned to the relevant CONTROL-M. For example, you can view a jobs log and modify the job script statements. Specific downloads are also performed in the following cases:
Any action you perform, such as holding, deleting, or re-running a job, is transferred automatically to the relevant CONTROL-M via synchronized communication. When an event occurs in a CONTROL-M (for example a job ends OK), CONTROL-M automatically transfers the information and updates the Active environment in CONTROL-M/EM.
Defining CONTROL-M installations

Before CONTROL-M/EM can view and administer jobs on a CONTROL-M installation, the CONTROL-M must be defined in the CONTROL-M/EM database. A CONTROL-M definition includes information that CONTROL-M/EM uses to identify the CONTROL-M and communicate with it. CONTROL-M installations that are registered in the CONTROL-M/EM database are listed in the Communication Administration window. For more information about defining CONTROL-M installations, see the CONTROL-M/Enterprise Manager Administrator Guide.
Root menu operations

Many administrative functions can be performed using the root menu on Unix computers. CONTROL-M/EM includes a special menu system that can be accessed from the root menu in order to perform these functions. The menu functions affect only CONTROL-M/EM components and processes installed on Unix computers. The root menu and its sub-menus can be used to
create and maintain the CONTROL-M/EM database start and stop the database server, the CORBA Server, or the maintenance agent troubleshoot problems in the gateway, the database, and the Global Conditions Server
34
CONTROL-M/Server concepts
NOTE
The root menu can be used only on a Unix machine to affect components on Unix machines. To administer CONTROL-M/EM on both Windows and Unix computers, use the Administration facility. For more information about the root menu and the Administration facility are described in the CONTROL-M/Enterprise Manager Administrator Guide.
The following topics are described:

Automated job scheduling Load balancing Allocation and monitoring of system resources Tracking and monitoring job execution Immediate detection and notification of problems Variables in a dynamic working environment Sysout (job log) control Shout messages
CONTROL-M Server/Agent technology

For most operating systems and platforms, CONTROL-M/EM communicates with a CONTROL-M/Server that in turn manages one or more CONTROL-M/Agents.
CONTROL-M/Server runs on a Unix or Microsoft Windows computer (referred to as the Server platform). CONTROL-M/Server performs all scheduling and job tracking functions. It also maintains the CONTROL-M database and communicates with CONTROL-M/EM. CONTROL-M/Agent runs on each production platform (referred to as an Agent platform) and executes job handling requests received from CONTROL-M/Server. Any number of Agents on various operating systems can be managed by a single CONTROL-M/Server.
NOTE
For OS/390 or z/OS computers, CONTROL-M is run as a single application that performs both server and agent functions. For more information, refer to the CONTROL-M for OS/390 and z/OS User Guide.
Chapter 1
CONTROL-M/EM basics
35
A typical job flow proceeds as follows: 1. A job waits to be submitted on the Server platform. 2. When all its prerequisite conditions, resource requirements and scheduling requirements are satisfied, CONTROL-M/Server instructs CONTROL-M/Agent to submit the job. 3. CONTROL-M/Agent submits the job for execution. 4. CONTROL-M/Agent monitors the job and reports any exceptional situations to CONTROL-M/Server. 5. Upon completion of the job, CONTROL-M/Agent performs post-processing analysis. No job output (Sysout) needs to be transmitted over the network, keeping network resource consumption at an absolute minimum. Each Agent platform is known to CONTROL-M/Server by its node ID. This is the Agent platforms host name. The node ID is used in various parameters related to scheduling jobs, as described below. To specify on which Agent platform a job should be submitted by CONTROL-M/Server, you can specify the Agent platforms node ID in the Jobs Processing definition (in the field Node ID/Group).
NOTE
You can also use the load-balancing feature to distribute jobs dynamically between Agent platforms according to available resources. For more information, see Load balancing on page 54.
Automated job scheduling

Jobs can be scheduled by date and time, job priority, predecessor job completion, availability of input, and dependencies upon other events. This information is specified by the user in job processing definitions. Jobs can also be scheduled according to special calendars that are created using the Calendar facility. Calendars can define work days, weekends, holidays, and so on for each CONTROL-M installation. Even after a job has been scheduled, it is not submitted for execution until its runtime requirements (for example, availability of a tape drive) are satisfied. When the runtime requirements are satisfied, the job is submitted automatically (without requiring operator approval).
36
Load balancing
In CONTROL-M installations using Server/Agent technology, CONTROL-M can monitor resource availability on Agent platforms across the network. Using load balancing, CONTROL-M can then determine which Agent platform has sufficient available resources to handle execution of a job at a given moment and submits the job to that platform. In this way, CONTROL-M ensures efficient utilization of available resources and helps achieve maximum production performance. For more information about how load-balancing works, see Load balancing on page 54.
Allocation and monitoring of system resources

CONTROL-M monitors resources according to logical names specified by the user. CONTROL-M submits a job only when all resources required by the job are available. CONTROL-M allocates the necessary resources and submits the job. Resource management prevents bottlenecks with multiple jobs waiting for a particular resource. CONTROL-M also allows logical definition of resources that are otherwise not usually controlled (for example, CPU utilization). Utilization of the resource is controlled by logically defining how much of the resource is available and how much of it is required by each job. For more information about resources, see Handling system resources on page 29.
Tracking and monitoring job execution

CONTROL-M automatically follows all processing stages of scheduled jobs (in queue, executing, and completed). Information about jobs being processed is downloaded to CONTROL-M/EM. For more information about job tracking, see Chapter 2, Viewing the production environment.
Immediate detection and notification of problems

When a problem or an unexpected situation occurs, CONTROL-M notifies appropriate personnel. These situations are detected by analysis of error messages, operating system prompts, and so on.
Chapter 1
CONTROL-M/EM basics
37
Notification can be issued using either a Do Mail message or a Shout message. Do Mail sends messages to one or more e-mail addresses. A Shout message can be sent to a variety of destinations, including the CONTROL-M/EM workstation, the CONTROL-M log, e-mail, a logical or specific user, or any terminal. For more information, see Do Mail and Do Shout in the CONTROL-M Job Parameter and Variable Reference Guide. CONTROL-M can also be instructed to:
issue a Shout message if an exception occurs during submission or execution of a job (for example, a job completes well before, or takes longer than, its anticipated execution time) issue an alert to the Alerts window using the Global Alert facility (for more information, see Chapter 5, Monitoring alerts and errors)
Variables in a dynamic working environment

CONTROL-M allows you to include special variables (AutoEdit variables) in job processing definitions. These variables can be used to automatically assign values that identify the operating environment to job execution parameters. Before the job is submitted, the jobs AutoEdit variables are resolved by CONTROL-M. The resolved values can then be passed as parameters of the job submission command and be used for the current execution of the job. The original job processing definition remain unchanged. For example, if the original scheduling date of a job is required as a submission parameter for the job, the AutoEdit variable representing the original scheduling date (%%ODATE) can be assigned to a submission parameter in the job processing definition. CONTROL-M automatically resolves the variable to the original scheduling date of the job and passes that value to the job when it is submitted for execution. For more information, see the CONTROL-M Job Parameter and Variable Reference Guide.
Sysout (job log) control

CONTROL-M can print or delete a jobs log, or move or copy the log to a specified library or directory. Based on specifications in the job processing definition, CONTROL-M can dynamically determine how to handle the jobs log.
38
Scheduling concepts
Shout messages
A Shout message is a communication sent to one or more destinations if certain specified conditions exist when a job is executed or completes execution. Destinations for Shout messages include the CONTROL-M/EM Alerts window, the CONTROL-M log, the system console, terminals, or a specific users. Potential recipients of Shout messages are defined in the Shout Destination table of the CONTROL-M installation. By switching to a different Shout table, you can alter the recipients of messages targeted for specific logical addresses.
Scheduling concepts
The following concepts are described in this section:

Job processing definitions Group scheduling tables New Day processing Date definition concepts Submission criteria
Job processing definitions

A job processing definition is a user-defined set of parameters that specify how CONTROL-M should handle a particular job (for example, when to schedule the job, when to submit it, and what to do after the job executes). Job processing definitions consist of the following types of parameters:
General Scheduling Criteria General information about the job (including a description of the job, and where the job script is stored). When the job should be scheduled (when it should be inserted into the Active Jobs file). Actions that CONTROL-M should perform after execution of the job.
Submission Criteria Criteria that must be satisfied before the job is submitted for execution. Post-Processing
Job processing definitions are grouped into scheduling tables. For example, you can organize jobs that are run together (concurrently or in sequence) by placing them in the same scheduling table.
Chapter 1
CONTROL-M/EM basics
39
Scheduling concepts
Job processing definitions and Scheduling tables are created and maintained using the CONTROL-M/EM Graphical User Interface (GUI). They need only be defined once. After being created or modified, they are uploaded from CONTROL-M/EM to the CONTROL-M installation, where they are stored in the CONTROL-M database.
Group scheduling tables

Jobs whose processing (scheduling, submission and post-processing) should be handled as a group, can be defined in a special Scheduling table, called a Group Scheduling table. Each Group Scheduling table consists of the processing definitions for each job in the group. It also contains preprocessing and post-processing parameters to be applied to all jobs in the Group Scheduling table. Defining common information for all jobs in a group saves you time and enforces standardization of production handling for the relevant jobs.
NOTE
CONTROL-M/EM does not support definition of Group Scheduling tables for CONTROL-M for OS/390 and z/OS versions earlier than 6.0.00.
A Group Scheduling table contains processing parameters usually found in the job processing definitions of individual jobs. The processing parameters defined for the Group Scheduling table are applied to all jobs in the table. The following types of information can be defined for a Group Scheduling table: Table 4 Group scheduling parameters
Description Indicate conditions that must exist before any job in the group can be run. Indicate conditions that may be created depending on the completion status of the group. Variables to be set before each job in the group is submitted.
Parameter Type In conditions Out conditions AutoEdit variables
Shout messages Messages to be sent under certain conditions when all the jobs in the group have finished executing. Post-processing Indicate actions to be performed when all jobs in the group have finished executing. Schedule Tags A Schedule Tag is an identifier given to a set of scheduling criteria. Each Group Scheduling table contains one or more Schedule Tags and associated sets of scheduling criteria. Each job processing definition in the Group Scheduling table specifies one or more Schedule Tags to be combined with basic scheduling criteria using And/Or logic. Scheduling criteria (tags) for the Group Scheduling table and the jobs basic scheduling criteria are combined using the Relationship parameter. For more information, see Group scheduling workflow on page 41 below, and the Schedule Tag and Relationship parameters in the CONTROL-M Job Parameter and Variable Reference Guide.
40
Scheduling concepts
Group scheduling workflow

The scheduling of a job in a Group Scheduling table is dependant on:
scheduling criteria specified in the job processing definition scheduling criteria of the Schedule Tags that are referenced in the job processing definition scheduling criteria of the Schedule Tags that are not referenced in the job processing definition the Relationship parameter
The following scheduling algorithm applies to Group Scheduling tables:
1 Before jobs in a group can be scheduled, the group must be eligible for scheduling
for the current day (at least one of the Schedule Tags in the Group Scheduling table must be satisfied).
2 If (and only if) the group is eligible for scheduling, each job processing definition in
the Group Scheduling table is individually considered for possible scheduling.
3 For each job processing definition: A The jobs basic scheduling criteria are checked. B The Relationship parameter (AND/OR) is checked.
If the jobs basic scheduling criteria are satisfied and the relationship is OR, the job is scheduled according to the jobs basic scheduling criteria. No further checks are performed. If the jobs basic scheduling criteria are not satisfied and the relationship is AND (i.e., the job requires that a the jobs basic scheduling criteria be satisfied), the job is not scheduled. No further checks are performed. If the jobs basic scheduling criteria are satisfied and the relationship is AND, or if the jobs basic scheduling criteria are not satisfied and the relationship is OR, the criteria of a Schedule Tag specified for the job must be satisfied. The algorithm continues with the next step.
NOTE
If there are conflicting MAXWAIT values in the jobs basic scheduling criteria and the Schedule Tag criteria, and Relationship is AND, the MAXWAIT value from the jobs basic scheduling criteria is used.
Chapter 1
CONTROL-M/EM basics
41
Scheduling concepts
C Schedule Tags in the job processing definition are checked sequentially

beginning with the first tag. If the criteria of a Schedule Tag are satisfied the job is scheduled. No further checks are performed on the remaining Schedule Tags. If the criteria of none of the Schedule Tags are satisfied, the job is not scheduled.
NOTE
For each job in the Group Scheduling table, the AutoEdit variable %%$TAG contains the name of the Schedule Tag by which the job was scheduled. If the Group Scheduling table was forced, or if the job was scheduled based on the jobs basic scheduling criteria, this value resolves to blanks.
Figure 2 on page 42 illustrates the Group Scheduling algorithm. Figure 2 Group scheduling flowchart
42
New Day processing
Group completion status and postprocessing

Post-processing for a group is performed only after all jobs that were ordered in the Group Scheduling table have been completed or timed out. At this time the group is assigned a completion status, and the post-processing actions specified for the group completion status are performed.
If one or more jobs ended with errors (NOTOK), the group is assigned a status of Not OK. If all jobs in the group ended successfully, the group is assigned a status of OK.
If a group is reactivated because jobs in the group were rerun or new jobs were ordered into that group after the group finished, the completion status of the group is reevaluated when the new jobs are completed, and post-processing for the group is performed dependant on the new completion status.
NOTE
If there are no jobs submitted in a group (for example, due to basic scheduling criteria), the completion status of the group is OK. Post-processing actions for a group completion status OK are performed.
New Day processing

At the beginning of each working day CONTROL-M activates the New Day procedure to automatically order jobs (place them in the Active Jobs file) based on scheduling criteria. This procedure also performs various maintenance tasks for CONTROL-M. Many sites (generally larger sites with many jobs and departments) prefer to schedule jobs via User Daily jobs. In this case, the New Day procedure activates a User Daily job for each department and then each User Daily job scans the related departments Scheduling tables for potential job orders. The advantage of scheduling jobs via a User Daily rather than the New Day procedure is that it provides a department (or comparable entity) with greater control over the daily ordering of its own Scheduling tables.
Chapter 1
CONTROL-M/EM basics
43
New Day processing
New Day processing works as follows: 1. The New Day procedure scans the Scheduling tables assigned to it and determines which jobs in the Scheduling tables are potential job orders for that day (based on scheduling criteria). This includes the ordering of User Daily jobs, if defined. 2. The New Day procedure places potential job orders (copies of the selected Job processing definitions) in the Active Jobs file. Each job is assigned a unique order ID. 3. If User Daily jobs exist (and are activated by the New Day procedure), these jobs scan assigned Scheduling tables, select jobs (based on scheduling criteria) and place job orders in the Active Jobs file. 4. After the job orders are placed in the Active Jobs file, CONTROL-M controls their processing. For information about what happens next, see CONTROL-M job flow and handling on page 51.
Date definition concepts

CONTROL-M includes a wide variety of date parameters that can be used to determine when jobs will be scheduled. To understand how date parameters are processed, it is important for you to understand the following date types:
System date The regular calendar date as supplied by the operating system (i.e., starting and ending at midnight).
Installation working Many sites do not use midnight as the formal time for changing to a date new date. For example, at a bank transactions between the hours of 1:00 p.m. and midnight may belong to the next days transactions. In this case, the installation working date at the site changes at 1:00 p.m., not at midnight.
The installation working date ( the time at which the date changes at the site) is defined in CONTROL-M installation parameters. The processing of a new date (execution of the New Day procedure) starts at this time. Original Scheduling Job orders and prerequisite conditions managed by CONTROL-M date are assigned an original scheduling date (referred to as Odate).
For jobs, the Odate is the date on which the job should be scheduled for execution. For conditions, the Odate in the date on which the condition was created.
The importance of the Odate is illustrated by the following example.
44
New Day processing
EXAMPLE
A computer is down for repairs on Feb. 2nd and 3rd. When it is brought up on Feb. 4th, a two-day backlog of jobs must be run in addition to the jobs of the current day. When the New Day procedure scans Scheduling tables on Feb. 4th, it places job orders in the Active Jobs file for all three days (if those jobs had Yes specified for the Retro parameter). Jobs that should have run on Feb. 2nd are assigned an Odate of Feb. 2nd. Jobs for Feb. 3rd are assigned an Odate of Feb. 3rd, etc. Each job is executed as if it is running on its originally-scheduled execution date.
Submission criteria
To prevent bottlenecks and help guarantee successful execution of jobs, CONTROL-M provides tools to ensure that a job is not submitted for execution until:

All requirements for the job have been met. All resources required by the job are available.
This is accomplished by specifying submission criteria as part of the job processing parameters for each job handled by CONTROL-M. Submission criteria include:

Job priority Control resources Quantitative resources Prerequisite conditions Agent platform resources (see Load balancing workflow on page 62). Time limits for the job Elapsed time since the jobs last run (for cyclic jobs, or when job recovery is performed).
Job priority
A job priority can be specified in the job processing definition. When competing for the same resource, jobs with higher priority take precedence over jobs with lower priority. You can also assign a critical path priority to jobs that must be submitted with the least delay possible:
A job with critical path priority is allocated required resources as soon as they become available. When all required resources are available, the job is submitted. Non-critical jobs are not allocated resources until all the required resources are available.
Chapter 1
CONTROL-M/EM basics
45
New Day processing
Control resources
Specification of Control resource requirements for a job helps prevent resource contention between jobs. For each resource, you can specify whether it is required by the job in Exclusive or Shared mode. CONTROL-M considers the mode of resource usage required when allocating Control resources and prevents jobs whose resource usage is incompatible from executing simultaneously. Example Three different jobs require access to a specific database. Job DB_Access and job DB_Update can each access the database without interfering with each other. The third job, DB_Reorg, requires exclusive access to the database when it runs; it cannot share access to the database with other jobs. The three jobs are defined with job processing parameters as follows:
Job DB_Access Control Resource: DB Type: shared Job DB_Update Control Resource: DB Type: shared Job DB_Reorg Control Resource: DB Type: exclusive
The name DB is assigned by the user to represent the database. CONTROL-M handles access to this resource as follows: 1. Initially, Control resource DB has no status since it is not in use. 2. When job DB_Access is running, resource DB is classified as shared. 3. If the DB_Update job and the DB_Reorg job are both ready to submit while the DB_Access job is running, CONTROL-M will submit DB_Update because this job can access the DB resource in shared mode. The DB_Reorg job is not submitted because it requires exclusive access to the resource. 4. When the DB_Access and DB_Update jobs both complete execution, the DB resource is no longer classified as shared. 5. CONTROL-M now submits the DB-Reorg job. While DB_Reorg is running, the DB resource is classified as exclusive. 6. If the DB_Access job or the DB_Update job is reordered at this point, CONTROL-M will not submit the job until the DB_Reorg is finished, because the DB resource is classified as exclusive.
46
New Day processing
Quantitative resources
Specification of Quantitative resource requirements for a job (for example, tape drives, CPU utilization, cartridge drives, database access-rate) helps prevent execution bottlenecks due to resource contentions (when more than one job requires the same resource at the same time. CONTROL-M monitors the status of the installations Quantitative resources, and stores this information in the Resources table. When a Quantitative resource is specified for a job, CONTROL-M determines if a sufficient quantity of the specified resource is available before submitting the job. When the job is submitted, the specified quantity of the resource is allocated to that job and is unavailable to other jobs. When the job finishes executing, the resource is made available to other jobs. The quantity of each resource available in the installation is specified using CONTROL-M utilities.
NOTE
Quantitative resource requirements for a job can be modified even after the job has been ordered, by selecting the job in the CONTROL-M/EM window and modifying the job definition.
Example The JK_A and JK_B jobs each require access to two tape drives. The installation possesses three tape drives. The two job processing definitions include the following job processing parameters:
JK_A: JK_B: Quantitative Resource: Tape Quantity: 2 Quantitative Resource: Tape Quantity: 2
The three tape drives are defined in the Quantitative Resources window as follows:
Quantitative Resource: Tape Maximum quantity: 3
Chapter 1
CONTROL-M/EM basics
47
New Day processing
The name Tape is assigned by the user to represent the tape drives resource in the CONTROL-M installation. CONTROL-M handles access to this resource as follows: 1. Initially, the available quantity of the Tape resource is 3 because no tape drives are in use. 2. When the JK_A job is ready to be submitted, CONTROL-M determines if the required quantity (2) of the Tape resource is available. The quantity available is 3. Therefore CONTROL-M submits the JK_A job. 3. The available quantity of the Tape resource is changed to 1 until the JK_A job is ended. 4. When the JK_B job is ready to be submitted (while the JK_A job is running), CONTROL-M determines that the quantity (2) of resource Tape required by JK_B is not available. Therefore CONTROL-M does not submit the JK_B job. 5. When the JK_A job is ended, the available quantity of the Tape resource is changed back to 3. The available quantity of the Tape resource is now sufficient for the JK_B job and CONTROL-M submits it for execution.
Quantitative resources are used to specify the resources available on each Agent platform. CONTROL-M monitors each platform and records the resource information each agent platform in the Resources table. If load balancing is implemented, CONTROL-M examines the Quantitative resource requirements specified in the job processing definition and compares these requirements to the availability of Quantitative resources on various Agent platforms to determine the platform on which the job should be submitted. (For more information, see Load balancing on page 54.)
Prerequisite conditions
A prerequisite condition is a user-defined, descriptive name given to a certain situation, or condition. Submission of a job for execution can be made dependent upon the existence of one or more prerequisite conditions (created either manually by the user, or by other jobs). By using prerequisite conditions, any kind of dependency can be created. For example, a CONTROL-M job can be dependent on whether or not another job finished successfully, or it can be dependant on whether or not a certain program is running.
48
New Day processing
Prerequisite conditions are usually added or deleted according to parameters in the job processing definition. They can also be added or deleted either manually using the CONTROL-M/Enterprise Manager GUI, or by an application program using a supplied CONTROL-M utility. By defining them as global conditions, prerequisite conditions can be used to create dependencies between jobs in various CONTROL-M installations. For more information about global conditions, Chapter 6, Displaying and defining resources and conditions. Example 1 A prerequisite condition can be assigned a meaningful name that indicates the purpose of the condition. For example:
Condition PAYCALC-OK INVENTORY-DATASET-CREATED MOUNTAPE1-FINISHED Description Successful execution of a job. Creation of a data set. Completion of a manual operation.
Example 2 Given that the payroll-calculating job (Job PAYCALC) must be run before the Payroll-check-printing job (Job PRINTPAY). You can establish this dependency by specifying prerequisite conditions, in the following manner: Figure 3 Job Dependency
Chapter 1
CONTROL-M/EM basics
49
New Day processing
1. The post-processing parameters for the PAYCALC job specify that the PAYCALC-OK prerequisite condition should be added to the Conditions table. This condition is added only after successful completion of the PAYCALC job. 2. The submission criteria for the PRINTPAY job specify that prerequisite condition PAYCALC-OK must exist for the job to run. The job is not submitted unless the prerequisite condition PAYCALC-OK already exists in the Condition/Resources tables, i.e., it is not submitted unless job PAYCALC was executed successfully. In this example, job dependency was established by specifying the same prerequisite condition as a post-processing parameter in one program and as submission criteria in another program.
NOTE
You can also specify in the post-processing parameters for job PRINTPAY that the PAYCALC-OK condition should be deleted. After job PRINTPAY has been successfully executed, and the paychecks printed, the prerequisite condition is removed from the Conditions table.
Example 3 This example illustrates how a prerequisite condition can be used to ensure that a required manual operation has been performed:
EXAMPLE
The job processing definition of JOB-A specifies prerequisite condition MOUNTAPE1-FINISHED as submission criteria. This means that this condition must exist before JOB-A can be run. When the operator sees that JOB-A is waiting for this condition to be satisfied, the operator can mount the tape and then manually add the condition to the Conditions table using CONTROL-M/EM. The job can then be submitted by CONTROL-M.
Example 4 Using post-processing parameters, you can distinguish between different completion statuses of the job and specify which prerequisite conditions to add or delete in each case. For example, if a job generates an error code of FILE NOT FOUND, CONTROL-M can be instructed to delete the MASTER-FILE-OK condition. All jobs depending on the MASTER-FILE-OK condition will not run. After the status of the file is corrected (for example, by running an automatic restoration job), the MASTER-FILE-OK condition can be added again, and all jobs depending on it can be run.
50
CONTROL-M job flow and handling

CONTROL-M jobs are described in job processing definitions. The following topics describe how job processing definitions are handled and used to manage your production environment.

Issuing job orders Selecting jobs for submission Tracking the job Analyzing job results Performing post-processing actions Resubmitting cyclic jobs Manual intervention by the user
Each of above operations is described in the following pages. Figure 4 shows how CONTROL-M processes information. Figure 4 CONTROL-M workflow
Issuing job orders

Job ordering is the process of adding job processing definitions to the Active Jobs file. Jobs are normally ordered using one of the following methods:
Most jobs are ordered by the New Day procedure or User Daily jobs (see New Day processing on page 43).
Chapter 1
CONTROL-M/EM basics
51
You can manually add individual jobs or entire scheduling tables to the Active Jobs file using the Order or Force options from CONTROL-M/EM. The Order option places jobs in the Active Jobs file only if their scheduling criteria are satisfied. The Force option places jobs in the Active Jobs file regardless of scheduling criteria. For more information, see Job actions on page 204. As part of its post-processing actions, a job can also force other jobs to be placed in the Active Jobs file.
Before a job order is placed in the Active Jobs file, the job processing parameters of the job can be passed to a user exit routine for security management (authorization, auditing, etc.). For information about user exits, see the CONTROL-M/Enterprise Manager Administrator Guide. When each job order is placed in the Active Jobs file, it is assigned a unique order ID. This ID is especially useful if you need to differentiate between multiple orders of the same job.
Selecting jobs for submission

When a job order is placed in the Active Jobs file, CONTROL-M ensures that all the conditions required by the job (the submission criteria) are fulfilled before the job is submitted. Some examples of the conditions checked by CONTROL-M are:

Existence of prerequisite conditions (including manual conditions). Availability of Control and Quantitative resources. Time limits specified for the jobs start time. Job priority. Manual confirmation (if specified by the operator in the job processing parameters). Elapsed time since the jobs last execution (for cyclic jobs or when job recovery is performed).
When submission criteria are met, CONTROL-M allocates all required resources for the job. It then issues a command that submits the job script with specified environmental parameters (using AutoEdit variables). For more information, see Submission criteria on page 45.
Tracking the job

CONTROL-M keeps track of each job through all stages (in queue, during execution, and completion). If CONTROL-M determines that a job is taking too long to execute, it can notify the appropriate personnel or departments by sending messages via the Shout facility (see the Shout parameter in the CONTROL-M Job Parameter and Variable Reference Guide).
Analyzing job results

When a job finishes executing, CONTROL-M scans the job log for specific data regarding job execution. CONTROL-M assigns the completion status (OK or NOTOK) based on information in the log and on the operating system completion status.
Performing post-processing actions

Based on its analysis of job execution results and on the contents of job processing parameters, CONTROL-M determines which post-processing actions should be performed. Examples of post-processing actions that can be performed include the following:
The jobs completion status of OK or NOTOK can be altered (using the Do NOTOK and Do OK parameters). Messages can be sent via the Shout facility to specified destinations (for example, specific user, CONTROL-M/EM Alerts window). Prerequisite conditions can be added or deleted, thereby starting or preventing execution of dependent jobs. The output (Sysout) of the job can be controlled (for example, printed, moved to another library or directory). For more information, see Sysout Handling in the CONTROL-M Job Parameter and Variable Reference Guide. Additional job orders can be placed in the Active Jobs file (using the Do Forcejob parameter.
NOTE
Resources (for example, tape, CPU) assigned to the job by CONTROL-M are released for general use upon job completion.
Resubmitting cyclic jobs

A job can be defined as a cyclic job. When a cyclic job completes execution and the results have been analyzed by CONTROL-M, the job is rescheduled for another possible execution. After a pre-defined interval, CONTROL-M rechecks to ensure that all the required submission criteria are satisfied. If they are, the job is resubmitted. For more information, see the Cyclic parameter in the CONTROL-M Job Parameter and Variable Reference Guide.
Chapter 1
CONTROL-M/EM basics
53
Load balancing
Manual intervention by the user

CONTROL-M tracks all jobs under its control and automatically updates the information in the Active Jobs file. In certain cases it may be necessary to modify information manually. Using CONTROL-M/EM, you can perform the following actions on the Active Jobs file:
Track jobs (check the status of jobs in the Active Jobs file, and view the job log, statistics and documentation). Order or force jobs. Change job processing parameters of scheduled jobs. Delete jobs from the Active Jobs file. Add or delete prerequisite conditions and resources. Hold or free jobs. Confirm job submissions, job reruns and job restarts (when required by the job processing definition). Terminate an active job and its associated processes.
For more information, see Job actions on page 204.
Load balancing
Load-balancing is the process of distributing jobs to various CONTROL-M/Agents (nodes) associated with a CONTROL-M/Server according to availability of resources. When load balancing is implemented, CONTROL-M considers availability of resources such as disk space, I/O load, CPU usage, and Software licenses on each Agent platform, and determines which platform is best suited to execute the job when it is submitted. The following topics relevant to load balancing are described below:

Node groups Job processing definition Quantitative resources Checking available resources (ctmloadset utility) Load balancing workflow
54
Load balancing
Node groups
A Node group is logical name that is used to refer to a list of node IDs representing Agent platforms. When the name of a node group is specified in the Node ID/Group parameter of a the job processing definition, CONTROL-M automatically applies load-balancing to the related job. Node Groups are defined in the Node Group menu in CONTROL-M/Server. All nodes in each group must share the following characteristics:

Similar operating systems (for example, various Unix computers). User environment (for example, access to the same file systems). They should all be able to execute the jobs assigned to the Node group.
For more information, see the description of the Node Group menu in your CONTROL-M/Server Administrator Guide.
Job processing definition

The job processing definition for a job contains two key parameters used by load balancing:
The Node group (specified using the Node ID/Group parameter), represents a list of Agent platforms, any one of which is capable of executing the job. The specification of a node group and not a node ID in the Node ID/Group parameter is your indication to CONTROL-M that it should use load balancing to determine where the job should be submitted.
Quantitative resources are specified with an at sign (@) at the end of the resource name. When CONTROL-M detects this type of resource, it will search for agent-specific resources in the resources table. For more information about Quantitative resources, see Quantitative resources on page 56.
Example Given that Agent platforms diana, bill and ruby are all members of the node group NY.
If diana is specified in the Node ID/Group parameter of a job processing definition, the job will be submitted only to Agent platform diana. If NY is specified in the Node ID/Group parameter of a job processing definition, the job can be submitted to any of the platforms: diana, bill or ruby. Load balancing determines to which platform the job is submitted.
Chapter 1
CONTROL-M/EM basics
55
Load balancing
Quantitative resources for load balancing must be specified appropriately in the job processing definition and in the resources table.

In the job processing definition, the resource name must end with @. In the Resources table, the resource must be defined as necessary for each agent platform (as described below).
Defining Quantitative resources

The Quantitative Resource table (part of the CONTROL-M database) contains a list of Quantitative resources that have been defined by the user for each Agent platform. These resources are specified via the Quantitative Resources window in CONTROL-M/EM using the format:
<resource_name>@<node_ID>
When you define the maximum available units of a resource on the various Agent platforms in a node group, you should assign to each platform a number of units relative to the capability of that platform. For more information about defining resources, see Quantitative resources on page 246. Example Given that the processor on Agent platform diana is twice as fast as the processor on Agent platform bill. A Quantitative resource called CPU, representing CPU performance, could be defined as follows in the Quantitative Resource window:
Resource name CPU@bill CPU@diana Type D D Max 50 100
56
Load balancing
Quantitative resource status

CONTROL-M maintains the following information for each Agent platform regarding each defined Quantitative resource: Table 5
Resource Max Total Used
Quantitative resource information

Description Maximum quantity of the resource existing in the platform. Units of the resource currently in use. This parameter represents the sum of:
Used by CONTROL-M Units of the resource currently in use by jobs submitted by CONTROL-M. Used by Others Units of the resource currently in use by non-CONTROL-M jobs.
It is up to the user to make sure that CONTROL-M is aware of the load imposed on the Agent platform by non-CONTROL-M tasks. This is done using the utility ctmloadset (described below). Reserved Not Used Free Units of the resource currently reserved for critical-path jobs (see Critical-path jobs on page 59). Units of the resource that are not in use by any currently-executing job. Units of the resource available for allocation. This is the number of units that are in the Not Used category and that are not reserved for any critical-path job.
The relationship between these parameters can be visualized as follows:

Max (number of units existing) Total Used Used by CONTROL-M Used by Others Not Used Reserved Free
NOTE
The value for the Reserved parameter can not exceed the value for Not Used. For more information, see Critical-path jobs on page 59.
These parameters are maintained automatically by CONTROL-M (except for Used by Others). When a job requiring x units of a resource is submitted to an Agent platform, CONTROL-M adds that number of units to the Used parameter and subtracts the same number from the Free parameter. When a job completes execution the process is reversed. The following table indicates the effect of various functions on the parameters in the Quantitative Resources table when allocating or releasing x units of a resource:
Chapter 1
CONTROL-M/EM basics
57
Load balancing
Table 6
Reaction of Quantitative resources to system events

Total Used Used by CONTROL-M +x -x +x -x +x +x -x -x -x +x -x +x Used by Others
Function Job submission by CONTROL-M Completion of CONTROL-M job Submission of critical-path job Start execution of critical-path job Use of utility ctmloadset to allocate resources Use of utility ctmloadset to release resources
Reserved
Not Used Free -x +x -x +x -x
Example Given that the status of Quantitative resource CPU on Agent platform diana is as follows:
Total Used Resource CPU@diana Max 100 Reserved 0 Used by CONTROL-M 40 Used by Others 15 Not Used 45 Free 45
When a Job requiring 30 units of CPU is submitted by CONTROL-M/Server to the platform, the Quantitative Resource table is modified as follows:
When the job completes execution the status of the Quantitative resource returns to its previous status.
58
Load balancing
Critical-path jobs
When a job that is defined as a critical-path job is ready to be submitted, the job receives preferential treatment in allocation of resources. If the job is handled by the load balancing mechanism, CONTROL-M/Server uses the following procedure to assure that the job is submitted for execution as soon as possible: 1. CONTROL-M begins reserving the required resources on each Agent platform in the node group until one platform with sufficient resources is located. 2. If no appropriate platform is located, CONTROL-M continues reserving resources on each platform as they become available. 3. When sufficient resources are reserved on one Agent platform to execute the critical-path job, the job is submitted on that platform; the resources on all the other platforms are released and made available to run other jobs. Example Node group NY contains three Agent platforms whose current status is as follows:
Total Used Resource CPU@diana CPU@bill CPU@ruby Max 100 50 100 Reserved 0 0 0 Used by CONTROL-M 95 40 75 Used by Others Not Used 5 10 25 Free 5 10 25
A job that requires 30 units of CPU@ and whose Node ID/Group parameter contains node group NY is ready to submit. However, none of the Agent platforms in node group NY currently has sufficient free units of CPU to execute the job. Consequently, CONTROL-M reserved the required number of units on all Agent platforms in the group. The status of the Agent platforms is now as follows:
Total Used Resource CPU@diana CPU@bill CPU@ruby Max 100 50 100 Reserved 30 30 30 Used by CONTROL-M 95 40 75 Used by Others Not Used 5 10 25 Free -25 -20 -5
Since there are no free units of CPU on any of Agent platforms, no new job requiring this resource will be submitted.
Chapter 1
CONTROL-M/EM basics
59
Load balancing
When a job using 20 units of CPU completes execution on Agent platform bill, that platform has sufficient free units of CPU to execute the critical-path job. CONTROL-M submits the job to bill and immediately releases the reserved resource on all the platforms. The status of the Agent platforms is now as follows:
Total Used Resource CPU@diana CPU@bill CPU@ruby Max 100 50 100 Reserved 0 0 0 Used by CONTROL-M 95 50 75 Used by Others Not Used 5 0 25 Free 5 0 25
Checking available resources (ctmloadset utility)

The ctmloadset utility is used to report usage of a Quantitative resource on an Agent platform. This utility is typically invoked by a cyclic job that runs on the Agent platform and measures the usage of a certain resource on the platform at regular intervals. This usage data is reported to the server platform, where it is recorded in the Quantitative Resources table. Load balancing uses the data recorded in the Quantitative Resources table to determine to which Agent platform a job should be submitted. The following options exist for using this utility to update the resource usage values in the Quantitative Resources table:
Specify the value for Total Used for a resource. ctmloadset subtracts the value for Used by CONTROL-M from the value specified and places the remainder in the field Used by Others. Specify the value for Used by Others for a resource. This value is added to the value Used by CONTROL-M to calculate the value Total Used for the resource.
Values for the utility can be expressed as an absolute number of units or as a percentage of the Max value (total units defined). Example 1 Agent platform diana is used to execute both CONTROL-M jobs and non-CONTROL-M jobs. A Quantitative resource called CPU has been defined, representing the usage of the platforms processor.
60
Load balancing
When a CONTROL-M job requiring 25 units of resource CPU is submitted, the Quantitative Resources table contains the following values:
The user has defined a job that runs at fixed intervals to measure the load on the computers processor and then uses ctmloadset to update the resource CPU in the Quantitative Resources table. The load-measuring job determines that the current load on the processor (including both CONTROL-M and non-CONTROL-M jobs) is equivalent to 60 units of resource CPU. The job uses utility ctmloadset to update the Total Used value in the Quantitative Resources table. The table now contains the following values:
Total Used Resource CPU@diana Max 100 Reserved 0 Used by CONTROL-M 25 60 Used by Others 35 Not Used 40 Free 40
Example 2 Agent platform bill is used to execute both CONTROL-M jobs and non-CONTROL-M jobs. A Quantitative resource called CPU has been defined, representing the usage of the platforms processor. When a CONTROL-M job requiring 30 units of resource CPU is submitted, the Quantitative Resources table contains the following values:
Total Used Resource CPU@bill Max 200 Reserved 0 Used by CONTROL-M 30 Used by Others 0 Not Used 170 Free 170
The user may wish to reserve 25% units of resource CPU for use by non-CONTROL-M jobs. Use utility ctmloadset to update the Quantitative Resources table, specifying that the parameter Used by Others for resource CPU contains 25%.
Chapter 1
CONTROL-M/EM basics
61
Load balancing
Utility ctmloadset calculates 25% of 200 and places the value in the Used by Others parameter. The table now contains the following values:
Total Used Resource CPU@bill Max 200 Reserved 0 Used by CONTROL-M 30 80 Used by Others 50 Not Used 120 Free 120
Load balancing workflow

When CONTROL-M passes a job order for load balancing, CONTROL-M examines the following information:
The Quantitative resources required to execute the job. This data accompanies the job order. The list of Agent platforms capable of executing the job (as determined by the node group specified for the job).
CONTROL-M examines the Agent platforms one by one. For each platform, the current status of the platforms resources is retrieved from the Quantitative Resources table. As soon as an Agent platform is found with the necessary Quantitative resources available, the job is submitted to that platform. If an Agent platform with the necessary resources is not found during the first pass, CONTROL-M continues cycling repeatedly through the platforms in the node group until a platform is found on which sufficient resources have been freed to execute the job. Example A job submitted to CONTROL-M/Server contains the following job processing parameters:
Node ID/Group NY Quantitative Resources
CPU@ IO@
30 8
Node Group NY contains three Agent platforms: bill, diana and ruby.
62
Load balancing
The status of these platforms in the Quantitative Resources table is as follows:

Total Used Resource CPU@diana IO@diana CPU@bill IO@bill CPU@ruby IO@ruby Max 100 20 50 10 100 30 Reserved 0 0 0 0 0 0 Used by CONTROL-M 40 8 40 6 75 10 Used by Others 45 10 Not Used 15 2 10 4 25 20 Free 15 2 10 4 25 20
Load balancing retrieves the status of each Agent platform in turn from the Quantitative Resources table. In each instance, CONTROL-M compares the platforms free resources with the resource requirements specified in the job processing parameters. When no Agent platform has the necessary free resources, the job is not submitted. CONTROL-M repeatedly examines each Agent platform in turn to determine if the required resources were released by the completion of another job. After two minutes a CONTROL-M job completes execution on Agent platform bill. The Quantitative Resources table now contains the following values:
Total Used Used by CONTROL-M 40 8 10 2 75 10 Used by Others 45 10 Not Used 15 2 40 8 25 20
Resource CPU@diana IO@diana CPU@bill IO@bill CPU@ruby IO@ruby
Max 100 20 50 10 100 30
Reserved 0 0 0 0 0 0
Free 15 2 40 8 25 20
Agent platform bill now contains sufficient free resources to execute the job. Load balancing submits the job to this platform and update the Quantitative Resource table.
Chapter 1
CONTROL-M/EM basics
63
Language capabilities
Language capabilities
Western European languages
CONTROL-M/EM, CONTROL-M/Desktop, CONTROL-M/Server, CONTROL-M/Agent, Batch Impact Manager, and CONTROL-M/eTrigger, support Western European language characters (the Latin-1 character set). These products can accept characters in English, German, Spanish, and French from the Latin-1 character set (ISO 8859-1) in almost all text fields and parameters. For additional information, see the following guides.
Task Indications of which parameters do not support Western European language special characters A list of all parameters that do support Western European language special characters Topic and guide Individual parameter descriptions in the CONTROL-M/Enterprise Manager Parameter and Variable Reference Guide
CONTROL-M Language Customization Guide
A list of Western European language special CONTROL-M Language Customization Guide characters that are not supported at any time Language configuration instructions Migration instructions
CONTROL-M Language Customization Guide
CONTROL-M/Enterprise Manager Migration Guide
Japanese
CONTROL-M can run on Japanese-enabled operating systems. CONTROL-M components, such as the CONTROL-M/EM GUI and CONTROL-M/Desktop, do not accept Japanese characters in any free text fields or parameters and display values only in English. For example, Japanese job sysouts do not display correctly. Therefore, in these cases, job sysout analysis is not possible. Japanese configuration and installation instructions for running CONTROL-M components with Japanese-enabled operating systems are provided in the CONTROL-M Language Customization Guide.
64
Basic tasks
Basic tasks
NOTE
American English is the display language of the CONTROL-M/EM GUI and CONTROL-M/Desktop. In addition, Western European language special characters are supported in most fields and parameters. However, if files (for example, log files or JCL) contain other, non-supported characters, they may not be accurately displayed. Language capabilities on page 64
Logging in
To start CONTROL-M/EM: 1 Double-click the CONTROL-M/EM GUI icon on the Microsoft Windows desktop.
-orChoose Start => Programs => CONTROL-M/Enterprise Manager 6.1.00 => CONTROL-M/Enterprise Manager GUI. The following dialog box is displayed when CONTROL-M/EM is started: Figure 5 CONTROL-M/Enterprise Manager Login dialog Box
2 Specify your user name and password.
Chapter 1
CONTROL-M/EM basics
65
Logging in
The name of the last accessed CONTROL-M/EM GUI Server is automatically displayed in the Server list box. If desired, select a different GUI Server from the list. The list displays all GUI Servers registered with the current CORBA Naming Service.
NOTE
The first time a user logs in, the default GUI Server as specified during installation is displayed. To log in to a GUI Server that is registered with a different Naming Service, see Logging in to a GUI Server with a different Naming Service on page 67.
3 Click Login. The CONTROL-M/Enterprise Manager window is displayed (see

Figure 6 on page 68).
NOTE
The CONTROL-M/EM administrator is responsible for startup of CONTROL-M/EM background processes (Database server, GUI Server, Global Conditions Server, Global Alerts Server, and the gateways) that must be running before the CONTROL-M/EM GUI can be started. For more information, see the CONTROL-M/Enterprise Manager Administrator Guide.
66
Logging in
Logging in to a GUI Server with a different Naming Service

To log into a GUI Server registered with a different Naming Service, change the CONTROL-M/EM login properties as described in the following procedure. This procedure will display a different list of GUI Servers in the Server list box in the Login dialog box.
1 In the Login Dialog Box, click Advanced. The Login dialog box is redisplayed with
additional controls:
2 Enter the host name of the CORBA Naming Service host computer in the Host
Name text box.
3 Enter the port number on the CORBA Naming Service host computer in the Port
Number text box.
4 Click Apply Settings. The following occurs:

The bottom portion of the window is hidden. Login becomes available. The list of all GUI Servers registered with the CORBA Naming Service is updated and becomes available from the Server list box.
NOTE
Click Restore Default Settings to enter the CORBA host name and port values that were specified when CONTROL-M/EM was installed.
Chapter 1
CONTROL-M/EM basics
67
Logging in
Logging in from the command line

You can also log in to CONTROL-M/EM from the command line (to bypass the Login dialog box.
To log in from the command line: 1 Choose Start => Run. 2 Enter the following command in the Open text box:
emgui -u <user_name> -p <password> -m <hostname> [-vp <ViewPoint>] Table 7
Parameter user_name
Log in command parameters

Description Name of the CONTROL-M/EM user. Note: If the username or password is incorrect, the Log in dialog box is displayed. Reenter the username and password.
password
CONTROL-M/EM user password. Note: If the user name or password is incorrect, the Log in dialog box is displayed. Reenter the user name and password.
hostname ViewPoint
Name of the host computer on which the GUI Server is installed. Name of the ViewPoint that is displayed automatically when CONTROL-M/EM starts. Optional. Note: If the ViewPoint name is incorrect (due to incorrect spelling or because the ViewPoint does not exist), the Open ViewPoint dialog box is displayed.
3 Press Enter. The CONTROL-M/EM window is displayed (see Figure 6 on

page 68). Figure 6 CONTROL-M/Enterprise Manager window (truncated)
68
Working with list displays
The CONTROL-M/Enterprise Manager window is used to view and access jobs in the active environment.
Changing your password

After logging in to CONTROL-M/EM you can change your password, as follows:
1 Choose Tools => Change Password. The Change Password dialog box is
displayed. Figure 7 Change Password dialog box
NOTE
The Change Password option is available only if your administrator has set the UserChangePassword system parameter to 1.
2 Enter your current password in the Current Password field. 3 Enter your new password in the New Password field.
(Your keystrokes will appear as asterisks as you type them.)
4 Re-enter your new password in the Verify Password field.

(Your keystrokes will appear as asterisks as you type them.)
5 Click OK to confirm your new password. 6 Log out of all CONTROL-M/EM components for the change to take effect.

Certain dialog boxes display lists of items, for example, lists of CONTROL-M definitions or lists of prerequisite conditions, from which you can make a selection. Many list displays contain an Item counter at the bottom that indicates the number of items appearing in the list. You can modify many list displays, and perform other tasks in list displays. The following pop-up menus enable the various modification and other tasks:
Chapter 1
CONTROL-M/EM basics
69
The column header pop-up menu Column header pop-up menu for list displays
Figure 8
This menu is used for performing most modifications. To display this menu, right-click in the header of the desired column in the list display. Changes made are saved and redisplayed the next time the list is displayed.
The list display pop-up menu List display pop-up menu
Figure 9
To display this menu, click anywhere in the list display except the column header.
Modifying list displays

The following modifications can be made to list displays:

Toggle the item counter on and off Sort the list according the values in a column Remove a column from the list Add fields to the list display Resize a columns width Reorder columns
Toggling the item counter is performed from the list display pop-up menu. The other modifications are performed from the columns headers or the column header pop-up menu.
NOTE
Not all list displays can be modified, and not all modifications are possible in modifiable list displays. Furthermore, some modifications require Administrator permissions.
To display/hide the item count in a list display

Click the Item Count option in the list display pop-up menu.
To sort the list according to the values in a column

Perform one of the following:
Right-click the column header. Select either Sort Ascending or Sort Descending, as desired.
-or
Click the column header.
The selected column initially sorts in ascending order (default). Once the column is already being used as the sort column, each click of the column header toggles between ascending and descending sort. An alphabetic sort is performed, except if the selected column is Last Update, in which case the sort is by date. The format of the date is determined by the locale setting of the computer. For information about how to change the date format, see the manual of your operating system.
To add a field to the display 1 Right-click the column header. Select the Field Chooser option.
The Field Chooser menu is displayed with the appropriate fields.
2 Click and drag the field from the Field Chooser menu to the desired location in the
column header of the list.
To remove a field from the display

Right-click the column header and select the Remove This Column option. -or-
Chapter 1
CONTROL-M/EM basics
71
Right-click the column header and select the Field Chooser menu. Then drag the header from the list to the Field Chooser.
To rearrange the fields in the display

Click and drag (right or left) the column header of the field to be moved.
To resize a column in the display according to its best fit

Right-click the column header of the column to be adjusted and select the Best Fit option. -or-
Double-click the headers right border. The column width is adjusted to fit the longest value in the column.
Performing other tasks in the list display

You can perform the following tasks from the list display pop-up menu, which is displayed by right-clicking anywhere in the list display (except the column header).

Save the contents of the list display to a comma-delimited (CSV) file Print the contents of the list display
These tasks can also be performed in the CONTROL-M/EM Administration facility, on the list of CONTROL-M/EM components and system parameters.
To save the contents of a list display to a CSV file

Select the Export to File option in the pop-up menu of the list display, and perform the save in the Export to File dialog box. .csv files are comma-delimited files that can be used in applications such as Microsoft Excel.
To print the contents of a list display

Select the Print option in the pop-up menu of the list display.
72
Specifying pattern-matching strings

Fields used to select data (for example, in the Alerts window and Control resources window), accept pattern-matching strings, or expressions, as input. Using these strings, the user can select many different entities by specifying a relatively simple combination of characters and symbols.
NOTE
The use of complex expressions tends to reduce CONTROL-M/EM performance.
Table 8 describes the symbols used to compose pattern-matching strings. Table 8

Symbol *
Symbols used to compose pattern-matching strings

Name Asterisk wildcard Usage Denotes any number of characters (including no characters). This can be inserted in place of a string. Note: If filtering is not needed, it is more efficient to leave filter criteria fields blank than to use a * character. Used to repeat the preceding regular expression at least once. For example, 'ca+r' matches 'car' and 'caaaaaar', but does not match 'cr'. Use "\" to escape + where it is used as a literal character. For example, 'red\+blue' matches the expression red+blue.
Repeat character
? or . !
Question mark Denotes any single character. This can be inserted in wildcard, or period place of any number of characters. Exclamation Denotes all possibilities that do not match the pattern that immediately follows the ! character. This can be specified to exclude the pattern immediately following the ! from the result. If a pattern begins with !, the escape character backslash "\" can be used to escape the ! and either include or exclude a pattern (required only if ! is the first character). For example, to include occurrences of "!wip", use the pattern "\!wip", whereas "!\!wip" excludes "!wip". Notes: ! must be the first character of the string, for example, in the expression (first!,!one) the exclamation is part of the string "first!", but is used to exclude the string "one". Denotes different possibilities for a single character. The brackets enclose a string of possible values. In addition, the following symbols can be used within the brackets: denotes a range of characters. ^ used as the first character denotes "not".
[]
Brackets
Chapter 1
CONTROL-M/EM basics
73
Table 8
Symbol , or |
Symbols used to compose pattern-matching strings

Name Comma or pipe Usage Used to separate pattern-matching strings, allowing the user to specify more than one string (the comma represents a Boolean OR). Example (host01, host02, host03) Any character, other than one of the above, denotes the specific character. Note: In case-sensitive fields, CONTROL-M/EM differentiates between uppercase and lowercase characters. "a" and "A" are treated as different characters. Denotes the literal value of the special character. The special characters are the symbols described in this table. Examples To specify \, type \\. If you specify \. then "." has the meaning of period and not the same meaning as ?. Use "\" to escape ! only where ! is the first character.
<character>
Character
\<special_ character>
Escape character
Anchor (start)
Denotes "not" when used as the first character in brackets [ ]. Denotes the start of a word when not specified in brackets [ ].
Anchor (end)
Denotes the end of a word.
NOTE
XML term files support the use of "," to separate values and "!" to exclude values (use OP="LIKE").
TIP
If you use special characters, such as asterisk, as a literal part of the object name (for example, glo*-job1_started), and when you filter you want to include only these objects (for example, you do not want to include glo-job1_started), specify \ before the special character in the filter prefix (for example, glo\*). Otherwise, objects without the special character (for example, glo-job1_started) will also be included. (Wherever possible, try to avoid defining object names with special characters as literals.)
Table 9 lists expressions used to select data centers. Specifying any one of them would include data center DALLAS.
74
Table 9
Pattern
Examples of expressions
Includes... The three data centers DALLAS, NY, LA. All data centers whose name starts with D and ends with S. All data centers that start with DALL, and end with AS, where the character L is repeated as many times as is required to match the pattern. All data centers whose name starts with D, ends with S, and consists of six characters. All data centers whose name starts with D and ends with five letters matching the pattern signified by ALL?S. All data centers except for NY. Data centers LA and DALLAS, excluding NY. All data centers whose name starts with D and whose second letter is A, B or C. All data centers whose name starts with D, whose second letter is in the range of A-E and whose name consists of six characters. All data centers whose name starts with D and whose second letter is not in the range of B-Z. Data center NY and all data centers matching the pattern signified by D*S.
DALLAS, NY, LA D*S DAL+AS
D????S D*ALL?S !NY LA,!NY,D*S D[ABC]* D[A-E]???? D[^B-Z]* NY,D*S
DALLAS,TEXAS\* The data centers DALLAS and TEXAS*.
Using SQL wildcards

The SQL wildcards:

% denotes any or no character _ denotes any one character
These wildcard characters, when used in ViewPoint collections and filter definitions, are evaluated as literal % and _ and not as wildcards.
Chapter 1
CONTROL-M/EM basics
75
76
Chapter
Viewing the production environment

The CONTROL-M/Enterprise Manager (CONTROL-M/EM) production environment consists of all jobs that have been scheduled for execution in the associated CONTROL-M installations. The jobs are related to each other by priorities and dependencies specified by user-defined job processing parameters. The CONTROL-M/Enterprise Manager window displays jobs in the active environment. The jobs can be filtered and ordered in a hierarchical structure. The filter and hierarchical specifications are saved in ViewPoints, which is the work area through which you view the jobs in the production environment that are relevant at that time. This chapter describes how to work with ViewPoints in the CONTROL-M/Enterprise Manager window.
Introduction
After you log into CONTROL-M/EM, the CONTROL-M/Enterprise Manager window is displayed.The CONTROL-M/Enterprise Manager window is used to view and access jobs in the active environment using ViewPoints. Each ViewPoint is displayed in its own ViewPoint window. Figure 10 Extract of an empty CONTROL-M/Enterprise Manager window
Chapter 2
77
Introduction
NOTE
By default, an empty CONTROL-M/Enterprise Manager window is displayed at the start of a session. However, the default can be changed so that a Viewpoint window (or the Open Viewpoint dialog box) is displayed at the start of a session. For details, see Chapter 10, Customization.
Multiple ViewPoint windows can be opened at the same time. Figure 11 illustrates the CONTROL-M/Enterprise Manager window with an open ViewPoint window. Figure 11 CONTROL-M/Enterprise Manager window with one ViewPoint window
Navigation Tree
Flow Diagram
Net Overview
ViewPoint windows consist of the following panes:
Navigation Tree Hierarchical view of jobs in the current environment, mainly for navigation purposes.
FlowDiagram Graphic representation of job production flow, based on job dependencies established by prerequisite conditions specified in job processing definitions (IN and OUT conditions).
78
Understanding the Navigation Tree and its components
Components of the active environment are represented by boxes called nodes. The information displayed in a node varies depending on the type of node and on how certain customization options. For information about node types, see Table 11 on page 83 and Table 12 on page 83. For information about customizing how the FlowDiagram is displayed, see Flowdiagram General panel on page 329.
Net Overview Miniature version of the FlowDiagram, indicating the part of the network currently displayed in the FlowDiagram. By dragging the selected area in this view to a different part of the network, you can quickly navigate in a complex environment. For more information, see Understanding the Net Overview and its components on page 80.
TIP
Each of the three panes of the ViewPoint window can be re-sized separately by dragging their borders to the desired position.
Understanding the Navigation Tree and its components

The left part of the ViewPoint window displays a tree representing the nodes in the current ViewPoint. This tree, called the Navigation Tree, can be used to navigate quickly through the production environment. The Navigation Tree is arranged according to the hierarchy of the current ViewPoint. The color of each node in the Navigation Tree provides information about the status of the node. For information regarding what each color represents, see Job node statusesand High-Level node status on page 84. Using the Navigation Tree, you can:
Hide or display sets of nodes in the tree (for example, groups in an application, jobs in a group). This makes viewing selected nodes in the Navigation Tree easier. Click a node in the tree, to select it simultaneously in the Navigation Tree, the FlowDiagram and the Net Overview. Displaying and Hiding Nodes Using the Navigation Tree
Chapter 2
79
Understanding the Net Overview and its components
Display high-level and low-level nodes. Each node in the Navigation Tree that contains lower-level nodes is referred to as a high-level node. For example, a CONTROL-M, an application or a group is represented by a high-level node. Expand or collapse levels of the Navigation Tree. Initially, the Navigation Tree is displayed with only the highest-level nodes visible (for example, CONTROL-M installations). You can expand or collapse the tree by clicking the + or - . Highlight nodes in the FlowDiagram and Net Overview by clicking a node in the Navigation Tree. The corresponding graphic representation of the node is selected and highlighted in FlowDiagram and Net Overview if it is part of the hierarchy displayed.
TIP
The level of detail displayed in FlowDiagram is dependent upon the current setting of the Level option or Step In/Step Out option (for information, see Stepping In and Stepping Out on page 96).
Display a job or group editing form by double-clicking its node. Display a menu for the node by right-clicking it. in the Navigation Tree. Different types of nodes have different menus. When you right-click a node either in the Navigation Tree, a context-sensitive, menu is displayed from which you can perform operations on the selected entity (node).
NOTE
To perform operations on multiple jobs, hold down the Ctrl key while selecting the jobs.
For a comprehensive list of all menu bars and menu options, see Appendix C, Menu options.
Understanding the Net Overview and its components

The bottom pane of the ViewPoint window contains a graphical overview of the currently displayed ViewPoint. It is displayed on a miniature scale and provides an overview of what is displayed in the FlowDiagram. The part of the Net Overview window that is enclosed in a rectangle is displayed in the FlowDiagram in the pane above. The Net Overview allows you to navigate more easily in the current environment.
80
Understanding the FlowDiagram and its components
Figure 12
Net Overview display
When there are too many nodes in the current level to be displayed in the Net Overview pane, only a part of the current level is displayed. Net Overview contains a scroll bar at the bottom and side of the pane that allows you to view other parts of the current display level.
To select an area in the Net Overview pane: 1 Position the cursor inside the rectangle in the Net Overview pane. 2 Depress the left button and move the rectangle until the outline surrounds the area
you would like displayed in the FlowDiagram. As you navigate in the Net Overview pane, the display in the FlowDiagram changes simultaneously.
3 Release the left mouse button when the desired area is inside the rectangle.
-orPosition the cursor over the desired node in the Net Overview pane and click the left button. The rectangle moves over the desired area and the display in the FlowDiagram changes simultaneously.

Each node in the FlowDiagram is displayed with its title at the top of the node and an additional piece of user-selected data immediately below. Additional information about the node is provided in a graphical manner, such as pictures, icons, shapes, and color. Conditions and resources that affect nodes on any particular level can also be viewed in the FlowDiagram. Graphics are also used to represent production flows and hierarchical levels. These visual aids allow you to locate problems quickly and to assess the entire state of the production flow at a glance.
Chapter 2
81
Default characteristics of the FlowDiagram display (for example, node color) can be modified in the Flowdiagram panels of the Options dialog box. For more information, see Chapter 10, Customization. The following FlowDiagram components are described in this section: Node types Node type icons Node state icons Job node statuses High-Level node status Job node operational status and state Pop-up menus for nodes Condition nodes
Node types
Several types of nodes (entities) are displayed in the FlowDiagram. Each entity is represented by a unique icon in the upper left corner of the node. Additional icons and text also appear in the job node to identify the type of job.

High-level nodes: CONTROL-Ms, Applications, and Groups Low-level nodes: Jobs
Sample node types are illustrated in Table 10. Table 10

Node type Application
Sample node types

Sample node
Regular Job
Cyclic job
NOTE
Nodes for Started Tasks and Emergency jobs are relevant only for MVS jobs. For more information about these job types, see the CONTROL-M for OS/390 and z/OS User Guide.
82
Node type icons

Icons in the upper left corner of the node indicate the node type, as shown in Table 11. Table 11
Node type CONTROL-M Disconnected CONTROL-M Application Group Group scheduling table Scheduling table
Node type icons

Symbol
Node state icons

Icons are also used to display the current state of the job, as shown in Table 12. Table 12
Node state Description Deleted Critical Emergency Ended Task Type Odate Cyclic Owner Status Node ID
Node state icons

Symbol
Chapter 2
83
Job node statuses

The status of a job is indicated by the color of the title bar of its node. The statuses are described in Table 13. Table 13
Status Wait Condition
Job statuses
Color Gray Meaning Waiting for the specified date, time, or prerequisite conditions Note: Jobs with this status may have any of the following statuses in CONTROL-M/Server:

CYCLIC WAITTIME WAIT_ODAT POST_ODAT
Ended OK Executing Wait Resource Wait User
Green Yellow Blue Pink
Processing finished successfully. Executing Waiting for Control or Quantitative resources, or waiting for a CONTROL-M/Agent to be available Waiting for user confirmation Note: Jobs with this status are assigned WAITCONFIRM status in CONTROL-M/Server.
Ended Not OK
Red
Processing finished unsuccessfully Example: The Agent platform on which the job was running was changed to Disabled by a user.
Unknown Not in AJF
White purple
Communication with the Agent platform was interrupted Job not in the Active Jobs file. This status is displayed only in Archived viewpoints.
For more information about a jobs status, you can right-click the job node and choose Why from the menu.
High-Level node status

A high-level node title bar color is determined by the status of its descendant nodes. If all descendant nodes have the same status, the title bar of the high-level node is colored in the relevant color. If the descendant nodes have a different status, the high-level node has a title bar color as well as vertical bars of various colors on the bottom of the node.
84
Title bar color

CONTROL-M/EM determines the title bar color of the high-level node by checking for the following situations in the given order: Table 14
Color White Red Pink Blue Yellow Gray Green
High-level node status colors

Description At least one job has a status of Unknown. At least one job has a status of Ended Not OK. At least one job has a status of Wait User. At least one job has a status of Wait Resource. At least one job currently has a status of Executing. All the jobs have the status Wait Condition. At least one job has a status of Ended OK.
The color of the Group Scheduling table node is determined by both the status of the jobs in the node and the status of the Scheduling Group itself. The color representing the greatest degree of urgency is the title bar display color.
NOTE
Emergency jobs are not considered when determining the basic color of a node.
EXAMPLE
Assume that all the jobs with a common application have Ended OK. The Application node title bar is colored similar to the following:
Vertical color bars

In addition to a title bar color, vertical color bars appear on the bottom of the node. vertical color bars indicate the distribution status of descendant nodes. They indicate the number of jobs with the corresponding status in proportion to the number of descendant nodes.
Chapter 2
85
EXAMPLE
If an application has some jobs that have Ended OK and some that have Ended Not OK. The application node looks as follows:
Job node operational status and state

A job node is displayed with the title bar colored according to its status. In addition to the node status, each job node is assigned a state that provides more information about the node, as indicated in the following table: Table 15
State Free
Job node states

Description Default state. The job is not Held or Deleted. Node appearance
Held
The job is held by a CONTROL-M/EM user.
Deleted
The job was deleted by a CONTROL-M/EM user.
BMC Batch Impact Manager Job
BMC Batch Impact Manager users: The job is defined as part of a critical batch service.
On Request
No visible change in the node Interim state. A CONTROL-M/EM user request to Free, Hold or Delete the job has appearance not yet been processed by CONTROL-M. The job is late (as determined by the job processing parameter Shout). No visible change in the node appearance
Late
The node state (other than Free) is also displayed in the States field in the Active panel of the Job Editing form. For more information about node states, see Job actions on page 204.
86
Pop-up menus for nodes

When you right-click a node in the FlowDiagram, a context-sensitive, pop-up menu is displayed from which you can perform operations on the selected entity (node).
NOTE
To perform operations on multiple jobs, hold down the Ctrl key while selecting the jobs.
For a comprehensive list of all menu bars and menu options, see Appendix C, Menu options.
Production flows
Production flows are influenced by prerequisite conditions. Prerequisite conditions are represented by colored lines and arrows connecting job nodes. These lines indicate dependencies either in a single CONTROL-M or between jobs in different CONTROL-M installations. The connecting lines are colored as follows: Table 16
Color Black Green
Connector line colors

Description Condition does not exist yet (inactive). Condition exists (active).
Additionally, the connecting lines may be displayed using dotted lines. A dotted line between two jobs indicates a conditional link between the two jobs. This means that the jobs contain the same defined condition but one of the jobs contains one of the following parameters:
Out conditions which delete a condition (-) Conditions specified with the Do Condition parameter based on conditional post processing actions Optional In conditions (In conditions that are defined using Or logic, so that not all specified In conditions must exist in order for a job to run)
The direction of the arrows at the ends of the lines indicates the flow direction (such as the relative relationship) of the connected nodes.
Chapter 2
87
NOTE
The display of dotted lines is based on the settings of the following options as described in Chapter 10, Customization.

Display Do Conditions Display Out Conditions with Minus Sign Display Optional In Condition
Example
Assuming that there are no resource requirements or time limits, the diagram reflects the following:
After job Job51 ends OK, condition Job51-ENDED is created in the Conditions/Resources file. As soon as condition Job51-ENDED exists, jobs Job52 and Job75 are started.
Click the right mouse button on the line connecting any two nodes to display a menu with the options described in Table 17. Table 17
Option Go To Out Condition Go To In Condition
Connector line menu options

Description Highlights the node that contains the Out Condition Highlights the node that contains the In Condition
Hold down the left mouse button on a top or bottom arrow to display a list of the In/Out Conditions for the node. This list indicates which CONTROL-M initiated the condition and whether the condition is a global condition.
88
Figure 13
Node-specific conditions
An arrow that is displayed on the top or bottom of a node without a connecting line indicates one of the following:
The In Condition is a manual condition, a condition that does not get added automatically by another job. The Out Condition has no corresponding In Condition or job dependent upon the condition.
Condition nodes
Prerequisite conditions can be displayed in the FlowDiagram. When displayed, conditions appear as elliptical icons (condition nodes) linked to CONTROL-M/Desktop Nodes, SetNodes, GroupNodes and JobNodes in the FlowDiagram. Figure 14 Condition node
Condition nodes describe dependencies between jobs in CONTROL-M/EM. They are most useful when viewing a small number of jobs. For example, a condition node is displayed between two SetNodes when one or more jobs in one SetNode are dependent on one or more jobs in the other SetNode.
Chapter 2
89
Figure 15
Condition node in the FlowDiagram
NOTE
The Expand function is not available when condition nodes are displayed. Use the Step In and Step Out functions to move in and out of the node hierarchy. These functions are described under Stepping In and Stepping Out on page 96 and Expanding and collapsing on page 98.

Hundreds or even thousands of active jobs can exist in the CONTROL-M/Enterprise Manager database at one time. While it is possible to load and view all jobs in a ViewPoint window, it is more efficient to focus on certain areas (such as specific CONTROL-M installations) or certain types of jobs (such as jobs that ended with errors) and display them according to specific criteria. Each ViewPoint contains the following components:
Collection: Which jobs in the enterprise are loaded into memory from the CONTROL-M/EM Database. Jobs are selected for a collection according to the values in the job processing parameters specified in the jobs job processing definition. Instructions for creating collections are provided under Creating and modifying collections on page 133.
Hierarchy: The order in which the selected jobs are displayed. The criteria available for hierarchy levels are the parameters in job processing definitions (for example, Application, Group, Cyclic, etc.), job status (for example, Ended OK) and job state (for example, Held).
90
Opening existing ViewPoints
The maximum number of hierarchy levels is five. The default hierarchy is CONTROL-M; Application; Group Name. For a complete description and an example of a hierarchical structure, see Chapter 1, CONTROL-M/EM basics. Instructions for creating hierarchies are provided under Creating and modifying hierarchies on page 150.
Filter: Which jobs are displayed in the CONTROL-M/Enterprise Manager window at a specific time (even though other jobs may have already been loaded into memory from the CONTROL-M/EM Database using collections). The following types of filters are available: Dynamic filters: These filters are defined as you need them and are discarded when you are finished with them. Only you have access to these filters. Filter presets: These are dynamic filters that are saved on the local computer for a later time. Global filters: These filters are defined in the CONTROL-M/EM Database and are available to all users in the enterprise. (In previous versions of CONTROL-M/EM, these filters were called regular filters.) Every ViewPoint is associated with a global filter, which is the default filter for that ViewPoint. The various types of filters, as well as how to create filters, are described in depth under Creating and modifying filters on page 139.
Opening existing ViewPoints

To open an existing ViewPoint: 1 Choose File => Open ViewPoint, or click
displayed. Figure 16 Open ViewPoint dialog box . The Open ViewPoint dialog box is
Chapter 2
91
Switching filters
2 Select the ViewPoint that you want and click OK. NOTE
To filter an existing ViewPoint as it is opened, select the ViewPoint, and then click Dynamic Filter before clicking OK. For instructions, see Creating filters dynamically on page 140.
Switching filters
You can, at any time, display the currently-open ViewPoint according to different filter criteria using one of the following methods:
creating a new dynamic filter on the fly for instructions, see Creating filters
dynamically on page 140
choosing a dynamic filter that you saved earlier as a filter preset for instructions,
see To display a ViewPoint using a filter preset on page 145.
choosing a global filter, by selecting a different global filter from the Filter box on the toolbar for instructions, see To use an existing global
filter: on page 127.
These methods affect the display of the current ViewPoint only, and are in effect only for the current session of CONTROL-M/EM.
Switching collections and hierarchies

You cannot display the currently-open ViewPoint according to a different collection or hierarchy. Instead, create a new ViewPoint with the desired collection and/or hierarchy, or open a ViewPoint that was created with the desired collection and/or hierarchy. Instructions for creating hierarchies are provided in Creating and modifying hierarchies. Instructions for creating collections are provided in Creating and modifying collections.
Displaying condition nodes In the FlowDiagram

1 With the FlowDiagram displayed, choose Tools => Options. 2 Select the Flowdiagram - Links panel in the Options dialog box.
92
Refreshing the display
Figure 17
Flowdiagram-Links panel
3 Select or clear the Display condition nodes check box and click OK. NOTE
When the Display condition nodes check box is selected, the Double Click on item to option is not available.
Refreshing the display

When jobs are ordered in a CONTROL-M (using the CONTROL-M Order or Force command), the display in the ViewPoint window must be refreshed that is, redisplayed) to include the ordered and forced jobs in the FlowDiagram. Choose View => Refresh Now to display these jobs. -orClick .
Even if the display has not been updated, the Active environment that is stored in the CONTROL-M/EM database is always updated immediately (such as soon as a job is ordered/forced).
Chapter 2
93
Navigating in the production environment
Navigating in the production environment

This section describes methods for navigating through the ViewPoint. After these methods, a summary is provided.

Locating a node in a FlowDiagram using the Navigation Tree Finding nodes Stepping In and Stepping Out Expanding and collapsing Zooming in/out Identifying dependent job nodes: Critical path Enhanced Why Neighborhood Branch Menus Navigating within a set of selected nodes Navigating: a summary
Locating a node in a FlowDiagram using the Navigation Tree

When you click a node in the Navigation Tree, the node is selected and highlighted in FlowDiagram and Net Overview if it is part of the hierarchy displayed. If it is not part of the hierarchy displayed, it can be found quickly and easily via the Navigation Tree.
To locate a node in a FlowDiagram using the Navigation Tree: 1 Right-click the node in the Navigation Tree. 2 Choose Find In Flowdiagram from the menu.
Appropriate levels are then expanded or collapsed, and the node is selected in the Navigation Tree, the FlowDiagram and the Net Overview:
If the level displayed in FlowDiagram is a higher level than the one requested, CONTROL-M/EM executes the Expand function to display the node level requested and highlights the node. If the level displayed in FlowDiagram is the same level as the node requested, CONTROL-M/EM highlights the node. If the level in FlowDiagram is lower than the one requested, CONTROL-M/EM executes the Step Out function and highlights the specified node.
94
Finding nodes
NOTE
For more information on the Expand/Collapse and Step In/Step Out functions, see Stepping In and Stepping Out on page 96 and Expanding and collapsing on page 98.
Finding nodes
You can find and select nodes in the current ViewPoint through use of the Find/Select Jobs dialog box. Each found node is highlighted in the Net Overview, and both highlighted and selected in the FlowDiagram, of the ViewPoint window.
To open and use the Find/Select Jobs dialog box: 1 Choose Edit => Find/Select Jobs.
-orClick (Find) on the toolbar.
The Find/Select Jobs dialog box is displayed (Figure 18). Figure 18 Find/Select Jobs dialog box
2 In the dialog box, fill in values for fields and click on states, as needed.
Chapter 2
95
Stepping In and Stepping Out
This dialog box is almost identical to the Dynamic Filter dialog box, and most fields correspond to fields in the job editing form. For a description of most fields, see Job node details on page 181. For additional information relevant to the dialog box, see Filling in dynamic filter fields on page 142. You can specify pattern-matching strings in some fields. Pattern matching rules are described in Specifying pattern-matching strings on page 73. Specified values are compared against job processing definitions to determine job selection.
3 Click Find/Select.
All nodes matching the criteria are selected, and the first node that fits the criteria is displayed. If desired you can:
Toggle between selected jobs, using the Selection buttons on the toolbar. View all selected jobs in a new ViewPoint, by choosing View => View Selection. Save or delete a preset, by clicking Save ( Find Presets area. ) or Delete ( ), respectively, in the
4 Click Close.

CONTROL-M/EM enables you to narrow the scope of the FlowDiagram by displaying the lower/higher level nodes for selected entities. Step In and Step Out are used to move between the levels in the hierarchy in FlowDiagram. Figure 19 Navigating with Step In and Step Out
96
For example, using the Default hierarchy, if the application level is currently being viewed, Step In causes the nodes on the group level to be displayed. Step Out causes the nodes on the CONTROL-M level to be displayed. The following rules apply for Step In/Step Out operations:
Activating the Step In/ Step Out operation changes the level displayed in FlowDiagram and repositions the Net Overview pane. Activating the Step In operation does not change the levels displayed in the Navigation Tree. Only collapsing and expanding levels in the Navigation Tree changes the levels displayed. Activating the Step In/Step Out operation from the toolbar causes all nodes in the current scope of the display to be represented by their lower-level or higher-level nodes. Multiple entities can be selected for Stepping In.
To Step In to an entity in FlowDiagram: 1 Right-click a high-level node and choose Step In from the menu, or click
-orDouble-click the high-level node if the Tools => Options => Flowdiagram - Nodes => Double Click option is set to Step into item (the default). For details about FlowDiagram options, see Chapter 10, Customization. .
To Step In to multiple entities in FlowDiagram: 1 Hold down the Ctrl key and select the high-level nodes. 2 Right-click a selected node and choose Step In from the menu. To Step Out of an entity in FlowDiagram: 1 Right-click a high-level node and choose Step Out from the menu, or click
.
Clicking the Hierarchy Display Level icons on the ViewPoint toolbar specifies the level of nodes to be displayed in FlowDiagram. The nodes displayed are still in the scope of the entities selected prior to clicking a Hierarchy Display Level icon.
Chapter 2
97
Expanding and collapsing
Expanding and collapsing

You can expand and collapse entities and their corresponding sub-entities (such as scheduling tables in a CONTROL-M, or jobs in a group) display and/or hide entities from the display.
NOTE
The Expand function is not available when condition nodes are displayed. Instead, use the Step In and Step Out functions to move in and out of the node hierarchy. This functions is described under Stepping In and Stepping Out on page 96.
To expand or collapse the display: 1 Right-click a node, and select Collapse or Expand from the menu.
-orDouble-click the node to toggle the Collapse/Expand function.
To collapse or expand multiple nodes in the Flow Diagram: 1 Hold down the Ctrl key and select the desired nodes.
-orRight-click a node and select Collapse or Expand from the menu.
Zooming in/out
Zooming out enables you to view a larger portion of the job production flow, while zooming in gives you a close-up view of the production enviornment.
To zoom in/out:
Use any of the following methods:
Click
or
. Repeat as necessary. box on the toolbar. You can
Select the size in the FlowDiagram Zoom also enter an alternative size and press Enter.
98
Identifying dependent job nodes
Right-click anywhere in the background of the FlowDiagram, and select Zoom In or Zoom Out from the menu. Repeat as necessary.
TIP
Use the Zoom In/Out feature together with a collection of jobs in the draft to view a specific part of the job production flow in a single window.

In the CONTROL-M/EM FlowDiagram, there are several tools that enable you to identify job nodes that have a dependent relationship (as predecessor jobs or as dependent jobs) with a job node that you specify. Each of these tools has its own advantages as a diagnostic tool, enabling you to maintain a more efficient scheduling environment. Each tool identifies related sets of nodes in a different way:
Critical path identifies the maximum runtime for a series of jobs and identifies the dependent job nodes in the longest path. For more information, see Critical path on page 99. Enhanced why identifies predecessors of a selected job that failed to run OK. For more information, see Enhanced Why on page 104. Neighborhood identifies jobs that are predecessors or dependents of a selected job. For more information, see Neighborhood on page 109. Branch menus display predecessor or successor jobs, jobs/scheduling tables, and conditions, within the ViewPoint. For more information, see Branch Menus on page 114.
Critical path
A critical path is the maximum runtime for a series of jobs or the longest path between those jobs. Critical path is calculated by selecting the nodes for the first and last jobs in the series in the FlowDiagram of the active ViewPoint. All nodes between the selected nodes are considered, and the critical path calculation returns the expected runtime for the longest possible combination of jobs between the selected nodes.
Chapter 2
99
NOTE
Jobs that have not yet run, or do not have runtime statistics, have an expected runtime of 0. These jobs are not factored into the calculation of the critical path.
Calculating critical path can help you make decisions about when and under what conditions to run complicated procedures that may involve various combinations of interdependent jobs.
To calculate a critical path: 1 In the FlowDiagram, expand all relevant group nodes so all jobs to be included in
the critical path are visible.
2 Select the first and last nodes in the path in the FlowDiagram. Last node should be
a descendent of the first node, but not immediately below it.
3 Right-click the node and choose Critical Path, or choose Action => Critical Path to
display the Critical Path dialog box. Figure 20 Critical Path dialog box
Table 18
Field
Critical Path dialog box fields (Part 1 of 2)

Description Data center name, member name, and order ID of the first and last jobs in the critical path. Statistics to be used to calculate the runtime for each job in the path. Average Runtime uses the average runtime for each job. Last Runtime uses the runtime of the last run of each job. Maximum time, in seconds, that the end of one job can overlap the start of the subsequent job while still allowing the critical path to be calculated.
From and To Use
Overlapping Tolerance
100
Table 18
Field
Critical Path dialog box fields (Part 2 of 2)

Description
Number of Number of nodes in the critical path nodes in path Total runtime Total runtime for all jobs in the critical path in HH:MM:SS format for path
NOTE
The Critical Path dialog box is a modeless window that stays on top of the current ViewPoint window until closed.
4 Choose either Average Runtime or Last Runtime. 5 If desired, specify an Overlapping Tolerance, in seconds. 6 Click Find Path. The number of nodes in the path and the total runtime for the
path are displayed. In the FlowDiagram, all nodes in the critical path are displayed with a gray background.
To display Critical Path details: 1 Calculate a critical path, as described in the preceding procedure. 2 Click Details to view details of the nodes in the critical path.
Chapter 2
101
3 Double-click a job in the Details list to open the Job Editing form for that job. TIP
Right-click a job in the Details list to display the following options: Item Count displays or hides the counter at the bottom of the Details list. Find in FlowDiagram highlights the selected jobs in the FlowDiagram. Properties opens the Job Editing form for that job.
4 Click Close to close the Critical Path dialog box. NOTE

To calculate a critical path for a different set of nodes, close the Critical Path dialog box, select the nodes for the new path, and re-open the Critical Path dialog box.
102
To export details about jobs in a critical path to a comma-delimited (CSV) file 1 Calculate a critical path, as described on page 100. 2 Right-click a job in the Details list and select Export to File. A Windows Export to
File dialog box is displayed.
A Browse to the location where you want to save the file. B Enter the file name and click OK. The file is saved with a .csv extension. To create and view a report containing the details about jobs in a critical path 1 Calculate a critical path, as described on page 100. 2 Click Create Report to save this information as a file. A Browse to the location where you want to save the report. B Enter the reports name and click OK. The report is saved as a text file, which
contains the following information:

Title (Critical Path Report) The date and time that the report was created Details about the two selected nodes: Data Center, Mem Name and Order ID Critical path criteria Number of nodes found Total runtime for the path List of all jobs that were found, with the following information for each job: Order ID, Data Center, Application, Group Name, Mem Name and Job Name
Chapter 2
103
3 Click Show Report to open the report that you just created in your default text
editor, as shown below:
4 To print the report, choose File => Print. A standard Windows Print dialog box
appears.
5 Click Close to close the Critical Path dialog box.
Enhanced Why
Enhanced Why enables you to identify jobs that failed to run OK that are predecessor jobs (jobs that are In conditions for a subsequent job) of a selected job. You can choose to identify only the oldest predecessor job that failed to run OK, or all predecessor jobs. This feature can help you determine why a selected job or Group Scheduling table failed to run as expected. The Enhanced Why option is available when a single node in Wait status is selected in either the FlowDiagram or Tree View of the active ViewPoint.
104
To get additional information about why a job failed using Enhanced Why: 1 Select a job or group scheduling table node from the FlowDiagram or Navigation
Tree.
NOTE
Enhanced Why is available only when the selected job or Group Scheduling table has In conditions and Wait status (it has not yet run).
2 Right-click the node and choose Enhanced Why, or choose Action => Enhanced
Why. The Enhanced Why dialog box is displayed. Figure 21 Enhanced Why dialog box
Table 19
Field
Enhanced Why dialog box fields

Description Number of nodes in the predecessor jobs and Group Scheduling table Data center name, member name and order ID of the selected job or Group Scheduling table node Indication that all predecessor jobs and Group scheduling tables that did not end or did not end OK are displayed when Find is clicked. Indication that the oldest predecessor jobs and Group scheduling tables that did not end or did not end OK are displayed when Find is clicked.
Number of Nodes Found Start Node Details With path Without path
NOTE
The Enhanced Why dialog box is a modeless window that stays on top of the current ViewPoint window until closed.
3 Select either With path or Without path. 4 Click Find. The predecessor jobs that failed to run OK are highlighted in the
FlowDiagram.
Chapter 2 Viewing the production environment 105
5 Click Close to close the Enhanced Why dialog box. To display Enhanced Why details: 1 Display predecessor jobs that failed to run OK, as described in the preceding
procedure.
2 Click Details to display details for the selected jobs and Group Scheduling tables.
Right-click a job in the Details list to display the following options:

Item Count displays or hides the counter at the bottom of the Details list. Find in FlowDiagram highlights the selected jobs in the FlowDiagram. Properties opens the Job Editing form for that job.
4 Click Close to close the Enhanced Why dialog box.
106
To export Enhanced Why details to a comma-delimited (CSV) file: 1 Display predecessor jobs that failed to run OK, as described on page 105. 2 Right-click a job in the Details list and select Export to File. A standard Windows
Export to File dialog box appears.
A Browse to the location where you want to save the file. B Enter the file name and click OK. The file is saved with a .csv extension. To open Enhanced Why details in a new ViewPoint: 1 Display predecessor jobs that failed to run OK, as described on page 105. 2 Click Open ViewPoint.
The new ViewPoint has the following properties:
You cannot change the filter on the new ViewPoint. Changes made to the original ViewPoint are reflected in the new ViewPoint, but the Enhanced Why search is not recalculated as a result. Deletion of a job in the original ViewPoint is reflected in the new ViewPoint, but jobs that are connected to the deleted job are not deleted. The Refresh Needed button functions as in any ViewPoint. The hierarchy of the new ViewPoint is inherited from the original ViewPoint.
TIP
For more information about opening selected nodes in their own ViewPoint, see Viewing selected nodes in a new ViewPoint on page 120.
3 Click Close to close the Enhanced Why dialog box.
Chapter 2
107
To create and view a report containing the Enhanced Why details: 1 Display predecessor jobs that failed to run OK, as described on page 105. 2 Click Create Report to save this information as a file. A Browse to the location where you want to save the report. B Enter the report name and click OK. The report is saved as a text file, which
contains the following information:

Title (Enhanced Why Report) The date and time that the report was created Details about the two selected nodes: Data Center, Mem Name and Order ID Enhanced Why criteria Number of nodes found Total runtime for the path A list of all jobs that were found, with the following information for each job: Order ID, Data Center, Application, Group Name, Mem Name and Job Name
3 Click Show Report to open the report that you just created in your default text
editor, as shown below:
4 To print the report, choose File => Print. A Windows Print dialog box is displayed. 5 Click Close to close the Enhanced Why dialog box.
Neighborhood
The Neighborhood option identifies jobs that are predecessors or dependents of a selected job or Group Scheduling table and highlights the nodes of those jobs in the FlowDiagram. This option is available when a single node is selected in either the FlowDiagram or the Navigation Tree of the active ViewPoint. The Neighborhood option is not available when:

condition nodes are displayed more than one node is selected
To view jobs in the neighborhood of the current job: 1 Select a job or Group Scheduling table node in the FlowDiagram or the Navigation
Tree.
2 Right-click the node and choose Neighborhood, or choose

Action => Neighborhood. The Network Neighborhood dialog box is displayed. Figure 22 Network Neighborhood dialog box
Chapter 2
109
Table 20
Field
Network Neighborhood dialog box fields

Description Data center name, member name and order ID of the selected job or Group Scheduling table node Type of Neighborhood nodes in the current display which may be selected. Radial Direct Relationships Identifies relevant job nodes branching in all directions. Identifies the predecessor and the dependent nodes directly above and below the selected node. Note: The number of levels above and below are determined by the Radius parameter. Predecessor Identifies the predecessor nodes of the selected job. Note: The number of levels that are surveyed is determined by the Radius parameter. Dependent Identifies the nodes dependent on the selected job. Note: The number of levels that are surveyed is determined by the Radius parameter.
Node Details Direction
Radius Number of Nodes Found
Number of nested levels of nodes to be included in the Neighborhood, branching out from the selected node. Valid values: 1-99999. Number of nodes found in the Neighborhood selection process.
NOTE
The Neighborhood dialog box is a modeless window that stays on top of the current ViewPoint window until closed.
3 Select a value from the Direction list box to indicate the direction in which to
extend the search for applicable nodes. Direction values are described in Table 20.
4 Specify a numeric value in the Radius text box. 5 Click Find. The applicable job nodes in the FlowDiagram are selected. NOTE
The Queried Collection system parameter specifies whether the identified jobs are located in the current ViewPoint only (default) or in all jobs. For more information, see the System Parameters appendix in the CONTROL-M/Enterprise Manager Administrator Guide.
6 Click Close to close the Network Neighborhood dialog box.
110
To display Neighborhood details: 1 Display neighboring jobs for a particular node, as described in the preceding
procedure.
2 Click Details to display details for the predecessor or dependent jobs.
Right-click a job in the Details list to display the following options:

Item Count displays or hides the counter at the bottom of the Details list. Find in FlowDiagram highlights the selected jobs in the FlowDiagram. Properties opens the Job Editing form for that job.
4 Click Close to close the Network Neighborhood dialog box.
Chapter 2
111
To export Neighborhood details to a comma-delimited (CSV) file: 1 Display neighboring jobs for a particular node, as described on page 109. 2 Right-click a job in the Details list and select Export to File. A standard Windows
Export to File dialog box is displayed.
A Browse to the location where you want to save the file. B Enter the file name and click OK. The file is saved with a .csv extension. To open Neighborhood details in a new ViewPoint: 1 Display neighboring jobs for a particular node, as described on page 109. 2 Click Open ViewPoint to display the selected jobs in their own ViewPoint. The new
ViewPoint has the following properties:

The job on which the Neighborhood action was performed is highlighted. You cannot change the filter on the new ViewPoint. Changes made to the original ViewPoint are reflected in the new ViewPoint. Deletion of a job in the original ViewPoint is reflected in the new ViewPoint, but jobs are not added to this ViewPoint. Additional Neighborhood, Enhanced Why, and Critical Path functionality is enabled in the new ViewPoint. The Refresh Needed button functions as in any ViewPoint, but no jobs can be added to or deleted from the new ViewPoint. The hierarchy of the new ViewPoint is inherited from the original ViewPoint.
TIP
For more information about opening selected nodes in their own ViewPoint, see Viewing selected nodes in a new ViewPoint on page 120.
3 Click Close to close the Network Neighborhood dialog box. NOTE

To define a Neighborhood for another node, close the Neighborhood dialog box, select a different node, and re-open the Neighborhood dialog box.
112
To create and view a report containing Neighborhood details: 1 Display neighboring jobs for a particular node, as described on page 109. 2 Click Create Report to save this information as a file. A Browse to the location where you want to save the report. B Enter the name of the report and click OK. The report is saved as a text file,
which contains the following information:

Title (Neighborhood Report) The date and time that the report was created Details about the two selected nodes: Data Center, Mem Name and Order ID Neighborhood criteria Number of nodes found Total runtime for the path A list of all jobs that were found with the following information for each job: Order ID, Data Center, Application, Group Name, Mem Name and Job Name
3 Click Show Report to open the new report in the default text editor:
4 To print the report, choose File => Print. A Windows Print dialog box is displayed. 5 Click Close to close the Network Neighborhood dialog box.
Chapter 2
113
Branch Menus
Using the Branch Menus option in the menu of a node in the FlowDiagram, you can display the following within the ViewPoint: predecessor or successor jobs jobs/scheduling tables dependencies (indicated by arrows pointing in the appropriate direction) if working in Conditions mode
To display predecessor or successor jobs/groups/conditions for a node: 1 From the menu for the node, select the Branch Menus option. 2 From the submenu, select Predecessor or Successor. The next submenu displays a
list of jobs, groups, and conditions (if you are working in Condition mode).
3 Select the job, group, or condition you want to display. The selected job, group, or
condition node (and relevant connected nodes) will be displayed and will become the new current node.
NOTE
In the CONTROL-M/EM GUI, Branch Menus can also be selected from the Navigation Tree.
The FlowDiagram modes set in the Tools => Options dialog box will impact the display as follows:
If you are working in Condition mode, condition nodes (see page 89) are displayed in addition to job and job/scheduling group nodes, in the menu selection list. In addition, Branch menus will be available for Condition nodes. Note that if your site displays deleted Out conditions with dotted lines, any such deleted Out conditions will be displayed. If you are working in Expand/Collapse mode (see page 98) and you select a job, the upper nodes will be automatically expanded in the FlowDiagram (if necessary). If you are working in Step In/Step Out mode (see page 96): if the selected job is at the same level as the current node, the selected job is added to the job list. if the selected job is at a higher level than the current node, the FlowDiagram changes to the level of the FlowDiagram to the selected job.
114
Navigating: a summary
Navigating: a summary
There are various methods for moving around the current ViewPoint window. The following levels of movement are possible:
Same-level movement Allows you to move up, down, left, or right on the current hierarchical level being displayed. For example, if you view entities on the group level, it is possible to move to those groups that are not currently displayed in the window, and bring them into view. Different-level movement Allows you to move between various levels of the hierarchy. For example, in the default hierarchy, if the group level is being used, you can move up one level and view the application level.
Same-level movement
Same-level movement is used to navigate in all directions in the current hierarchical level. This is most useful when the network is larger than the size of the window. There are several ways to navigate on the same level in the ViewPoint window: Using the scroll bars on the bottom and sides of FlowDiagram and Net Overview Moving the rectangle in Net Overview Using production flow links in FlowDiagram Selecting a different same-level node in the Navigation Tree Using the Find window (described in Locating a node in a FlowDiagram using the Navigation Tree on page 94) Toggling between nodes in a set of selected nodes, all of which are on the same level (described in Navigating within a set of selected nodes on page 117.)
Different-level movement
Different-level movement is used to move between levels in the hierarchy. There are several ways to navigate to a different level in the ViewPoint window: Using the Hierarchy Display Level icons on the ViewPoint toolbar. Using the Step In/Step Out buttons on the CONTROL-M/EM toolbar. Using the Step In/Step Out options in the menus in the FlowDiagram. Double-clicking a node if the Using the Double Click: Step Into Item option is selected in the Flowdiagram-Nodes panel under Tools-->Options. See Chapter 10, Customization.) Using the Find/Select Jobs dialog box (described in Finding nodes on page 95.) Toggling between nodes in a set of selected nodes, which are on different levels (described in Navigating within a set of selected nodes on page 117.)
Controlling the production environment
Controlling the production environment

Selecting nodes manually
Nodes can be selected in either the Navigation Tree or FlowDiagram. Selection of nodes works differently in these panes of the ViewPoint window. The following lists methods of selecting nodes.
When you click a node in the Navigation Tree, the node is highlighted in the tree, and the corresponding graphic representation of the node is also highlighted in the FlowDiagram, if it is part of the hierarchy displayed. The level of detail displayed in the FlowDiagram is dependent upon the current setting of the Hierarchy Display Level option or Step In/Step Out option. When you click a node in the FlowDiagram, the node is highlighted with a dark background. The node is not highlighted in the Navigation Tree. When you click a node in the Flow Diagram view, the node is highlighted with a colored background and has a rectangle surrounding it, indicating that it is also the focused node. (The color of the rectangle can be changed using the Tools => Options menu option.) When you select a set of nodes, one node remains the focused node. However, you can toggle between all the selected nodes, wherever they appear in the FlowDiagram (as described under Navigating within a set of selected nodes). Actions are performed on all selected node.
After selecting a node or set of nodes, certain operations (for example, Hold, Edit JCL, Free) can be performed on the job(s) associated with the node(s). These operations are described in Job actions on page 204.
NOTE
In addition to the methods for selecting nodes described below, nodes are also selected (highlighted) after performing the following operations:

Locating a node in a FlowDiagram using the Navigation Tree Finding nodes Critical path Enhanced Why Neighborhood Branch Menus
116
Navigating within a set of selected nodes
Navigating within a set of selected nodes

If several nodes are selected simultaneously in the Flow Diagram, it is possible to navigate between the selected nodes, changing the focus from node to node. For instructions on how to select multiple nodes, see Selecting nodes manually on page 116
To navigate within a set of selected nodes

With a set of nodes selected, click the following buttons in the CONTROL-M/Enterprise Manager window toolbar (or corresponding options in the View => Toggle Selection menu) to navigate:
Button Description Navigate to the first node in the set, making it the focused node. Navigate to the previous node in the set, making it the focused node. Navigate to the first next in the set, making it the focused node. Navigate to the last node in the set, making it the focused node.
Performing actions on selected nodes

To perform an action on a node in the FlowDiagram: 1 Click the node to be selected. The shaded background of the node indicates that
the node has been selected.
2 Click the right mouse button on the selected job node/nodes and choose the
desired action from the menu.
To perform an action on a single node from the Navigation Tree: 1 Select a node in the Navigation Tree. 2 Choose an option from the Action menu, or right-click the node and choose the
Chapter 2
117
To perform an action on multiple nodes in the FlowDiagram (Method 1): 1 Click the left mouse button on the first node to be selected.
The shaded background of the node indicates that the node is selected.
2 Press the Ctrl key and click the left mouse button on the next node to be selected.
A shaded background also is displayed for this node.
3 Repeat as necessary until all nodes are selected. 4 Click the right mouse button on the selected job node/nodes and choose the
To perform an action on multiple nodes from the FlowDiagram (Method 2): 1 In the FlowDiagram, click and drag to select the required nodes. A dotted
rectangle is displayed as you drag the cursor.
2 Choose an option from the Action menu, or right-click one of the nodes, and
choose the desired action from the menu.
To perform an action on all nodes in the FlowDiagram:

This option selects those nodes currently displayed in the FlowDiagram, but does not select all nodes in the Net Overview window.
1 Choose View => Select All. All nodes displayed in the FlowDiagram are selected. 2 Choose an option from the Action menu, or right-click one of the nodes and choose
the desired action from the menu.
NOTE
Select All can select nodes of any type other than condition nodes.
To de-select one of the selected nodes:

Press the Ctrl key and click the left mouse button on the node to be de-selected.
To de-select all selected nodes:

Click anywhere in the pane outside the selected nodes.
118
Handling Errors
If errors occur while performing an action, the Job Action Report window is automatically displayed. You can also display the Job Action Report window by request:
To display the Job Action Report window

In the CONTROL-M/Enterprise Manager window, select the View => Action Report menu option.
Messages remain in the window until you clear them or until the maximum number of messages allowed has been reached. (The maximum is defined in the Display n last Job Actions in Report option in the Options window. For details, see Chapter 10, Customization.) Review the errors, and either click Hide or Clear:
Hide
Closes the Job Action Report window, but CONTROL-M/EM continues to record all messages that are issued.
Clear
Erases all messages displayed in the Job Action Report window, leaving the window open.
Chapter 2
119
Viewing selected nodes in a new ViewPoint
Viewing selected nodes in a new ViewPoint

You can open a special ViewPoint that contains only the selected nodes in the current, regular ViewPoint.
NOTE
If high level entities (for example, scheduling groups) are selected in addition to job nodes, all jobs in the high level entity are also considered to be selected. The resultant FlowDiagram is opened at the level of the high level node.
This type of ViewPoint is similar to regular ViewPoints. However, because it is based on a fixed set of nodes:

filters cannot be applied nodes may be deleted from the ViewPoint, but not added (including during a refresh of the ViewPoint)
To view selected nodes in their own ViewPoint: 1 With a set of nodes selected, select the View => View Selection menu option. The
special ViewPoint opens.
TIP
This type of ViewPoint can also be opened as a result of performing the Neighborhood, Critical Path, and Enhanced Why operations.
Creating ViewPoints
The following options are available for creating ViewPoints:
ViewPoint Wizard ViewPoint Manager A step-by-step guide to creating a new ViewPoint. See Creating ViewPoints using the ViewPoint Wizard on page 121. Enables you to define new ViewPoints or modify existing ones. The ViewPoint Manager can also be used to define or modify collections, filters, and hierarchies. See Creating and editing ViewPoints using ViewPoint Manager on page 129.
120
Creating ViewPoints using the ViewPoint Wizard

The ViewPoint Wizard is used to create a new ViewPoint. It automatically displays screens that allow you to define new collections, global filters, and hierarchies or select existing ones. These components determine which active jobs are displayed in the ViewPoint window and how they are displayed. You are taken step-by-step through the process of creating a new ViewPoint. The ViewPoint Wizard window can be opened at any time during a CONTROL-M/EM session to create a new ViewPoint.
To create a new ViewPoint using the ViewPoint Wizard: 1 Choose File => New ViewPoint or click
.
A series of windows (called the ViewPoint Wizard) is displayed. The wizard leads you through the steps in creating a new ViewPoint. Each window contains instructions for completing the necessary step.

Click Next to accept the data entered and proceed to the next step. Click Back to return to the previous window.
As you click Next, you will progress through the following windows, described below:

Step 1 of 5: ViewPoint Step 2 of 5: Hierarchy Step 3 of 5: Collection Step 4 of 5: Filter Step 5 of 5: Finish
Chapter 2
121
Step 1 of 5: ViewPoint
Figure 23 ViewPoint Wizard First window
This window prompts for the name and description of the new ViewPoint:
1 Specify a name for the new ViewPoint. This field is required. 2 Enter a description of the new ViewPoint. This field is optional.
The description is displayed in the Open ViewPoint dialog box to assist in locating a ViewPoint.
3 Click Open this ViewPoint at the end of the wizard to have this ViewPoint opened
automatically upon completing the steps of the ViewPoint Wizard (Default).
4 Click Next to continue.
122
Step 2 of 5: Hierarchy
Figure 24 ViewPoint Wizard Hierarchy window
This window prompts for the hierarchy to be used in the new ViewPoint. You can use an existing hierarchy or define a new hierarchy. A hierarchy defines how the selected jobs are displayed in the ViewPoint. The criteria available for hierarchy levels are the parameters in job processing definitions (for example, Application, Group, Cyclic, and so on), job status (for example, Ended OK) and job state (for example, Held). For a description of the job processing parameters, see the CONTROL-M Job Parameter and Variable Reference Guide. For a description of job status and states, see Chapter 2, Viewing the production environment. The ViewPoint Wizard allows you to define up to four levels for a new hierarchy. The default hierarchy is CONTROL-M, application, group. For a complete description and an example of a hierarchical structure, see Chapter 1, CONTROL-M/EM basics.
To choose an existing hierarchy: 1 Select Existing Hierarchy. 2 Select a hierarchy from the list. The levels for that hierarchy are displayed. 3 Click Next to continue.
To define a new hierarchy: 1 Select New Hierarchy. 2 Specify a name for the new hierarchy.
As a default, the system uses the name that you specified for the ViewPoint, appending Hier to the end. Hierarchy names are not case sensitive.
3 Select criteria for each level of the new hierarchy from the lists, and click Next to
continue.
Step 3 of 5: Collection
Figure 25 ViewPoint Wizard Collection window Existing Collection pane
This window prompts for the collection to be used in the new ViewPoint. You can use an existing collection or define a new collection. A collection defines which jobs in the enterprise are loaded into memory. Jobs are selected for a collection according to the values in the job processing parameters specified in the jobs job processing definition.
124
To use an existing collection: 1 Select Existing Collection. 2 Select a collection from the list. 3 Click Next to continue. To edit an existing collection: 1 Select Existing Collection. 2 Select a collection from the list. 3 Click Edit. The Collection Definition window opens. Instructions for completing
this window are described in Creating and modifying collections on page 133.
4 Click Next to continue. To define a new collection: 1 Select New Collection. 2 Specify a name for the new collection.
As a default, the system uses the name that you specified for the ViewPoint, appending Coll to the end. Collection names are not case sensitive.
3 Select which jobs to include in the new collection.

Select criteria from lists for each field or enter data as required. Instructions for completing the Edit table are described in Defining selection criteria for the collection on page 135. The New Collection option provides the capability of defining up to four collection criteria. Multiple collection criteria are defined using the Boolean OR. All jobs that satisfy at least one of the criteria are in the collection.
Example
The following collection criteria includes jobs that meet either of the following criteria:

Job name begins with JOB4. Job belongs to a group whose name begins with GRP5.
Figure 26
ViewPoint Wizard Collection window Collection pane
Step 4 of 5: Filter
Figure 27 ViewPoint Wizard Filter window Existing Filter pane
126
This window prompts for the global filter to be used in the new ViewPoint. You can use an existing global filter or define a new global filter. A global filter defines which jobs are displayed in the ViewPoint. Jobs are selected for a global filter according to the values in the job processing parameters specified in the jobs job processing definition or according to the jobs status (for example, Ended OK), and state (for example, Held).
NOTE
A ViewPoints global filter can be changed temporarily at any time during a CONTROL-M/Enterprise Manager session by selecting a different global filter from the Filter box on the toolbar. This changes the global filter criteria for the current session only.
To use an existing global filter: 1 Select Existing Filter. 2 Select a global filter from the list. 3 Click Next to continue. To edit an existing global filter: 1 Select Existing Filter. 2 Select a global filter from the list. 3 Click Edit.
The Filter Definition window opens. Instructions for completing this window are similar to the Collection Definition window described in Defining selection criteria for the collection on page 135.
4 Click Next to continue. To define a new global filter: 1 Select New Filter. 2 Specify a name for the new global filter.
As a default, the system uses the same name that you specified for the ViewPoint, appending Filt to the end of the name. Global filter names are not case sensitive.
Chapter 2
127
3 Select which jobs to include in the new global filter. Select criteria from lists for
each field or enter data as required. Instructions for completing the Edit table are described in Defining selection criteria for the collection on page 135.

A New Filter option can define up to four global filter criteria. Multiple global filter criteria are combined using a Boolean OR relationship.(All jobs that satisfy at least one of the criteria are in the global filter.)
Example
This global filter includes all jobs that ended Not OK or are cyclic jobs. Figure 28 ViewPoint Wizard Filter window New Filter pane
128
Creating and editing ViewPoints using ViewPoint Manager
Step 5 of 5: Finish
Figure 29 ViewPoint Wizard Finish window
This window summarizes the properties of the new ViewPoint.

Click Back to modify any of the ViewPoints components. Click Finish to save the new ViewPoint. If the Automatically open this ViewPoint check box was selected in Step 1, the ViewPoint is automatically opened in the ViewPoint window.

The ViewPoint Manager is used for

Creating and modifying ViewPoints Creating and modifying collections Creating and modifying filters Creating and modifying hierarchies
Chapter 2
129
To open the ViewPoint Manager: 1 Select Edit => ViewPoint Manager from the CONTROL-M/Enterprise Manager
menu bar, or click Figure 30 . The ViewPoint Manager window is displayed: ViewPoint Manager Window
Creating and modifying ViewPoints

ViewPoints are the means for adapting the view of the enterprise to suit your various requirements. Each ViewPoint consists of a collection, filter, and hierarchy. The ViewPoint Manager is also used to create, modify or delete existing collections, filters, and hierarchies. CONTROL-M/EM is supplied with several default ViewPoints, the most comprehensive of which is called the All Jobs ViewPoint. This ViewPoint consists of the following components that cannot be edited or deleted: Table 21
Component All Jobs collection All Jobs filter Default hierarchy
Data fields of the All Jobs ViewPoint

Description Loads all jobs in the enterprise into memory Displays all jobs in the ViewPoint window Structures the ViewPoint according to CONTROL-M, Application, Group Name hierarchy
To create a new ViewPoint: 1 Select the word ViewPoints or the name of any ViewPoint in the ViewPoint Tree. 2 Click New, or right-click and choose New from the menu.
130
The following dialog box is displayed.
3 Specify a name for the new ViewPoint and click OK. The ViewPoint Properties
window is displayed. Figure 31 ViewPoint Properties Dialog Box
4 Enter a description for the ViewPoint. This field is optional. 5 Select a collection, global filter and hierarchy from the list boxes for each
component.
6 To edit a selected item, click Edit next to the selection.

The corresponding Definition window for that component is displayed (see Creating and modifying collections on page 133, Creating and modifying filters on page 139, and Creating and modifying hierarchies on page 150).
Chapter 2
131
7 After selecting a hierarchy, select the Initial Level of the Hierarchy to display when
the ViewPoint is opened. As a default, CONTROL-M/Enterprise Manager opens the ViewPoint with the highest hierarchy level nodes displayed in the FlowDiagram.
8 Click OK to save the new ViewPoint settings. To edit an existing ViewPoint: 1 Select the ViewPoint from the ViewPoint Tree and either click Edit, or right-click
and choose the Edit option from the menu. -orDouble-click the ViewPoint in the ViewPoint Tree. The ViewPoint Properties window is displayed.
2 Modify the description and components of the ViewPoint. 3 Click OK to save the modified settings. To delete an existing ViewPoint: 1 Select the ViewPoint from the ViewPoint Tree. 2 Click Delete, or right-click and choose Delete from the menu.
The following message is displayed:
3 Click OK.
132
Creating and modifying collections

The ViewPoint Manager is also used to create a new collection or modify an existing one. A collection defines which jobs in the enterprise are loaded into memory. Jobs are selected for a collection according to the values in the job processing parameters specified in the jobs job processing definition.
To create a new collection: 1 Select the word Collections or the name of any collection in the ViewPoint. NOTE
If the collection item is selected from a hierarchical ViewPoint branch of the tree, the new collection will not replace the selected item. To replace the original collection with the new collection, use the ViewPoint Properties window to select the new collection after it has been defined in the system.
2 Click New, or right-click and choose New from the drop-down menu.
The following dialog box is displayed.
3 Specify a name for the new collection and click OK.

The Collection Definition window is displayed.
Chapter 2
133
Figure 32
Collection Definition window
4 Enter a description for the collection. This field is optional. 5 Define selection criteria for the collection, as described below. 6 Click OK to save the new collection definition. To edit an existing collection: 1 Select the collection from the ViewPoint Tree and click Edit.
-orSelect the collection from the ViewPoint Tree, right-click and choose the Edit option from the menu. -orDouble-click the collection in the ViewPoint Tree. The Collection Definition window is displayed.
134
2 Modify the collection description and criteria as described below. 3 Click OK to save the modified settings. To delete an existing collection: 1 Select the collection from the ViewPoint Tree. NOTE
Collections cannot be deleted from a hierarchical ViewPoint branch in the ViewPoint Tree.
2 Click Delete, or right-click and choose Delete from the menu.

A Confirmation window is displayed.
3 Click OK.
Defining selection criteria for the collection

The Edit table in the Collection Definition window contains a combinations of fields, operators and values for defining the collection. The field values are compared against the parameters in job processing definitions (for example, Application, Group, and so on) to determine if the jobs should be included in or excluded from the collection. Job parameters are described in the CONTROL-M Job Parameter and Variable Reference Guide. Table 22
Column Field Operator Value
Collection selection criteria

Description Field to be checked in the job processing definition Relational operator to be applied to the specified value Value that determines whether or not the criteria are satisfied
The Field column in the table is a list box. By clicking the arrow to the right of the field, a list of possible parameters is displayed.
Chapter 2
135
NOTE
Not all job processing parameters in the job processing definition are available for selection criteria.
The Operator column in the table is also a list box. When you click inside the column, a list of possible operators is displayed. Figure 33 Collection Definition edit operators
Valid operators are listed in Table 23.
136
Table 23
Operator = LIKE > < !=
Valid operators
Description Value in the job must equal the value in the table. Value in the job must be contained within the value in the table, similar to using a wildcard * in the value field. Value in the job must be greater than the value in the table. Value in the job must be less than the value in the table. Value in the job must not equal the value in the field.
The Value column is used to specify the value of the field. If applicable, a list of possible values is displayed when you click inside the column.
NOTE
Each completed row in the table is added to the appropriate Include In/Exclude From Collection list described below.
Applying the criteria

The middle section of the Collection Definition window contains Include In Collection and Exclude From Collection lists that are used to specify how the selection criteria are applied. Each line in the Include In/Exclude From Collection list can include multiple criteria. The relationship between these criteria is an AND relationship. Only jobs that fulfill both conditions are included in/excluded from the collection. The relationship between separate lines in the Include In/Exclude From Collection list is an OR relationship. All jobs that fulfill either the criteria of the first line or the criteria of any subsequent line are included in/excluded from the collection.
To add a line in the Include In/ Exclude From collection list: 1 Click anywhere in the list. 2 Click Add. 3 Create criteria for this line. 4 Click anywhere in the list again, click Add, or press the Tab key until a new edit
line is displayed.
Chapter 2
137
To add or modify criteria to a line in the Include In / Exclude From collection list 1 Select a line from the Include In/ Exclude From Collection list.
The criteria are displayed in the Edit table.
2 Modify or add to the criteria. 3 Click the selected line, click Add or press the Tab key until a new edit line is
displayed.
To delete criteria from a line in the Include In / Exclude From collection list 1 Select the line to be changed.
The criteria are displayed in the Edit table.
2 Select the criterion you wish to delete by clicking its number in the Edit table. 3 Press the Delete key. 4 Press the Tab key twice. To delete a line in the Include In / Exclude From collection list 1 Select the line to delete. 2 Click Delete. Example
The following collection criteria will include only jobs that meet either of the following criteria:

Job name ends with JOB4. Job belongs to a group whose name is APPL.
138
Creating and modifying filters
Figure 34
Collection Definition window

Filters determine which jobs are displayed in the CONTROL-M/Enterprise Manager window at a specific time (even though other jobs may have already been loaded into memory from the CONTROL-M/EM Database using collections). This section provides instructions for

Creating filters dynamically Saving dynamic filters (filter presets) for private use Configuring how dynamic filters are saved Creating and modifying global filters
Chapter 2
139
Creating filters dynamically

Dynamic Filters are defined as you need them (on the fly) and are discarded when you are finished with them. Dynamic filters are not defined in advance, as are global filters (also known as regular filters), which are pre-defined. Dynamic filter definitions can be saved locally. For more information, see Saving dynamic filters (filter presets) for private use. The default location for saving dynamic filters is under the user profile, but this can be configured (see Configuring how dynamic filters are saved on page 145).
Accessing the Dynamic Filter Definition dialog box

Dynamic filters are defined using the Dynamic Filter dialog box (Figure 35), which is accessed using the following methods:

With the desired ViewPoint open, select the File --> Dynamic Filter menu option. With the desired ViewPoint open, select the <Dynamic Filter> value in the ViewPoints Filter list. When opening a ViewPoint using the File --> Open option in CONTROL-M/EM, select the desired ViewPoint and click Dynamic Filter in the CONTROL-M/Enterprise Manager Viewpoints dialog box. The dynamic filter is displayed with the last-used dynamic filter loaded by default (or empty if no dynamic filter was used before). For a description of dynamic filters, see Creating filters dynamically on page 140 and Saving dynamic filters (filter presets) for private use on page 144.
NOTE
When you open the Open ViewPoint dialog box and click Dynamic Filter..., the Dynamic Filter dialog box is, by default, empty. However, once you have defined a dynamic filter for a ViewPoint, the dynamic filter definition is kept, and redisplayed whenever you click Dynamic Filter... for the ViewPoint, until you clear this filter definition. (The dynamic filter definition is displayed even if you subsequently selected a different filter from the filter selection list.) To clear the dynamic filter definition, click Clear in the Dynamic Filter dialog box.
140
The Dynamic Filter dialog box is opened, with the name of the ViewPoint displayed in the title bar. Figure 35 Dynamic Filter dialog box
TIP
If desired, use the Filter Presets field at the top of the dialog box to call up an existing dynamic filter or define a new dynamic filter. For details, see Saving dynamic filters (filter presets) for private use on page 144.
Defining a dynamic filter 1 Access the Dynamic Filter dialog box, as described under Accessing the Dynamic
Filter Definition dialog box.
2 Enter the fields of the dialog box. See Filling in dynamic filter fields on page 142. 3 When you are done, click OK.
Nodes are displayed in the currently-open ViewPoint as specified in the dynamic filter. The Filters list at the top of the CONTROL-M/Enterprise Manager window shows <Dynamic Filter> as the current filter.
Chapter 2
141
NOTE
Reopening the Dynamic Filter dialog box displays the last-saved dynamic filter values for the ViewPoint (meaning, not the last-used dynamic filter).
Filling in dynamic filter fields

Most filtering fields correspond to fields in the job editing form. For a description of most fields, see Job node details on page 181; some runtime filter fields, such as Average Run Time, are described in Table 38 on page 186 (which describes the fields of the Active panel).
NOTE
When specifying a filter with Time From and To fields, the filter processes values in the Start Time and End time fields in the Job Detail screen (not the From and Until fields in the Job Detail screen).
The Dynamic Filter dialog box provides basic filter-defining capabilities that enable specification of most filtering options. (If you require a more complex filter, you can create it using the ViewPoint Manager and save it as a global filter in the CONTROL-M/EM database.)
The filter uses the LIKE operator for all text fields except the Odate and Time parameters. For Odate From and Time From, the >= operator is used. For the Odate To and Time To fields, the <= operator is used. Fields can contain several criteria, separated by commas (for example, CONTROLM = A*,B*). Checkboxes at the bottom of the dialog box allow you to filter on State. To filter on Emergency or Critical jobs, use the checkboxes as follows: To display all emergency jobs and/or tasks in MVS (only), select Emergency (and select Job and/or Task in the TaskType dialog box). To display all critical CONTROL-M for Distributed Systems jobs, select Critical.
NOTE
Do not select both Emergency and Critical or no jobs will be displayed.
The Status and TaskType fields each have a button ( ) that when clicked, opens an appropriate dialog box (with relevant checkboxes) as follows:
142
Status Selection dialog box Filtering by Status To dynamically filter by job status (for example, Ended OK), click the button in the Status field. This displays the Status Selection dialog box.
By default, all check boxes are selected, and therefore loaded. Clear the checks for the options that should not be loaded.
NOTE
If no boxes are selected, all options are loaded.
To select all checkboxes, click To clear all checks, click .
Task Type Selection dialog box Filtering by Task Type To dynamically filter by task type (for example, Job or Started Task), click TaskType, which displays the Task Type Selection dialog box.
By default, all checkboxes are selected, and therefore loaded. Clear the check for the options that should not be loaded.
Chapter 2
143
NOTE
If no boxes are selected, all options are loaded.
To select all checkboxes, click To clear all checkboxes, click .
NOTE
Task type for MVS jobs can correspond to the following fields of Unix jobs: Task Type, Cyclic and Emergency. To correctly filter on certain task types for MVS jobs, you must specify the desired states (for example, Cyclic and/or Critical) along with the desired task type. For example, to filter for Cyclic Jobs, select Cyclic Only in the main dialog box and Job in the Task Type dialog box.
Saving dynamic filters (filter presets) for private use

Saved dynamic filters can be used again at a later time. Only users with access to the computer on which these filter presets are saved can access these filters.
EXAMPLE
If you generally view problematic payroll jobs whose names begin with the prefix PAY, you can define a dynamic filter called PAYROLL_NOTOK that filters on the job name PAY* and status NOTOK.
Dynamic filter definitions are stored locally, each in its own file. The default storage location is under the user profile directory. The default location of dynamic filters, as well as the sort order of the list of dynamic filters, can be configured in the Options dialog box (see Configuring how dynamic filters are saved on page 145).
To save a dynamic filter as a preset: 1 Open the Dynamic Filter dialog box, as described under Accessing the Dynamic
Filter Definition dialog box on page 140. Notice the topmost field of the Dynamic Filter dialog box, which is a selection field called Filter Presets.
2 In the Dynamic Filter dialog box, enter the values to be included in the dynamic
filter.
144
TIP
Before filling in the fields, you can click Clear at the bottom of the Dynamic Filter dialog box to clear all values.
3 Enter the name for the dynamic filter in the Filter Presets field, and click
save.
to
To display (and optionally modify) a filter preset 1 Open the Dynamic Filter dialog box, as described under Accessing the Dynamic
Filter Definition dialog box on page 140.
2 Select the name of the dynamic filter in the Filter Presets field. 3 To modify the criteria of the filter, make the desired changes and click To display a ViewPoint using a filter preset 1 Open the Dynamic Filter dialog box, as described under Accessing the Dynamic
Filter Definition dialog box on page 140. to save.
2 Select the name of the dynamic filter in the Filter Presets field. 3 Click OK. The ViewPoint is displayed according to the selected filter. To delete a saved dynamic filter 1 Select the name of the filter in the Filter Presets field. 2 Click
to delete.
Configuring how dynamic filters are saved

The following characteristics can be configured:
Location at which dynamic filters are saved. By default, dynamic filters are stored in <user_profile>\Application Data\CONTROL-MEM\Presets.) The order in which dynamic filters are listed in the Filter Presets field. By default, filters are sorted alphabetically.
Chapter 2
145
To configure dynamic filter characteristics: 1 Display the Environment-General panel of the CONTROL-M/Desktop Options
dialog box (using the Tools => Options menu option).
Configuration changes for dynamic filters are made in the Filter Presets area of this panel.
2 To change the location to which dynamic filters are saved, browse to the desired
location in the Preset Location field.
3 To change the sort order of the listed dynamic filters, check or clear the Sort
Presets by name checkbox. When not sorted by name, dynamic filters are sorted by the last modified date/time value.
4 Click OK.
Creating and modifying global filters

The ViewPoint Manager can be used to create new global filters or modify existing ones. Similar to dynamic filters, global filters determine which jobs are displayed in the ViewPoint. However, global filters are accessible by all users. Filter criteria can be specified according to job processing parameter values, job status (for example, Ended OK) and state (for example, Held).
146
NOTE
A ViewPoints global filter can be changed temporarily at any time during a CONTROL-M/Enterprise Manager session by selecting a different global filter from the Filter box on the toolbar. This changes the filter criteria for the current session only.
To create a new global filter: 1 Select the word Filters or the name of any global filter in the ViewPoint Tree in the
ViewPoint Manager window.
NOTE
If the global filter item is selected from a hierarchical ViewPoint branch of the tree, the new filter will not replace the selected item. To replace the original filter with the new filter, use the ViewPoint Properties window to select the new filter after it has been defined in the system.
2 Click New, or right-click and choose New from the menu.

The following window is displayed.
3 Specify a name for the new global filter and click OK.
Chapter 2
147
The Filter Definition window is displayed. Figure 36 Filter Definition window for defining global filters
4 Enter a description for the global filter. This field is optional. 5 Define selection criteria for the global filter, as described below. 6 Click OK to save the new global filter. To edit an existing global filter: 1 Select the global filter from the ViewPoint Tree and click Edit
-orright-click the global filter and choose Edit from the menu -orDouble-click the global filter in the ViewPoint Tree.
148
NOTE
Dynamic filters can be defined in the ViewPoint Tree by selecting <dynamic filter>.
The Filter Definition window is displayed.
2 Modify the global filter description and criteria as described below. 3 Click OK to save the modified settings. To delete an existing filter: 1 Select the global filter from the ViewPoint Tree. NOTE
Global filters cannot be deleted from a hierarchical ViewPoint branch in the ViewPoint Tree.
2 Click Delete, or right-click and choose Delete from the menu. A Confirmation
window is displayed.
3 Click OK. Defining selection criteria for the global filter

The bottom of the Filter Definition window contains an Edit table in which combinations of fields, operators and values can be specified. These combinations act as selection criteria for defining the filter. The field values are compared against the parameters in job processing definitions (for example, Application, Group, Cyclic, and so on) or against the jobs status (for example, Ended OK) or state (for example, Held) to determine if the job should be included in the filter. The filter criteria are listed on page 127. For a description of these parameters, see the CONTROL-M Job Parameter and Variable Reference Guide. For a description of job status and states, see Understanding the FlowDiagram and its components on page 81. The Edit table, Include In Filter and Exclude From Filter lists are the same as in the Collection Definition window, described under Creating and modifying collections on page 133.
Chapter 2
149
Creating and modifying hierarchies
Example
The following filter criteria include only jobs that meet both of the following criteria:

Job ended OK. Job belongs to a group whose name begins with GRP5. Filter Definition window Detailed
Figure 37

The ViewPoint Manager is also used to create a new hierarchy or modify an existing one. A hierarchy defines how the selected jobs are displayed. The criteria available for hierarchy levels are the parameters in job processing definitions (for example, Application, Group, Cyclic, etc.), job status (for example, Ended OK) and job state (for example, Held). The maximum number of hierarchy levels is five. The default hierarchy is CONTROL-M; Application; Group Name. For a complete description and an example of a hierarchical structure, see Chapter 1, CONTROL-M/EM basics.
150
To create a new hierarchy: 1 Select the word Hierarchies or the name of any hierarchy in the ViewPoint Tree. NOTE
If the hierarchy item is selected from a hierarchical ViewPoint branch of the tree, the new hierarchy will not replace the selected item. To replace the original hierarchy with the new hierarchy, use the ViewPoint Properties window to select the new hierarchy after it has been defined in the system.
2 Click New, or right-click and choose New from the menu. The following dialog box
is displayed.
3 Specify a name for the new hierarchy and click OK.

The Hierarchy Definition window is displayed. Figure 38 Hierarchy Definition window
4 Enter a description for the hierarchy. This field is optional.
Chapter 2
151
5 Select criteria for each level of the hierarchy from the lists.
For a description of these parameters, see the CONTROL-M Job Parameter and Variable Reference Guide. For a description of job status and states, see Chapter 2, Viewing the production environment.
6 Click Default Levels to return to the default hierarchy. 7 Click Reset Levels to clear fields and reset all levels. 8 Click OK to save the new hierarchy definition. To edit an existing hierarchy: 1 Select the hierarchy from the ViewPoint Tree and click the Edit button, or select the
hierarchy from the ViewPoint Tree, right-click and choose Edit from the menu. -orDouble-click the hierarchy in the ViewPoint Tree. The Hierarchy Definition window is displayed.
2 Modify the description and levels of the hierarchy. 3 Click OK to save the modified settings. To delete an existing hierarchy:
NOTE
Hierarchies cannot be deleted from a hierarchical ViewPoints branch in the ViewPoint Tree.
1 Select the hierarchy from the ViewPoint Tree. 2 Click Delete, or right-click the hierarchy and choose Delete from the menu. A
Confirmation window is displayed.
3 Click OK.
152
Printing the production environment
Printing the production environment

Printing a FlowDiagram enables you to print the production flow on paper. The printed pages are labelled so that you can easily assemble the pages side-by-side in the correct order, in a poster-like format. The printout is generated to match the FlowDiagram as it is currently displayed. For example, the resolution of the printout is determined by the resolution on your screen. You can adjust the resolution, and subsequently the amount of information printed on each sheet of paper, by zooming in or zooming out of the FlowDiagram. The printout can also include an index of all the nodes displayed in the production flow. The index is printed as the last page, after the graphical representation of the production flow. The following topics are described:

Previewing a FlowDiagram Working with the Print Preview window Adjusting print settings Printing the FlowDiagram
Previewing a FlowDiagram
Before printing, preview the production flow to make sure it will print as desired.
To Preview the FlowDiagram 1 Display the FlowDiagram you want to print. 2 Choose File => Print Preview. The Print Preview window is displayed, displaying a
graphical representation of how the FlowDiagram will print.
Chapter 2
153
Working with the Print Preview window
Figure 39
Print Preview window example

Rulers
Rulers are located on the left and top areas of the Print Preview window. The marks on the rulers indicate relative distance, not inches or centimeters. Use the marks to locate specific nodes. The rulers can also appear on the FlowDiagram printout. Columns are labelled alphabetically from right to left, and column numbering begins with A. Rows are labelled numerically from top to bottom, and row numbering begins with 0.
154
Pages are labelled:
alphabetically in the order they should be assembled horizontally (A, B, C, and so on) numerically in the order they should be assembled vertically (0, 1, 2, 3, and so on)
EXAMPLE

B.A corresponds to the first column on the second page horizontally. 3.2 corresponds to the second row on the third page vertically.
Status bar
The Print Preview window status bar provides additional information to aid in navigating the window. Table 24
Measure Pages of diagram pages index pages
Status bar information

Description Page(s) currently displayed Total number of pages Number of pages in the FlowDiagram Number of pages in the index
Available actions
From the Print Preview window, you can perform any of the following actions. Table 25
Click... File => Print Setup Print... Next Page Prev Page Two Page / One Page Zoom In Zoom Out Close
Print Preview actions

To... Change settings before printing. For more information, see Adjusting print settings on page 158. Open the Print window and print the FlowDiagram. For more information, see Printing the FlowDiagram on page 159. Display the page(s) after the currently displayed page(s). Display the page(s) preceding the currently displayed page(s). Toggle between a one-page view and a two-page view. Display the current page(s) at a larger magnification. Display the current page(s) at a smaller magnification. Close the Print Preview window and returns to the main CONTROL-M/EM window.
Chapter 2
155
FlowDiagram Index
An index describing the contents of the current FlowDiagram can be displayed in the Print Preview window. When printing the FlowDiagram, the index can be printed also. The index display can be toggled on and off using the Index Table option from the Print Setup dialog box (File => Print Setup). The first line of the index summarizes the number of nodes, columns and rows in the FlowDiagram. Figure 40 illustrates a sample index. Table 26 describes the columns of the index. Figure 40 Sample Index
Table 26
Column
Index columns (Part 1 of 2)

Description The job name of the node. Type of the node (for example, Application, Data Center, Job). Full path indicating where the node is displayed in the FlowDiagram hierarchy.
Node Name Node Type Node Hierarchy
156
Table 26
Column Column
Index columns (Part 2 of 2)

Description The column of the FlowDiagram in which the node is displayed. Column numbering begins with A, and is displayed in the following format: x.y x is a letter representing the current page in the order the pages should be assembled horizontally. y is a letter representing the current column on the page. Example: B.A corresponds to the first column on the second page horizontally.
Row
The row of the draft in which the node is displayed. Row numbering begins at 0, and is displayed in the following format. m.n m is a number representing the current page in the order the pages should be assembled vertically. n is a number representing the current row on the page. Example: 3.2 corresponds to the second row on the third page vertically.
To sort the index table in a different order, use the Sort Order field in the Print Setup dialog box.
Chapter 2
157
Adjusting print settings
Adjusting print settings

1 Display the draft. 2 Choose File => Print Setup. The Print Setup window is displayed.
3 Change settings as desired. Settings for printing a FlowDiagram are in Table 27. 4 Click OK.
Table 27
Parameter Ruler Index table Sort order Zoom Page Footer
FlowDiagram-specific print settings

Description Flag for printing the ruler at the top and the left side of the FlowDiagram. Flag for printing the index at the end of the FlowDiagram. The index can only be printed if rulers are printed. Order for sorting the index (by node name, type, column, row, and hierarchy). Screen magnification percentage or flag to use same zoom factor as display. If the page footer should be printed.
Page Header If the page header should be printed.
158
Printing the FlowDiagram

The Print function divides the area contained in the FlowDiagram into pages. Each page corresponds to part of the diagram that is displayed on your monitor.
NOTE
Settings which will affect how the FlowDiagram itself is displayed are disabled.
To print the entire FlowDiagram 1 Display the FlowDiagram. 2 Choose File => Print to display the Print window and click OK. To print selected pages of the FlowDiagram 1 Display the FlowDiagram. 2 Choose File => Print to display the Print window. 3 In the Print window, select the Pages option in the Print Range section of the Print
window.
4 In the from and to text boxes, enter numbers of the first and last pages in the range
of pages you wish to print and click OK.
Chapter 2
159
160
Chapter
Defining a production environment: Introduction to CONTROL-M/Desktop

3
Jobs managed by CONTROL-M are handled according to parameters that are specified in job processing definitions. These definitions are created using CONTROL-M/Desktop and are stored in scheduling tables (job directories) according to various criteria that you determine. For example, jobs that generally run together (concurrently or in sequence) should be placed in the same Scheduling table. In each CONTROL-M installation, the New Day procedure at the beginning of each working day, and User Daily jobs during the day review jobs in specified Scheduling tables and determine if they can be submitted on the current day. For more information about job ordering, see Ordering and forcing jobs or scheduling tables on page 167 and New Day processing on page 43. Table 28 Product
CONTROL-M/ Desktop CONTROL-M/ Desktop CONTROL-M/ Desktop CONTROL-M/ Desktop CONTROL-M/EM
Overview of defining and tracking jobs and scheduling tables Task Reference
1. Define job processing definitions for jobs CONTROL-M/Desktop User Guide that typically run at the same time and associate them with a scheduling table. 2. Write the scheduling table to CONTROL-M/EM 3. Upload the scheduling table to CONTROL-M 4. Order or force the scheduling table 5. Monitor progress of the jobs as they are ordered, as they run, and as they finish. CONTROL-M/Desktop User Guide CONTROL-M/Desktop User Guide CONTROL-M/Desktop User Guide CONTROL-M/Enterprise Manager User Guide
Chapter 3
161
Defining job processing definitions in CONTROL-M/Desktop
Defining job processing definitions in CONTROL-M/Desktop

The basic process of job definition is described below. For detailed information about this process, see the CONTROL-M/Desktop User Guide.
1 Choose Tools => CONTROL-M/Desktop in the CONTROL-M/EM window to

start CONTROL-M/Desktop.
2 Either create new scheduling tables and job processing definitions, or modify
existing ones by loading definitions into CONTROL-M/Desktop using the following steps:
A Choose File => Load jobs from CONTROL-M/EM. B Enter filter criteria to help locate the relevant data center, scheduling tables, and
jobs.
C Select the scheduling tables and job processing definitions to load. D Select either online or local mode. E Click Load. The jobs are loaded into the current CONTROL-M/Desktop draft. 3 Choose Edit => Job => New Job for a new job or double-click an existing job to
display the Job Editing form to create or modify the job processing parameters.
4 When you have finished modifying the jobs and scheduling tables: A If definitions were loaded to CONTROL-M/Desktop in local mode, choose Edit
=> Scheduling Tables => Write to CONTROL-M/EM to save the definitions to the CONTROL-M/EM database.
B In the Scheduling Table Manager (accessed using the Edit => Scheduling
Tables => Scheduling Table Manager option), select the scheduling tables and click Upload to save the definitions to the CONTROL-M database.
162
Creating many jobs using a job template in CONTROL-M/Desktop
Creating many jobs using a job template in CONTROL-M/Desktop

CONTROL-M/Desktop includes a mass job creation facility that uses job templates (called skeletons) to set default parameters for job created using that template. The basic steps are provided below. For more information, see the CONTROL-M/Desktop User Guide.
NOTE
The mass job creation facility is not available when definitions were loaded into CONTROL-M/Desktop in online mode.
1 Use the Mass Job Creation and Skeleton facilities to create multiple job processing
definitions.
2 Use the Job Editing form to modify the new job processing parameters as
necessary.
3 Use the FlowDiagram View in the CONTROL-M/Desktop window to create

dependencies between jobs.
4 Upon completion, choose Edit => Scheduling Tables => Write to

CONTROL-M/EM. Upon completion of the changes to scheduling tables or calendars, they should be uploaded to the appropriate CONTROL-M installations to make them available to CONTROL-M for scheduling jobs. Use the Scheduling Table Manager and Calendar Manager for the upload process.
Synchronizing the tables in CONTROL-M/EM and CONTROL-M/Server databases

A separate copy of each scheduling table and calendar resides in two locations:
In the CONTROL-M/EM database, where it is available to the user for defining and viewing job processing definitions and calendars. In the CONTROL-M/Server database in the indicated CONTROL-M installation, where it is always available to CONTROL-M for scheduling jobs.
Chapter 3
163
Synchronizing the tables in CONTROL-M/EM and CONTROL-M/Server databases
CONTROL-M/Desktop can be used to modify scheduling tables and calendar definitions in the CONTROL-M/EM database, even when there is no communication between the CONTROL-M/EM workstation and the CONTROL-M installation. However, for changes become effective, you must upload (copy) the table to the CONTROL-M/Server database in the appropriate CONTROL-M installation. Similarly, a newly-defined table must be uploaded to the CONTROL-M installation before it can be used by CONTROL-M.
NOTE
Downloading scheduling tables and calendars is a user-initiated manual operation, not to be confused with downloading the Active (production) environment as described in other chapters of this guide. The term table in the following explanation refers to scheduling tables and calendars.
CONTROL-M/EM uses the following methods to ensure synchronization between scheduling tables and calendars in CONTROL-M/EM and each CONTROL-M installation:
When you create or modify a table in the CONTROL-M/EM database, the Modified field for that table (appearing in the Scheduling Table Manager and Calendar Manager windows) is set to Yes to signify that the version of the table in the CONTROL-M/EM database is later than the version (if any) in the CONTROL-M/Server database. When you upload the table to the CONTROL-M/Server database, the Modified field is set to No, signifying that the table is now identical in the two databases. When you upload a table from the CONTROL-M/EM database to the CONTROL-M/Server database, CONTROL-M/EM verifies that the table being overwritten (if any) in the CONTROL-M/Server database is an earlier version than the table replacing it. If you download a table from the CONTROL-M/Server database to the CONTROL-M/EM database, CONTROL-M/EM verifies that the Modified field for that table is not set to Yes. If it is, CONTROL-M/EM requests confirmation before performing the download. If you confirm the action, the download is performed and the Modified field is set to No. When you delete a table from the CONTROL-M/EM and CONTROL-M/Server databases, CONTROL-M/EM verifies that the same version of the table exists in the two databases or that the version in the CONTROL-M/EM database is later than the version in the CONTROL-M/Server database. If the version of a table in the CONTROL-M/EM database is earlier than the version of the same table in the CONTROL-M/Server database, CONTROL-M/EM does not allow you to perform upload, delete, order or force actions on the table.
164
Uploading and downloading scheduling tables to/from the CONTROL-M/Server database
Uploading and downloading scheduling tables to/from the CONTROL-M/Server database

After making changes to job processing definitions, the scheduling tables containing those definitions must be uploaded to the CONTROL-M/Server database in the appropriate CONTROL-M installation so that the changes can be applied to jobs handled by that CONTROL-M. Similarly, a newly-defined scheduling table must be uploaded before it can be used by CONTROL-M. Upload and download operations are performed using the Scheduling Table Manager in CONTROL-M/Desktop. For more information, see the CONTROL-M/Desktop User Guide.
NOTE
Normally, there is no need to download a table from the CONTROL-M. However, you may choose to download a table to the CONTROL-M/EM database in order to overwrite changes made in CONTROL-M/Desktop that you have decided to reject.
For CONTROL-M installations on an MVS platform:

The Download operation in the CONTROL-M/Desktop Scheduling Table Manager is used to copy tables originally defined using the CONTROL-M Online facility, from CONTROL-M/Desktop, to the CONTROL-M/EM database. When a CONTROL-M for OS/390 and z/OS installation is first connected to a CONTROL-M/EM workstation, this option can be used to copy all existing scheduling tables and calendars to the CONTROL-M/EM database. BMC Software recommends that when an MVS CONTROL-M is connected to CONTROL-M/EM, maintenance of scheduling tables and calendars be performed by using CONTROL-M/EM.
Chapter 3
165
Other handling of scheduling tables in CONTROL-M/Desktop
Other handling of scheduling tables in CONTROL-M/Desktop

The Scheduling Table Manager is a component of CONTROL-M/Desktop and is used to:

View a list of scheduling tables Modify or delete an existing scheduling table, or create a new scheduling table Force or order a table Upload new or modified tables to the CONTROL-M/Server database in a specified CONTROL-M installation Download tables from a CONTROL-M/Server database to the CONTROL-M/EM database The Scheduling Table Manager window
Figure 41
Uploading and downloading scheduling tables is discussed on page 165. For data about the Scheduling Table Manager, see the CONTROL-M/Desktop User Guide.
166
Ordering and forcing jobs or scheduling tables

Typically, jobs are placed in the Active Jobs file when the New Day procedure or User Daily job scans job processing definitions. However, you can also manually place jobs in the Active Jobs file by using the Order or Force options.
When you order a job, CONTROL-M examines the jobs scheduling criteria. If the criteria are satisfied, the job is placed in the Active Jobs file. The Order option is useful for newly-defined or modified jobs that did not exist or were not selected at the time the New Day or User Daily procedure was executed. When you force a job, CONTROL-M places the job in the Active Jobs file regardless of the jobs scheduling criteria.
Jobs can be ordered or forced in one of the following ways:
Using the Order/Force Jobs dialog box in CONTROL-M/EM for details, see To order or force jobs using the Order/Force Jobs dialog box: on page 168. Using the Scheduling Table Manager in CONTROL-M/Desktop for details, see the CONTROL-M/Desktop User Guide. Using the Command line utility (cli) for details, see the description of the cli utility in the CONTROL-M/EM Utility Guide.
The following rules apply for duplicate Job Names and Mem Names:

You can define duplicate Job Names in the same table. You can define duplicate Mem Names in the same table. If there are multiple Job Names in a table, you can order the entire table to place the jobs with the duplicate Job Names in the Active Jobs file. This can be executed from both CONTROL-M/EM and the CONTROL-M platform.
NOTE
You must have the appropriate privileges to order or force jobs and Scheduling tables. For more information about authorizations, see the CONTROL-M/Enterprise Manager Administrator Guide.
Chapter 3
167
To order or force jobs using the Order/Force Jobs dialog box: 1 Select Tools => Order/Force, or click
displayed (Figure 42). Figure 42 Order/Force Jobs dialog box . The Order/Force Jobs dialog box is
This dialog box allows the ordering or forcing of regular jobs on the current date.
NOTE
A dialog box with additional fields that provide greater flexibility is displayed if you click the Advanced button. For details, see Advanced Order/Force Jobs dialog box on page 170.
2 Select the desired CONTROL-M name and Table name in their respective fields.
For MVS, you can also select a Library name. The fields are described in Table 29. The list of jobs available in the selected scheduling table is displayed in the job list area. You can adjust the sort order of the job list by clicking on the column heading that you want to be the sort key.
3 To order or force the entire table, skip to the next step. Otherwise, select the
desired job in the job list. The name of the selected job will appear in the Job field. Alternatively, you can just type the name of the job in this field instead of selecting the name from the list.)
168
NOTE
Group Scheduling tables and jobs that were created using CONTROL-M do not appear in the dialog box if they were created after performance of the last update between CONTROL-M and the CONTROL-M/EM database. To order or force such a job, or to specify such a table, type its name in the appropriate (Job or Table) text box.
4 The default order/force date depends on the CONTROL-M version. For

CONTROL-M versions 6.0.0 and higher, the default date is the CONTROL-M ODAT; for versions prior to 6.0.0, the default date is the CONTROL-M/EM machine date. To assign the job a date other than the default, click the Advanced button and continue with Advanced Order/Force Jobs dialog box on page 170.
5 To add the job to a Group scheduling table in the Active Environment, click the
Advanced button and continue with Advanced Order/Force Jobs dialog box on page 170.
6 Click either Order or Force. 7 Repeat step 2 through step 6 for each job to be ordered or forced. When done, click
Close.
Fields of the Order/Force Jobs dialog box

Table 29 describes the fields of the Order/Force Jobs dialog box.
NOTE
Details of the job to be ordered or forced (table, job, and library) are not checked for accuracy when they are entered in the dialog box. If the specified values do not exist or are not accessible as entered, an error message is displayed when the order or force request is issued.
Chapter 3
169
Table 29
Field Table Library Job
Fields of the Order/Force Jobs dialog box

Description Name of the scheduling table to order or force, or name of the scheduling table containing the job to order/force. MVS: Name of the library (DSN) containing the scheduling table of the job. After the CONTROL-M installation and scheduling table are chosen, the jobs in the table are listed in the Job List area. When a job from the Job list is selected, its name is displayed in the Job field. A name can also be typed into this field. Notes Only one job can be entered at one time. Mask characters are supported. If this field is blank, all jobs in the specified table are ordered or forced. For most platforms, the job field represents the Job Name parameter. For MVS users, the job field represents the jobs Mem Name parameter.
CONTROL-M Name of the CONTROL-M in which to order or force the job.
Buttons of the Order/Force Jobs dialog box

Table 30 describes the buttons of the Order/Force Jobs dialog box. Table 30
Button Order Force Close Advanced
Buttons of the Order/Force Jobs dialog box

Description Requests that the specified job or table be ordered. A job will be placed in the Active Jobs file if its Scheduling criteria are satisfied. Forces the specified job or table. The job or table will be placed in the Active Jobs file regardless of its scheduling criteria. Closes the dialog box. Toggles between displaying and hiding the following additional fields entry areas at the bottom of the dialog box: Order/Force Into Group Odate
Advanced Order/Force Jobs dialog box

Figure 43 illustrates the Order/Force Jobs dialog box when the Advanced button has been pressed.
170
Figure 43
Advanced Order/Force Jobs dialog box
The Advanced dialog box is like the regular dialog box, except it has two field areas added at the bottom: Order/Force Into Group Odate These fields allow you to: add the job to a Group scheduling table in the Active Environment assign the job a date other than the default date The usage, fields and buttons of the regular dialog box are described in To order or force jobs using the Order/Force Jobs dialog box: on page 168. The advanced fields of the dialog box are described in Table 31.
To fill in the Advanced fields in the dialog box: 1 Ensure that the non-advanced fields in the dialog box are filled in. 2 To add the selected job to a Group scheduling table in the Active Environment: A Select the appropriate group scheduling table pointer (for example, New or
Recent) that identifies to which group scheduling table the job should be added. For details, see Table 31.
B To duplicate a job that already exists in the table, select the Duplicate check box. 3 To assign a different date than the default date to the job being ordered or forced,
click the button by the date selection field, and select the desired date.
Chapter 3
171
4 If a job runs under CONTROL-M for z/OS version 6.2.00 or later, you can ensure
that it does not run before the Odate by selecting Wait for Odate to run. If this check box is not selected, the job runs as soon as the execution criteria are satisfied.
5 When you have filled in all fields in the dialog box, click Order or Force to order or
force the job. Table 31
Field Order/ Force Into Group
Advanced fields of the Order/Force Jobs dialog box

Description Relevant only for jobs in a group scheduling table. Indicates if a job should be added to a group scheduling table in the Active Jobs file and, if so, to which one. MVS: You can force but not order individual jobs in a group scheduling table. Select one of the values below (additional fields are displayed for some values): New Place the ordered or forced job into a new group scheduling table in the Active Jobs file. MVS: The New option is not supported. Add the job to the group scheduling table that was most recently ordered. Forces the job without adding it to a Group scheduling table. Displays an ellipsis (...) button that allows you to select a Group scheduling table to which to add the job. Click the button to open the Select Active Group window from which you can select the group scheduling table. The Order ID of the group scheduling table is displayed in the Order ID text box. If this box is checked, a job will be added to the group scheduling table even if that same job already exists in that same group scheduling table. This setting applies only to one of the following selected values: Recent, or Order ID for a Selected Group Scheduling table.
You can only use the options below to force but not order an individual job. Recent Stand alone Selected
Duplicate
Odate
CONTROL-M date at the time the job is ordered. To specify a different date, select a date from the selection list. If the jobs Odate matches its scheduling criteria, the job is placed in the Active Jobs file.
The default order/force date depends on the CONTROL-M version. For versions prior to 6.0.0, the default date is the CONTROL-M/EM machine date. For CONTROL-M versions 6.0.0 and higher, the default date is the CONTROL-M ODAT.
Wait for If this box is checked, the job does not run before the Odate, even if all the Odate execution criteria of the job are satisfied. This option is only available for jobs to run running under CONTROL-M for z/OS version 6.2.00 or later.
172
Defining calendars in CONTROL-M/Desktop
Defining calendars in CONTROL-M/Desktop

Special calendar definitions are used by CONTROL-M to hold sets of scheduling dates that can be applied to job processing definitions, and optionally combined with additional scheduling parameters in the job processing definitions.

The dates in the calendar can be working days, accounting dates, holidays, etc. Any number of calendars can be defined, where each one corresponds to a different set of dates. The dates on which a job can be ordered are limited by the calendars named in the Scheduling parameters of the job processing definition (for example, Days Calendar). If no calendar is specified, the job is ordered solely on the basis of other Scheduling parameters (for example, Days, Months).
Calendars are defined and modified using the Calendar Manager and Calendar Definition windows in CONTROL-M/Desktop. Each newly created or modified calendar is saved in the CONTROL-M/EM database. The calendar must be uploaded to the CONTROL-M/Server database for it to be available to CONTROL-M. Uploading and downloading of calendars is performed in the same way as uploading and downloading Scheduling tables (see Uploading and downloading scheduling tables to/from the CONTROL-M/Server database on page 165). CONTROL-M uses the following types of calendars: Table 32
Regular
Calendar types
A regular calendar consists of a succession of dates, specifying when a job can or cannot be ordered. A job whose job processing definition points to a calendar in the Days Calendar and/or Week Days Calendar parameter is ordered based on the set of dates in that calendar. Other Scheduling parameters can be used in conjunction with a regular calendar to further control the dates on which the job is ordered. [MVS] A relative calendar is one which is intended for use in conjunction with another calendar. A relative calendar is combined (using the CONTROL-M IOABLCAL utility) with a regular calendar or with another relative calendar to generate a new regular calendar. The new calendar that results from this process is a combination of the two calendars input to the utility. For more information regarding relative calendars and examples of how the IOABLCAL utility is used, refer to the CONTROL-M for OS/390 and z/OS User Guide. A periodic calendar can be used to divide the year into working periods (that is, 13 periods, 20 periods, and so on), instead of into twelve months. Each period can be the same or different in length. Periods do not have to be specified using consecutive dates, and they can overlap. A periodic calendar is used in conjunction with the Days or Week Days parameters to specify on which dates a job should be ordered.
Calendar type Description
Relative
Periodic
Chapter 3
173
Calendar Manager
For examples of how calendars are used to schedule jobs, see the description of the Days Calendar parameter in the CONTROL-M Job Parameter and Variable Reference Guide. For examples of how calendars are used to schedule jobs under MVS, refer to the description of basic scheduling criteria in the CONTROL-M for OS/390 and z/OS User Guide.
Calendar Manager
Calendars are listed by name in the Calendar Manager window. This window is a component of CONTROL-M/Desktop and enables you to:
Delete existing calendars. Define new calendars and edit existing calendars. Upload calendars from the CONTROL-M/EM database to the CONTROL-M/Server database. Download calendars from the CONTROL-M/Server database to the CONTROL-M/EM database.
To open the Calendar Manager window, choose Edit => Calendars in CONTROL-M/Desktop. Figure 44 Calendar Manager window
For more information, see Chapter 8 of the CONTROL-M/Desktop User Guide.
174
Calendar Definition window

The Calendar Definition window enables you to define new calendars and edit existing calendars.
To open the Calendar Definition window: 1 Choose Edit => Calendars in CONTROL-M/Desktop. The Calendar Manager
window is displayed.
2 Click New or Update. The calendar definition window is displayed.

Figure 45 Calendar Definition Window
Chapter 3
175
176
Chapter
Managing job processing definitions

Each node appearing in the CONTROL-M/EM window can be used to access additional information about the element that it represents.
High-level nodes (CONTROL-M, group, or application) can be accessed for statistical data about the jobs under that node. Job nodes can be used to display a Job Editing form with information about all aspects of the job, and if necessary, to modify that information. Changes made using the job node are sent to the relevant CONTROL-M, where the changes are applied to the job in the Active Jobs file.
High-level node details

CONTROL-M, application, and group nodes are high-level nodes. You can request more details about any of these nodes by right-clicking the node, and choosing Status Summary from the popup menu.
NOTE
Nodes for group scheduling tables include functionality similar to job nodes. For more information about these special nodes, see Group scheduling tables on page 220.
To display high-level node details: 1 Right-click the desired node to display a pop-up menu. 2 Choose Status Summary. The Status Summary window is displayed.
Chapter 4
177
General panel
yes
NOTE
The General panel of the Status Summary window is displayed for all high-level nodes. The CONTROL-M panel is available only if displaying the properties of a CONTROL-M node.
General panel
Figure 46 Status Summary window General panel
Fields of the General panel (Table 33) provide job status summaries for the selected high-level node.
178
General panel
Table 33
Field Name Jobs
Fields of the General panel

Description Name of the high-level node. Number of jobs with a particular status (for example, Wait Condition, Executing, Ended Not OK). Each node status appears color coded on its own line with the following information:

# column - number of jobs with that status. % column - percentage of the total number of jobs with that status.
The color coding is used in the node title bar and in the vertical bars (histogram) displayed in the body of the high-level node. The color code alerts you to the most critical status of the jobs contained in the node. Color coding is explained in Job node operational status and state on page 86. The panel also provides the following totals of the summary information.
Wait Schedule - total number and percentage of jobs with any of the following Wait statuses: Wait Condition, Wait Resource, Wait User. TOTAL - total number and percentage of jobs used in the calculations. Percentages appearing in all status summary line are calculated against the total number of jobs in this line (the percentage in this line is always 100%). (# Scheduling Groups) - total number of groups used in the calculations.
Chapter 4
179
CONTROL-M panel
CONTROL-M panel
For CONTROL-M nodes, an additional panel is included in the Status Summary window. Figure 47 CONTROL-M Status Summary panel
The fields of the CONTROL-M panel are described in Table 34. Table 34
Field Name Platform CONTROL-M ver. Sync Refresh Needed
Node properties CONTROL-M panel

Description Name of the CONTROL-M. Type of CONTROL-M platform (for example, MVS, Unix). Version of CONTROL-M. Indicates if the current display is synchronized with the CONTROL-M Active Jobs file. Indicates if the Refresh Needed button in the CONTROL-M/EM window should be clicked to display recently forced or ordered jobs.
180
Job node details
Job node details

Details about specific jobs can be used for analyzing the jobs and managing the job scheduling flow. Job details are viewed and updated using the Job Editing form. Note that updated details will affect only the parameters of the job in the Active Jobs file in CONTROL-M. The original job processing definition cannot be changed from the CONTROL-M/EM window.
e
NOTE
To update details, hold the job before opening the Job Editing form, and free the job when you are finished. For more details regarding Hold and Free operations, refer to Job actions on page 204.
Use any of the following methods to display job details:

Double-click the job node. Select the job and choose Action => Properties. Right-click the job. Choose Properties from the popup menu.
The Job Editing form is displayed (see Figure 48). Figure 48 Job Editing form
Table 35 describes the panels of the Job Editing form.
Chapter 4
181
General panel
Table 35
Panel General Active Execution Conditions Resources Set Steps Post-proc
Panels of the Job Editing form

Description Parameters identifying the job and where it is located. Run time, scheduling and status information about the job. Parameters related to the execution of a job and processes that accompany the job's execution. In Conditions and Out Conditions defined for the entire group as well as conditions defined for the individual jobs. Quantitative and Control resources required for job submission. AutoEdit variables to be set whenever the job is submitted. Conditional post-processing instructions. Shout When and Sysout-handling post-processing instructions.
Each of these panels is described below. For a description of each parameter in the Job Editing form, see the CONTROL-M Job Parameter and Variable Reference Guide. Click OK on the bottom of the Job Editing form to update the job in the Active Jobs file of the appropriate CONTROL-M installation.
NOTE
Apostrophes are not supported in the Job Editing form. Do not include apostrophes in any values entered into this form.
General panel
The General panel indicates what the job does and where it is located, as well as other miscellaneous information.
NOTE
This panel may appear slightly different if the current job is for an application-specific job (for example, SAP or Oracle Applications), or if it is for CONTROL-M on an MVS platform. For more information about the different versions of the General panel, see the CONTROL-M/Desktop User Guide.
182
General panel
Figure 49
Job Editing form General panel
Table 36
Field Job Name File Name Path Over Lib Owner Author
Job Editing form General panel fields

Description Name of the job. Name of the file that contains the job script. Name of the path that contains the job script file. Name of the library/directory to use instead of the library/directory specified in the Mem Lib field. (Text) Owner (user ID) on whose behalf the job is executed. This parameter is used by the CONTROL-M security mechanism. CONTROL-M/EM user who defined the job. Note: This argument is used by the CONTROL-M security mechanism and, under certain circumstances, cannot be modified. For more information, see the Security chapter and the description of the AuthorSecurity system parameter in the CONTROL-M/Enterprise Manager Administrator Guide. Type of the job (task) to be performed by CONTROL-M. Valid values: Job, Detached Job, and Command. Name of the Scheduling table to which the job belongs. Name of the application to which the jobs group belongs. Name of the group to which the job belongs. Name of the member in which the documentation resides. This can be viewed using the Documentation option in the Action menu. Note: To access the documentation, the user must be defined and have authorization on the CONTROL-M where the documentation resides.
Task Type Table Application Group Doc Mem
CONTROL-M Name of the CONTROL-M to which the job belongs.
Chapter 4
183
General panel (for MVS)
Table 36
Field Doc Lib
Job Editing form General panel fields

Description Name of a library or directory containing the documentation file. Note: To access the documentation, the user must be defined and have authorization on the CONTROL-M where the documentation resides.
Time Zone Command Description
Global time zone used to calculate the interval for time-related conditions. Text of the command line to be submitted for the job when the Task Type parameter is Command. Description of the job.
General panel (for MVS)

The General panel indicates what the job does and where it is located, as well as other miscellaneous parameters.
NOTE
Users of CONTROL-M for z/OS version 6.2.00 or higher may have parameters available that are not shown in Figure 50. For more information about these parameters, see Table 37.
Figure 50
Job Editing form General panel (for MVS)
184
Active panel
Table 37
Field
Job Editing form General panel fields (for MVS)

Description Name of the file that contains the job script. Name of the path that contains the job script file. Name of the library/directory to use instead of the library/directory specified in the Mem Lib field. (Text) Owner (user ID) on whose behalf the job is executed. This parameter is used by the CONTROL-M security mechanism. Type of the job (task) to be performed by CONTROL-M. Valid values: Job and Started Task. Name of the Scheduling table to which the job belongs. Name of the library that contains the scheduling table. Note: This field is displayed only for MVS jobs. Name of the application to which the jobs group belongs. Name of the group to which the job belongs. Name of the CONTROL-M to which the job belongs. Name of the member in which the documentation resides. This can be viewed using the Documentation option in the Action menu. Name of a library or directory containing the documentation file. Indicates the global time zone used to calculate the interval for time-related conditions. Description of the job.
Mem Name Mem Lib Over Lib Owner Task Type Scheduling Table Name Scheduling Table Lib Application Group CONTROL-M Doc Mem Doc Lib Time Zone Description
Use In-Stream JCL Whether CONTROL-M for z/OS submits the JCL stream from the job definition, overriding the MEMLIB parameter value. Only displayed for jobs running in CONTROL-M for z/OS version 6.2.00 or later.
Active panel
The Active panel indicates run time, scheduling, and status information about the job.
NOTE
This panel does not appear in the CONTROL-M/Desktop version of the Job Editing form. It is relevant only to jobs that have been scheduled (jobs in the Active Jobs file).
Users of CONTROL-M for z/OS version 6.2.00 or higher may have parameters available that are not shown in Figure 51. For more information on these parameters, see Table 38.
Chapter 4
185
Active panel
Figure 51
Job Editing form Active panel for MVS jobs
Table 38
Field
Job Editing form fields of the Active Panel for MVS jobs
Description Original scheduling date of the job. Time at which the job must start executing. + num Days The day on which the job must start executing. The + num Days subparameter is relevant only for jobs running in CONTROL-M for z/OS version 6.2.00 or later.
Current Status Status (such as Ended OK) of the job. Order Date Due In
Due Out
Time by which the job must finish executing. + num Days The day by which the job must finish executing. The + num Days subparameter is relevant only for jobs running in CONTROL-M for z/OS version 6.2.00 or later.
Elapse Next Time
Length of time (in minutes) that the job is expected to run. Indicates the next expected submission time for the job. For reruns or cyclic jobs that use the Interval option. For MVS jobs, only the time can be specified. For all other jobs, the time and the date can be specified. 1 indicates that the job was sent for execution to a computer that is connected to CONTROL-M through NJE (the node does not share a spool with CONTROL-M). Note: Normally, the value in this field should not be changed. However, beginning with CONTROL-M/EM version 6.1.03, it is possible to update this field. For example, if an NJE job was purged from the spool on a remote node, its status remains Executing. By removing the NJE indicator, you can change NJE job status to Disappeared. Node ID of the NJE terminal. Number of times CONTROL-M has looked for the job.
NJE
NJE Node Search count
Rerun counter Number of times the job has been rerun.
186
Active panel
Table 38
Field Logical Partition Hold Deleted Restart Average Run Time Standard Deviation Statistics period From Step To Step From Proc To Proc Job Name Order ID Job ID Start Time End Time
Job Editing form fields of the Active Panel for MVS jobs
Description For CONTROL-M for z/OS version 6.2.00 and later: Logical partition where the job is running. Indicates if job is held. Indicates if job is deleted. Indicates if job has been restarted. Average time (in minutes) for the job to run. The field displays the runtime statistic generated by the latest run of utility CTMJSA (which generates a statistic based on the last successful runs of the job). Standard deviation from the average runtime. This statistic is compiled from the last successful runs of the job. MVS only: 1-character identifier of the actual days in the CONTROL-M periodic calendar for which statistics relating to the job are calculated. MVS only with CONTROL-M/Restart: Step from which to rerun the job. MVS only with CONTROL-M/Restart: Step until which to rerun the job. MVS only with CONTROL-M/Restart: Procedure step from which to rerun the job. MVS only with CONTROL-M/Restart: Procedure step until which to rerun the job. MVS only: Name of the job. Unique job order ID in CONTROL-M. ID assigned to the job by the operating system. Date and time the job began executing. Date and time the job finished executing.
Chapter 4
187
Execution panel
Execution panel
The Execution panel of the Job Editing form includes parameters that are related to the execution of a job and processes that accompany the jobs execution. The panel style is different for MVS jobs. This panel is displayed on page 190. Figure 52 Job Editing form Execution panel
188
Execution panel
Table 39
Field Cyclic Critical
Job Editing form Execution panel fields

Description If selected, indicates that the current job is cyclic (it should be rerun at specified intervals). When selected, resources for the job are reserved exclusively for that job as they become available. When all necessary resources are available, the job is executed. Note: This parameter is not available for MVS jobs.
Priority Rerun
Internal job priority under CONTROL-M. Parameters that control the rerun of a cyclic job or the rerun of a job as the result of the execution of a Do Rerun parameter. The following parameters are used to control reruns: Interval Specifies the length of time to wait between reruns of a job or between cyclic runs of a job. The default setting is 0. Indicates if time for the next run of a cyclic job should be calculated from the beginning or from the end of the previous run. Amount of time (minutes) to wait between reruns, or between cycles of a cyclic job. Default: 0. Specifies the maximum number of reruns that can be performed for a job. The default setting is 0. Specifies a unit of time for the numerical value indicated by the Interval parameter. Valid values: Minutes (1-64800) Hours (1-1080) Days (1-45)
From
Maximum Units
Maxwait Time
Maximum number of days that the job can wait to be executed after its original scheduling date has passed. From and Until. The Job is executed at a time no earlier than a time specified by the From subparameter and will not be executed at a time later than that specified by the Until subparameter. Both subparameters are optional. Each subparameter may be used singly or together. Node ID of the host on which the job was most recently run. Note: This parameter is not available for MVS jobs.
Node ID
Node Group
Host name of the Agent platform or Node Group on which you want the job to run. This field can be configured. Note: This parameter is not available for MVS jobs.
Multi Agent
Specifies that job submission details be broadcast to all Agents within a specified node Group. All available Agents run an identical job, and each such job will have a unique Order ID.
Chapter 4
189
Execution panel
Figure 53
Job Editing form Execution panel for MVS
NOTE
Users of CONTROL-M for z/OS version 6.2.00 or higher may have parameters available that are not shown in Figure 53. For information about these parameters, see Table 40.
Table 40
Field PreventNCT2 Confirm Cyclic
Job Editing form Execution panel for MVS fields (Part 1 of 2)

Description MVS only: Indicates if CONTROL-M/Restart (if installed) should prevent NOT CATLGD 2 errors during job executions that are not restarts. If selected, indicates that the job will not be run until the administrator confirms that the should be submitted. If selected, indicates that the current job is cyclic (it should be rerun at specified intervals).
190
Execution panel
Table 40
Field Rerun
Job Editing form Execution panel for MVS fields (Part 2 of 2)

Description Parameters that control the rerun of a cyclic job or the rerun of a job as the result of the execution of a Do Rerun parameter. The following parameters are used to control reruns: Interval From Specifies the length of time to wait between reruns of a job or between cyclic runs of a job. The default setting is 0. Indicates if time for the next run of a cyclic job should be calculated from the beginning or from the end of the previous run, or from the target (TRGT) time (which calculates from when the current run was scheduled). Amount of time (minutes) to wait between reruns, or between cycles of a cyclic job. Default: 0.
Maximum Specifies the maximum number of reruns that can be performed for a job. The default setting is 0. Member Units MVS only: Name of member to be submitted in case of rerun. Specifies a unit of time for the numerical value indicated by the Interval parameter. Valid values: Minutes (1-64800) Hours (1-1080) Days (1-45)
Maxwait Category Priority Emergency Time
Maximum number of days that the job can wait to be executed after its original scheduling date has passed. MVS only: Name of a CONTROL-D Report Decollating Mission category to be scheduled whenever the job is run. Internal job priority under CONTROL-M. MVS only: Indicates that the current job or started task is an emergency job or started task. From and Until. The Job is executed at a time no earlier than a time specified by the From subparameter and is not executed at a time later than that specified by the Until subparameter. Both subparameters are optional. Each subparameter may be used singly or together.
+ num days Number of days after the original scheduling date of the job during which execution of the job can begin (From + num days) or end (Until + num days). Scheduling Indicates the JES2 workload management scheduling environment that is Environment to be associated with the job. System Affinity Indicates the identity of the system in which the job must be initiated and executed (in JES2). Indicates the identity of the processor on which the job must execute (in JES3). Request NJE Node Specifies the node in the JES network on which the job is to execute.
Chapter 4
191
Conditions panel
Conditions panel
The Conditions panel describes prerequisite IN and OUT conditions. This panel contains two sections. IN conditions are defined in the left section; OUT conditions are defined in the right section.
NOTE
Figure 54
Job Editing form Conditions panel
After editing or adding a condition in this panel, click the check button condition to save the changes and/or add the condition to the list. The following buttons are available for each section of this panel:
Button Action Enter a new condition. Delete the selected condition. and Change the order of the list. Copy data. Paste data.
next to the
192
Conditions panel
Defining IN Conditions
The IN Condition Text line contains boxes for defining condition subparameters. Table 41
Condition Name Date
In Condition parameters
Description Name of the prerequisite condition. 4-character date reference for the condition. Valid values are:
date a 4-character date reference in mmdd or ddmm format (depending on the site standard) offset [Only for jobs running under CONTROL-M for z/OS version 6.2.00 or later]: + or - followed by a number from 0 through 999, indicating the number of days in the future (+), or in the past (-), relative to the actual order date ODAT original scheduling date PREV previous scheduling date NEXT next scheduling date **** / $$$$ any scheduling date
And/Or
Logical relationship between multiple conditions. [MVS] Parentheses Box. Use to clarify And/Or relationships.
Defining OUT Conditions

The following fields are used to define each Out condition.
Condition Name Date +/Description Name of the prerequisite condition. Date reference. Same as IN Condition. Indicates whether to add or delete the condition.
Chapter 4
193
Resources Panel
Resources Panel
The Resources panel is used to define Quantitative and Control resources. The panel contains two sections. Quantitative resources are defined in the left section; Control resources are defined in the right section.
NOTE
Figure 55
Job Editing form Resources panel
After editing or creating a resource, click the check button and/or add the resource to the list.
to save the changes
The following buttons are available for each section of this panel:
Button Action Enter a new resource. Delete the selected resource. and Change the order of the list. Copy data. Paste data.
194
Resources Panel
Defining Control Resources

The following fields are used to define Control resources:
Parameter Name Shared/Exclusive On Fail Description Name of the resource. Type of control required for the resource. Indicates whether to keep a Control resource tied to a job if the job does not end OK. Valid values: Release The resource is not kept tied to the job. Default. Keep The resource is kept tied to the job until one of the following occurs: the job ends OK the job is deleted the job is forced OK This parameter is available only for jobs running in CONTROL-M for z/OS version 6.2.00 or later.
Defining Quantitative Resources

The following fields are used to define Quantitative resources:
Parameter Name Quantity On Fail Description Name of the resource. (Text) Quantity of the resource required. (Text) Indicates whether to keep the resource tied to a job if the job does not end OK. Valid values: Keep the resource is kept tied to the job until one of the following occurs: the job ends OK the job is deleted the job is forced OK Release the resource is not kept tied to the job. Default. This parameter is available only for jobs running in CONTROL-M for z/OS version 6.2.00 or later. On OK Indicates whether to keep the resource tied to a job if the job ends OK. Valid values: Release The resource is not kept, and is returned to the total quantity available for other jobs. Default. Discard The resource is not reusable, meaning that the quantity of the resource is permanently removed from the total quantity available for other jobs. This parameter is available only for jobs running in CONTROL-M for z/OS version 6.2.00 or later.
Chapter 4
195
Set panel
Set panel
The Set panel is used to specify AutoEdit variables to be set up in the jobs script before job submission. Figure 56 Job Editing form Set panel
This panel contains a list of already-specified variables. Below this box is a Text line (corresponding to the AutoEdit Assignment parameter) used for specifying additional variables. When you select a variable in the list, its contents are displayed in the Text line. After editing or creating a variable, click the check button save the changes and/or add the variable to the list. The following buttons are available:
Button Action Enter a new variable. Delete the selected variable. and Change the order of the list. Copy data. Paste data.
next to the text line to
196
Steps panel
The following fields are used to define AutoEdit variables in the Set panel:
Parameter Name Value Description User-defined AutoEdit variable. It is not required to add the %% prefix. If omitted, it will automatically be added to the variable name. (Text) Either a single value (for example, 5) or an AutoEdit system variable or previously defined user-defined variable (for example, %%ODATE) provided it resolves to a single value. (Text)
Steps panel
The Steps panel indicates conditional post processing actions to be performed, depending on the outcome of specified statements.
NOTE
The Steps panel shown in Figure 57 is not for MVS jobs. For more information about the Steps panel for MVS, see Steps panel (for MVS) on page 199.
Figure 57
Job Editing form Steps panel
This panel is used to define On Statements and Do Statements. It contains a list of already-defined On/Do Statements. Below the list is the Text line for defining new On Statements. The line for defining new Do Statements is not displayed.
Chapter 4
197
Steps panel
To display the Do Statement line: 1 Click the DO button

at the side of the Step Codes section.
To display the On Statement line: 1 Click the ON button

.
After editing or creating an On/Do Statement, click the check button at the lower corner of the panel to save the changes and/or add the statements to the list. The following buttons are also available:
Button and Action Delete the selected statement. Change the order of the list. Copy data. Paste data.
On Statement definition line

This line is used to specifying statement/code criteria. The Text line provides individual boxes for defining subparameters. Table 42
Item Statement Code
On Statement Criteria
Description Character string that is matched to the jobs log statement records. Character string that is searched for in the jobs log error code.
Do Statement definition line

This line is used to define actions to be performed when the On statement criteria are satisfied. To display this line, click the DO button at the side of the Step Codes Criteria section. All available Do Statements and their subparameters are described in the CONTROL-M Job Parameter and Variable Reference Guide. After editing or creating each On statement or Do Statement, click the check button at the lower corner of the panel to save the changes and/or add the statements to the list.
198
Steps panel (for MVS)

The Steps panel indicates conditional post-processing actions to be performed, depending on the outcome of specified steps. Figure 58 Job Editing form Steps panel (for MVS jobs)
The various sections of this panel are described below.
Step range
This section is used to define a range of steps to be checked for specific outcomes. Specifying a step range eliminates the need to define separate On Step Code events and accompanying Do actions for each step in the range. The following buttons are available:
Button Action Enter a new step. Delete the selected step. and Change the order of the list. Copy data. Paste data.
Chapter 4
199
The following fields are used to specify On Step Range statements:

Parameter Name From Description Identifying name assigned to the specified step range. (Text) First step in the step range. This subparameter contains two separate boxes: In the left box, specify the PGM step name. (Text) In the right box, optionally specify the PROC step name. (Text) Last step in the step range. This subparameter contains two separate boxes: In the left box, specify the PGM step name. (Text) In the right box, optionally specify the PROC step name. (Text)
To
Click the check button range to the list.
next to the text line to save the changes and/or add the step
Step codes
This section is used to define On statements and Do Action statements. It contains a list of already-defined On/Do Action statements. Below the list is the Text line for defining new On statements. The line for defining new Do Action statements is not displayed.
To display the Do statement line: 1 Click the DO

button at the side of the Step Codes section.
To display the On statement line: 1 Click the ON

button.
After editing or creating an On/Do Action statement, click the check box at the corner of the Step Codes section to save the change or add the statement to the list. The following buttons are available for the Step Codes section:
Button and Action Delete the selected statement. Change the order of the list. Copy data. Paste data.
200
On statements
The following options are available for defining ON statements for MVS jobs: On Stmt On Sysout
On Stmt definition
Figure 59 shows a blank set of the fields that are displayed when the On Stmt button is selected. These fields are described briefly in Table 43. For more detailed information about these fields, see the CONTROL-M Job Parameter and Variable Reference Guide. Figure 59 On Stmt fields
Table 43
Parameter PGMST PROCST Codes And/Or
On Statement parameters
Description Name of the program step to be checked for the specified code criteria. Name of the procedure step, in which the program step is found. Codes for the indicated step which satisfy the criteria. Type in each code separately, and press Enter after each code. Option buttons that set the logical relationship between multiple On statements.
On Sysout definition
This definition shows a blank set of the fields that are displayed when the On Stmt button is selected. These fields are described in Table 44. For more information about these fields, see the CONTROL-M Job Parameter and Variable Reference Guide. Table 44
Parameter From Column
On Stmt parameters
Description A number from 001 through 132, indicating the column at which the search should start. If this field is blank, the value 001 is assumed. The value in this field must be lower than that in the To Column field. A number from 001 through 132, indicating the column at which the search should end. If this field is blank, the value 132 is assumed. The value in this field must be higher than that in the From Column field. Option buttons that set the logical relationship between multiple On statements.
Sysout Pattern A string of up to 40 characters.
To Column
And/Or
Chapter 4
201
PostProc panel

This line defines DO actions to perform when the step code criteria are satisfied. To display this line, press the DO button at the side of the Step Codes Criteria section. For more information about available Do parameters, see the CONTROL-M Job Parameter and Variable Reference Guide, and the job production parameters chapter in the CONTROL-M for OS/390 and z/OS User Guide. After editing or creating an On/Do Condition statement, click the check button at the corner of the Step Codes section to save changes or add the statement to the list.
PostProc panel
The PostProc panel describes actions to be performed when the job ends. Figure 60 Job Editing form PostProc panel
The panel is partitioned into the following sections:
Shout
This section describes messages to be sent (shouted) to various destinations on various occasions. Currently defined Shout statements are displayed. Fields below this list can be used to specify additional statements (or to edit a selected statement in the current list). For more information about Shout parameters, see the description of the Shout parameter in the CONTROL-M Job Parameter and Variable Reference Guide.
202
Undo and Redo in the Job Editing form
After editing or creating a Shout message, click the Check box to save the changes and/or add the message to the list. The following buttons are also available:
Button Action Enter a new message. Delete the selected message. and Change the order of the list. Copy data. Paste data.
Sysout handling
This section is used to specify the handling of the output (sysout) of the job when the job ends OK. For more information, see the description of the Sysout Handling parameter in the CONTROL-M Job Parameter and Variable Reference Guide.
Undo and Redo in the Job Editing form

During the editing process, actions in the Job Editing form can be undone or redone.
Ctrl+z undoes the most recent action. Each successive press of Ctrl+z undoes the action performed prior to the one that was most recently undone. Ctrl+y redoes the most recent action that was undone. Each successive Ctrl+y redoes the undo action that was performed prior to the most recently redone action.
If a number of actions have been undone and a new action is performed, you can no longer redo the undone actions. Data entry in all methods of the Job Editing form (described previously) can be undone or redone. The Undo/Redo feature can be toggled on and off, and the number of undo levels can be configured manually (the default is 100). These functions are located on the EnvironmentGeneral panel of the Options dialog box. For more information about the Options dialog box, see Chapter 10, Customization.
NOTE
Undo and redo are not confined to the page of the Job Editing form that is currently displayed. The undo and redo features automatically move among pages in the Job Editing form as dictated by the order of the undo list.
Chapter 4
203
Job actions
Job actions
Table 45 describes actions that be performed on jobs in a CONTROL-M/EM ViewPoint. These actions can be accessed using any of the following methods:

Job node menu. Action menu of the CONTROL-M/EM window. Job Action buttons on the ViewPoint toolbar. Not all actions have an associated icon.
NOTE
Job actions require that the CONTROL-M/EM user be defined and have proper authorization on the CONTROL-M where the job resides.
Table 45
Action Bypass Confirm Delete
Job actions
Description Specify criteria and resources to be ignored. [Only for jobs running under CONTROL-M for z/OS version 6.2.00 and later.] Confirm the job. Delete the job. View the jobs documentation. Edit the jobs JCL or job script statements. View the predecessors jobs and Group Scheduling table for a selected job or Group Scheduling table. Set the job status to OK. Set the job status to OK without performing the post-processing actions of the job. [Only for jobs running under CONTROL-M for z/OS version 6.2.00 and later.] Free the job. Hold the job. Terminate the job and its associated processes. View log messages for the job. [MVS] Reactivate post-processing for the selected job. Rerun the job. [MVS] Restart the job using CONTROL-M/Restart. View statistics of the jobs latest runs. Undelete the deleted job. View the jobs JCL or job script statements. Determine why the job has not yet been executed.
Documentation Edit JCL/Script Enhanced Why Force OK Force OK no Post Processing Free Hold Kill Log React Rerun Restart Statistics Undelete View JCL/Script Why
View Sysout List View the jobs Sysouts.
204
Bypass (MVS only)
Menu options can be disabled in specific situations. For example: Why option is disabled when the job is executing or has completed. Hold option is disabled when the job is already held. Confirm option is disabled when CONTROL-M/Restart is not active. All options (excluding the Properties option) are disabled when communication is temporarily not synchronized. When any one of these actions is selected, CONTROL-M/EM accesses and/or updates the relevant CONTROL-M installation database.
NOTE
Before updating a jobs details, you must Hold the job. After updating, you should Free the job.
If errors occur as a result of the action, the Job Action Report window is displayed. For instructions on how to use this window, see Handling Errors.
Bypass (MVS only)

NOTE
The Bypass option is only available for jobs running under CONTROL-M for z/OS version 6.2.00 and later.
Choosing Bypass from the Action menu opens a dialog box containing a list of options with a check box for each. The default for these check boxes is unchecked, but if some options were selected in a previous Bypass action, these settings are retained. The available options are described in Table 46. Table 46
Option Time Limit Quantitative Resources Control Resources Pipes JCL (Run as Dummy Job)
Bypass options
If checked, ... The job runs regardless of the Time From and Time Until parameter values. The job runs regardless of whether Quantitative resources specified in the job definition are available. The job runs regardless of whether Control resources specified in the job definition are available The job runs regardless of whether other jobs using the same Pipe as that specified in the definition of this job are ready to run. When the prerequisite criteria and conditions of the job are satisfied the job runs as a dummy job the status of the job is changed to ENDED OK only the job post-processing actions are performed
IN Conditions The job runs even if prerequisite IN conditions are not satisfied.
Chapter 4
205
Confirm
Confirm
Choose Confirm from the Action menu or job node popup menu, or click the Confirm button. When this option is chosen for a job with Wait User [pink] status, the job is confirmed and can run.
Delete
Choose Delete from the Action menu or job node popup menu, or click the Delete button. This option changes the state of the job and its appearance in the CONTROL-M/Enterprise Manager window as follows: Figure 61 Deleted Job
If the job has not yet started, it is prevented from running even after all submission criteria are satisfied. The job remains visible until after the next cleanup of the Active Jobs file by the New Day procedure or by a manual request If the job is currently executing, the Delete option is not available. If the job has completed executing, it cannot be manually rerun after it is deleted.
Documentation
Choosing Documentation from the Action menu or job node popup menu opens the Documentation window. This window enables you to view the documentation member (DOC MEM) of the selected job. Figure 62 Job Documentation window
206
Edit JCL/Script
Edit JCL/Script
Choose Edit JCL/Script from the Action menu, from the job node popup menu, or by clicking the Edit JCL/Script button. This option opens a window that in which you can edit the job script using a text editor and update the job script member in the relevant CONTROL-M installation.
NOTE
Lines of greater than 200 characters cannot be edited.
While editing the job script member, it is marked in the CONTROL-M as in use. This ensures that other users cannot edit the job script member while it is being edited. However, the job script member can still be viewed.
NOTE
If you want to edit job scripts for CONTROL-M on a Unix computer, you must be defined in the computers /etc/passwd file.
NOTE
The Edit JCL/Script action cannot be performed with SAP jobs.
Figure 63
Job Script window
Chapter 4
207
Enhanced Why
Enhanced Why
Selecting Enhanced Why from the Action menu or the job node popup menu displays the Enhanced Why dialog box. This feature enables you to display the predecessor jobs and Group Scheduling tables for a selected job or Group Scheduling table. For more information, see Enhanced Why on page 104.
Force OK
The Force OK option changes the status of the job to Ended OK and changes the color of the job node to green. It can be used for jobs with a status of Ended Not OK or for jobs in a Wait status (such as Wait Time, Wait Cond). You can activate Force OK from the Action menu, or from the job node popup menu of jobs that Ended Not OK.
NOTE
CONTROL-M for z/OS always performs the Force OK post processing actions, regardless of the default setting in the CTMPARM member.
Force OK no Post Processing

The Force OK no Post Processing option changes the status of the job to Ended OK and changes the color of the job node to green. Job post processing actions, however, are not performed. This option can be used for jobs with a status of Ended Not OK or for jobs in a Wait status (such as Wait Time, Wait Cond). You can activate the option from the Action menu, or from the job node popup menu of jobs that Ended Not OK.
NOTE
This option is available only for jobs running under CONTROL-M for z/OS version 6.2.00 and later.
Free
Choose the Free option from the Action menu, the job node popup menu, or by clicking the Free button. This option removes the padlock from the job node of Held job in the CONTROL-M/Enterprise Manager window. When freed by the user, the job resumes processing at whatever point it was stopped by the Hold option.
208
Hold
NOTE
Before updating the details of any job, you must Hold the job. After updating, you should Free the job so that it can continue processing.
Hold
Selecting Hold from the Action menu, the job node popup menu, or clicking the Hold button, changes the state of the job. In the CONTROL-M/Enterprise Manager window, a padlock is added to the job node (shown below).
If the job has not started to execute, it is prevented from executing even after all submission criteria are satisfied. The job remains in this state until released using the Free option (described below). Any job that is executing when held will remain with Executing status until it is freed. If the job has completed executing, it cannot be manually rerun until released by you via the Free option.
Kill
Choose Kill from the Action menu or from the job node popup menu. This option terminates a job that is currently running and its processes. The action is recorded in the job log.
NOTE
Killing a specific instance of a cyclic job does not affect subsequent runs of that job.
Chapter 4
209
Log
Log
Choose Log from the Action menu or the job node popup menu. This option displays the log of the specified job. The Job Log window enables you to view job records extracted from the CONTROL-M log in the CONTROL-M installation. Figure 64 Job Log window
React (MVS only)

Choose React from the Action menu or the job node popup menu. This reactivates post-processing for the selected job.
Rerun
Select Rerun from the Action menu or job node popup menu, or click the Rerun button. This option reruns the job.
Restart (MVS only)

Choose Restart from the Action menu or the job node popup menu. This option opens the Job Restart dialog box. In this dialog box, specify the procedure and/or program steps for the job restart. Optionally, you can also specify whether to perform abend code and condition code recapture and step adjustment, and the name of a member in the CONTROL-R PARM library that contains defaults to be applied to the restart.
210
Statistics
NOTE
Only uppercase letters can be used in this dialog box.
Figure 65
Job Restart dialog box
1 Enter the range of steps to be restarted. 2 Check any of the following tasks you want performed if necessary:

Recapture Abend Codes Recapture Cond Codes Perform Step Adjustment
3 If desired, specify the name of the member in the CONTROL-R PARM library that
contains processing defaults you want applied to the job.
4 Click OK.
Statistics
Choose Statistics from the Action menu or job node popup menu. This option opens a popup window containing the following job statistics:

Job ID. The Job ID of the job. Start Time. Time when the job began to run. End Time. Time when the job finished running. Elapsed. The jobs elapsed run time. CPU. CPU time used to process the job.
Chapter 4
211
Undelete
Undelete
Choose Undelete from the Action menu or from the job node popup menu of a job with Delete status. This option causes the job to revert to its appearance and state before the job was deleted.
NOTE
A job can be undeleted only if it still exists in the Active Jobs file (cleanup has not yet been performed since the job was deleted).
View JCL/Script
Choose View JCL/Script from the Action menu or job node popup menu, or click the View JCL/Script button. This option opens a window that allows you to view the job script statements. Figure 66 Job Script window
212
View Sysout List
View Sysout List

Choose Sysout from the Action menu or job node popup menu, or click the Sysout button. This option opens a window that displays a list of the jobs Sysout (output) information. Figure 67 Sysout Display
Select the output element to view and click OK.
NOTE
For MVS: This option is available only if CONTROL-M/Restart is installed in the CONTROL-M.
Why
Choose Why from the Action menu or job node popup menu, or click the Why button (available only for those jobs that have not begun executing). This option opens the Why window. You can use this window to:

View the conditions, resources, etc., for which the job is waiting. Create a missing prerequisite conditions that is needed by the job, so that the job can be submitted for execution. Enter a specific date for a condition with the date values **** or $$$$.
Chapter 4
213
Why
Figure 68
Why Window
To add missing prerequisite conditions listed in this window by selecting them and then clicking the Add Condition button. To add missing prerequisite conditions:
1 Click on the line in the Why window that describes the missing condition. 2 Click the Add Condition button. A Confirm Details window is displayed. 3 Click OK to confirm the addition of the condition. NOTE
You can add prerequisite conditions only if you have the appropriate authorizations.
214
Activating Applications
Activating Applications
The Applications Activation feature enables you to insert job processing parameters from a CONTROL-M job or Group Scheduling table into a command line used to activate a third-party program. For any application, you define the command line, including the job processing parameters, using the Activate Applications Editor, and then save the Application Activation definition. The definition can then be used whenever needed. To use the definition to activate the application, select the desired CONTROL-M job or Group Scheduling table in the active environment, and run the application using the application activation definition (as described in Running an application on page 219). The job processing parameters in the application activation definition are replaced at runtime with the values from the job or Group Scheduling table you selected.
NOTE
This feature is available from the CONTROL-M/EM GUI only.
This section discusses:

Defining Application Activation Definitions Running an application
Defining Application Activation Definitions

When you create an Application Activation definition in the Activate Applications Editor, you specify a unique identifying name for the definition and parameters (including any job processing parameters) to be used when activating the application. The dialog box contains the following fields for defining parameters:
Program location (full path) and name of the application to be executed. Initial Dir working directory (full path) of the program (if different than the storage location of the program). Parameters parameters, flags or switches to be passed to the program (including job processing parameters.
Chapter 4
215
To insert a job processing parameter into a field, select the desired parameter from a pop-up menu. The selected job processing parameter is inserted at the end of the field. (Inserted job processing parameters are displayed in red; literal values are displayed in black.) The Activate Applications Editor creates a command line that will be used to activate the application when the Activate Application definition is run. Job processing parameters appearing in the command line are resolved at runtime. To display the Activate Applications Editor:
1 Choose Tools => Activate Applications Editor.

The Activate Applications Editor is displayed. Fields in the panel are described in Table 47.
Table 47
Field
Fields in the Activate Applications Editor

Description Lists existing Application Activation definitions. Definitions can be selected for modification. New definitions can be added by clicking New ( ). Name of the application to run. Specify the full path to the program location. Job processing parameters can be specified. Working directory (full path) of the program. If not specified, the default is the path specified in the Program parameter above. Job processing parameters can be specified. Non-path parameters to be provided to the program. Job processing parameters can be specified.
Applications Program Initial Dir
Parameters
Buttons in the Activate Applications Editor are described in Table 48.
216
Table 48
Button
Buttons in the Activate Applications Editor

Button Name New Description Opens a line in the Applications window for defining a new Application Activation definition. Specify a unique name for the definition. Permanently removes the selected Application Activation definition from the CONTROL-M/EM database. Moves the selected Application Activation definition up so that it comes before the definition that preceded it. Moves the selected Application Activation definition down so that it follows the definition that came after it. Opens a window that allows you to browse to a directory or folder and select a file or folder: The button by the Program field allows you to select only a file (the program to be executed). The button by the Initial Dir field allows you to select only a folder (the initial directory for the programs execution). Displays menus for selecting job processing parameters for insertion into the field to the left of the button. Multiple parameters can be inserted (one at a time) and any parameter can be inserted multiple times.
Delete Move Entry Up Move Entry Down Browse
Menu
To define an Application Activation definition: 1 Perform one of the following actions in the Activate Applications Editor:
If you are creating a new Application Activation definition:
A Click New (
). A blank entry box is displayed in the Applications window.
B Specify a unique name for the Application Activation definition.
If you are modifying an existing Application Activation definition, select the definition in the Applications window. The current parameters for the definition are displayed in the Program, Initial Dir and Parameters fields.
2 Fill in (or modify the entries in) the Program, Initial Dir, and Parameters fields as
follows:
To browse to the desired path (relevant for the Program and Initial Dir fields): ) to the right of the field.
A Click Browse (
B Navigate to the desired program or directory level. C Click the mouse. The selected program or path appears in the field.
Chapter 4 Managing job processing definitions 217
To specify a literal value, type the value in the field. To insert a job processing parameter: ) to the right of the field. Parameter categories (for example,
1 Click Menu (
General, Active, Execution) are displayed.
2 Place the cursor over one of the categories. Parameters in that category (for
example, Job Name, Owner) are displayed.
A Select the desired parameter. A specially formatted version of the parameter is

inserted in the field (in red) at the end of the field (for example, $$JOB_NAME$$ or $$OWNER$$).
NOTE
When inserting a parameter after a path, a space is automatically inserted between the path and the variable. This space should be manually deleted if it is not needed.
B Repeat this step for as many parameters as required. The same parameter can be
inserted more than once.
C You can type the job processing parameter names manually, but you must
ensure that each parameter appears exactly as it is displayed in the CONTROL-M/EM database, enclosed in double dollar signs. (You can consult with your Database Administrator on how to access the CONTROL-M/EM database.) For this reason, BMC Software highly recommends that you select the desired variables from the menu.
3 When you are done defining the Application Activation Definition, click OK (or
Apply if you want the editor panel to remain open).
NOTE
When you click OK or Apply, changes made to all definitions in the current session (not just the changes made to the currently selected definition) are accepted.
To change the order definitions appear in the Applications window: 1 In the Applications window of the Activate Applications Editor, select the name of
a definition that you want to move.
2 Move it to the desired relative location by either dragging it, or by clicking the
Move Up (
) or Move Down (
) button until the definition entry is in the desired
location.
218
Running an application
To change the name of an Application Activation definition: 1 In the Applications window of the Activate Applications Editor, double-click the
entry that you want to rename.
2 Edit the name as desired, and press Enter. To delete an Application Activation definition: 1 In the Applications window of the Activate Applications Editor, select the name of
the definition you want to delete.
2 Click Delete. 3 If a confirmation prompt is displayed, confirm the deletion.

The definition is removed.
Running an application
You can run an Application Activation definition from the:

FlowDiagram Navigation Tree Actions menu on the CONTROL-M/EM menu bar
NOTE
The following steps must be performed every time you want to run an application using an application action definition.
To run an application using an Application Activation definition: 1 Select a job or Group Scheduling table node in the flow diagram or the navigation
tree.
NOTE
The CONTROL-M on which the selected job was run does not have to be operational.
Chapter 4
219
2 Right-click the node. A popup menu is displayed, listing the Activation options for
the job.
3 Choose Activate Application. A list of available application action definitions is

displayed.
4 Select the Application Activation definition that you want to run. The popup menu
closes and the program runs, using the command line and Scheduling table parameters specified in your definition.

Group scheduling tables are sets of jobs that can be controlled, activated, and displayed together in the CONTROL-M/Enterprise Manager window. All jobs in a Group Scheduling table are influenced by the same In Conditions and Resources defined for the group, and together create the Out Conditions for the group. The group scheduling table node is a high-level node (group level) that includes functionality similar to a job node. This functionality includes a Group Editing form, submission criteria, ordering, holding, and freeing all the jobs in the group, a Log window, and a Why window. The symbol indicates a group scheduling table. Figure 69 Group Scheduling Table node
The following conditions apply to group scheduling tables:
Order A group scheduling table can only be ordered as a unit. Single jobs in the group cannot be ordered individually. Multiple appearances A group scheduling table is displayed on the group node level. If it is ordered more than once during the day, it is displayed once for each order in the CONTROL-M/Enterprise Manager window. Each group scheduling table node contains details about the jobs in the table that have already run at the current time. See Properties below. In/Out Conditions The In Conditions and Out Conditions displayed for a group scheduling table are conditions that were defined for the entire table as well as conditions defined for the individual jobs in the table. When displaying each job node in the group scheduling table, only conditions defined for the individual jobs are displayed in the flow diagram.
220
Actions Different actions can be performed on group scheduling tables depending on the current context, for example, whether or not the group is defined for an MVS platform. Available actions are described in Table 49. Group scheduling tables Action menu
Description Assigns a Held status to all jobs in the Group Scheduling table. The Hold indicator (lock) appears only on the group node. Job nodes do not have the lock symbol, but are nonetheless reality, in Hold status. Removes Hold status from all jobs in the Group Scheduling table. Allows viewing of the jobs log records. Confirmation of job activation for jobs in Wait Confirmation status. Indicates why jobs in the Group Scheduling table are waiting for execution. Allows viewing and updating of the Group Editing form for the group. Deletes a Group Scheduling table and all its jobs. (Only possible if the Group Scheduling table is in Hold status.) Restores a previously deleted Group Scheduling table and all its jobs. Displays the time that elapsed from the start of the first job in the Group Scheduling table until the end of the last job in the Group Scheduling table.
Table 49
Action Hold
Free Log Confirm Why Edit Delete Undelete Statistics
To display or perform an action on a group scheduling table: 1 Right-click the Group Scheduling Table node. 2 Choose Properties from the popup menu. The Group Editing form is displayed.
Figure 70 Group Editing form
Chapter 4
221
General panel
The Group Editing form is divided into the panels described in Table 50. Each panel contains a group of related parameters. When the OK button is clicked, each change is immediately propagated to the Active Jobs file in the appropriate CONTROL-M installation. Table 50
Panel General Active Conditions Set Shouts Post-proc
Group Editing Form panels

Description Parameters identifying the group scheduling table and where it is located. Run time, scheduling, and status information about a group scheduling table. In Conditions and Out Conditions defined for the entire group as well as conditions defined for individual jobs. Create new AutoEdit variables and modify existing AutoEdit variables. Parameters for determining the content and destination of Shout messages. Parameters for specifying conditional post-processing actions that are performed after group completion.
General panel
The General panel indicates what the group scheduling table does and where the jobs are located. Figure 71 Group Editing form General panel
222
General panel
Table 51
Field
General panel fields

Description
File name or Mem Name of the file that contains the job script (JCL) statements for the jobs Name (MVS) in the Group Scheduling table. Owner Task Type Scheduling Table Name Scheduling Table Lib Application Group CONTROL-M Confirm Priority Doc Mem Log-on ID of the user responsible for the jobs in the Group Scheduling table. Always has the value Scheduling group. Name of the Group Scheduling table. Name of the directory or library that contains the Group Scheduling table. Name of the application to which the Group Scheduling table belongs. Name of the Group Scheduling table. Name of the CONTROL-M installation where the Group Scheduling table is defined. Indicates whether or not confirmation is required for submission of the Group Scheduling table. Priority of the jobs in the Group Scheduling table. Name of a file containing detailed information about the Group Scheduling table. Note: To access the documentation, the user must be defined and have authorization on the CONTROL-M where the documentation resides. Doc Lib Name of the library or directory containing the documentation (Doc Mem) file. Note: To access the documentation, the user must be defined and have authorization on the CONTROL-M where the documentation resides. Adjust Condition Time From Time Until Description Indicates if prerequisite conditions normally set by predecessor jobs are ignored if the relevant predecessor jobs are not scheduled. Indicates the earliest time for submission of the first job in the Group Scheduling table. (Valid time value) Indicates the latest time for submission of the last job in the Group Scheduling table. (Valid time value) Brief free-text description of the Group Scheduling table.
Chapter 4
223
Active panel
Active panel
The Active panel indicates the run time and status of jobs in the Group Scheduling table. Figure 72 Group Editing form Active panel
Table 52
Field
Active Panel Fields

Description Original scheduling date of the jobs in the group scheduling table. Time by which the group scheduling table should finish executing. + num Days Number of days that job execution can be extended after the Order Date. z/OS only: This subparameter is relevant only for jobs running in CONTROL-M for z/OS version 6.2.00 or later.
Current Status Status (for example, Ended OK) of the jobs in the group. Order Date Due Out
Due In
Time at which the group scheduling table must begin to execute. + num Days Number of days that job execution can be extended after the Order Date. z/OS only: This subparameter is relevant only for jobs running in CONTROL-M for z/OS version 6.2.00 or later.
Elapse Hold Deleted Maxwait Time From/Until Order ID
Time (in minutes) that jobs in a group scheduling table are expected to run. Indicates if the group scheduling table is currently in Held status. Indicates if the group scheduling table has been deleted. Number of extra days the group scheduling table will remain in the Active Jobs file waiting for execution. Time range limit for execution of the jobs in the group scheduling table. ID assigned to the current instance of the group scheduling table by the CONTROL-M installations operating system.
224
Conditions panel
Conditions panel
The Conditions panel is used to define prerequisite IN and OUT conditions. The panel contains two sections: IN conditions are defined in the left section; OUT conditions are defined in the right section. Figure 73 Group Editing form Conditions panel
The main part of each section lists already-defined conditions. Below this box is a Text line used for editing already-defined conditions or defining new conditions. When you select a condition in the list, its contents are displayed in the Text line. After editing or creating a condition, click the check box the condition to the list. The following buttons are available for each section:
Button Action Enter a new condition. Delete the selected condition. and Change the order of the list. Copy data. Paste data.
to save the changes or add
Chapter 4
225
Conditions panel
Defining IN conditions
The following fields are used to describe each IN condition:
Parameter Name Date Description Name of the prerequisite condition. A 4-character date in mmdd or ddmm format (depending on the site standard) or one of the following keywords: ODAT original scheduling date PREV previous scheduling date of the job NEXT next scheduling date of the job **** / $$$$ any scheduling date Logical relationship between multiple conditions.
And/Or
Defining OUT conditions

The following fields are used to describe each OUT condition:
Item Name Date +/ Description Name of the prerequisite condition. Date reference. Same as IN Condition. Indicates whether to add or delete the condition.
226
Set Panel
Set Panel
The Set panel is used to specify AutoEdit variables to be set up in the jobs script (JCL) before job submission of all jobs in the group scheduling table. Figure 74 Group Editing form Set panel
This panel contains a list of already-specified variables. Below this area are fields (similar to the AutoEdit Assignment fields) that are used to specify additional variables. If you select a variable in the list, its contents are displayed in these fields. After editing or creating a variable, click the check button next to the text line to save changes or add the variable to the list. The following buttons are also available:
Button Action Enter a new variable. Delete the selected variable. and Change the order of the list. Copy data. Paste data.
The following fields are used to define AutoEdit variables

Parameter Description Name Value User-defined AutoEdit variable. It is not required to add the %% prefix. If omitted, it will automatically be added to the variable name. Either a single value, an AutoEdit system variable, or a previously defined userdefined variable (for example, %%ODATE) provided it resolves to a single value.
Chapter 4
227
Shouts panel
Shouts panel
The Shouts panel is used to specify messages to be sent (shouted) to various destinations on different occasions. Figure 75 Group Editing form Shouts panel
The parameter display contains a list of already-defined Shout statements. Below the list is a series of fields used for specifying additional Shout statements. After editing or creating a Shout message, click the Check box and/or add the message to the list. The following buttons are available:
Button Action Enter a new message. Delete the selected message. and Change the order of the list. Copy data. Paste data.
to save the changes
For more information about specifying Shout statements, see the descriptions of the Shout and Do Shout parameters in the CONTROL-M Job Parameter and Variable Reference Guide.
228
PostProc panel
PostProc panel
The PostProc panel specifies conditional post-processing actions to be performed upon group completion, depending on the outcome of specified statements. Figure 76 Group Editing form PostProc panel
This panel is used to define On Statements and Do Statements. It contains a list of already-defined On/Do Statements. Below the list are fields for defining new On Statements. The line for defining new Do Statements is not displayed initially.
To display the Do Statement line: 1 Click the DO button

at the side of the Step Codes section.
To re-display the On Statement line: 1 Click the ON button

. After editing or creating an On/Do Statement, click the check button at the lower corner of the panel to save the changes or add the statements to the list. The following buttons are also available:
Action Delete the selected statement. and Change the order of the list. Copy data. Paste data.
Button
Chapter 4
229
PostProc panel
On Statement definition line

The On statement specifies the status of the group on completion. There are two options, OK and NOTOK. Choose the required option from the popup list, and click the check button .

This line is used to define DO actions to be performed when the step code criteria are satisfied. To display this line, press the DO button at the side of the Step Codes Criteria section. For more information about available Do parameters, see the CONTROL-M Job Parameter and Variable Reference Guide. After editing or creating an On/Do Condition statement, click the check button at the corner of the Step Codes section to save the changes and/or add the statements to the list.
230
Chapter
Monitoring alerts and errors

Alerts are messages that provide important data for the CONTROL-M/Enterprise Manager (CONTROL-M/EM) user. These messages normally indicate that a problem or exception has occurred for a job controlled by CONTROL-M. All alerts are displayed in the Alerts window. Alerts can be generated by CONTROL-M and by CONTROL-M/EM in the following manner:
By CONTROL-M When creating a job processing definition, you can specify that a message be posted to the Alerts window using the CONTROL-M Shout facility. For more information, see Generating alerts on a CONTROL-M for MVS platform on page 351.
By CONTROL-M/EM CONTROL-M/EM can be customized to generate an alert automatically when a job terminates with Ended not OK status. This is useful if jobs do not issue Shout messages or if they direct Shout messages to other target users.
Alerts are also generated when a communications problem occurs (such as a communication breakdown between CONTROL-M and CONTROL-M/EM). This alert creation can be prevented through appropriate setting of the Gateway system parameters related to Alerts (described in the Gateway table in the System Parameter appendix in the CONTROL-M/Enterprise Manager Administrator Guide). Alerts can also be generated by other BMC Software products (for example, CONTROL-O) to relay messages of special importance. Refer to the user guide or administrator guide of the specific products for additional information.
Chapter 5
231
To open the Alerts window

Choose Tools => Alerts. The Alerts window is displayed, with your user name and the Global Alerts Server name shown in the title bar. Figure 77 Alerts window
The menu bar in the Alerts window provides a series of options, as explained in Table 53. Table 53 Alerts Window menu options (Part 1 of 3)
Description
Menu option
Communication The Alerts window is managed by a Global Alerts Client (GAC) that is connected to the CONTROL-M/EM GUI using a CONTROL-M/EM Server and a Global Alerts Server. The defaults for these servers are defined during installation. CONTROL-M/EM lets you change the way you use and select these servers, as follows:
Use the Communication => Connect option to connect to a different server. Enter the new Server Host Name in the displayed dialog box and click OK. Use the Communication => Disconnect option to disconnect from the current server. Use the Communication => Exit option to close the Alerts window.
232
Table 53
Alert
Alerts Window menu options (Part 2 of 3)

Description Select the action you want to take with regard to the specified alert. You can take any of the following actions:

Menu option
Details Opens the Alert Details window Notice Changes the status of the selected alert to Noticed Unnotice Changes the status of the selected alert to Not Noticed Handle Changes the status of the selected alert to Handled Unhandle Changes the status of the selected alert to Noticed Open into Viewpoint Opens the alert into a Local View ViewPoint Find Job Finds the job that produced the alert
View
Includes the following options:
Filter Toggles the display to show or hide the Filter Alerts section of the Alerts window. For more information about the Filter Alerts section, see page 235. Status Bar Toggles the display of the Status Bar to show or hide all of the following information: Filter Whether the Filter is On or Off Items The number of items in the Alerts window Not Noticed Total number of alerts that have not been Noticed or Handled by the user Not Handled Total number of alerts that have been Noticed but have not been Handled by the user
Note: When a new alert message is displayed in the window, the Not Noticed total is incremented and the message is added to the end of the list. You can change the state of an alert to Noticed or Handled. The totals are automatically updated.
Refresh Now Resorts the list according to the current sort column order.
Chapter 5
233
Table 53
Alerts Window menu options (Part 3 of 3)

Description Select the action you want to take with regard to the appearance of the Alerts window. You can take any of the following actions:
Menu option Preferences
Always On Top Keeps the Alerts window open on top of all other windows (unless the Alerts window is minimized). Show Gridlines Toggles the display of gridlines between the rows and columns of the Alerts window Show Info Tips If the displayed column is not wide enough, the sub-item text is partially hidden. If you select this preference option, a tooltip with the complete text will be displayed when you move the mouse on a partially displayed sub-item. Font Enables you to change the display fonts used in the Alerts window Scroll to New Alert If a new alert arrives, the list scrolls to ensure that the new alert is displayed (although the selection being viewed at the time the new alert arrives is not changed).
Note: Preferences are saved and become the default setting the next time the Alerts window is opened.
When an alert is received or modified in CONTROL-M/EM
the Alerts window can be opened automatically, even if CONTROL-M/EM is not the currently active application (by setting the Bring Alerts Window to Front option in the Alerts panel of the Tools => Options menu). the Alerts button on the task bar can flash automatically (by setting the Flash Alerts Window on Taskbar option in the Alerts panel of the Tools => Options menu).
For more information, see Alerts panel on page 334. Alerts are displayed only for jobs that you are authorized to view. For more information, see the Security chapter in the CONTROL-M/Enterprise Manager Administrator Guide. Alerts listed in the window are colored according to their urgency as specified by the Shout Urgency parameter in the Job Processing definition. Table 54 explains the relationships of colors to severity of alert types.
234
Handling alerts
Table 54
Alert
Alert Status Colors

Color Red Orange Yellow
Very urgent Urgent Regular
After an alert is Handled, the alert is displayed in white. Using the scroll bars, you can view all the alerts in the list. You can also filter the list to display only certain alerts, such as alerts that have not yet been Handled.
NOTE
If CONTROL-M/EM user changes an alerts status or details in the Alerts window, those changes are visible in the Alerts windows of all other CONTROL-M/EM users who have Browse authorization or higher.
You can filter the alerts that are displayed in the Alerts window. Filtering fields are described in Table 56 on page 237. For instructions on how to filter the display, see To filter the alert messages displayed: on page 236. In addition to the filter criteria you can specify in the foregoing fields, you can choose to further limit the alerts to be displayed by selecting one or more status check boxes (Not Noticed, Noticed, and Handled). The Handling alertssection provides additional information about alert status. You can also narrow the search to particular alerts by selecting one or more severity check boxes (Regular, Urgent, and Very Urgent).
Handling alerts
CONTROL-M/EM tracks the status of all alerts. When you resolve the problem indicated by an alert, you assign that alert a status of handled. Table 55 describes the possible alert statuses. Table 55 Alert Status
Description Not seen by the user. These Alerts appear with an R, U or V icon (for Regular, Urgent or Very Urgent) at the left of the alert. Default. Seen by the user but not handled. Handled by the user.
Alert Status Not Noticed Noticed Handled
Chapter 5
235
Handling alerts
You can change the status of an alert as follows:
To notice or handle alerts: 1 Right-click the Alert line and choose the Notice or Handle option from the pop-up
menu. You can select multiple Alert lines. The Not Noticed and Not Handled totals are automatically updated in the Status Bar. The status of an alert can also be changed to Not Noticed. The Alert Details window indicates when the alert was last changed and by whom. For more information, see Alert Details window on page 237.
To view details of an alert, change the severity of an alert, or add notes: 1 Double-click on the line containing the alert message.
The Alert Details window displays details about the alert. It enables changes to be made to the severity of the alert and lets you add notes to the alert message. For more information, see page 237.
To focus on the job in the FlowDiagram to which an alert refers: 1 Right-click the line containing the alert. 2 Choose Find Job from the pop-up menu.
The relevant node is displayed and selected in the CONTROL-M/Enterprise Manager ViewPoint window.
To filter the alert messages displayed: 1 Click the Filter Alerts check box, and fill in the filtering criteria in the filter fields.
The filtering fields are described in Table 56. You can supply multiple values in each field, separated by commas or semicolons. You can also use pattern-matching strings in the filter fields to simplify the task of inserting multiple criteria. For details, see Specifying pattern-matching strings on page 73. (To clear the values in all filter fields, click Clear.)
236
Alert Details window
Table 56
Field
Alerts window Filter criteria

Description When selected, indicates that the filter criteria entered in the remaining filter criteria fields should be used to limit the alerts displayed in this window. Host name of a node group to which the job should be submitted. Show alerts for only the specified File Names. Name of a job processing definition. Free text description of the alert. Unique serial number assigned to each job order in the Active Jobs file. Show alerts for only the specified times. Name of the application to which the group of the specific job belongs. Used to supply a descriptive name to a set of related groups of jobs. Name of the group to which the job belongs. Unique serial number assigned to each alert. Free text description of data that is displayed in the Notes field of the Alert. Status of the alert. Valid values: Not Noticed Not seen by the user (default). Noticed Seen by the user but not handled. Handled Handled by the user. Date and time when the alert was last changed. User ID of the last user who changed the severity, notes, or Noticed/Handled status. Owner of the job which generated the message.
Filter Alerts
CONTROL-M Show alerts for only the specified CONTROL-M. Node ID Mem Name Job Name Message Order ID Time Application Group Alert ID Notes Status
Changed By Update Time Owner
2 Click Apply.
The Alerts window display is adjusted according to the new filtering criteria.

The Alert Details window lets you view alert details, including the severity of the alert, when the alert was last responded to or modified, and so on. You can also change the severity of the alert and add notes to the message.
To open the Alert Details window: 1 Double-click the alert message in the Alerts window.
The Alert Details window is displayed.
Chapter 5
237
Figure 78
The fields of the Alert Details window are described in Table 57. Table 57
Field Status Mem Name Job Name Application Group Message Severity
Alert Details window fields

Description Status of the alert (Not Noticed, Not Handled, Handled). Member name of the job that generated the message. Job name of the job that generated the message. Application with which the job that generated the message is associated. Group with which the job that generated the message is associated. Text of message from CONTROL-M Shout facility or CONTROL-M/EM. Level of urgency specified in the Shout parameter of the job that issued the alert. You can reset this parameter to one of the values in the list box: REGULAR URGENT VERY_URGENT Order ID assigned to the job that generated the message. Owner of the job that generated the Shout message. Date and time when the alert was generated. User who last modified the alert status. Time at which the alert status was last modified. Area for providing additional information in free text format. For example, the text job was rerun informs other users of how a problem was handled. Unique ID of the node on which the job that generated the alert was run. Unique identifier for the alert.
Order ID Owner Alert time Changed By Update Time Notes
CONTROL-M CONTROL-M in which the alert was generated. Node ID Alert ID
238
Local View
Local View
Tracing the cause of an error can help you troubleshoot problems in the CONTROL-M/EM environment. The Local View feature helps you analyze an alert and its work environment by examining the job that prompted the alert.
To display a Local View: 1 Click

, or choose Tools => Alerts to display the Alerts window.
2 Select an alert from the window. 3 Right-click the alert to display the pop-up menu. Choose Open into ViewPoint.
A new ViewPoint is displayed in the GUI.
NOTE
Alerts with an empty Order ID are not created by jobs. Local View does not deal with these alerts. When they are right-clicked, Open into ViewPoint and Find Job are disabled on the pop-up menu.
This ViewPoint contains the job node of the job that prompted the selected alert. In addition, job nodes of jobs that depend on or are predecessors for the job are also shown in this ViewPoint.
4 To open multiple Local View ViewPoints, repeat step 2 and step 3. There is no need
to re-open the Alerts window. It does not close when the Local View ViewPoint is displayed.
NOTE
Certain nodes may not be displayed due to the currently-selected ViewPoint. This setting can be modified. For more information, see Modifying the ViewPoint of the Local View on page 240.
NOTE
The job that prompted the selected alert may have finished executing and may no longer be in the CONTROL-M/EM environment. Selecting a Local View for such a job displays an empty ViewPoint.
Chapter 5
239
Local View
Modifying the ViewPoint of the Local View

You can alter the display properties of ViewPoints for the Local View by adjusting the Open into Local View settings on the Alerts panel of the Options dialog box.
To modify the display properties of Local View ViewPoints 1 Choose Tools => Options, and in the displayed Options dialog box, select the Alerts
panel. Figure 79 Alerts panel of the Options dialog box
2 Adjust the values of the fields In the Open into Local View area, as needed. These
fields are described in Table 58. Table 58
Field Use Radius of n nodes ViewPoint Name
Open Into Local View section of the Alerts panel

Description Length of the chain of dependent and predecessor jobs branching out from the job that prompted the alert. You can display a radius of up to ten levels. Selects an existing ViewPoint (filter and node display hierarchy) in which to view job nodes in a Local View. Existing ViewPoints can be chosen from a list box.
240
Chapter
Displaying and defining resources and conditions

6
A set of conditions and resources windows allows you to view and change entries in all Control resources, Quantitative resources and prerequisite conditions in the production environment. To access one of these windows, select the appropriate option from among the following in the Resources menu in the CONTROL-M/Enterprise Manager window:

Control resources Quantitative resources Prerequisite conditions Global conditions
Generally, before a requested window (example: Control Resources window) is displayed, an appropriate filtering dialog box (example: Resources dialog box) is opened. Note however that no filtering dialog box is displayed before the Global Conditions window. Filtering reduces not only clutter in the window, but retrieval overhead as well. The filtering criteria last specified in the dialog box are redisplayed when the dialog box is reopened. Filtering is performed according to pattern-matching rules applied to the values specified in the dialog box. The pattern-matching rules that are used for filtering are described in Specifying pattern-matching strings on page 73. The filtering fields that appear in the dialog box also appear at the top of the window, where they display the values entered in the dialog box. You can change the filtering criteria and re-retrieve.
Chapter 6
241
Control resources
Control resources
The Control Resources window lists all Control resources in the production environment.
To display the Control Resources window: 1 Choose Resources => Control Resources. The Resources Filter dialog box is
displayed. Figure 80 Resources Filter dialog box
The fields of this dialog box are described in the Table 59. Table 59
Field Name
Filtering criteria for Control resources

Description Name or mask of the Control resources.
CONTROL-M Name or mask of CONTROL-M installations for which the resources are defined. Type Type of Control resource: Exclusive: Exclusively owned by a job. Shared: Shared by any number of jobs. Requested: Requested by a critical job. Relative Byte Address (for MVS jobs) for the jobs that require the resources.
RBA
2 Enter filter criteria and click OK. The Control Resources window is displayed
(Figure 81). The Filter area at the top of this window contains the same filtering fields that appear in the Resources filter (Figure 80 on page 242, described in Table 59 on page 242). The columns in the Control Resources window are described in Table 60; the buttons in this window are described in Table 61 on page 243.
242
Control resources
Figure 81
Control Resources window
Table 60
Column Resource Type
Control Resources window columns

Description Name of the Control resource (corresponds to the Name filtering field). Type of Control resource: Exclusive: Exclusively owned by a job. Shared: Shared by any number of jobs. Requested: Requested by a critical job. A Requested entry exists for each job that requests the resource. Relative Byte Address (unique identifier for the job) for MVS jobs. Y or N, indicating whether or not the job identified in RBA is critical. Note: This field is irrelevant for shared resources. Number of jobs currently using the resource. For exclusive resources, this field always has a value of 1. For required resources, this field in not relevant. For shared resources, the number jobs currently using the resource.
CONTROL-M Name of the CONTROL-M. RBA Priority Counter
Table 61
Button Clear Apply New
Control Resources Window Buttons (Part 1 of 2)

Description Clears all filter fields. Re-applies (modified) filter criteria to the displayed resources. For details, see To re-retrieve Control resources using different filtering criteria on page 244. Opens the Control Resource dialog box to allow you to define a new control resource. For details, see To define a new Control resource on page 244.
View Jobs Opens a dialog box listing all jobs and group scheduling tables for which the selected Control resource is specified. For details, see Viewing the Control Resource job list on page 245.
Chapter 6
243
Control resources
Table 61
Button Delete Refresh Close
Control Resources Window Buttons (Part 2 of 2)

Description Removes (deletes) the selected resources. For details, see To delete Control resources on page 244. Updates the display in the window to show the current status of Control resources in the current environment. Exits the Control Resources window.
To re-retrieve Control resources using different filtering criteria

In the Control Resources window, modify the values of the fields in the Filter area, and click Apply. (To clear all filter fields, click Clear.) The displayed resource list is adjusted according to the new filtering criteria.
To define a new Control resource 1 In the Control Resources window, click New. The Control Resource dialog box is
displayed. Figure 82 Control Resource dialog box
2 In the Control Resource dialog box, fill in the necessary details The fields in the
dialog box correspond to fields in the Control Resources window and are described in Table 60 on page 243.
3 Click Add Resource. The new resource is added to the database. To delete Control resources
In the Control Resources window, select the resources to be deleted and click Delete. Shared Control resources can be deleted only if: No jobs own or request the resource. (The Counter field is 0 for all resource table entries for the resource.) No jobs are requesting the resource. (There are no table entries for this resource with a Requested resource type.)
Viewing the Control Resource job list
Viewing the Control Resource job list

You can view a list of jobs and group scheduling tables for which a selected Control resource is specified. Because the list of Control resources only displays resources in use at time of last update, only jobs and tables that use those resources are in the list. From the displayed list of jobs, you can display a job in the Job Editing form.
NOTE
This option is available only for Control resources defined for CONTROL-M for OS/390 and z/OS version 6.1.00 or later.
To view the job list for a resource 1 Double-click the resource in the Control Resources window (or select the resource
and click View Jobs). The View Jobs window is displayed (Figure 83 on page 245). The information in the window depends on your resource authorizations. Figure 83 View Jobs window
2 To edit a job in the list (optional), double-click that job. The Job or Group Editing
form is displayed for the selected job or group scheduling table. If you do not have authorization to view job details, the Job and Group Editing forms are not displayed; only the RBA value is displayed.
Chapter 6
245
The Quantitative Resources window is used to view and update Quantitative resources in the production environment.
To display the Quantitative Resources window: 1 Choose Resources => Quantitative Resources. The Resources Filter dialog box is
displayed (Figure 84). Figure 84 Resources Filter dialog box
The fields of this dialog box are described in Table 62. Table 62
Field Name
Filtering Criteria for Quantitative Resources

Description Name or mask for the Quantitative resources.
CONTROL-M Name or mask of the CONTROL-M installations for which the resources are defined. Type Type of Quantitative resource entries to display. Valid values:
Defined: General information about the resource. Only one definition entity exists per resource. This entity is added by the user to define a new Quantitative resource. In Use: Indication that the resource is currently being used by a job. An In Use entity exists for each CONTROL-M job that is currently using the resource. Required: Indication that the resource has been requested by a critical job. A Required entity exists for each critical job that requests the resource.
RBA
Relative Byte Address (for MVS jobs) for the jobs that require the resources.
2 Enter filter criteria and click OK. The Quantitative Resources window is displayed.
246
Figure 85
Quantitative Resources window
The Filter area at the top of this window contains the same filtering fields as the Resources filter (see Figure 84 on page 246, described in Table 62 on page 246). The columns in the Quantitative Resources window are described in Table 63. The buttons in this window are described in Table 64.
NOTE
Most fields in this window are updated automatically by CONTROL-M and cannot be modified by the user. However, you can modify the Resource and Max fields for entries with the Defined type. For details, see To update Quantitative resources on page 250
Chapter 6
247
Table 63
Column Resource
Quantitative Resources window columns

Description Name of the Quantitative resource (corresponds to the Name filtering field). Quantitative resources used for load balancing are named using the format: resource_name@node_ID where node_ID specifies the Agent platform on which the resource is located. If a critical job, to be submitted by the load balancing mechanism, is waiting for available resources, the required resources are displayed in this window using the format: resource_name@ Note: Load balancing is available only for certain platforms with CONTROL-M version 2.20 or later.
Type
Type of the Quantitative resource entry in the table. Multiple entries can exist for one Quantitative resource each describing a different aspect of the resource. Entry types are:
Defined: General data about the resource. One Defined entity exists for each resource. The user adds this entity when defining a new Quantitative resource. In Use: Indicates that the resource is currently being used by a job. An In Use entity exists for each CONTROL-M job currently using the resource. Required: Indicates that the resource has been requested by a critical job. A Required entity exists for each critical job requesting the resource. For an entry whose type is Defined, this column indicates the number of units of the resource that are currently available. For In Use and Required entries, this column indicates the number of units of the resource currently used by the job specified by its RBA. For an entry whose type is Defined, this column indicates the maximum quantity of the resource existing in the CONTROL-M installation. For In Use and Required entries, the value in this column is 0.
CONTROL-M Name of the CONTROL-M in which the resource is located. Quant

Max
Priority
For an entry whose type is Defined, this field is not applicable. For entries with a type of In Use or Required, Y or N indicates whether or not the job identified in RBA is critical. Note: This field is irrelevant for shared resources.

RBA
For an entry whose type is Defined or Required, RBA (Relative Byte Address) is not applicable. For In Use entries, this column contains the RBA of the MVS job using the resource. Note: This field is not relevant for shared resources or required resources.
248
Table 64
Buttons Clear Apply New Delete Update Refresh Close
Quantitative Resources window buttons

Description Clears all filter fields. Applies specified filter criteria to the displayed resources. For details, see To re-retrieve Quantitative resources using different filtering criteria below. Opens the Quantitative Resource dialog box to allow you to define a new resource. For details, see To define a new Quantitative resource on page 249. Removes (deletes) the selected resources. For details, see To delete Quantitative resources on page 250. Opens the Quantitative Resource dialog box to allow you to modify an existing resource definition. See To update Quantitative resources on page 250. Updates the display in the window to show the current status of Quantitative resources in the current environment. Exits the Quantitative Resources window.
To re-retrieve Quantitative resources using different filtering criteria

In the Quantitative Resources window, modify the values of the fields in the Filter area, and click Apply. (To clear all filter fields, click Clear.) The displayed resource list is adjusted according to the new filtering criteria.
To define a new Quantitative resource 1 In the Quantitative Resources window, click New. The Quantitative Resources
dialog box (Figure 86) is displayed. Figure 86 Quantitative Resources Dialog Box
Chapter 6
249
2 In the Quantitative Resource dialog box, fill in the updatable fields and click Add
Resource. (The fields in the dialog box correspond to fields in the Quantitative Resources window and are described in Table 63 on page 248.) The resource is added.
To update Quantitative resources 1 In the Quantitative Resources window, click Update. The Quantitative Resource
dialog box (Figure 86 on page 249) is displayed.
2 In the Quantitative Resource dialog box, modify the updatable fields as desired
and click Add Resource. (The fields in the dialog box correspond to fields in the Quantitative Resources window and are described in Table 63 on page 248.) The resource is modified.
To delete Quantitative resources

In the Quantitative Resources window, select the resources to be deleted and click the windows Delete button. The selected resources are deleted. Defined Quantitative resources can only be deleted in the following situation: If no jobs own or request the resource (that is, there are no Requested or In Use entities in the window for the resource). -and All resources are available (that is, the Quant field is equal to the Max field).
250
The Prerequisite Conditions window lists all prerequisite conditions in the CONTROL-M environment. Conditions can be added and deleted using this window. (For detailed information describing Prerequisite (In and Out) conditions, see the In Condition and Out Condition descriptions in the CONTROL-M Job Parameter and Variable Reference Guide.)
NOTE
Addition and deletion of prerequisite conditions in one CONTROL-M may affect prerequisite conditions in other CONTROL-M installations. See Global conditions on page 255.
To display the Prerequisite Conditions window: 1 Choose Resources => Prerequisite Conditions. The Prerequisite Conditions Filter
dialog box is displayed. Fields of this dialog box are described in Table 65. Figure 87 Prerequisite Conditions Filter dialog box
Table 65
Field Condition Order Date
Filtering criteria for Prerequisite conditions

Description Name of the prerequisite condition. Original date reference of the condition (in mmdd or ddmm format depending on the site standard). Name of the CONTROL-M in which the prerequisite condition exists.
CONTROL-M
2 To display all prerequisite conditions, leave the filter criteria fields blank and click
OK. Otherwise, enter filter criteria and click OK to display those conditions that satisfy the filter criteria. The Prerequisite Conditions window is displayed.
Chapter 6
251
Figure 88
Prerequisite Conditions window
The Filter area at the top of this window contains the same filtering fields that appear in the Prerequisite Conditions filter (Figure 87 on page 251, described in Table 65 on page 251). The columns in the Prerequisite Conditions window are described in Table 66. The buttons in this window are described in Table 67. Table 66
Column Automatic Refresh Condition Order date
Prerequisite Conditions window columns

Description Automatically refreshes the prerequisite conditions displayed in the window at the interval defined in the Environment - Display panel of the Options dialog box. Name of the prerequisite condition. Original date reference of the condition (in mmdd or ddmm format, depending on the site standard).
CONTROL-M Name of the CONTROL-M in which the prerequisite condition exists.
252
Table 67
Button Clear Apply New Delete
Prerequisite Conditions window buttons

Description Clears all filter fields. Applies specified filter criteria to the displayed conditions. See To re-retrieve Prerequisite conditions using different filtering criteria on page 253. Opens a dialog box that is used to specify information for a new prerequisite condition. For details, see To create new Prerequisite conditions on page 253. Removes (deletes) the selected conditions. For details see To delete Prerequisite conditions on page 254.
Refresh Updates the display in the window to show the current status of prerequisite conditions in the current environment. Close Exits the Prerequisite Conditions window.
To re-retrieve Prerequisite conditions using different filtering criteria

In the Prerequisite Conditions window, modify the values of the fields in the Filter area, and click Apply. (To clear all filter fields, click Clear.) The displayed prerequisite conditions list is adjusted according to the new filtering criteria.
To create new Prerequisite conditions
NOTE
Prerequisite conditions are usually created by dragging between job and Group Scheduling table nodes in the CONTROL-M/EM flow diagram. For more information, see Handling conditions on page 29.
1 In the Prerequisite Conditions window, click New. The Prerequisite Condition

dialog box (Figure 89) is displayed. Figure 89 Prerequisite Condition dialog box
Chapter 6
253
2 Enter information for the new condition. The fields in the dialog box correspond to
fields in the Prerequisite Condition window, and are described in Table 66 on page 252.
3 Click Add Condition. The condition is added. To delete Prerequisite conditions

In the Prerequisite Conditions window, select conditions to be deleted. Click Delete.
254
Global conditions
Global conditions
Prerequisite conditions generally create dependencies between jobs running in the same CONTROL-M installation. Global conditions are a special case of prerequisite conditions that create job dependencies between CONTROL-M installations. (For example, you can specify that jobs in CONTROL-M installations ROME and PARIS begin executing only after the successful completion of a job in SYDNEY.) Global conditions are defined using the Global Conditions window. The window also displays already defined Global conditions. To define a Global condition, you must specify:
A name prefix that indicates that a prerequisite condition is a global condition. CONTROL-M installations for which that global condition prefix is relevant.
NOTE
A Global Condition prefix for CONTROL-M/Server version 6.1.00 or later can be up to 255 characters long. Earlier versions of CONTROL-M can accept prefixes of up to 39 characters. When you define global condition definitions, you designate relevant CONTROL-M installations as From and/or To CONTROL-Ms. In the production environment, when CONTROL-M/EM detects the addition or deletion of a global condition in a From CONTROL-M, it automatically adds or deletes the same global condition in the designated To CONTROL-M installations. By appropriately designating the same CONTROL-M installations as both From and To CONTROL-Ms, you can create bi-directional flows (as opposed to From/To flows). In this case, addition or deletion of a global condition in any such installation will always result in the automatic addition or deletion of the global condition in the opposite direction. To implement bi-directional global conditions, BMC Software recommends that you review the best practices described under Bi-directional global conditions on page 264, and implement accordingly. Once you have defined a global condition, you can handle it like other (non-global) prerequisite conditions (for example, you can view, create, and delete global conditions using the Prerequisite Conditions window).
NOTE
Depending on how your CONTROL-M installation was implemented, certain security definitions may be required in a target CONTROL-M installation to enable the creation or deletion of global conditions. For more information, see the Security chapter of the CONTROL-M/Enterprise Manager Administrator Guide.
Chapter 6
255
Global conditions
To open the Global Conditions window: 1 Select Resources => Global Conditions. A Global Conditions window appears. NOTE
A separate filter dialog box is not displayed for global conditions. Filter fields are included in the Global Conditions window.
Figure 90
Global Conditions window
The window contains two main parts: The Filter area allows specification of criteria for filtering global conditions. The display area displays the (filtered) list of existing global conditions definitions. The Filter fields in this window correspond to the column headers in the display area. They are described in Table 68 on page 256. Table 68 Global Conditions window Filter fields and Columns
Description When checked, allows you to filter the global conditions in the window. See To filter the display of global condition definitions on page 257. Names of the CONTROL-M installations from which prerequisite conditions that match the value of the Prefix field will be recognized as Global conditions. Up to 512 characters can be typed in this field. Names of the CONTROL-M installations that should add or delete the specified global condition when that condition is added or deleted in a corresponding CONTROL-M installation listed in the From CONTROL-M field. Up to 512 characters can be typed in this field.
Field or Column Filter (check box)
Conditions Prefix Prefix used to identify a prerequisite condition as a Global condition. From CONTROL-M(s) To CONTROL-M(s)
256
Global conditions
Table 69
Button Clear Apply New Delete Update Refresh Close
Global Conditions window buttons

Description Clears all filter fields. Applies specified filter criteria to the displayed global conditions. For details, see To filter the display of global condition definitions on page 257. Opens a dialog box used to specify information for a new global condition. For details, see To create a new global condition definition: on page 258. Removes (deletes) the selected global conditions. For details, see To delete a global condition definition: on page 260. Opens a dialog box used to update the selected global condition. For details, see To modify an existing global condition definition: on page 259. Updates the Global conditions list display. Exits the Global Conditions window.
NOTE
Changes in the Global Conditions window (for example, defining a new prefix) affect only conditions that are created or deleted after the change was saved.
To filter the display of global condition definitions

Select the Filter check box, fill in the Filter fields (see Table 68), and click Apply. Note that asterisks can be used as wildcards in the filtering criteria.
Chapter 6
257
Global conditions
To create a new global condition definition: 1 In the Global Conditions window, click New. The Global Condition Definition
dialog box is displayed (with Add New Global Condition in the title bar). Figure 91 Global Condition Definition dialog box
2 In the Prefix text box, specify the prefix for the new global condition definition. WARNING
When filling in the Prefix text box, do not specify special characters, such as asterisks, as prefix indicator. Special characters in this field are treated as text characters, not wildcards, and unless you intend them as literals, they may cause undesired results. For example, if you specify glo* instead of glo as a global prefix, glo*-job1_started will be a global condition, but not glo-job1_started.
WARNING
Even truncated strings of the global condition prefixes must be unique or unpredictable results may occur. For example, do not define both a DA prefix and a DAY prefix because DA is a substring of DAY and therefore not unique.
3 In the From area, select the CONTROL-M installation(s) that should recognize
conditions with this prefix as global conditions. You can select more than one CONTROL-M name at a time. However, you must not exceed 512 characters in the From area. (To select all CONTROL-M installations, select the All checkbox in the From area.)
4 Click Add.
Global conditions
The CONTROL-M name is moved from the list on the left to the list on the right. If you selected All, an asterisk is displayed in the From CONTROL-M(s) column in the Global Conditions window when it is redisplayed.
5 In the To area, select the target CONTROL-M installation(s) where you want
conditions to be automatically added or deleted when the same condition is added or deleted in a source CONTROL-M specified in the From list. You can select more than one CONTROL-M name at a time. However, you must not exceed 512 characters in the To area. (To select all CONTROL-M installations, select the All checkbox in the To area.)
6 Click Add. The CONTROL-M name is moved from the list on the left to the list on
the right. If you selected All, an asterisk is displayed in the To CONTROL-M(s) column in the Global Conditions window when it is redisplayed.
7 Click OK. NOTE

Although it is possible to create any combination of global condition prefixes, BMC Software recommends that you: limit the global condition prefixes to very specific, less general prefixes that do not match large numbers of conditions refrain from defining prefixes that encompass a large number of CONTROL-Ms in the From and To fields The more general the prefix, the more stress is added to the system. This can slow down other requests and data transmissions. For more information about implementing global conditions efficiently, see Best practices on page 263, or contact CONTROL-M/EM Technical Support.
To modify an existing global condition definition: 1 In the Global Conditions window, select the prefix of the global condition to be
modified.
2 Click Update. The Global Condition Definition dialog box (Figure 91 on page 258)
is displayed.
3 Make the necessary changes as follows:
To add CONTROL-Ms to the From or To list, follow step 3 through step 6 in the procedure To create a new global condition definition: on page 258. To remove CONTROL-Ms from the From or To list, select the CONTROL-Ms in the right list and click Remove.
4 Click OK.
Chapter 6
259
Adding an anticipated CONTROL-M to a global condition
To delete a global condition definition:

In the Global Conditions window, select the prefix of the global condition definition to be deleted and click Delete. The Global condition definition is deleted.
Adding an anticipated CONTROL-M to a global condition

When you create or modify a global condition definition in the Global Condition Definition dialog box (Figure 91 on page 258), existing CONTROL-M installations are displayed in To and From selection lists, allowing you to select the desired installations. It may occur, however, that your site is planning on adding a new CONTROL-M installation, and you want to add that CONTROL-M to particular global condition definitions, even though that CONTROL-M is not yet functional and does not yet appear in the selection lists.
To add an anticipated CONTROL-M installation to an existing global condition definition: 1 In the Global Conditions window, select the global condition definition and click
Update. The Global Condition Definition dialog box (Figure 91 on page 258) is displayed.
2 In the Global Conditions Definition dialog box, click Add New CONTROL-M in
the From or To area. The New CONTROL-M Name dialog box is displayed. Figure 92 New CONTROL-M Name dialog box
3 Specify the name of the anticipated CONTROL-M installation and click OK. The
CONTROL-M installation name is added to the corresponding From or To list on the right side (not to the master list on the left side) of the Global Condition Definition dialog box.
260
Viewing (global) conditions for job nodes in the CONTROL-M/Enterprise Manager window
Viewing (global) conditions for job nodes in the CONTROL-M/Enterprise Manager window
You can view conditions, including global conditions, required for nodes in the Enterprise Manager window.
To view (global) conditions for job nodes 1 In the CONTROL-M/Enterprise Manager window, hold down the left mouse
button on the top or bottom arrow of a job node. The pop-up window (Figure 93) displays a list of the In/Out conditions for the node. This list indicates which CONTROL-M created the condition and whether the condition is a global condition. Figure 93 Condition List for a job node
The sources/targets of global condition additions and deletions are determined using information in the Global Conditions window.
Global condition logic and examples

A global condition is assigned the same condition date as the CONTROL-M/EM that triggered its creation. This must be taken into account when sending global conditions to target CONTROL-M installations in different time zones. For example, if a global condition is created in Rome on July 2 at 6:00 a.m., and is duplicated in San Francisco, its condition date in San Francisco is assigned as July 2, even though it was created on July 1, San Francisco time. Global conditions fail to work as expected if the condition is created in one CONTROL-M after the New Day procedure has run and then is submitted to another CONTROL-M, prior to the running of the New Day procedure for that CONTROL-M. When the new day procedure for the second CONTROL-M is run, it clears all old global conditions, including the new condition, which it perceives as old. This example illustrates the problem:
Chapter 6
261
Global condition logic and examples
EXAMPLE
Red (New day at 7:00) is the From CONTROL-M. Blue (New day at 9:15) is the To CONTROL-M. The job that prompts the global condition is run in the Red CONTROL-M and the global condition correctly submitted to the Blue CONTROL-M at 8:00. The New Day procedure is run at 9:15 and clears existing global conditions, including the one that was submitted at 8:00. The job in the Blue CONTROL-M that is dependent on the global condition does not run.
In the event of a temporary communication failure between CONTROL-M/EM and a CONTROL-M installation, global conditions are accumulated and transmitted when communication is resumed. The following examples illustrate how global conditions behave in a complex CONTROL-M network. They are based on information displayed in Figure 94. Figure 94 Example of global conditions in CONTROL-M installations
Examples
If prerequisite condition GL1_JOB_END is added in CONTROL-M ROME, the same condition is automatically added in CONTROL-M installations NY, LA, and SF. The Prerequisite Conditions window displays four different conditions called GL1_JOB_END, each belonging to a different CONTROL-M (ROME, NY, LA, and SF). However, if this condition is added in any CONTROL-M other than ROME, the addition is not automatically duplicated in other CONTROL-M installations. If CONTROL-M NY adds the condition GL1_JOB_END, it will not be automatically added in ROME (or anywhere else).
262
Best practices
If the prerequisite condition GL1_JOB_END is deleted in CONTROL-M ROME, CONTROL-M/EM deletes the condition GL1_JOB_END in CONTROL-M installations NY, LA, and SF (if the condition exists there). If condition GL1_JOB_END is created in CONTROL-M ROME but CONTROL-M SF is disconnected or downloading, CONTROL-M/EM creates this condition in NY and LA only, and sends the change to SF when SF is able to receive updates. If condition GLALL_OK is added or deleted in any CONTROL-M, the condition is automatically added or deleted in CONTROL-M installations PARIS and SYDNEY. The asterisk (*) in the From CONTROL-M field specifies all CONTROL-M installations. If condition GLNY_OK is added or deleted in CONTROL-M NY, the condition is automatically added or deleted in all other CONTROL-M installations. If a condition beginning with the GL2WAY prefix is added or deleted in either CONTROL-M HQ or CENTER1, the same operation is performed on the corresponding condition in the other CONTROL-M.
Best practices
This section provides recommendations for implementing global conditions between different CONTROL-M installations.
Frequent updates to a global condition (toggles)

If the status of a global condition frequently changes (is added and deleted) within a short period of time, the Global Conditions server may become overloaded and the global conditions may not be distributed correctly. To prevent this problem, find the appropriate balance for Global Conditions server processing by setting values using Global Conditions Server Parameters options from the root menu. These parameters define how the Global Conditions server should handle frequent updates to global conditions. For details, see the following menu options in the CONTROL-M/Enterprise Manager Administrator Guide:

Delete Time For Sent Conditions Method for Handling Conflicting Conditions The Mode for Handling Conflicting Conditions
Chapter 6
263
Best practices
Bi-directional global conditions

Global conditions can be bi-directional, meaning that if a global condition is added or deleted in one of several CONTROL-M installations, it is automatically added to or deleted from the others. However, the definition of bi-directional global conditions generates additional overhead and puts additional stress on system processing, particularly in the Global Conditions server. This can slow down other requests and data transmissions. For this reason, BMC Software recommends that you avoid implementing bi-directional global conditions. You can achieve the benefits of bi-directional global conditions using regular, one-way global conditions. This more efficient alternative involves:
definition of additional dummy jobs for maintaining (adding and deleting) global conditions definition of two global condition prefixes (instead of one), each representing a direction between the CONTROL-M installations definition of two extra dummy global conditions for triggering the maintenance functions performed by the two dummy jobs
A sample implementation is provided below, first using bi-directional global conditions and then by simulating the use of bi-directional global conditions.
Sample scenario
A set of jobs can only run if the companys intranet is up and running at all sites. Therefore, all sites (CONTROL-M installations) have cyclic jobs that check and update intranet status at regular intervals using global conditions. If a particular intranet site in the company is down, a job deletes the global conditions that indicate that the intranet is up and running. In this scenario, the company has two sites:

one CONTROL-M installation exists in Seattle another exists in London
In Seattle, a job called CheckS checks and updates conditions starting with the Intranet prefix (such as IntranetS-Up and IntranetL-Up). In London, a job named CheckL performs the same function. Addition and deletion of conditions with the Intranet prefix in either location should always occur in both locations.
264
Best practices
Using bi-directional global conditions (not recommended)

The following representation of the Global Conditions window illustrates a basic and intuitive way to define bi-directional global conditions. Prefix
Intranet
From CONTROL-Ms
Seattle, London
To CONTROL-Ms
London, Seattle
This definition specifies that addition and deletion of a condition that begins with the characters Intranet in either the Seattle or London site automatically generates the same update at the other site. This is a valid definition for bi-directional global conditions, but is not efficient.
Using regular global conditions (recommended)

For more efficient distribution and processing of global conditions, define jobs and global condition prefixes as follows.
The setup
Create the following job processing definitions.
Jobs CheckS Purpose In Seattle, this job checks intranet status and updates global conditions starting with the prefixes (defined below) accordingly. This job updates two global conditions (instead of one, Intranet, as was done in the sample above) with each global condition representing one direction. CheckS updates conditions with an West2East prefix. Updates to these conditions are passed towards the East to London. CheckL In London, checks intranet status and updates global conditions starting with the prefixes (defined below) accordingly. This job updates two global conditions (instead of one, Intranet, as was done in the sample above) with each global condition representing one direction. CheckL updates conditions with an East2West prefix. Updates to these conditions are passed towards the West to Seattle. MaintainS Dummy job processing definition in Seattle for removing global conditions that are no longer necessary; serves administrative and maintenance purposes only. MaintainS tracks, and deletes, unnecessary conditions by updating dummy global conditions. Dummy job processing definition in London for removing global conditions that are no longer necessary; serves administrative and maintenance purposes only. MaintainL tracks, and deletes, unnecessary conditions by updating dummy global conditions.
MaintainL
Chapter 6
265
Best practices
Define the following job global condition prefixes. Prefix

East2West West2East
From CONTROL-Ms
Seattle London
To CONTROL-Ms
London Seattle
Processing flow: an overview

The following figure provides an overview of the processing flow of jobs defined when implementing the recommended practice for simulating bi-directional global conditions. Each phase in the processing flow is numbered and described in detail under Processing flow: step-by-step on page 266.
Processing flow: step-by-step 1 The CheckS cyclic job in Seattle runs when the East2West-Maint global condition
is created (the first time, manually): checks intranet status creates a global condition named West2East-Check. The Global Conditions server passes this condition to London.
266
Best practices
2 The CheckL job is triggered by the creation of the West2East-Check In condition.

This job: checks intranet status. creates the East2West-Check condition deletes the West2East-Check condition locally (meaning, at the local CONTROL-M installation only), because West2East is a one-way prefix
3 The MaintS job, which waited for the creation of its In condition
East2West-Check, runs and: creates the West2East-Maint condition deletes the East2West-Check condition locally deletes the West2East-Check condition in both Seattle and London. Because this condition was already deleted by CheckL in London, processing is minimal
Chapter 6
267
Best practices
4 The MaintL job, which waited for the creation of its In condition West2East-Maint,
runs and: adds the East2West-Maint condition, which will trigger job CheckS in Seattle deletes the West2East-Maint condition locally deletes the East2West-Check condition in both Seattle and London. Again, because this condition was already deleted in Seattle, processing is minimal.
5 The cycle begins again. The CheckS job is again triggered by its In condition,
East2West-Maint (this time, not manually). When the CheckS job runs, it: checks intranet status recreates the West2East-Check condition, which will trigger job CheckL in London deletes the East2West-Maint condition locally deletes the West2East-Maint condition in both Seattle and London, with minimal effect on processing.
268
Best practices
6 The CheckL job is again triggered by its In condition, West2East-Check, and the
cycle continues. When the CheckL job runs, it: checks intranet status recreates the East2West-Check condition. deletes the West2East-Check condition locally deletes the East2West-Maint condition in both Seattle and London, with minimal effect on processing.
7 The cycle is repeated beginning with Step 3 above.
Chapter 6
269
Best practices
270
Chapter
This chapter describes how to view the communication status between CONTROL-M/EM components and CONTROL-M installations. It also includes instructions for maintaining this communication.
NOTE
This information is intended for the typical CONTROL-M/EM user. If more complicated communication issues arise, contact your CONTROL-M/EM administrator.
Communication with CONTROL-M installations

CONTROL-M/Enterprise Manager (CONTROL-M/EM) depends on a constant flow of information from CONTROL-M installations to present you with an up-to-date picture of the status of jobs. Operator requests and global conditions are transmitted back and forth between CONTROL-M/EM and the CONTROL-M installations. The Communication Status window displays the status of communication between each CONTROL-M installation and the CONTROL-M/EM workstation. This window can remain open while working in other CONTROL-M/EM windows.
To open the Communication Status window:

Choose Tools => Communications => Status. The Communication Status window is
displayed.
Chapter 7
271
Figure 95
Communication Status window
Each component in the communication path is represented graphically as described in Table 70. If a symbol is green, the relevant component is active. If a symbol is red, the relevant component is inactive. Table 70
Element No label
Communication Status window components

Icon Description A green check indicates that the CONTROL-M installation is enabled. A red X indicates that the CONTROL-M is disabled. When the gateway is restarted, CONTROL-M/EM attempts to communicate with the CONTROL-M.
CONTROL-M Workstation
Name of the CONTROL-M installation. CONTROL-M/EM workstation connected to the gateway (WS-GTW) for this CONTROL-M. If this symbol is red, communication is inactive at the workstation. CONTROL-M/EM gateway (WS-GTW) connected to the CONTROL-M. The communication route between the gateway (WS-GTW) and the CONTROL-M. Synchronization of the active environment with the Active Jobs file in the CONTROL-M. If this symbol is red, CONTROL-M/EM is not synchronized with the specified CONTROL-M installation.
Gateway Communication Sync
272
Table 71
Field Net Status
Communication Status fields

Description Status of communication between the CONTROL-M/EM workstation and the CONTROL-M installation. The following statuses appear in this field: Up The CONTROL-M is connected and available. The data displayed in the CONTROL-M/EM ViewPoint window may not necessarily be synchronized with the data in the CONTROL-M Active Jobs file (see Network communication on page 32). The workstation is attempting to reconnect to the CONTROL-M. The Active environment is not yet loaded. The workstation is attempting to connect to the CONTROL-M. The Active Jobs file cannot be accessed because either the New Day procedure or Active Jobs File Compress procedure is in progress at the CONTROL-M. Workstation is receiving a download from the CONTROL-M.
Reconnecting Initial
Formatting AJF
Downloading Last Update Remarks
Time the last message was sent from a CONTROL-M. This field is displayed in 24-hour clock format. If the Sync symbol is not green, this field displays the reason. One of the possible reasons is: Loading Jobs The CONTROL-M/EM Server is loading jobs from the CONTROL-M/Server database.
NOTE
The Communication Status window is automatically refreshed every two minutes. When a new CONTROL-M installation is added to CONTROL-M/EM using the Communication Administration window (see the CONTROL-M/Enterprise Manager Administrator Guide), the new entry is automatically displayed in this window the next time it is refreshed.
Click Refresh to manually refresh the Communication Status window.
Chapter 7
273
Communication between CONTROL-M/EM components
Communication between CONTROL-M/EM components

CONTROL-M/EM must be constantly connected to the GUI server. The GUI server handles communication between each GUI and other CONTROL-M/EM components.
Overview
If the connection to the GUI server fails, CONTROL-M/EM attempts to reestablish the connection using alternate servers. CONTROL-M/EM attempts to connect to the first available alternate GUI server defined in the Reconnection panel of the Options dialog box (see Reconnection panel on page 335).
If successful, the CONTROL-M/EM GUI continues to function, restoring ViewPoints as desired. The CONTROL-M/EM GUI Reconnect dialog box closes and a message in the status bar indicates that a communication problem was resolved. If unsuccessful, CONTROL-M/EM attempts to connect to the next server in the list. If CONTROL-M/EM cannot establish a connection with any of the alternate servers, it re-attempts connection with the servers at regular (user-defined) intervals, until the maximum number of allowed retries has been attempted. If a connection still cannot be established, CONTROL-M/EM displays a message notifying you that it is about to shut down.
By clicking Stop, you can stop the reconnection process to:

Modify reconnection settings (by clicking Settings in the Advanced dialog box). Terminate CONTROL-M/EM (by clicking Exit Application).
Using the CONTROL-M/EM GUI Reconnect dialog box

When the connection to the GUI server is lost, the following dialog box is displayed. Figure 96 CONTROL-M/EM GUI Reconnect dialog box
274
If reconnecting in Automatic mode, CONTROL-M/EM immediately attempts to reconnect to one of its alternate servers. (If reconnecting in Prompt mode, the user must first click Connect.) For additional options, and a more detailed view of the reconnect process, click Advanced. The following dialog box is displayed: Figure 97 CONTROL-M/EM GUI - Reconnect Advanced dialog box
Table 72 describes the operations that can be performed in the Reconnect dialog box. Table 72
Operation Connect
Reconnect operations
Description Starts the reconnection process. CONTROL-M/EM attempts to connect to the alternate GUI servers listed in the Connecting to: list. While the reconnect is in progress, this button toggles as the Stop button (see below).
Stop
Stops the reconnection attempt. At this point, you can modify reconnection settings if necessary or terminate CONTROL-M/EM. When the reconnect is stopped, this button toggles as the Connect button (see above).
Advanced
Alternates between hiding and displaying advanced options and details.
Exit Application Closes the CONTROL-M/EM GUI - Reconnect window and terminates CONTROL-M/EM. Settings Displays the Reconnection panel of the Options dialog box, so that you can modify reconnection settings. See Reconnection panel on page 335.
Chapter 7
275
276
Chapter
Reporting Facility
The Reporting facility allows you to define and generate reports to provide you with important information about your CONTROL-M installation. Beginning with CONTROL-M/EM version 6.2.01, the reporting facility uses the Crystal Report application to produce reports. Each report must be of a predefined report type (for example, Alerts report, Active Jobs report) provided with the facility. For details, see Available Report Types on page 309.
NOTE
Only users having Administrator privileges for a particular computer can generate reports on that computer.
Reporting Facility Basics

Report Definitions and Reports The Reporting facility differentiates between report definitions and their corresponding reports:
Report definitions (and report templates) A report definition defines a reports characteristics such as report title, data source, filtering criteria, and information fields displayed. Report definitions required for one-time use need not be saved. Report definitions intended for reuse are called report templates, and are saved in report template files.
Chapter 8
Reporting Facility
277
Starting the Reporting Facility
Reports A report is output that is generated and displayed for viewing. When you generate a report, the Reporting facility retrieves and organizes data according to the specifications found in the report definition (or template). When you save a report, it is written to a report (.rpt) file. Report files and report template files are saved locally.
Dynamic Report Definition (using Parameters) You can include variables in report templates, and supply the values for the variables when the report is generated. The report will then vary depending to the values supplied. You supply values either via pop-up dialogs (when you work online), or in an arguments file (when generating the reports in batch).
EXAMPLE
To allow dynamic specification of the relevant job name at runtime, define the Job Name
parameter in the report template with a variable (for example, Job Name Like <MyJobs>). At runtime, the user will supply a value (for example, J*) for the variable, and the report data will be retrieved for the corresponding jobs.

To start the Reporting facility 1 In Microsoft Windows, choose Start => Programs => CONTROL-M Enterprise
Manager 6.2.01 => Reporting Facility. The CONTROL-M/EM Reporting Facility login window is displayed.
2 Log in.
The Reporting Facility Start Page window is displayed (Figure 98).
278
Figure 98
Reporting Facility Start Page window
The Start Page contains the following areas:
Create Report from Template to generate a new report from an existing template. Opening Existing Report to view an existing report.
Chapter 8
Reporting Facility
279
Generating a report
Generating a report
To generate a report 1 In the Reporting Facility Start Page, select a template in the Create Report from
Template area (Figure 98).
TIP
The last four templates you used to generate a report are listed at the top. All defined templates are listed beneath these, grouped by type. Alternative methods for running a report are described in Alternative methods for selecting a report template on page 281.
2 If the report was defined with variables that require input values at time of report
generation, the Enter Parameter Values dialog box (Figure 99) is displayed. If it is displayed, do the following for each parameter listed in the Parameter Fields area:
A Select a parameter. B Specify a value in the Discrete Value field, and click OK.
Figure 99 Enter Parameter Values dialog box
A new report is generated from the template and displayed in the Report Preview Window (Figure 101 on page 282).
280
Alternative methods for selecting a report template
Alternative methods for selecting a report template

As an alternative to performing step 1 on page 280, you can generate a report by selecting a report template from the Report Template Manager window. For details, see Working with Report Templates in the Report Template Manager on page 303. You can also use the following alternative set of steps to select a report template for generating a report:
1 Do either of the following:
In the Reporting facility toolbar, click the New ( File => New menu option.
) button or select the
or
In the Start Page only, click Create report with new template (located near the bottom of the window under the Create Report from Template area).
The New Report dialog box is displayed. The contents of the lower area of the dialog box vary according to your selection in the Create a New Report area.
2 In the Create a New Report area, select Generate Report From a Template.
Figure 100 illustrates what the New Report dialog box looks like after you have selected Generate Report From a Template. The lower area of the dialog box lists available templates. Figure 100 New Report dialog box Generate Report From a Template
3 In the Choose a Template area, double-click the desired template.
Chapter 8
Reporting Facility
281
Displaying and working with reports

When you generate a report, it is automatically displayed in the Report Preview window (Figure 101 on page 282). You can also display any previously run report that has been saved.
To display a previously run report 1 Do either of the following:
In the Reporting facility toolbar, click or select the File => Open menu option. Browse to and select the report for viewing.
or
In the Reporting Facility Start Page, select the report in the Open Existing Report list box (Figure 98).
TIP
The Open Existing Report list box displays the names of the last four report files you opened or saved. You can browse to additional reports stored on your computer or network by clicking More Reports ... in the list box.
The selected report is displayed in the Report Preview window. Figure 101 Report Preview window
282
The Report Preview window consists of the following panes.

Group Tree (left pane) - displays the list of groups in the report. Report pane (right pane) - displays report pages, one page at a time.
A tab (in the window task bar) for each opened report allows you to toggle between reports. Tabs list either the report title or file name, depending on your configuration.
NOTE
An asterisk following the name in the tab indicates that the data has not been saved (that is, the report is new or has been refreshed).
Note that in the Report Preview window, you can:
refresh the data displayed in the report using the Refresh button ( selecting the Edit => Refresh Report Data menu option.
) or by
toggle between showing and hiding the Group Tree by clicking the toggle button ( ) or by selecting View => Group Tree. jump to the display for a particular group in the Report pane by clicking its name in the Group tree. navigate through report pages using the First ( ), Back ( ), Next ( ), and Last ( ) navigation buttons, or through the corresponding options in the Edit => Navigate menu. go to a specific report page using the Go To button ( Edit => Go To. perform a text search using the Find button ( ) or selecting
) or selecting Edit => Find.
export the report to a file. For details, see Exporting reports on page 283. save your current report as a template by clicking the Save as Template button ( ) or by selecting File => Save As Template.
Exporting reports
You can export a displayed report from the Report Preview window using the Export button ( ) or selecting File => Export. (You can also export a report using the emreportscli utility. For details, see Generating and exporting reports in batch on page 308.) Exported files are saved locally. Exported reports can later be imported into other reporting applications or data manipulation tools.
Chapter 8 Reporting Facility 283
Defining Report Definitions and Templates
Available export file formats are:

PDF Excel Excel (Data only) CSV HTML XML Word Tab-separated text
Defining Report Definitions and Templates

When creating report definitions and templates, consider the following:
If you expect to run the report only once, you can create the report definition without defining a template. If you expect to generate the report more than once, you can define a report template. If you plan to use different source data criteria (for example, a different source CONTROL-M, or different filtering criteria) whenever you regenerate the report, you can: define dynamic parameters that allow you to specify the desired sources at runtime, or define a different report template for each data source (so that runtime input is not required).
When defining a report template, you can: build the report template from scratch, or copy a similar report template and modify it as needed.
The Reporting facility provides a fixed and predefined set of report types (for example, Alerts Report or Prerequisite Conditions Report), and each template or report that you define must be of one of these predefined types. Templates and reports are defined using the Report Wizard.
284
Defining a New Report Template
Defining a New Report Template

To define a new report template 1 In the Report Template Manager (Figure 119 on page 303), select the template and
click the New Template button ( ) in the toolbar. The New Template dialog box is displayed (Figure 102). Figure 102 New Template dialog box
In the New Template dialog box:
the left pane displays several report categories representing different types of data environments (for example, Active or Definition environment). the right pane displays the report types available for a particular category. (The report type display varies according to the selected category.) For a brief description of available report types, see Available Report Types on page 309.
2 In the left pane, select the appropriate category. If you are not sure which, you can
select All Reports, which will result in all report types being displayed in the right pane.
3 In the right pane, select the report type. 4 Enter a name for the report (template) that you are creating and click OK.
The first panel of the Report Wizard (the General panel) is displayed (Figure 104 on page 287).
Specifying Report Definition Criteria in the Report Wizard
5 To define the template, fill in fields of the report wizard panels. For instructions on
filling in the report wizard, see Specifying Report Definition Criteria in the Report Wizard on page 286.

The Report Wizard consists of a series of panels that are used for creating reports, and creating or modifying templates. The wizard is displayed whenever you perform any of the following procedures:

To create a one-time report on page 300 To modify an existing template on page 300 To define a new report template on page 285
The title bar of Wizard panels identifies both the report type (for example, Prerequisite Condition), and what you are editing (a report template). The name of the panel (for example, General) appears below the title bar. This is illustrated in Figure 103. Figure 103 Wizard Title Bar and Panel Name For Report Template Definition
The first panel of the Report Wizard is the General panel. The wizard contains the following panels: General, Data Source, Filter, Columns, Group By, Sort, Style, and Summary, though depending on the report type, certain panels may not appear in the Wizard. A particular panel (for example, General) generally contains the same fields, regardless of whether you are editing a report or template, and regardless of report or template type. (Exceptions will be noted in the descriptions.)
To use the Report Wizard to define a report template (or report definition) 1 Fill in the fields of each panel. Click Next to display the next panel. 2 When you are done defining the report or template, click Finish.
286
NOTE
Some panels have a checkbox for setting the defined values as defaults. This refers to new definitions of the same report type.When you set values as defaults, they will appear the next time you open the Wizard to create a new template (or report) of the same type.
The Report Wizard panels are described on the following pages. For purposes of illustration, Report Wizard panels for the Prerequisite Conditions Report Template will be used and described.
General panel
The General panel (Figure 104) is used for defining general information about the report. Figure 104 Report Wizard General panel
To fill in the General panel

Specify a report title, author, and a general description. When filling in the description, press Ctrl + Enter to move to the next line in the description area. Both the title and general description will appear at the beginning of the report.
Chapter 8
Reporting Facility
287
Data Source panel

The Data Source panel (Figure 105) is used for defining from where (which CONTROL-Ms) the report data is taken. This panel is only displayed for Active report types.
NOTE
The Data Source panel for the Active Links report has special features. For details, see Data Source panel for the Active Links report on page 297.
Figure 105 Report Wizard Data Source panel
288
To Fill in the Data Source panel 1 From the source list of CONTROL-Ms on the left, select the name of the source
CONTROL-M, and click the right arrow to move it to the target list. Repeat as needed. (You can remove a CONTROL-M from the target list by selecting it and clicking the left arrow.)
2 To add a mask: A Select the CONTROL-M in the target list and click Add Mask.
The Add Mask dialog box is displayed. Figure 106 Add Mask dialog box
B Specify the CONTROL-M name mask using * and/or ? wildcards. 3 Repeat Steps 1 and 2 for each CONTROL-M to be added as a data source. 4 Select from which network the report data will be loaded:

Current Active network Latest Archived Network Archived Network from the selected date
Filter panel
The Filter panel (Figure 107) is used to specify the filtering criteria for which data are retrieved.
NOTE
The Filter panel for the Links Definition report has special features. For details, see Filter panel for the Links Definition report on page 298. The Filter panel for the Audit report also has special features. For details, see Filter panel for the Audit report on page 299.
Chapter 8
Reporting Facility
289
Figure 107 Report Wizard Filter panel
To Fill in the Filter panel: 1 In the Field Name field, select the field that you want to use for filtering. You can
specify the same field name on more than one line.
2 In the Operator field, select the operator (for example, = or >) to be used with the
value specified in the next substep.
NOTE
The LIKE and = operators work the same, except that the = operator treats * and ? characters specified in the value as literals the LIKE operator treats * and ? characters specified in the value as wildcards
3 If the value to be used for filtering on the field should be dynamically specified
when the report is run, click Param. In this case, the Value/Param Name field defines the parameter name to be used to prompt you for a value at run time. And by default (that is, if no previous Value/Param Name was set as the default), the Value/Param Name field value will automatically be set to the Field Name (for example, Odate). You can modify the value in the Value/Param Name field.
4 If you did not click Param, specify in the Value/Param Name field the value to be
used for filtering the field. The Value/Param Name field allows you to specify * and ? wildcards, the ! symbol for Not logic, and the , symbol for Or logic. Example
Jobname LIKE A*,B* Application LIKE !APPL*
Explanation: Retrieve all jobs whose jobname begins with A or B, but whose application names do not start with APPL.
NOTE
If you specify wildcard or special logic symbols in the Value/Param Name field, you must set the operator to LIKE (or these symbols will be treated as literals).
5 Click Fix for any entries that you want to appear in the panel the next time you
create a new report or template of this type.
6 Repeat steps 1 through 5 for each field that should be used for filtering. And logic
is assumed between multiple lines (fields).
Fields panel
The Fields panel (Figure 108) is used to define which report fields will appear in the report.
Chapter 8
Reporting Facility
291
Figure 108 Report Wizard Fields panel
To define the fields to be in the report: 1 Select the field in the source (left) list box, and click the right arrow to copy it to the
defining (right) list box. (To remove a field from the report, select it in the right list box, and click the left arrow.)
2 Repeat step 1 for each field that should appear in the report. TIP
To move a field up or down (that is, to re-sequence fields) in the target list, select the field (in the target list), and click the up or down arrow above the list.
Group By panel
The Group By panel (Figure 109) is used to define by which fields the report rows will be grouped. Group By criteria should not be confused with Sort criteria (defined in the next panel). Group By criteria provide the following functionality:
Group By criteria create branches and subbranches in a navigation tree.
292
Group By criteria supersede Sort criteria. That is, data are first organized according to Group By criteria, and only then, within the lowest group, are they sorted according to Sort criteria.
Figure 109 Report Wizard Group By panel
To define Group By criteria 1 Select the field in the source (left) list box, and click the right arrow to copy it to the
target (right) list box. (To remove a Group By criterion, select it in the right list box, and click the left arrow.)
2 Repeat Step 1 for each field that should be used for grouping. NOTE
The Group By panel defines a grouping hierarchy. A Group By field lower down in the target list is a subgroup of a Group By field higher up in the target list.
TIP
To move a field up or down (that is, to re-sequence the fields) in the target list, select the field (in the target list), and click the up or down arrow above the list.
Chapter 8
Reporting Facility
293
Sort panel
The Sort panel (Figure 110) is used to define by which columns the report will be sorted. You can specify up to three sort fields in ascending or descending order. Figure 110 Report Wizard Sort panel
1 In the Sort By field, select the field to sort on, and click whether the sort should be
in ascending or descending order.
2 Optionally, repeat the process for the second and third sort fields.
294
Style panel
Predefined report styles are provided with the product. The Style panel (Figure 111) is used to select in which style the report will be displayed. When you select a style, it appears in a preview area in the panel, allowing you to determine whether you want to keep your selection or select a different style. Figure 111 Report Wizard Style panel
1 Select the style and check the results in the Preview area. Change the selection if
you do not like the results.
Chapter 8
Reporting Facility
295
Summary panel
The Summary panel (Figure 112) provides a summary of your report definition. Figure 112 Report Wizard Summary panel
(The Summary panel has different fields at the bottom if you are defining a report definition instead of a report template. For details, see Defining a one-time report on page 300.
1 To run the report immediately upon exiting the Report Wizard, click the Yes
selection button near the bottom of the panel.
NOTE
The Yes or No value you choose is saved and used as a default the next time you edit a template in the Report Wizard.
2 Click Finish.
The template is defined and saved. You can use it whenever you want to run the report.
296
Filling in special Report Wizard panels

Several Report Wizard panels contain unique fields for certain reports. These panels are displayed and described in this section.
Data Source panel for the Active Links report

Figure 113 illustrates the Data Source panel for the Active Links report. Figure 113 Report Wizard Data Source panel for the Active Links report
The Data Source panel for the Active Links report has a checkbox called Produce Global Links Report. If this box is checked, the CONTROL-M list areas appear twice; otherwise, they appear once.
1 To produce a Global Links report: A Ensure this checkbox is checked. B In the top list, indicate the source CONTROL-Ms. C In the bottom list, indicate the target CONTROL-Ms.
In this case, the output is generated according to the Global Links definition.
Chapter 8
Reporting Facility
297
2 If you do not want to produce a Global Links report, ensure that this checkbox is
not checked.
3 Fill in the rest of this panel. Filter panel for the Links Definition report
Figure 114 illustrates the Filter panel for the Links Definition report. Figure 114 Report Wizard Filter panel for the Links Definition report
The Filter panel for the Links Definition report has a Produce Global Links Report checkbox.
To produce a Global Links report 1 Ensure that the Produce Global Links Report checkbox is checked. 2 Fill in the rest of this panel.
298
Filter panel for the Audit report

Figure 115 illustrates the Filter panel for the Audit report. Figure 115 Report Wizard Filter panel for the Audit report
The Filter panel for the Audit report contains special fields, Audit Type and Audit Operation.
1 In the Audit Type field, select which type of Audit data should be retrieved, or
select <All> if all Audit types should be included.
2 In the Audit Operation field, select for which type of Audit operation data should
be retrieved, or select <All> if all operations of the selected Audit type should be included. The available list of operations changes according to the selected Audit type. The list of Field Names changes according to the selected operation. If Audit Type <All> is selected, the Audit Operation field is disabled.
3 Fill in the rest of this panel.
Chapter 8
Reporting Facility
299
Editing an existing report template
Editing an existing report template

To modify an existing template 1 In the Report Template Manager (Figure 119 on page 303), double-click the
template, or select the template and click the Edit Template button ( toolbar. ) in the
The Report Wizard is displayed. The panels of the Report Wizard display the currently defined values for the template you selected. For details on using the Report Wizard, see Specifying Report Definition Criteria in the Report Wizard on page 286.
2 Modify only those values in the Report Wizard that need modification. To jump to
a particular panel, click on the panel name in the left pane of the wizard.
3 When you finish modifying the template, click Finish.
Defining a one-time report

If you plan to use a report only once, you can define it as a report definition instead of as a report template.
To create a one-time report 1 In the Start Page only, click Create report with new template (located near the
bottom of the window under the Create report from template list area). Alternatively, in the Reporting Facility toolbar, click the New ( ) button or select the File => New menu option. The New Report dialog box is displayed. The contents of the lower area of the dialog box vary according to your selection in the Create a New Report area.
2 In the Create a New Report area, select Create Report Using the Report Wizard.
Figure 116 illustrates what the New Report dialog box looks like after you have selected Create Report Using the Report Wizard. The lower area of the dialog box is called Choose a Report Type.
300
Figure 116 New Report Dialog Box Create Report Using the Report Wizard
In the Choose a Report Type area:
the left pane in the dialog box displays several report categories representing different types of data environments (for example, Active or Definition environment). the right pane displays the reports types available for a particular category. (The report type display varies according to the selected category.) For a brief description of available report types, see Available Report Types on page 309.
3 In the left pane, select the appropriate category. If you are not sure which, you can
select All Reports, which will result in all report types being displayed in the right pane.
4 In the right pane, select the report type.

The Report Wizard is displayed. The title bar of the Report Wizard panel indicates that you are editing a Report instead of a Report Template (Figure 117). Figure 117 Report Wizard Title Bar and Panel Name For Report Definition
Chapter 8
Reporting Facility
301
5 Fill in fields of the report wizard panels. For details on using the report wizard, see
Specifying Report Definition Criteria in the Report Wizard on page 286. Note that the Data Source and Fields panels of the report wizard each contain a checkbox that allows you to set the fields selected in that panel as defaults when you subsequently define new reports or templates of that report type. For example, the checkbox for the Data Source panel looks as follows:
The Summary panel for a (one-time) report definition is different than the Summary panel for a report template. Figure 118 illustrates the Summary panel for a report definition. The checkbox at the bottom of the panel enables you to save the report definition as a report template (even though you initially planned the report definition for one time use). Figure 118 Report Wizard Summary panel for a Report Definition
TIP
To save the report definition as a report template, click the Save report as template checkbox and specify a template name.
6 Click Finish.
302
Working with Report Templates in the Report Template Manager
Working with Report Templates in the Report Template Manager

The Report Template Manager is used for managing report templates. You can perform the following tasks from the Report Template Manager:
edit an existing template. For details, see To modify an existing template on page 300. define a new template. For details, see To define a new report template on page 285. copy a template. For details, see To copy a template on page 304. delete a template. For details, see To delete a template on page 304. generate a report from a selected template. For details, see To generate a report from its template on page 304.
To display the Report Template Manager 1 In the Reporting facility toolbar, click the Report Template Manager button (
or select the Tools => Report Template Manager menu option. The Report Template Manager is displayed (Figure 119). Figure 119 Report Template Manager )
Chapter 8
Reporting Facility
303
Setting Defaults
The Report Template Manager lists your available templates, grouped by category and report type.
To copy a template 1 In the Report Template Manager, select the template, and click the Copy template
button ( ) in the toolbar.
2 In the dialog box that is displayed, enter a name for the template copy.
The template copy is added to the list in the Report Template Manager window.
To delete a template 1 In the Report Template Manager, select the template, and click the Delete template
button ( ) in the toolbar.
2 If you are prompted for confirmation (depending on site defaults), confirm the
deletion. The template is deleted.
To generate a report from its template 1 In the Report Template Manager, select the template, and click the Generate report
button ( ) in the toolbar. The report is generated.
Setting Defaults
You can customize certain Reporting facility defaults using the facilitys Options panels.
To customize Reporting facility defaults 1 Select the Tools => Options menu option. 2 Modify the default values displayed in the Options panels and click OK.
The Options panels and their fields are described on the following pages.
304
Setting Defaults
Environment panel
The Environment panel (Figure 120) contains several general default settings for the Reporting facility. These default settings are described in Table 73. Figure 120 Reporting facility Environment panel
Table 73
Area Field
Environment panel (Part 1 of 2)

Description Settings that apply to report tabs in the task bar of the Preview window. If checked, (default), tabs for each open report (and the Start Page) are displayed in the task bar at the bottom of the screen. If not checked (so that tabs are not displayed), you can still toggle between open reports through the Window menu option.
Report Tabs Display Report Tabs
Use flat buttons
Determines the appearance of the tabs. When not checked, tabs appear more raised and distinct. When checked, tabs appear as separate areas on a flat bar. If checked, the report icon ( displayed in the taskbar. ) appears in the report tabs in
Display Report Icons Close Report on Double Click
If checked, double clicking the report tab closes the report. Depending on other options, a confirmation prompt may be displayed.
Chapter 8
Reporting Facility
305
Setting Defaults
Table 73
Area Field
Environment panel (Part 2 of 2)

Description If checked, the full report path will be displayed in a tooltip for the tab when you pass the cursor over the tab. Determines what text will appear in the tab. Valid values: Filename name of the report file Title report title (may be abbreviated)
Display full path in tooltips Display Report
Viewer panel
The Viewer panel (Figure 121) contains several display default settings for the Reporting facility Preview window. These default settings are described in Table 74. Figure 121 Reporting facility Viewer panel
Table 74
Area Field
Viewer Panel (Part 1 of 2)

Description Defaults for the Preview window. If checked, a border is displayed around the report. If checked, a background edge (between the frame and the top of the page of the report) is displayed. If checked, the last field that would appear in the viewer is not be displayed if it would be truncated.
Preview Pane Display Border Display Background Edge Conceal Last Shown Fields if Truncated (Upon Generation)
306
Setting Defaults
Table 74
Area Field
Viewer Panel (Part 2 of 2)

Description Defines the Zoom Level in the Preview Panel. Defines the Default Zoom Level when viewing reports. Select any of the following levels as the default:

Zoom Level Default Viewer Zoom Level
Zoom Factor: n% sets a fixed percentage zoom. Fit Page Width page width fills the screen. (It may be necessary to scroll the length of the page.) Fit Whole Page full page is displayed in the screen.
Confirmations panel
The Confirmations panel (Figure 122) determines which confirmation requests and warnings should be displayed for various actions. Figure 122 Reporting facility Confirmations panel
To adjust your confirmation settings 1 To define that a confirmation prompt or warning should be displayed in a
particular situation, check the relevant check box.
2 To reassign the default settings as originally provided, click Restore Defaults.

Generating and exporting reports in batch
Generating and exporting reports in batch

The emreportcli command line utility generates reports in a selected format. This utility runs only on Microsoft Windows in batch mode.
NOTE
You are required to specify CONTROL-M/EM server login information when you invoke this utility.
Input arguments file

Input for the utility is an arguments file containing the XML specifications for the report to be generated, including all required parameters. The following sample XML arguments file is provided at em_home\Data\Reporting\sample_args.xml. A list of possible elements and values for the arguments is provided in the DTD file: em_home\Data\Reporting\emreportcli.dtd.
EXAMPLE
<!DOCTYPE ReportDefinitions SYSTEM "emreportcli.dtd"> <ReportDefinitions> <ReportDefinition> <SourceFile templateName="alerts3"/> <OutputFile type="PDF" filepath="D:\MyAlerts3.pdf"/> <Parameters> <Parameter name="MY_PARAM" value="job*"/> <Parameter name="Application" value="a*"/> </Parameters> </ReportDefinition> </ReportDefinitions>
To use the emreportcli report generation utility 1 Log in as a CONTROL-M/EM user. 2 Open a command prompt window. 3 Enter the following command and press Enter.
emreportcli [{(-U db_user -P db_pass) | -pf password_filename}] -s EM_server -arg XML_arguments_file
NOTE
You can specify the DBO user name and password on the command line, in a password file, or as the response to an online prompt.
The parameters in this command is described in Table 75.

Available Report Types
Table 75
Parameter db_user db_pass password_ filename
emreportcli utility parameter

Description CONTROL-M/Enterprise Manager database user name. CONTROL-M/Enterprise Manager database user password. Flat file containing an unencrypted username and password in the format: user=username password=password Note: If both -U and -pf are specified, an error message is generated. If neither is specified, an online prompt is issued for the CONTROL-M/EM database owner name and password. Host name of the CONTROL-M/EM Server. Note: If you need to address a GUI Server and multiple GUI Servers exist, set this parameter to the logical name of the relevant GUI Server. Full path and name of the input arguments file.
EM_server
XML_ arguments_ file
Available Report Types

Report types are categorized as follows:

Active data for the report are taken from the Active environment Definition data for the report are taken from the Definition environment General included in this category are the Alerts report and Audit report.
For convenience, there is also an All category that lists all report types. Available report types are described on the following pages, grouped by category.
Active Report Types
Active Jobs report lists all jobs and job details determined by selection and display criteria. It also includes a count of the number of jobs contained in the report. Note that in the case of multiple jobs, these can from the same or different scheduling (or group scheduling) tables. Prerequisite Conditions report lists conditions according to selection and display criteria. This report is also called the Conditions report. The report is similar to the information displayed when Resource Map => Prerequisite Conditions is chosen from the CONTROL-M/Enterprise Manager GUI.
Chapter 8
Reporting Facility
309
Definition Report Types
Control Resources report lists Control resources and their attributes according to selection and display criteria. The information in the report is similar to the information displayed in when Resource Map => Control Resources is chosen from the CONTROL-M/Enterprise Manager GUI. Quantitative Resources report lists Quantitative resources and their attributes according to selection and display criteria. The report is similar to the information displayed when Resource Map => Quantitative Resources is chosen from the CONTROL-M/Enterprise Manager GUI. Active Links report shows all the links (dependencies) defined between all jobs or between selected jobs, as determined by selection and display criteria. Global conditions are also included in this report. For example, you can list all the dependencies and global conditions that are defined in a specific data center, or only those defined between two groups. Active Group Errors report performs validity checks and lists those groups, applications, scheduling tables or group scheduling tables that contains only one job. A group with only one job can be valid, but the list may reveal spelling errors in the job definitions Group field. For example, assume a group named SALARY, which is made up of a number of jobs. A new job, JOB_X, is added to this group, but the user specified a group called SALARIES. This generates a new group named SALARIES with a single job JOB_X. Active Loop Errors report performs validity checks on the current network and lists any job that contains matching IN and OUT conditions (with + sign). Active Manual report performs validity checks and lists any IN condition which is not defined as an OUT condition of another job. conditions are also included in the list report because manual conditions have no corresponding OUT conditions, but listed conditions may also reveal omissions and spelling errors.
Definition Report Types
Job Definitions report lists all jobs and job details determined by selection and display criteria. It also includes a count of the number of jobs contained in the report. Note that in the case of multiple jobs, these can from the same or different scheduling (or group scheduling) tables. Links Definition report shows all the links (dependencies) defined between all jobs or between selected jobs, as determined by selection and display criteria. Global conditions are also included in this report. For example, you can list all the dependencies and global conditions that are defined in a specific data center, or only those defined between two groups.
310
General Report Types
Definitions Group Errors report performs validity checks and lists those groups, applications, scheduling tables or group scheduling tables that contains only one job. A group with only one job can be valid, but the list may reveal spelling errors in the job definitions Group field. For example, assume a group named SALARY, which is made up of a number of jobs. A new job, JOB_X, is added to this group, but the user specified a group called SALARIES. This generates a new group named SALARIES with a single job JOB_X.
Definitions Loop Errors report performs validity checks and lists any job (active and definition) that contains matching IN and OUT conditions (with + sign). Manual Definitions report performs validity checks and lists any IN condition which is not defined as an OUT condition of another job. Though manual conditions normally have no corresponding OUT conditions, the listed conditions may nevertheless reveal omissions and spelling errors.
General Report Types
Alerts report lists alerts sent to the Alerts window. Audit report lists the results of auditing CONTROL-M/EM server for operations of a selected audit type.
Sample Outputs
Several sample report templates are provided with the Reporting facility during installation. When you generate reports with these templates, you may be prompted, in some cases, to supply input parameter values. For details on supplying parameter values, see step 2 under Generating a report on page 280. The following figures illustrate some of these reports.
Chapter 8
Reporting Facility
311
Sample Outputs
Figure 123 Job Definition report
Figure 124 Audit report
312
Converting Old Reports
Figure 125 Active Jobs report
Figure 126 Alerts Report

A menu option in the Start Page allows you to migrate (convert) old report definitions (from versions CONTROL-M/EM versions 6.0.xx and 6.1.xx) to definitions supported by a CONTROL-M/EM versions 6.2.01 and higher.
To migrate old reports 1 In the Reporting facility, select Tools = Convert/Import Old Reports. 2 In the Import Old Reports dialog box that is displayed, specify, or browse to and
select, your old CONTROL-M/EM home directory (and click OK). The display area lists your old reports, grouped by report type (Figure 127). You can expand or collapse the display.
Chapter 8
Reporting Facility
313
Figure 127 Import Old Reports dialog box
3 Select or report types that you want imported, and click Import.
The selected reports are converted and migrated to your current CONTROL-M/EM.
314
Chapter
Archived ViewPoints and Playback

The Archived ViewPoints and Playback features enable you to see the job information from a previous day in CONTROL-M. In this context, a day means the timeframe within which all jobs in an Active Job file are run.
An Archived ViewPoint is a static display of all the information on jobs that ran on a data center in one day. Jobs are displayed as they were at the end of that day. A Playback is a simulation of the production environment. It is displayed much like a recording of the events and jobs run in a specified day, and shows jobs as their status changes during the day.
These features help the user to review, track, and analyze problems of previous days. Both the Archived ViewPoint and the Playback information are saved automatically by CONTROL-M/EM.
NOTE
The Archive Net and Playback information remains saved for as long as specified in the MaxOldDay and MaxOldTotal parameter values. For more information, see the CONTROL-M/Enterprise Manager Administrator Guide or consult your system administrator.
The following topics and tasks are discussed in this chapter:
Archived Nets and Archived ViewPoints Playback
Chapter 9
315
Archived Nets and Archived ViewPoints
Archived Nets and Archived ViewPoints

An Archived Net is the data, conditions, and resources of jobs that were in the Active Jobs file of one data center during a specific day. Archived Nets are saved in the CONTROL-M/EM database. An Archived Net includes the recording of job changes, which can be played back much like an audio recording. For more information, see Playback on page 320.
NOTE
The term end of a day refers to each time a CONTROL-M/Server has a New Day procedure that resets its Active Jobs file.
CONTROL-M/EM automatically downloads the Active Net of each data center at the beginning of each working day to the CONTROL-M/EM database. The previous Active Net information in the database then becomes an Archived Net.
NOTE
The CONTROL-M/EM Administrator determines the length of time for which Archived Nets are saved in the system. For more information, see the CONTROL-M/Enterprise Manager Administrator Guide.
Selecting and displaying Archived ViewPoints

You can use the Open Archived ViewPoint option to select and display Archived ViewPoints. The ViewPoint Wizard window can be opened at any time during a CONTROL-M/EM session.
NOTE
This menu item is disabled if the user is not authorized to open Archived ViewPoint. For more information, see the CONTROL-M/Enterprise Manager Administrator Guide.
316
To Select and display Archived ViewPoints: 1 In the CONTROL-M/EM, select File => Open Archived ViewPoint.... The Open
Archived ViewPoint Wizard is displayed. Figure 128 Open Archived ViewPoint Wizard
Table 76 describes the columns that are displayed in the Nets list in the Open Archived ViewPoint Wizard. Table 76
Column Heading Net Name Date
Columns in the Open Archived ViewPoint Wizard

Description Name of the Archived Net. The date of the Archived Net in the data center. This date can vary from the Start Time and End Time dates (see below) due to various reasons, including differences in time zones and differently specified New Day procedures. The start time (and date) of the Archived Net. Note: The time is taken from the computer where the Gateway ran. The end time (and date) of the Archived ViewPoint. Note: The time is taken from the computer where the Gateway ran. The time span of the Archived Net.
Start Time End Time Duration
CONTROL-M Data center.
2 Select a data center from the CONTROL-M drop-down list.
Chapter 9
317
3 Select a Net from the Nets list, and click Next. The following window is displayed.
Figure 129 Open Archived ViewPoint Wizard second window
4 Select the ViewPoint definition you wish to display. NOTE

Only one Archived Net can be opened at a time in the Archive ViewPoint window. However more than one ViewPoint showing information from the same Archived Net can be displayed at one time, using the View => View Selection and Neighborhood =>Open ViewPoint options. For more information, see Chapter 2, Viewing the production environment.
5 Click Dynamic Filter to set filtering criteria in order to display the jobs as you
require, in the Archived ViewPoint. For more information about Dynamic filtering, see Creating and modifying filters on page 139. The selected Archived ViewPoint is displayed in the CONTROL-M/EM GUI.
NOTE
If the total number of Archived jobs in the GUI server exceeds the value specified in the LimitArchiveJobsInMem system parameter, the ViewPoint will not be displayed. For more information, see the CONTROL-M/Enterprise Manager Administrator Guide.
318
The following job actions are available in the Archived ViewPoint window.
NOTE
These actions are also available during Playback.
Log Sysout Properties Activate Application Enhanced Why Neighborhood Open View Selection Network Neighborhood ViewPoints Critical Path
Sysout and Log are available only if there is communication between CONTROL-M/EM and the respective CONTROL-M/Servers. In addition, the following applies:
Sysout and Log will be available for jobs running under CONTROL-M for MVS version 6.2.00 or later. Sysout will be available for other CONTROL-M jobs in CONTROL-M 6.2.00 or later.
Chapter 9
319
Playback
Playback
The Playback feature allows you to review past production events by playing them back in the Archived ViewPoints window. You can also stop the playback at any stage in order to analyze the Archived ViewPoint, and the status of the jobs at that point in time. On the Playback toolbar are buttons for playing, fast forwarding, rewinding, playing backwards, and stopping the production flow replay. You can review events from a specific time, second by second, or from event to event, at the speed you require. During the playback, all facilities provided in the CONTROL-M/EM ViewPoint window, such as management by color, navigation techniques, and selection facilities, are available.
EXAMPLE
The Playback window can be used by the system manager every morning to review the previous nights events.
Playing back archived events

You can use this procedure to play back events that were archived.
NOTE
If the Alerts window opens during Playback, it displays alerts from the current production Environment and not from the archive that is currently being played back. This ensures that the user is always notified when an alert occurs even while the user is using the Playback Facility.
Before You Begin

Select and display an Archived ViewPoint. For more information, see Selecting and displaying Archived ViewPoints on page 316.
NOTE
Hold, Free, Delete, Undelete, and Zoom and Save changes are not displayed in playback because they are not saved in the playback recording.
320
To use the Playback feature: 1 In the CONTROL-M/EM GUI, choose Tools => Playback. The following window
is displayed, showing the playback toolbar that is added to the CONTROL-M/EM GUI. Figure 130 Playback toolbar displayed in the CONTROL-M/EM GUI
2 Use the function buttons in the playback window to play back the events recorded
in the selected Archived ViewPoint. Table 77 describes the function buttons available in the Playback toolbar.
Chapter 9
321
Table 77
Function
Playback toolbar functions

Icon Description Go to the beginning of playback. Causes the time and date to display the start time. Go back one event. Go forward one event. Go to the end of playback. Causes the time and date to display the end time. Plays the events continuously backward in the CONTROL-M/EM ViewPoint window. Causes the clock to stop and events in the CONTROL-M/EM ViewPoint window are stopped. Plays the events continuously at the speed selected and the units selected. Events are displayed in the CONTROL-M/EM ViewPoint window. Specify the number of seconds or events that occur per step. Select the Seconds or Events playback unit from the drop-down list. Default: Seconds The time that the Archived Net started. (Read Only). Displays the playback time. While playing back an archived Net, the Time Display changes to reflect the relevant position of the playback time. You can also enter a specific time from which you wish to see the playback begin, and click Go. The time that the Archived Net ended. (Read Only). Click Go after specifying a time in the Time Display. The playback jumps to the specified time. The slider changes to reflect the relevant position of the playback time. You can move the marker on the slider to the time from which you wish to view the playback.
Playback controls Go to Start Previous Event Next Event Go to End Play Back Stop Play
Speed Units Duration Start Time Time Display
End Time Go button Slider
3 You can either:
Move the slider marker to the time from which you wish to view the playback, or Enter a specific time in the Time Display, and click Go.
NOTE
During playback, jobs not yet ordered to the Active Jobs file have the status Not in AJF. This status is relevant to archived jobs in Playback only.
322
Chapter
10
10
Customization
Several features in CONTROL-M/Enterprise Manager can be customized to suit site requirements and preferences. This customization is generally performed from the Options dialog box, which is displayed by selection Tools => Options drop-down menu option. This dialog box consists of two panes that are used to display any of several panels, each contain default settings pertaining to a particular feature. The left pane displays a tree that lists available panels, from which you can select a panel for display; the right pane displays the current panel. Figure 131 shows the Options dialog box as it appears when first opened. Figure 131 Options dialog box
To display the appropriate panel to modify particular CONTROL-M/EM default settings, you must first select the appropriate tree branch. Table 78 describes the features whose default settings can be accessed from each tree branch.
Chapter 10
Customization
323
Available branches and corresponding panels
NOTE
Some branches have sub-branches, each of which displays a different panel.
Table 78
Branch
Default settings accessed by branches in the tree

Description Defaults for the CONTROL-M/EM environment. This branch has sub-branches. Default settings for the FlowDiagram view in the CONTROL-M/Enterprise Manager window. This branch has sub-branches. Default settings for Alert communications in the CONTROL-M/EM environment. Default settings for reconnecting to the GUI server (or alternate GUI servers) if communication is lost. Troubleshooting settings for tracking technical problems with CONTROL-M/EM. Use this panel only when instructed by BMC Software Technical Support.
Environment Flowdiagram Alerts Reconnection Diagnostics
Confirmations Confirmation requests and warnings to display for various actions.
To modify any default setting 1 Open the Options dialog box by selecting Tools => Options in the drop-down
menu.
2 Click the appropriate branch to display its panel of default settings. 3 Change defaults as desired, and click OK.
Available branches and corresponding panels

The rest of this chapter describes the features that can be modified, by branch and corresponding panel.
324
Environment General panel

The Environment General panel (Figure 132) contains several general default settings for the CONTROL-M/EM environment. These default settings are described in Table 79. Figure 132 Environment General panel
Chapter 10
Customization
325
Table 79
Area Field Startup
Environment General panel default settings

Description Settings that apply when CONTROL-M/EM is started up.
Auto Open Viewpoint When this checkbox is not checked (default), an empty CONTROL-M/Enterprise Manager window is displayed when you start your CONTROL-M/EM session. To have a viewpoint automatically displayed when you start your CONTROL-M/EM session, click this checkbox and select one of the following options:
To have the same viewpoint always open automatically, click Select, and select the viewpoint. To have the last-opened viewpoint from the previous session open automatically, click Last Viewpoint. To have the Open Viewpoint dialog box (Figure 16 on page 91) automatically displayed, allowing selection of a viewpoint for the current session, click Display Open ViewPoint dialog.
Undo Enable JEF Undo up to Use this option to specify the number of levels of Undo or n actions Redo that can be performed in the Job Editing form. Default: 100. (To actually perform an Undo, click Ctrl+Z in the Job Editing form.) Filter Presets Sort Presets by name Click this box if private filters should be sorted by name. Otherwise, they will be sorted by the last modified date/time value. Browse and select the location for private filters.
Preset path
326
Environment Display panel

The Environment Display panel (Figure 133) contains several display default settings for the CONTROL-M/EM environment. These default settings are described in Table 80. Figure 133 Environment Display panel
Table 80
Area Field
Environment Display panel default settings (Part 1 of 2)

Description Determines if, when, and what information will be automatically updated in the CONTROL-M/EM GUI. When selected, enables information from CONTROL-M to be updated automatically in the CONTROL-M/EM GUI. If this option is not selected, you must click Refresh in the CONTROL-M/EM window, in order to display the latest changes in the production environment.
Automatic Refresh Reload active net
Rebuild Flowdiagram Determines the minimum number (n) of job changes (reloads when reload active net or removals) that causes the flow diagram to be rebuilt from for minimum n jobs scratch rather than updated when the user clicks Refresh. (Normally, when Refresh is clicked, the existing flow diagram is updated that is, jobs are reloaded or unloaded as necessary. But if there are too many changes, this process is slow, and it quicker and more efficient to rebuild the flow diagram from scratch). Default: This option is checked and n is 100 (if there are 100 or more job reloads/removals, the flow diagram is rebuilt.) Arrange All every n seconds Display Options Determines how often the flow diagram will be automatically refreshed. Determines the display defaults.
Chapter 10
Customization
327
Table 80
Area Field
Environment Display panel default settings (Part 2 of 2)

Description When selected, enables automatic update of the status of resources in the Active environment as displayed in the Prerequisite Conditions, Control Resources and Quantitative Resources windows. The automatic update occurs at intervals according to the number of seconds specified. When checked, colors representing the status of the job are displayed in the Navigation Tree. When selected, Group Scheduling tables are not displayed in the flow diagram if they do not contain any jobs.
Reload resources list every n seconds
Display status colors in Tree View Hide empty scheduling groups
Displays the scheduling group count, after the job count, in Display scheduling groups count in Status the status bar. Bar
Actions
Display n last Jobs Actions in Report
Maximum number of job actions to be displayed in the Job Action Report window. If more than the specified number of messages are issued, the oldest messages are removed from the window. n can be any number from 10 to 999. Default: 200
328
Flowdiagram General panel

The Flowdiagram General panel (Figure 134) contains several general default settings for flow diagrams. These default settings are described in Table 81. For more information about the flow diagram, see Chapter 2, Viewing the production environment. Figure 134 Flowdiagram General panel
Chapter 10
Customization
329
Table 81
Area Field General
Flowdiagram General panel default settings

Description When selected, prevents flickering of the display during navigation in the flow diagram. Note: Selecting this option slows navigation.
Smooth display
Enable tooltip in low zoom
When selected, enables the node title to be displayed as a tool tip (when the mouse pointer remains on the node). Note: This option is relevant only for zoom of 40% or lower. With a zoom 50% or higher, node titles are visible in the node.
Graph Graph Placement The combination box allows the user to specify Parent on the Left, Parent in the Middle, or Parent on the Right screen display options for the parent job in the flow diagram. The default is Parent in the Middle. Check mark indicates that the flow diagram is displayed as much as possible in vertical alignment rather than in horizontal alignment. Check mark indicates that the flow diagram accommodates the available screen space provided. Indicates the number of nodes to display in each stack in the Net Overview. Default: 10 (This is also the minimum value for this field). In high-level nodes, the number of jobs in the node are displayed in a Histogram in the bottom of the node. This option defines the number of jobs to count as a unit for each level of the Histogram. The default (and minimum) value is 10. Determines the default percentage of magnification of nodes displayed in FlowDiagram view when viewing a new network.Valid values are 10 through 400.
Maximize Downward Flow Minimize Graph Width Set Settings Display n nodes in pack Display n nodes in separator
Zoom Level Start Zoom Level
330
Flowdiagram Nodes panel
Flowdiagram Nodes panel

The Flowdiagram Nodes panel (Figure 135) contains several node default settings for flow diagrams. These default settings are described in Table 82. Figure 135 Flowdiagram Nodes panel
Display
Table 82
Area Field Titles Title
Flowdiagram Nodes panel default settings

Description Indicates whether to display the jobname, the memname, or the job description as the title of the job node. If JOB_NAME/MEMNAME is selected for MVS jobs, Memname is displayed for other jobs, Job name is displayed Indicates the job parameter to be displayed in the first field of the node. Check box for specifying if the text of fields in the job node should wrap to the next line or be truncated. If selected, the text wraps to the next line. If not selected, the fields are truncated. Shape of the nodes in the flow diagram. Valid values: Rounded Displays nodes with rounded corners. Rectangular Displays nodes with square corners.
First Field Wrap field text in node Display Shape
Behavior Double Click Indicates the action to be performed when a node in a flow diagram is on item to xxx double-clicked. Valid values: Expand item Expand or Collapse function. Expands the selected node to display levels lower than the current selected node, or collapses the selected node to hide all lower levels. This option is not available when condition nodes are displayed. Step Into item Changes the flow diagram to display nodes one level lower than the current selected node. See Stepping In and Stepping Out on page 96.
Chapter 10
Customization
331
Flowdiagram Links Panel
Flowdiagram Links Panel

The Flowdiagram Links panel (Figure 136) contains several link default settings for flow diagrams. These default settings are described in Table 83. Figure 136 Flowdiagram Links Panel
Table 83
Area Field
Flowdiagram Links panel default settings

Description Determines how links are displayed in the Flow diagram. When selected, indicates that condition nodes should be displayed in the flow diagram. When selected, displays job dependencies as lines between jobs in the flow diagram. These dependencies are determined by Do Cond statements and IN conditions defined in job processing definitions. When selected, displays connector lines for job dependencies. These line represent conditions that are set using the Out condition parameter. When selected, Do condition links are displayed using dotted rather than solid lines. When selected, Out condition links are displayed using dashes (minus signs) rather than solid lines.
Links Settings Display condition nodes Display links behind nodes
Show links between jobs Display Do Conditions (as dotted links) Display Out Conditions with minus sign (as dotted links) Display Optional In Condition as
Determines whether Optional In conditions (for example, two In conditions separated by an OR operator) will be displayed with solid or dotted lines.
332
Flowdiagram Colors panel
Flowdiagram Colors panel

The Flowdiagram Colors panel (Figure 137) contains several color default settings for flow diagrams. These default settings are described in Table 84. Figure 137 Flowdiagram Colors panel
Display
Table 84
Area Field
Flowdiagram Colors panel default settings

Description Color for the flow diagram background. Color for all high-level nodes in the hierarchy. Color for In/Out condition triangles. Color for frames of nodes in FlowDiagram view and in Net Overview. Color for condition nodes. Color of a link that has been selected. Background color for archived ViewPoints. Color of the currently focused item. Color for the node title. Color for the first field displayed in the node.
Color Settings Background Set Connector Frames Condition Nodes Selected Link Archived Background Focused Item Node Title Nodes First Field
Chapter 10
Customization
333
Alerts panel
Alerts panel
The Alerts panel (Figure 138) contains several default communication settings for the Global Alerts Server (GAS). These default settings are described in Table 85. Figure 138 Alerts panel
Table 85
Area Field
Alerts panel (Part 1 of 2)

Description Determines if CONTROL-M/EM automatically connects to the Global Alerts Server when accessing the Alerts window, and to which server.
Communication Settings
Automatically connect to If CONTROL-M/EM should automatically connect to Global Alerts Server when accessing the Alerts window, check the box and <server_name> select the name of the default Global Alerts Server. The server can be changed from the Alerts window using the Communication => Disconnect and Communication => Connect options (see Chapter 5, Monitoring alerts and errors). New Alert Notification None Flash Alerts window on task bar Bring Alerts window to front Open into Local View Determines how notification should be provided for new alerts. Select one of the following: Do not provide any special notification. Flash the Alerts window button on the Microsoft Windows task bar when an alert is received by CONTROL-M/EM. Open the Alerts window when an alert is received by CONTROL-M/EM. Selecting Open Into Local View for an alert in the Alerts window opens a special ViewPoint containing the job that prompted the alert and those jobs with which that job has a dependency relationship.
334
Reconnection panel
Table 85
Area Field
Alerts panel (Part 2 of 2)

Description Dependency levels that should be displayed in the ViewPoint specified in ViewPoint. You can specify a value of up to ten levels. Existing ViewPoint (filter and node hierarchy) in which to view job nodes displayed in a Local View.
Use Radius of n nodes
ViewPoint Name <name>
Reconnection panel
The Reconnection panel (Figure 139) contains several default settings for reconnecting to an alternative server if the connection to the CONTROL-M/EM GUI server is lost. CONTROL-M/EM attempts to (re)connect to the first server in a user-defined list of alternate servers. If this fails, CONTROL-M/EM attempts to reconnect to the next server in the list, and this process continues either until there is a successful reconnection or until there are no more servers in the list. Once there is a successful reconnection, CONTROL-M/EM continues to function using that alternate server as its GUI server, even restoring ViewPoints if desired. If CONTROL-M/EM cannot connect to any server, a message is displayed indicating that CONTROL-M/EM will shut down. In addition to allowing specification of alternative servers, this panel allows specification of a number of other defaults, including the intervals at which reconnection should be attempted and the maximum number of retries allowed. These default settings are described in Table 86.
Chapter 10
Customization
335
Reconnection panel
Figure 139 Reconnection panel
NOTE
Servers whose icons display in red have been manually added to the Alternate Servers list.
Table 86
Area Field
Reconnection panel default settings (Part 1 of 2)

Description Lists the alternative servers. Click the Select Servers button to add, delete, and change the order of, alternate servers. For details, see To modify the alternative server list: on page 337.
Alternative Servers
General Settings
These options indicate which ViewPoints, if any, should be opened when the connection is reestablished. Automatically reconnect Select this check box to indicate that CONTROL-M/EM should try to reconnect automatically without user intervention (Automatic mode). The user can monitor and intervene as necessary while the connection is being reestablished.
Restore xxx viewpoints
Select this check box to indicate which ViewPoints CONTROL-M/EM should open, and select appropriate values. Valid values.
Last active ViewPoint Only the ViewPoint that was last active should be opened. All open ViewPoints All ViewPoints that were open at the time of the disconnect should be opened.
336
Reconnection panel
Table 86
Area Field
Reconnection panel default settings (Part 2 of 2)

Description
Reconnection attempts
Reconnection is attempted based on these general settings.
Max reconnection retries Maximum number of reconnection attempts nn CONTROL-M/EM should make. Default: 5. Wait nn seconds between Number of seconds CONTROL-M/EM should wait reconnection attempts between reconnection attempts. Default: 5 seconds.
To modify the alternative server list: 1 In the Reconnection panel, click Select Servers.
The Alternative Server Selection dialog box is displayed, listing the available servers on the left and the servers already selected as alternate servers on the right.
2 Select the desired server(s), and click:
Add to designate them as alternate servers. Remove to remove them from the alternate server list. Add New to add a new server to the list of available servers. The Add New Server dialog box appears. Enter the name of the server and click OK.
3 Click OK.
The Alternative Server Selection dialog box closes.
Chapter 10
Customization
337
Diagnostics panel
Diagnostics panel
The Diagnostics panel (Figure 140) helps troubleshoot technical problems with CONTROL-M/EM by printing diagnostics at the desired severity levels into a log file. The log file should then be sent to BMC Software Technical Support. The settings in the Diagnostic panel are described in Table 87.
NOTE
Use this panel only when instructed by BMC Software Technical Support. Your technical support representative will notify you which fields to change.
Figure 140 Diagnostics panel
NOTE
The changes to the settings take effect immediately, except for changes made to the Cyclic Log File field(s). Changes to Cyclic Log File field settings take affect the next time the specified CONTROL-M/EM application files are run.
338
Diagnostics panel
Table 87
Area
Diagnostic Panel fields (Part 1 of 2)

Description Full name and path of the log file to which diagnostics should be printed. For display purposes only. When selected, diagnostics are printed to a log file. Default: Selected. If checked, all diagnostics are printed to the log at the selected diagnostic level or higher, even if diagnostic levels specified in the Diagnostic Levels fields (see below) are lower than the value specified here. Values can be selected from the drop-down list, or entered manually (keyword or numeric code). Default: 1 ERROR. Valid values are: 0 SEVERE 1 ERROR Only severe issues (crashes). Error messages (corba exceptions, errors that can cause the application to malfunction or crash at a later time). Default. Warning messages (unexpected events that do not stop the application but may limit functionality. General events. Information about the basic functionality of the application. More detailed information including the steps of an event, parameters, etc. Every entrance to a function/method. Every exit from a function/method.
Field Log File Name
General Enable Diag Use Minimum Diag Level
2 WARNING
3 (General) 4 INFO
5 DEBUG
6 FNC_ENTER 7 FNC_EXIT Cyclic Log File Number of Files Number of Messages Per File
When checked, diagnostics are printed to a set of log files (instead of one). Default: Not checked. The maximum number of files to which diagnostics are printed. Valid values: 1-300. Default: 1. The maximum number of messages that can be written to each cyclic log file. Valid values: 200-10000. Default: 200. If more diagnostics are generated than fit in the defined number of cyclic log files, CONTROL-M/EM writes over the existing log files, starting with the first in the set. Changes to these fields take affect the next time the specified CONTROL-M/EM application files are run (not immediately).
Chapter 10
Customization
339
Confirmations panel
Table 87
Area
Diagnostic Panel fields (Part 2 of 2)

Description Individual diagnostic level settings for each file or context (procedure). For valid values, see the Use Minimum Debug Level field. Diagnostics are generated on a file basis, at the level specified next to each file name. Diagnostics are generated on a procedural basis, at the level specified next to each context (procedure). Procedures listed in the Contexts tab can span several files or sub-procedures. When you change the level of a procedure, CONTROL-M/EM automatically changes the level of any sub-procedures. If selected, the diagnostic settings are saved as a default for future CONTROL-M/EM sessions. Otherwise, the settings take effect for this CONTROL-M/EM session only.
Field
Diagnostic Levels
Files tab Contexts tab
Save settings for next run
Confirmations panel
The Confirmations panel (Figure 141) determines which confirmation requests and warnings should be displayed for various actions. Figure 141 Confirmations panel
Confirmation and warning options are divided into the following sections:
340
Confirmations panel
Job Action Confirmations Select or deselect the job actions for which you want a confirmation dialog box to display before CONTROL-M/EM performs the job action. General Confirmations Select or deselect the general confirmations that you would like displayed. Warnings Select or deselect the warnings that you would like displayed.
To reassign the default settings as originally provided, click Restore Defaults.
Chapter 10
Customization
341
Confirmations panel
342
Appendix
CONTROL-M (MVS) and CONTROL-M/EM cross-reference

A
This appendix cross-references the functions and terminology of CONTROL-M for OS/390 and z/OS and CONTROL-M/Enterprise Manager (CONTROL-M/EM). The following tables list CONTROL-M functions and the screen used to perform each function along with the corresponding features in CONTROL-M/EM.
Job tracking and control

Table 88
Function Create a Scheduling Table List Scheduling Tables Delete Scheduling Tables
Job tracking and control terms (Part 1 of 3)

CONTROL-M (MVS) CONTROL-M Scheduling Facility Entry Panel CONTROL-M Scheduling Facility Entry Panel Option D (Delete) in the Table List screen CONTROL-M/EM CONTROL-M/Desktop Scheduling Table Manager CONTROL-M/Desktop Scheduling Table Manager CONTROL-M/Desktop Scheduling Table Manager CONTROL-M/Desktop Import Scheduling Tables or List View
List jobs in the Scheduling Table Option S (Select) in the Table List screen Define a new job View or Update an existing job definition Delete a job definition
Option I (Insert) in the Job List screen CONTROL-M/Desktop New Job option Option S (Select) in the Job List screen Option D (Delete) in the Job List screen CONTROL-M/Desktop Edit Job option or double-click Job node in any view CONTROL-M/Desktop Delete Job option
Appendix A CONTROL-M (MVS) and CONTROL-M/EM cross-reference
343
Table 88
Function

CONTROL-M (MVS) Option O (Order) or F (Force) in the Job List screen CONTROL-M/EM CONTROL-M/EM Order/Force Job window or Click or CONTROL-M/Desktop Scheduling Table Manager .
Order or Force a job
Order or Force a table
Option O (Order) or F (Force) in the Table List screen
CONTROL-M/EM Tools => Order/Force Job - or Click . - or CONTROL-M/Desktop Scheduling Table Manager Why Choose Action => Why or Click .
Display reasons why job awaits scheduling
Option ? (Why) in the Status screen
Hold execution of the job
Option H (Hold) in the Status screen Hold Choose Action => Hold or Click .
Free a held job
Option F (Free) in the Status screen
Free Choose Action => Free or Click .
Show logged messages
Option L (Log) in the Status screen
Log Choose Action => Log
344
Table 88
Function

CONTROL-M (MVS) CONTROL-M/EM Option Z (Zoom) in the Status screen Job Properties Choose Action => Properties or Choose Properties from the node popup menu or Double-click the job node
Display job details
Rerun a job
Option R (Rerun) in the Status screen Rerun Choose Action => Rerun or Click
Manually confirm that a job can be run
Option C (Confirm) in the Status screen
Confirm Choose Action => Confirm or Click .
View the jobs archived sysouts
Option V (View) in the Status screen, Sysout only if CONTROL-R is running Choose Action => Sysout or Click .
Display job run statistics in the Statistics screen
Option S (Stat) in the Status screen
Statistics Choose Action => Statistics or Choose Statistics from the node popup menu
Graphic overview of status of jobs running in CONTROL-M
VIEW GRAPH command in the Status screen
Print Choose File => Print
345
Job documentation and JCL
Job documentation and JCL

Table 89
Function Edit a jobs JCL
Job Documentation Terms (MVS)

CONTROL-M (MVS) CONTROL-M/EM Option Edit JCL in the Job List screen Edit JCL/Script Choose Action => Edit JCL/Script or Click
Display job documentation
DOC command in the job processing View Documentation definition screen or Choose Action => Documentation
IOA conditions/resources
Table 90
Function
IOA conditions/resources terms

CONTROL-M (MVS) CONTROL-M/EM Control Resources window and Quantitative Resources window Prerequisite Conditions window Quantitative Resources window
Display and change Control and Option 4 in the Main Menu Quantitative resources Display and change prerequisite Option 4 in the Main Menu conditions Add a Quantitative resource Enter ADD RESOURCE in the command line of the IOA Conditions/Resources screen Enter ADD CONTROL in the command line of the IOA Conditions/Resources screen
Add a Control resource
Control Resources window
Change the required amount of a Option C (Change) in the IOA Quantitative resource Conditions/Resources screen
Quantitative Resources window
346
IOA manual conditions
IOA manual conditions

Table 91
Function Display list of manual prerequisite conditions Add a condition Erase a manual condition Add a new prerequisite condition
IOA manual conditions - term cross-reference

CONTROL-M (MVS) Option 6 in the Main Menu Option A (Add) in the IOA Manual Conditions screen Option E (Erase) in the IOA Manual Conditions screen NEW COND command in the IOA Manual Conditions screen CONTROL-M/EM Prerequisite Conditions window Prerequisite Conditions window Prerequisite Conditions window Prerequisite Conditions window
Utilities under ISPF

Table 92
Function Issue a job order Add/Delete prerequisite condition Online AutoEdit simulation screen
ISPF utilities
CONTROL-M (MVS) Option CTMJOBRQ in the Utilities menu Option IOACCND in the Utilities menu Option CTMCAES in the Utilities menu CONTROL-M/EM Not handled Prerequisite Conditions window Job Properties Choose Action => Properties or Choose Properties from the node popup menu or Double-click the job node.
Simulation/tape pull list screen Prepare prompting facility screen Quick scheduling screen
Option CTMCSIM in the Utilities menu Option CTMPROMP in the Utilities menu Option CTMQUICK in the Utilities menu
Not handled Not handled Not handled
347
Job processing parameters

Table 93 cross-references job processing parameters as they are referred to in the CONTROL-M User Guide and as they appear in the Job Editing form in CONTROL-M/EM and CONTROL-M/Desktop. Some parameters appear only in the Group Scheduling Editing form. These instances are noted. Table 93
APPL AUTO-ARCHIVE ADJUST CONDITION AUTO-ARCHIVE SYSDB AUTO-ARCHIVE MAXDAYS AUTO-ARCHIVE MAXRUNS CONFCAL CONFIRM CONTROL CRITICAL CYCLIC D-CAT DATEMEM DATES DAYS DAYS AND/OR DCAL DEFINITION ACTIVE FROM DEFINITION ACTIVE TO DESC DO DO COND DO CTBRULE DO FORCEJOB DO IFRERUN DO MAIL DO NOTOK DO OK DO RERUN DO SET
MVS job processing parameters (Part 1 of 3)

CONTROL-M/EM Application Auto-Archive Adjust Condition SYSDB Max Days Max Runs Confcal Confirm Control Resources Critical Cyclic Category Days Calendar Dates Days And/Or Days Calendar Active From Date Active To Date Description DO Action DO Condition DO CTBrule DO Force-job DO IFrerun DO Mail Do NOTOK Do OK Do Rerun Do AutoEdit Job Editing Form panel General PostProc General Panel of the Group Editing form PostProc PostProc PostProc Scheduling Execution Resources General Execution Scheduling Scheduling Scheduling Scheduling Scheduling Scheduling Scheduling Scheduling General Steps Steps Steps Steps Steps Steps Steps Steps Steps Steps
CONTROL-M
348
Table 93

CONTROL-M/EM DO Shout DO StopCyclic DO Sysout Documentation Doc Lib Doc Mem Due Out Emergency Group Maxwait IN Conditions Interval Rerun Maximum Max Wait Mem Lib Mem Name Minimum Months NJE REQUEST NJE Node On Group End On Step Codes OUT Conditions Over Lib Owner PDS Prevent NCT2 Priority Critical Relationship Rerun Member Quantitative Resources Retro not supported Schedule Tag Scheduling Environment Job Editing Form panel Steps Steps Steps On the job node popup menu General General Active Execution General Active panel of the Group Editing form Conditions Execution Execution Execution General General Scheduling Scheduling Active Execution PostProc panel of the Group Editing form Steps Conditions General General Scheduling Execution Execution Execution Scheduling PostProc Resources Scheduling -Tag Selection Execution
CONTROL-M DO SHOUT DO STOPCYCLIC DO SYSOUT DOC DOCLIB DOCMEM DUE OUT EMERGENCY GROUP GRP MAXWAIT IN INTERVAL MAX RERUN MAXWAIT MEMLIB MEMNAME MINIMUM MONTHS NJE NJE NODE ON GROUP-END ON STEP/CODE OUT OVERLIB OWNER PDS PREVENT-NCT2 PRIORITY PRIORITY Critical Path RELATIONSHIP RERUNMEM RESOURCE RETRO SAC SCHEDULE TAG SCHENV
349
Table 93
SET VAR SHIFT SHOUT

CONTROL-M/EM AutoEdit Assignment Shift Option buttons Shout Statements Step Range Sysout Handling System Affinity Tasktype Time Week Days Calendar Weekdays Job Editing Form panel Set Scheduling PostProc PostProc PostProc Execution General Execution Scheduling Scheduling
CONTROL-M
STEP RANGE SYSOUT SYSTEM ID TASKTYPE TIME WCAL WDAYS
350
Generating alerts on a CONTROL-M for MVS platform

When specifying job processing parameters for CONTROL-M on an MVS platform, you can use the Shout parameter to generate alerts that are displayed in the Alerts window in the CONTROL-M/EM GUI. To specify how a Shout message should be displayed in the Alerts window, use one of the following values as the Shout message destination: Table 94
Destination OPER OPER2 U-ECS
MVS Shout message destinations

Description Sends the Shout message to the Alerts window and as a rollable message to the MVS operator console. Sends the Shout message to the Alerts window and as an unrollable message to the MVS operator console. Sends the Shout message to the Alerts window and to the CONTROL-M log.
For more information on using these Shout destinations, see the description of the Shout parameter in the CONTROL-M for OS/390 and z/OS User Guide.
351
352
Appendix
Messages and codes

This appendix describes the following types of messages:

Mainframe (MVS) CONTROL-M messages. CONTROL-M messages from other platforms.
All the messages included in this appendix are displayed in the CONTROL-M/EM GUI.
Appendix B
Messages and codes
353
Mainframe (MVS) CONTROL-M messages

The following are messages issued by CONTROL-M running on an MVS platform or by MVS Gateway for CONTROL-M/EM (IOAGATE) and which may appear in a pop-up window in the CONTROL-M/EM GUI:
BMCECS3000 SERVER INTERNAL ERROR TYPE type
Explanation: The server program detected an internal error. This error message is issued by program CTWSRVR, which is activated as part of IOAGATE, and is due to reasons beyond the users control. System Action: The user request is rejected. User Response: Contact Technical Support.
BMCECS3001 INCOMPATIBLE GATEWAY VERSIONS. MAINFRAME GATEWAY VERSION mainframe_version. WORKSTATION GATEWAY VERSION workstation_version
Explanation: The IOAGATE version is not compatible with the Workstation Gateway version. Both gateways should be installed from the same installation version. If only one gateway was upgraded, the link cannot become active. System Action: IOAGATE shuts down. User Response: Either upgrade the lower version gateway, or restore the upgraded gateway to the previous version.
BMCECS3002 DUPLICATION OF CONDITIONS/RESOURCES DETECTED IN JOB(S)
Explanation: During Download of the Active Jobs file or Update of the Active network, a job was encountered that contained a duplicate processing parameter entry. A job definition contained a duplicate In Condition, Out Condition, Control Resource, Quantitative Resource, Do Cond or Step Range entry. The processing parameter involved will be specified in IOAGATE message CTWG19W or CTWG22W. System Action: Only one of the duplicate entries will be downloaded. User Response: It is advisable to correct the job definition in the mainframe so that it does not contain any duplicate processing parameter entries.
BMCECS3003 JCL MEMBER member SAVED SUCCESSFULLY IN LIBRARY library
Explanation: This information message indicates that the specified JCL member was saved successfully following an Edit JCL operation.
354
BMCECS3004
OPEN OF CONTROL-M ACTIVE JOBS FILE FAILED. DDNAME DACKPT
Explanation: This message is issued by IOAGATE. Open of the CONTROL-M Active Jobs file failed (DD statement DACKPT). This may be due to one of the following:
DD statement DACKPT is missing. The dataset pointed to by DD statement DACKPT is not the CONTROL-M Active Jobs file.
System Action: CSGATE shuts down. User Response: Correct the IOAGATE JCL procedure and restart it.
BMCECS3005 INSUFFICIENT STORAGE FOR CONTROL-M/EM MAINFRAME GATEWAY
Explanation: Insufficient storage for IOAGATE to execute. This message is produced by IOAGATE. System Action: IOAGATE shuts down. User Response: Increase the REGION size and restart IOAGATE.
BMCECS3006 FILE ALLOCATED TO DDNAME DACKPT IS NOT YOUR CONTROL-M ACTIVE JOBS FILE
Explanation: This message is issued by IOAGATE. The dataset pointed to by DD statement DACKPT is not the CONTROL-M Active Jobs file. This may be due to one of the following:
The dataset pointed to by DD statement DACKPT is not the CONTROL-M Active Jobs file. The dataset pointed to by DD statement DACKPT is the CONTROL-M Active Jobs file, but of another CONTROL-M Monitor, or of a different CONTROL-M version.
System Action: IOAGATE shuts down. User Response: Correct the IOAGATE JCL procedure and restart it.
BMCECS3007 OPEN OF IOA CONDITIONS/RESOURCES FILE FAILED. DDNAME DARESF
Explanation: This message is issued by IOAGATE. Open of the IOA Conditions/Resources File failed (DD statement DARESF). This may be due to one of the following:
Appendix B Messages and codes 355
DD statement DASREF is missing. The dataset pointed to by DD statement DASREF is not the IOA Conditions/Resources File. The dataset pointed to by DD statement DASREF is the IOA Conditions/Resources File, but it is of a different version or of a different IOA Installation.
User Response: Correct the IOAGATE JCL procedure and restart it.
BMCECS3008 MEMBER IN USE
Explanation: An attempt was made to use the Edit JCL/Script option for a member which is currently held by another user. The member is currently being edited by another user, either in ISPF or in another CONTROL-M/EM Control Application. System Action: The Edit JCL/Script request is rejected. User Response: Try again later.
BMCECS3009 LOADING OF CONTROL-M INSTALLATION PARAMETERS FAILED
Explanation: Loading of the CONTROL-x Installation Parameters failed (load module CTxPARM). This may be due to one of the following:
The IOA Load Library is not in the load modules search list. Insufficient storage to load the IOA Installation Parameters. The module CTxPARM does not exist in the IOA Load Library. The IOA Load Library was updated while you were working, and the position of module CTxPARM has changed.
System Action: IOAGATE shuts down. User Response: Look on the system log for additional messages which may clarify the picture. Try one of the following:
If the IOA Load Library is not in the Search list, add a STEPLIB DD statement pointing to the library, to the IOAGATE JCL procedure. If the loading failed due to lack of storage, increase the REGION size.
356
If the Load Library has been modified and IOAGATE was executing, stop and restart IOAGATE. If the IOA Load Library is in the Linklist, a refresh to the LLE is needed (MVS/XA and up only), before the start command.
BMCECS3010
USER NOT AUTHORIZED
Explanation: You are not authorized to perform the requested function. This message is issued by the IOA security mechanism. System Action: The user request is rejected. User Response: Contact your system security administrator.
BMCECS3011 DUMMY LIBRARY, MEMBER NON EXISTENT
Explanation: An attempt was made to use the Edit JCL/Script option, but the Mem Lib field in the Job Details window contains DUMMY. The Job is a Dummy Job and therefore does not have a JCL member. System Action: The Edit JCL/Script request is rejected.
BMCECS3012 LIBRARY NAME IS BLANK
Explanation: An attempt was made to use the Documentation option, but the Doc Lib field in the Job Details window is blank. No Documentation library was specified in the Doc Lib field in the Job Details window. System Action: The Documentation request is rejected. User Response: Enter the name of the library in which the job documentation resides in the Doc Lib field of the Job Details window.
BMCECS3013 MEMBER NAME IS BLANK
Explanation: An attempt was made to use the Documentation option, but the Doc Mem field in the Job Details window is blank. No member name was specified in the Doc Mem field of the Job Details window. System Action: The Documentation request is rejected. User Response: Enter the name of the member in which the job documentation member resides in the Doc Mem field of the Job Details window.
Appendix B
Messages and codes
357
BMCECS3014
DSN dsn NOT A LIBRARY
Explanation: Dataset dsn is not a partitioned dataset. This message may appear after requests for Edit JCL/Script, View JCL/Script or Documentation options. These options are not available for members contained in datasets which are not partitioned. System Action: The user request is rejected. User Response: Correct the name of the dataset in the Mem Lib or Doc Lib field in the Job Details window to a partitioned dataset.
BMCECS3015 DSN dsn RECFM NOT FIXED
Explanation: The record format of dataset dsn is not fixed. This message may appear after requests for Edit JCL/Script, View JCL/Script or Documentation options. These options are not available for members contained in datasets in which the record format is not fixed. System Action: The user request is rejected. User Response: Correct the name of the dataset in the Mem Lib or Doc Lib field in the Job Details window to a dataset with fixed record format.
BMCECS3016 DSN dsn LRECL NOT 80
Explanation: The record length of dataset dsn is not 80. This message may appear after requests for Edit JCL/Script, View JCL/Script or Documentation options. These options are not available for members contained in datasets in which the record length is not 80. System Action: The user request is rejected. User Response: Correct the name of the dataset in the Mem Lib or Doc Lib field in the Job Details window to a dataset with record length 80.
BMCECS3017 DSN dsn IN USE (DISP=OLD)
Explanation: Dataset dsn is currently being held in DISP=OLD by another user. This message may appear after requests for Edit JCL/Script, View JCL/Script or Documentation options. These options are not available while the dataset is being held in DISP=OLD by another user. System Action: The user request is rejected. User Response: Try again later.
358
BMCECS3018
INTERNAL ERROR ON GETMEM: return_code. SEE MESSAGES AND CODES
Explanation: An internal CONTROL-M error occurred while trying to read a member from a library. This message may appear after requests for Edit JCL/Script, View JCL/Script or Documentation options. System Action: The user request is rejected. User Response: Look for additional messages in the CONTROL-M log and the computer log that may clarify the picture, and if possible, correct the problem. Contact Technical Support and provide the return code.
BMCECS3019 DSN dsn NOT IN CATALOG
Explanation: Dataset dsn is not in the catalog. This message may appear after requests for Edit JCL/Script, View JCL/Script or Documentation options. The requested dataset could not be found in the catalog. System Action: The user request is rejected. User Response: Correct the name of the dataset in the Mem Lib or Doc Lib field in the Job Details window.
BMCECS3020 DSN dsn DYNAMIC ALLOCATION FAILED
Explanation: Dynamic allocation failed for dataset dsn. This message may appear after requests for Edit JCL/Script, View JCL/Script or Documentation options. System Action: The user request is rejected. User Response: Contact Technical Support for assistance.
BMCECS3021 INTERNAL ERROR INVALID REQUEST TO CTMMEM. INFORM IOA ADMINISTRATOR
Explanation: An internal IOA error occurred while trying to read a member from a library. This message may appear after requests for Edit JCL/Script, View JCL/Script or Documentation options. System Action: The user request is rejected. User Response: Contact Technical Support for assistance.
Appendix B
Messages and codes
359
BMCECS3022
MAXIMUM NUMBER OF MEMBERS/LINES IN MEMBER EXCEEDED
Explanation: Insufficient storage to read a large member from the library. This message may appear after requests for Edit JCL/Script, View JCL/Script or Documentation options. System Action: The user request is rejected. User Response: Increase the REGION size and try again.
BMCECS3023 INVALID RETURN CODE FROM CTMMEM INFORM IOA ADMINISTRATOR
Explanation: An internal IOA error occurred while trying to read a member from a library. This message may appear after requests for Edit JCL/Script, View JCL/Script or Documentation options. System Action: The user request is rejected. User Response: Contact Technical Support for assistance.
BMCECS3024 ERROR WHILE PROCESSING DIRECTORY OF LIBRARY
Explanation: An internal CONTROL-M error occurred while trying to read a directory of a library. This message may appear after requests for Edit JCL/Script, View JCL/Script or Documentation options. System Action: The user request is rejected. User Response: Contact Technical Support for assistance.
BMCECS3025 LIBRARY OPERATION FAILED. REASON: reason
Explanation: An internal CONTROL-M error occurred while trying to read a member from a library. This message may appear after requests for Edit JCL/Script, View JCL/Script or Documentation options. System Action: The user request is rejected. User Response: Contact Technical Support for assistance.
360
BMCECS3026
DSN RECORD FORMAT DOES NOT MATCH THE REQUESTED RECORD FORMAT
Explanation: An error occurred in the CTMMEM module, indicating that the library has an unexpected record format. The CTMMEM module has detected that the record format of the library to be opened differs from the requested record format. System Action: The user request is rejected. User Response: Contact Technical Support.
BMCECS3027 CANNOT EDIT MEMBER IN DATASET WITH DSORG NOT PO
Explanation: An attempt was made to use the Edit JCL/Script option for a member which is contained in a dataset which is not a PDS. Save is not available for non-PDS dataset members. System Action: The Edit JCL/Script request is rejected. User Response: Use the View JCL/Script option instead.
BMCECS3028 CANNOT action TASK task ODATE odate UNEXPECTED CODE FROM CTMUCK
Explanation: Unexpected code from CONTROL-M internal utility CTMUCK. System Action: The user request is rejected. User Response: Contact Technical Support for assistance.
BMCECS3029 INTERNAL ERROR INVALID REQUEST TO CTMUCK request
Explanation: Internal error. Invalid request request to CONTROL-M internal program CTMUCK. System Action: The user request is rejected. User Response: Contact Technical Support for assistance.
BMCECS3030 CANNOT action TASK task ODATE odate NOT HELD
Explanation: Delete or Change was requested for a task which is not in Held status. Task task of the original scheduling date odate is not in Held status and therefore cannot be deleted/changed. System Action: The Delete/Change request is rejected. User Response: Hold the task. Wait until the Requested Held status is changed to Held, and then use the Change or Delete option.
Appendix B
Messages and codes
361
BMCECS3031
ACTIVE JOBS FILE IS IN USE, TRY AGAIN LATER
Explanation: Another user is updating the file. The Active Jobs file is currently in use by another user or by the CONTROL-M Monitor. System Action: The user request is rejected. User Response: Try again later.
BMCECS3032 action OF TASK task ODATE odate IGNORED STATUS HAS CHANGED
Explanation: Hold, Rerun, Free or Change was requested for task task of original scheduling date odate, but its status has already been changed. Between the time the request was sent from the CONTROL-M/EM Control Application and the time it was processed by IOAGATE, another user or the CONTROL-M Monitor changed the status of the task, or the contents of the production parameters. System Action: The user request is rejected. User Response: Check the task status and act accordingly.
BMCECS3033 CANNOT action TASK task ODATE odate MAX CHANGES EXCEEDED, TRY AGAIN LATER
Explanation: No more actions can be carried out at present. Maximum number of requests for action exceeded. The CONTROL-M Monitor must accept the requests before another action can be performed. System Action: The user request is rejected. User Response: If the CONTROL-M Monitor is up, try again. If it is down, it should be brought up again.
BMCECS3034 CANNOT action TASK task ODATE odate ALREADY DELETED
Explanation: Task task of original scheduling date odate has already been deleted and therefore no action can be performed on it. System Action: The user request is rejected.
BMCECS3035 CANNOT RERUN TASK task ODATE odate TASK NOT ENDED
Explanation: Task task of original scheduling date odate did not finish executing, and therefore it can not be rerun. System Action: The Rerun request is rejected.
362
BMCECS3036
CANNOT action TASK task ODATE odate IN REQUESTED CHANGE STATUS
Explanation: Free or Delete was requested for task task of original scheduling date odate, but the task is in Requested Change status. Free or Delete may not be specified for tasks which are in Requested Change status. System Action: The user request is rejected. User Response: Wait until the Requested Change status disappears and then try again.
BMCECS3037 CANNOT DELETE TASK task ODATE odate TASK IN PROCESS
Explanation: Delete was requested for task task of original scheduling date odate, but the task is in process. You can only delete a task which is awaiting scheduling or which has finished executing (ENDED). System Action: The user request is rejected. User Response: Free the task and let CONTROL-M analyze it and bring it to ENDED status.
BMCECS3038 CANNOT DELETE TASK task ODATE odate PATH REQUEST ACTIVE
Explanation: An attempt was made to delete task task which is in Wait Schedule status. However, the task, which is of critical path priority (*), has already reserved the resources for execution. A critical path priority (*) task reserves Control Resources and Quantitative Resources, in order to obtain all the runtime resources required for its execution. It is impossible to delete such a task while the resources are reserved. System Action: The user request is rejected. User Response: If you need to delete the task, perform the following steps: 1. Enter the Job Details Window. 2. Erase all the Control Resources and Quantitative Resources and Save. 3. Wait until the Requested Change status disappears. 4. Try to delete again. If you still receive this message, then wait a few seconds and try again.
Appendix B
Messages and codes
363
BMCECS3039
ACTION IGNORED STATUS OF TASK CHANGED
Explanation: Confirm or Rerun was requested for a job whose status has already been changed. Between the time the request was sent from the CONTROL-M/EM Control Application and the time it was processed by IOAGATE, another user or the CONTROL-M Monitor changed the status of the task, or the contents of the production parameters. System Action: The user request is rejected. User Response: Check the job status and act accordingly.
BMCECS3040 OPEN OF PRINT FILE FAILED, DDNAME DAPRINT
Explanation: Open of the message file failed in IOAGATE. This may be due to one of the following:
DD statement DAPPRINT is missing. The dataset allocated to DD statement DAPRINT cannot be opened for sequential write.
System Action: The user request is rejected. User Response: Correct the IOAGATE JCL procedure and restart it.
BMCECS3041 TASK IS NOT WAITING FOR CONFIRMATION
Explanation: An attempt was made to confirm the restart of a task which is not waiting for confirmation. Confirm is valid only for tasks which are in Wait Confirmation status. System Action: The Confirm request is rejected.
BMCECS3042 OPEN OF IOA LOG FILE FAILED
Explanation: Open of the CONTROL-M log file failed (DD statement DALOG). This may be due to one of the following:
DD statement DALOG is missing. The dataset pointed to by DD statement DALOG is not the CONTROL-M log File. The dataset pointed to by DD statement DALOG is the CONTROL-M log File, but it is of a different version or of a different IOA Installation.
364
System Action: IOAGATE shuts down. User Response: Look on the computer log for additional messages which will clarify the reason for the failure. Then, correct the IOAGATE JCL procedure and restart it.
BMCECS3043 CANNOT REACTIVATE JOB job ODATE odate JOB NOT DISAPPEARED
Explanation: An attempt was made to Reactivate a job which is not in Disappeared status. The Reactivate option is valid only for jobs which are in Disappeared status. System Action: The Reactivate request is rejected.
BMCECS3044 LIBRARY IS FULL, COMPRESS NEEDED
Explanation: The JCL library is full and therefore the member can not be saved. An abend Sx37 occurred while attempting to save a member. System Action: The Save JCL request is rejected. User Response: Compress the JCL library.
BMCECS3045 INTERNAL ERROR IN IOACND. NOTIFY THE IOA ADMINISTRATOR
Explanation: Internal error in IOAGATE. System Action: The user request is rejected. User Response: Contact Technical Support.
BMCECS3046 INVALID DATE FORMAT
Explanation: Invalid date format in Add/Delete Cond statement. The date format should be mmdd (USA) format or ddmm (International format). System Action: The condition is not added/deleted. User Response: Correct the date format.
Appendix B
Messages and codes
365
BMCECS3047
OPEN OF IOA SYNCHRONIZATION FILE FAILED. DDNAME DASINC
Explanation: Open of the IOA Conditions/Resources Synchronization File failed (DD statement DASINC). This may be due to one of the following:
DD statement DASINC is missing. The file allocated to DD statement DASINC is not the IOA Synchronization File. The file allocated to DD statement DASINC is the IOA Synchronization File, but it is of a different version or of a different CONTROL-M Monitor.
User Response: Correct the IOAGATE JCL procedure and restart it.
BMCECS3048 INTERNAL ERROR INVALID REQUEST TO CTMURS. NOTIFY THE IOA ADMINISTRATOR
Explanation: Internal error Invalid request to IOA internal utility CTMURS. System Action: The user request is rejected. User Response: Contact Technical Support for assistance.
BMCECS3049 INTERNAL ERROR INVALID RESOURCE TYPE (CTMURS). NOTIFY IOA ADMINISTRATOR
Explanation: Internal error. An invalid resource type was passed to IOA internal utility CTMURS. System Action: The user request is rejected. User Response: Contact Technical Support for assistance.
BMCECS3050 COND condition ODATE odate DOES NOT EXIST
Explanation: Condition condition of original scheduling date odate was marked for deletion, but it has already been deleted from the IOA Conditions/Resources File. Between the time the request was sent from the CONTROL-M/EM Control Application and the time it was processed by IOAGATE, another IOA or CONTROL-M/EM user (or one of the IOA Monitors) deleted the condition from the Conditions/Resources File.
366
System Action: The Delete request is rejected.

BMCECS3051 COND condition ODATE odate ALREADY EXISTS
Explanation: An attempt was made to add condition condition of original scheduling date odate, but this condition already exists in the Conditions/Resources File. System Action: The Add request is rejected.
BMCECS3052 ADD OF COND condition ODATE odate FAILED. FILE IS FULL
Explanation: An attempt was made to add condition condition of original scheduling date odate, but the Conditions/Resources File is full. System Action: The Add request is rejected. User Response: Try to manually delete conditions from the specified day of the odate, but in other months. If you need all the conditions in the file, then consult your system programmer about the possibility of increasing the capacity of the IOA Conditions/Resources File. It is highly recommended that you run the IOACLRES utility periodically. This utility erases unnecessary conditions from the Conditions/Resources File, thus preventing the current problem.
BMCECS3053 CONTROL RESOURCE resource ALREADY EXISTS
Explanation: An attempt was made to add Control resource resource, but this Control resource already exists in the IOA Conditions/Resources File. System Action: The Add request is rejected.
BMCECS3054 ADD OF CONTROL RESOURCE resource FAILED. FILE IS FULL
Explanation: An attempt was made to add Control resource resource, but the IOA Conditions/Resources File is full. System Action: The Add request is rejected. User Response: Consult your system programmer about the possibility of increasing the capacity of the IOA Conditions/Resources File. Contact Technical Support for advice.
BMCECS3055 CONTROL RESOURCE control_resource DOES NOT EXIST
Explanation: Control resource control_resource was marked for deletion, but it has already been deleted from the IOA Conditions/Resources File. Between the time the request was sent from the CONTROL-M/EM Control Application and the time it was processed by IOAGATE, another IOA or CONTROL-M/EM user (or one of the IOA Monitors) deleted the Control resource from the Conditions/Resources File. System Action: The Delete request is rejected.
Appendix B
Messages and codes
367
BMCECS3056
QUANTITATIVE RESOURCE quantitative_resource IN USE CANNOT DELETE
Explanation: An attempt was made to delete Quantitative resource quantitative_resource, but it is in use by a job under CONTROL-M. An Active Job under CONTROL-M is using a certain quantity of the Quantitative resource. Therefore, the resource cannot be deleted. System Action: The Delete request is rejected. User Response: Wait until the job finishes executing and then try again.
BMCECS3057 FILE IS FULL. CANNOT ADD QUANTITATIVE RESOURCE quantitative_resource
Explanation: An attempt was made to add Quantitative resource quantitative_resource, but the Conditions/Resources File is full. System Action: The Add request is rejected. User Response: Consult your system programmer about the possibility of increasing the capacity of the IOA Conditions/Resources File.
BMCECS3058 QUANTITATIVE RESOURCE quantitative_resource ALREADY EXISTS
Explanation: An attempt was made to add Quantitative resource quantitative_resource, but this Quantitative resource already exists in the IOA Conditions/Resources File. System Action: The Add request is rejected.
BMCECS3059 QUANTITATIVE RESOURCE quantitative_resource DOES NOT EXIST
Explanation: Quantitative resource quantitative_resource was marked for deletion, but it has already been deleted from the IOA Conditions/Resources file. Between the time the request was sent from the CONTROL-M/EM Control Application and the time it was processed by IOAGATE, another IOA or CONTROL-M/EM user (or one of the IOA Monitors) deleted the Quantitative resource from the Conditions/Resources File. System Action: The Delete request is rejected.
BMCECS3060 ONLY QUANTITATIVE RESOURCES MAY BE CHANGED
Explanation: A Change request was specified for a condition or a Control resource. The Change option can be specified only in order to change the quantity of a Quantitative resource.
368
System Action: The Change request is rejected.

BMCECS3061 SIGN OF QUANTITY MUST BE EITHER +, - OR BLANK
Explanation: An invalid operation sign was specified for a quantity resource change. The quantity sign must be - for subtracting the amount from the maximum available quantity, + for adding the amount to the maximum available quantity, or blank for setting a new quantity. User Response: Correct the operation sign.
BMCECS3062 VALUE OF CHANGE IS NEGATIVE OR MORE THAN 9999
Explanation: The quantity resulting from the Change operation is either negative, or more than 9999. System Action: The Change request is rejected. User Response: Correct the input.
BMCECS3063 BLDL/LOAD FAILED FOR THE MODULE module
Explanation: Loading of module module failed. This may be due to one of the following:
The IOA Load Library is not in the load modules search list (STEPLIB + Linklist). Insufficient storage. Another system-originated reason which may be found in the syslog.
System Action: The program may stop executing. User Response: Contact Technical Support for assistance.
BMCECS3064 TABLE table DOES NOT EXIST IN LIBRARY library
Explanation: The Table Download option was selected for a Scheduling table, but the member was not found in the specified library. System Action: The Table Download request is rejected. User Response: Enter a correct table/library name.
BMCECS3065 KSL INTERNAL ERROR XXXX. INFO: info
Explanation: The server program detected an internal error.
Appendix B
Messages and codes
369
This error message is issued by program CTWSRVR, which is activated as part of IOAGATE, and is due to reasons beyond the users control. System Action: The user request is rejected. User Response: Contact Technical Support and provide the information displayed in the message.
BMCECS3066 ARCHIVED SYSOUTS DO NOT EXIST FOR THIS TASK
Explanation: There are no sysouts to be viewed. Either no sysout has yet been generated, or the existing sysout has been (manually) deleted.
BMCECS3067 WHY OPTION CAN BE USED ONLY ON TASK IN WAIT SCHEDULE STATE
Explanation: The Why option is used to determine the reason that a task is waiting to be scheduled; it cannot be used unless the task is in the Wait Schedule status. System Action: The user request is rejected.
BMCECS3068 STATISTICS DO NOT EXIST FOR THIS MEMBER
Explanation: An attempt was made to view statistics of a job for which no statistics are available. The Statistics File is updated only by the JCL procedure CTMJSA. If the job is being run for the first time in this particular system, job statistics may not yet have been accumulated. If the job has previously been run on this system, it is likely that CTMJSA is not run on a regular basis at your site. User Response: Check whether or not CTMJSA is run regularly at your site. If job statistics are required, then ensure that CTMJSA is run regularly.
BMCECS3069 MEMBER IS NOT A VALID SCHEDULING TABLE
Explanation: The Table Download/Upload option was selected for a Scheduling table which contains invalid data. System Action: The Download/Upload request is rejected. User Response: Correct the scheduling data in the mainframe or CONTROL-M/EM as necessary.
BMCECS3070 JOB jobname NOT FOUND IN TABLE tablename IN LIBRARY library
Explanation: The job was ordered from CONTROL-M/EM, but the job does not exist in the specified table. System Action: The job order request is rejected by the MVS GATEWAY.
User Response: Make sure that the job specified exists in table table_name and order the job again.
BMCECS3071 TABLE IN USE
Explanation: The Table Upload option was selected for a Scheduling table which is currently being edited by another user. A Scheduling table may not be saved while it is being edited by another user or application. System Action: The Table Upload request is rejected. User Response: Try again later.
BMCECS3072 TABLE table SAVED SUCCESSFULLY IN LIBRARY library
Explanation: This information message indicates that the specified Scheduling table was saved successfully as a result of a Table Upload operation.
BMCECS3073 MEMBER IS NOT A VALID IOA CALENDAR
Explanation: The Download/Upload option was requested for a calendar which contains invalid data. System Action: The Download/upload request is rejected. User Response: Correct the calendar data in the mainframe or CONTROL-M/EM as necessary.
BMCECS3074 CALENDAR calendar SAVED SUCCESSFULLY
Explanation: This information message indicates that the specified calendar was saved successfully as the result of an Upload operation.
BMCECS3075 CALENDAR IN USE
Explanation: The Upload option was selected for a calendar which is currently being edited by another user. A calendar may not be saved while it is being edited by another user. System Action: The Upload request is rejected. User Response: Try again later.
Appendix B
Messages and codes
371
BMCECS3076
MAXIMUM NUMBER OF ON CODES EXCEEDED
Explanation: During Download of the Active Jobs file, Update of the Active network or Table Download, a job was encountered which contained too many ON Codes. There is insufficient space in the internal buffer for the number of ON Codes in the job definition. System Action: Download of the Active Jobs file or Update of the Active network will continue, but the specific job will not be downloaded. If the job was encountered during Table Download, the Table Download fails. User Response: It is advisable to correct the job definition in the mainframe.
BMCECS3077 MEMBER HAS CHANGED SINCE LAST UPLOAD/DOWNLOAD
Explanation: An attempt was made to upload a Scheduling table or calendar, which has been modified by another user since the last time it was downloaded to the CONTROL-M/EM or uploaded from it. The Upload operation includes a check that the member in the mainframe has not been modified (except by a previous CONTROL-M/EM Upload operation) since it was last downloaded to CONTROL-M/EM. Someone modified the Scheduling table/calendar on the mainframe using the CONTROL-M online facility, and these modifications do not appear in the version of the Scheduling table/calendar recorded in the CONTROL-M/EM database. An upload at this point would overwrite theses modifications. System Action: The Upload request is rejected. User Response: Check who modified the member and for what reason. If you wish to override the modifications, use the Forced Table Upload or Forced Calendar Upload option to upload the member. If you wish to incorporate the modifications with your changes, download the updated member, add your changes and then upload it.
BMCECS3078 TABLE ALREADY EXISTS
Explanation: A new Scheduling table was created in the CONTROL-M/EM and an attempt was made to upload it, but a table with the same name already exists in the library. In order to avoid Scheduling tables being unintentionally overwritten, when a new Scheduling table is defined in the CONTROL-M/EM and an attempt made to upload it, IOAGATE checks if a table with the same name already exists in the mainframe. System Action: The Table Upload request is rejected.
372
User Response: If you wish to overwrite the existing table, use the Forced Table Upload option.
BMCECS3079 CALENDAR ALREADY EXISTS
Explanation: A new calendar was defined in the CONTROL-M/EM and an attempt was made to upload it, but a calendar with the same name already exists. In order to avoid calendars being unintentionally overwritten, when a new calendar is defined in the CONTROL-M/EM and an attempt made to upload it, IOAGATE checks if a calendar with the same name already exists in the mainframe. System Action: The Upload request is rejected. User Response: If you wish to overwrite the existing calendar, use the Forced Calendar Upload option.
BMCECS3080 CALENDAR calendar DOES NOT EXIST IN LIBRARY library
Explanation: The Download option was requested for a calendar, but the member was not found in the specified library. System Action: The Download request is rejected. User Response: Enter a correct calendar/library name.
BMCECS3081 TABLE tablename DELETED FROM LIBRARY library
Explanation: The table table_name was deleted from library library as requested by the CONTROL-M/EM user.
BMCECS3082 CALENDAR calendar_name DELETED
Explanation: A request from CONTROL-M/EM to delete calendar calendar_name from the calendar library was processed successfully.
BMCECS3083 THIS REQUEST CAN NOT BE PROCESSED DUE TO MVS ERRORS. PLEASE CHECK MVS GATEWAY
Explanation: An error occurred in the MVS GATEWAY which prevented execution of the specific request. User Response: Ask the MVS system administrator to determine the cause of the error in the MVS GATEWAY and correct it.
Appendix B
Messages and codes
373
BMCECS3084
CANNOT SAVE JOB DATA. INSUFFICIENT SPACE IN FILE. USE LESS DATA
Explanation: Data was added from CONTROL-M/EM to a job in the CONTROL-M active environment. When a job order is placed on the Active Jobs file, a certain amount of space is reserved for possible future addition of data by the user. This message appears whenever this space is exhausted. System Action: The new job data is not saved. User Response: Try to delete some data in the Job Editing form. If you are trying to add ON STEP statements, try to delete other ON STEP statements, for OUT conditions, delete unnecessary OUT statements, and the like. Deleting SHOUT WHEN messages usually releases enough space.
BMCECS3085 UNABLE TO FORCE OK A CYCLIC JOB
Explanation: The user issued the line command O (FORCE OK) for a cyclic job. Cyclic jobs cannot be Forced OK. System Action: The user request is ignored.
BMCECS3086 JOB IS IN USE BY ANOTHER USER. TRY AGAIN LATER
Explanation: An attempt was made to modify parameters of an active job while the job is in use by another user. Another user is currently viewing details of this job, either in the IOA Online environment (under screen 3.Z), or in another CONTROL-M/EM GUI. System Action: Modifications to the jobs parameters are not saved. User Response: Try again later.
BMCECS3088 CANNOT EDIT/VIEW JCL MEMLIB library BUT NO DALIB LIBRARIES FOUND
Explanation: A request to edit or view JCL was passed from CONTROL-M/EM for a job with MEMLIB =library. The request cannot be honored, since no DALIB DD statement exists in IOAGATE. System Action: The request is rejected. Editing and viewing JCL from CONTROL-M/EM requires a DALIB DD in IOAGATE. User Response: None.
BMCECS3089 INVALID VALUE "xxxxxxxxxx" FOUND IN FIELD "yyyyyyyy"
Explanation: An invalid value was found in specified field. System Action: The request is not issued. User Response: Enter a valid value in the specified field and reenter the request.
374
BMCECS3090
TABLE/MEMBER DOES NOT EXIST
Explanation: An attempt was made to save a table or member that does not exist. System Action: The table/member is not saved. User Response: To save a new table or member, erase the Y in the SAVE field and mark Y in the CREATE field. Press Enter.
BMCECS3091 TABLE/MEMBER ALREADY EXISTS
Explanation: An attempt was made to create a table/member that already exists. System Action: The table/member is not saved. User Response: Either mark Y in the SAVE field to save the new table/member over the old one, or change its name to a new name.
BMCECS3092 THE JOB BELONGS TO A MVS SCHEDULING GROUP UPDATING ITS GROUP NAME IS NOT PERMITTED
Explanation: An attempt was made to update the Group Name of a job that belongs to an MVS scheduling group. System Action: The request is not issued. User Response: None.
BMCECS3093 INVALID GROUP ID SPECIFIED
Explanation: The GROUPID parameter in a CONTROL-M/EM job order request contained an invalid value. System Action: The job order request is rejected by the MVS GATEWAY. User Response: Make sure that the GROUPID parameter contains one of the following values: ALONE, NEWG, LAST, LASTX, LASTE, LASTW.
BMCECS3094 'NEWG' ORDER OPTION NOT SUPPORTED YET
Explanation: The option to dynamically order a job into a new group rather than an existing group is currently not supported by the MVS GATEWAY. System Action: The job order request is rejected by the MVS GATEWAY.
BMCECS3095 ORDER REQUEST FAILED - GROUP ENTITY NOT IN ACTIVE JOBS FILE
Explanation: The group scheduling table specified in the order request does not exist in the Active Jobs file. System Action: The job order request is rejected by the MVS GATEWAY. User Response: Ensure that the order request specifies a group scheduling table that currently exists in the Active Jobs file.
CONTROL-M Messages from Other Platforms

The following are messages issued by CONTROL-M which may appear in a pop-up window in the CONTROL-M/EM GUI and may be recorded in the CONTROL-M log. CONTROL-M messages appearing on CONTROL-M platforms (for example, Unix or iSeries (AS/400) are described in the CONTROL-M Administrator Guide for the specific platform.
BMCCTM5063 CALENDAR calendar_ID NOT FOUND OR NOT COMPLETE
Type: Error. Explanation: You attempted to download the calendar calendar_ID, but either the calendar is not found or does not contain all the relevant years in the CONTROL-M/Server database. This message can also occur when ordering the User Daily. For more information, see the CONTROL-M/Server Administrator Guide for either Unix or Microsoft Windows. System Action: The calendar is not downloaded. User Response: Use CONTROL-M/EM to either create the calendar or to verify that all relevant years appear in the calendar.
BMCCTM5260 WARNING: SCHEDULING TABLE table_name UP TO DATE. REQUEST REJECTED
Type: Warning. Explanation: An attempt was made to upload scheduling table table_name. The Scheduling table contained in the CONTROL-M/Server database in the data center is the same version that exists in the CONTROL-M/EM database. Each scheduling table is maintained in two locations: in the CONTROL-M/Server database in the data center and in the CONTROL-M/EM database. Normally, after you modify a scheduling table and save it in CONTROL-M/EM, you must then upload it to the CONTROL-M/Server database in the data center. In this instance, someone already uploaded the scheduling table after it was last modified. System Action: The scheduling table is not uploaded to the data center. User Response: No action is required.
376
BMCCTM5261
WARNING: CALENDAR calendar_name UP TO DATE. REQUEST REJECTED
Type: Warning. Explanation: You attempted to upload calendar calendar_name. The calendar contained in the CONTROL-M/Server database in the data center is the same version that exists in the CONTROL-M/EM database. Each calendar is maintained in two locations: in the CONTROL-M/Server database in the data center and in the CONTROL-M/EM database. Normally, after you modify a calendar and save it in CONTROL-M/EM, you must then upload it to the CONTROL-M/Server database in the data center. In this instance, you or another user already upload the calendar after it was last modified. System Action: The calendar is not uploaded to the data center. User Response: No action is required.
BMCCTM5262 SCHEDULING TABLE table_name IS NOT UP TO DATE
Type: Error. Explanation: You attempted to download Scheduling table table_name. The Scheduling table contained in the CONTROL-M/Server database in the data center is an older version than the Scheduling table that exists in the CONTROL-M/EM database. Each Scheduling table is maintained in two locations: in the CONTROL-M/Server database in the data center and in the CONTROL-M/EM database. If you attempt to download a Scheduling table from the data center to the CONTROL-M/EM database, CONTROL-M verifies that it will not overwrite a newer version of the table with an older one. In this instance, the Scheduling table contained in the CONTROL-M/EM database is a later version than the table contained in the CONTROL-M/Server database. System Action: The Scheduling table is not downloaded. User Response: No action is required.
BMCCTM5263 SCHEDULING TABLE table_name DOES NOT EXIST
Explanation: You attempted to order or force a Scheduling table, but the table cannot be located in the CONTROL-M/Server database. A possible cause is that the table was created in CONTROL-M/EM and not uploaded to the CONTROL-M/Server database. System Action: The request is not performed.
User Response: Determine why the table does not exist and correct the situation.
BMCCTM5301 SERVER INTERNAL ERROR TYPE type
Explanation: The server program detected an internal error. This error message is issued by program P_CTMCS, which is activated as part of the CONTROL-M/EM Data Center Gateway, and is due to reasons beyond the users control. System Action: The user request is rejected. User Response: Contact Technical Support.
BMCCTM5302 INCOMPATIBLE GATEWAY VER. DATA CENTER VER. data_center_version. W.S. VER. workstation_version
Explanation: The Data Center Gateway version is not compatible with the Workstation Gateway version. Both gateways should be installed from the same installation version. If only one gateway was upgraded, the link cannot become active. System Action: The CONTROL-M/EM Data Center Gateway shuts down. User Response: Either upgrade the lower version gateway, or restore the upgraded gateway to the previous version.
BMCCTM5304 CANNOT action JOB job_number JOB NOT HELD
Explanation: Delete or Change was requested for a job which is not in Held status. Job job_number is not in Held status and therefore cannot be deleted/changed. System Action: The Delete/Change request is rejected. User Response: Hold the job. Wait until the Requested Held status is changed to Held, and then use the Change or Delete option.
BMCCTM5305 ACTIVE JOBS FILE IS LOCKED, TRY AGAIN LATER
Explanation: Another user is updating the file. The Active Jobs file is currently in use by another user or by the CONTROL-M Monitor. System Action: The user request is rejected. User Response: Try again later.
378
BMCCTM5306
CANNOT action JOB job_number JOB DOES NOT EXIST
Explanation: Job job_number of original scheduling date has already been deleted and therefore no action can be performed on it. System Action: The user request is rejected.
BMCCTM5307 CANNOT RERUN JOB job_number JOB NOT ENDED
Explanation: Job job_number of original scheduling date did not finish executing, and therefore it can not be rerun. System Action: The Rerun request is rejected.
BMCCTM5308 CANNOT DELETE JOB job_number JOB IN PROCESS
Explanation: You attempted to delete job job_number, but the job is executing. You can only delete a job which is awaiting scheduling or which has finished executing (ENDED). System Action: The user request is rejected. User Response: Free the job. Let CONTROL-M analyze it and bring it to ENDED status.
BMCCTM5309 CANNOT HOLD JOB job_number JOB ALREADY HELD
Explanation: Hold was requested for a job which is already held. System Action: Hold request is rejected.
BMCCTM5310 JOB job_number IS NOT WAITING FOR CONFIRMATION
Explanation: An attempt was made to confirm the restart of a job which is not waiting for confirmation. Confirm is valid only for jobs which are in Wait Confirmation status. System Action: The Confirm request is rejected.
BMCCTM5311 ERROR PROCESSING XML REQUEST. xml_message
Explanation: This information message indicates that the request could not be processed due to xml_message.
Appendix B
Messages and codes
379
BMCCTM5311XXX Number changed CONDITION condition WITH ORDER DATE odate DOES NOT EXIST
Explanation: Condition condition of original scheduling date odate was marked for deletion, but it was already deleted from the IOA Conditions/Resources file. Between the time the request was sent from the CONTROL-M/EM Control Application and the time it was processed by the Data Center Gateway, another IOA or CONTROL-M/EM user (or one of the IOA Monitors) deleted the condition from the Conditions/Resources File. System Action: The Delete request is rejected.
BMCCTM5312 CONDITION condition WITH ORDER DATE odate ALREADY EXISTS
Explanation: An attempt was made to add condition condition of original scheduling date odate, but this condition already exists in the Conditions/Resources file. System Action: The Add request is rejected.
BMCCTM5313 CONTROL RESOURCE control_resource ALREADY EXISTS
Explanation: An attempt was made to add Control resource control_resource, but this resource already exists in the IOA Conditions/Resources File. System Action: The Add request is rejected.
BMCCTM5314 CONTROL RESOURCE control_resource DOES NOT EXIST
Explanation: Control resource control_resource was marked for deletion, but it has already been deleted from the IOA Conditions/Resources File. Between the time the request was sent from the CONTROL-M/EM Control Application and the time it was processed by the Data Center Gateway, another IOA or CONTROL-M/EM user (or one of the IOA Monitors) deleted the Control resource from the Conditions/Resources File. System Action: The Delete request is rejected.
BMCCTM5315 QUANTITATIVE RESOURCE quantitative_resource IN USE CANNOT DELETE
Explanation: An attempt was made to delete Quantitative resource quantitative_resource, but it is in use by a job under CONTROL-M. An Active Job under CONTROL-M is using a certain quantity of the Quantitative resource. Therefore, the resource cannot be deleted. System Action: The Delete request is rejected. User Response: Wait until the job finishes executing and then try again.
BMCCTM5316
QUANTITATIVE RESOURCE quantitative_resource ALREADY EXISTS
Explanation: An attempt was made to add Quantitative resource quantitative_resource, but this Quantitative resource already exists in the IOA Conditions/Resources File. System Action: The Add request is rejected.
BMCCTM5317 QUANTITATIVE RESOURCE quantitative_resource DOES NOT EXIST
Explanation: Quantitative resource quantitative_resource was marked for deletion, but it has already been deleted from the IOA Conditions/Resources file. Between the time the request was sent from the CONTROL-M/EM Control Application and the time it was processed by the Data Center Gateway, another IOA or CONTROL-M/EM user (or one of the IOA Monitors) deleted the Quantitative resource from the Conditions/Resources File. System Action: The Delete request is rejected.
BMCCTM5318 VALUE OF CHANGE IS OUT OF RANGE
Explanation: The quantity resulting from the Change operation is either negative, or more than the total value. System Action: The Change request is rejected. User Response: Correct the input.
BMCCTM5319 SYSOUT DOES NOT EXIST FOR THIS JOB
Explanation: There are no sysouts to be viewed. Either no sysout has yet been generated, or the existing sysout has been (manually) deleted.
BMCCTM5320 WHY OPTION APPLIES ONLY FOR JOB IN WAIT SCHEDULE STATE
Explanation: The Why option is used to determine the reason that a job is waiting to be scheduled; it cannot be used unless the job is in the Wait Schedule status. System Action: The user request is rejected.
BMCCTM5321 STATISTICS DO NOT EXIST FOR THIS FILE/MEMBER
Explanation: An attempt was made to view statistics of a job for which no statistics are available.
Appendix B
Messages and codes
381
The Statistics File is updated only by batch jobs which have completed successfully. User Response: Verify that job has completed successfully.
BMCCTM5323 SECURITY PROTECTION VIOLATION
Explanation: You are not authorized to perform the requested function. This message is issued by the CONTROL-M security mechanism. Your request may have been rejected for one or more of the following reasons:
You do not have a user account on the CONTROL-M platform. You do not have the required authority from the operating system on the CONTROL-M platform to perform the requested function. You do not have CONTROL-M authorization to perform the requested function.
System Action: The user request is rejected. User Response: Contact your system security administrator.
BMCCTM5324 SYSOUT FILE IS TOO WIDE
Explanation: You attempted to use the View Sysout option to examine job sysout, but one or more lines in the sysout are too long to be transmitted from the CONTROL-M data center to CONTROL-M/EM. System Action: The request sysout is not displayed. User Response: View the sysout directly in the CONTROL-M data center.
BMCCTM5330 AGENT node_ID/group is unavailable. Request desc failed
Explanation: A user request which was forwarded to an agent platform or to a group of platforms was not executed because of failed communication with the agent platform(s) or because the status of the agent platform is Disabled. The user attempted to use one of the following options from the Job Node menu: Sysout, Documentation, View JCL/Script or Edit JCL/Script. The job was scheduled to run on or was submitted to an agent platform. CONTROL-M/Server was not able to pass the request to the agent platform because of failed communication or because the status of the agent platform is Disabled. If the Job Processing definition contained the name of a node group, CONTROL-M/Server was not able to communicate with any of the agent platforms in the node group.
382
System Action: The user request is not executed. User Response: Verify that the status of the agent platform is not Disabled. Determine the cause of the failed communication and correct it.
BMCCTM5500 SERVICE NOT ALLOWED NOW reason
Explanation: A user request sent from CONTROL-M/EM to CONTROL-M cannot be performed temporarily due to the reason stated. System Action: The user request is rejected. User Response: Wait for the condition described in reason to pass, then re-issue the request.
BMCCTM5501 SERVICE INSTANCE CANCELED DUE TO INTERNAL ERROR
Explanation: A data packet sent by CONTROL-M/EM to CONTROL-M was not in the correct format. System Action: The request contained in the packet is rejected. User Response: Perform the rejected action again on CONTROL-M/EM.
Appendix B
Messages and codes
383
384
Appendix
C
Context Always available Always available Available when a ViewPoint is opened Always available
Menu options
This appendix contains tables that list all CONTROL-M/EM menu options, including descriptions and references to alternate methods for accessing the same option. File Menu options
Availability Option New ViewPoint Open ViewPoint Close ViewPoint Description Create a new ViewPoint using the ViewPoint Wizard. For more information, see Chapter 2, Viewing the production environment. Select an existing ViewPoint to display in a CONTROL-M/EM ViewPoint window. Close the current ViewPoint window. From Menu bar Entity ViewPoints
Table 95
Menu bar Menu bar
ViewPoints ViewPoints
Exit
Exit CONTROL-M/EM.
Menu bar
ViewPoints
Table 96
Option Find a Job
Edit Menu options

Availability Description Locate nodes based on specific search criteria. For more information, see Finding nodes on page 95. From Menu bar Entity Job nodes Context Available when a ViewPoint is opened Always available
ViewPoint Manager
Create a new ViewPoint, Collection, Filter or Menu bar Hierarchy, or modify an existing one. For more information, seeCreating ViewPoints using the ViewPoint Wizard on page 121.
ViewPoints Collections Filters Hierarchies
Appendix C Menu options
385
Table 97
Action Menu options (Part 1 of 4) Legend: M: Menu bar, N: Navigation tree, F: FlowDiagram
Availability Description M N F Entity Context
Option
This menu is displayed only if a job or group scheduling table is selected. Details about each of the job action options are described in Chapter 4, Managing job processing definitions. Expand / Collapse Expands the selected node to display levels lower than the current selected node, or collapses the selected node to hide lower levels. Step In Changes the display in FlowDiagram view to display nodes a level lower than the current selected node.

Available for High-level nodes, based high-level nodes on the current hierarchy Available for High-level nodes, based high-level nodes on the current hierarchy Always available Low-level nodes, based on the current hierarchy Always available High-level nodes, based for high-level on the current nodes only hierarchy
Step Out Changes the display in FlowDiagram view to display nodes a level higher than the current selected node.
Status Summary
CONTROL-M node: Displays details about the display and synchronization of CONTROL-M (for example, is a refresh needed). Other high-level node: Displays details about the status of the jobs in the set (for example, group, application).
Properties Views the editing form for the entities that are selected.

Jobs Group Scheduling tables Job Group Scheduling tables Job Group Scheduling tables
Can be performed on only one selected entity Can be performed on any number of entities Can be performed on any number of entities
Hold Holds (puts a lock on) the selected entities and allows the user to change their properties during run time.

Confirm Confirms the restart of selected jobs (if CONTROL-M/Restart is installed) or the submission of the jobs.

386
Table 97
Availability Description M N F

Option Free
Entity Job Group Scheduling tables Job
Context Can be performed on any number of entities Can be performed on any number of entities Can be performed on any number of entities Can be performed on any number of entities Can be performed on any number of entities Can be performed on any number of entities Can be performed on any number of entities Can be performed on any number of entities
Releases the hold (lock) on the selected entities so the entities can continue running.
Rerun Reruns the selected jobs.
Restart Restarts the selected jobs using CONTROL-M/Restart.
Job
React [MVS] Reactivates post-processing for the selected job.
Job
Delete Deletes the selected jobs.

Job Group Scheduling tables Job Group Scheduling tables Job
Undelete Undeletes the selected jobs.

Kill Stops the selected running jobs.
Force OK Sets the selected jobs status to OK.

Job Group Scheduling tables
387
Table 97
Option Sysout
Entity Job
Context Can be performed on only one selected entity Can be performed on only one selected entity Can be performed on only one selected entity Can be performed on only one selected entity Can be performed on only one selected entity Can be performed on only one selected entity Can be performed on only one selected entity Can be performed on only one selected entity
Views the selected jobs Sysouts.
Statistics Views statistics of the selected jobs latest runs.

Job Group Scheduling tables Job
Documentation Views the selected jobs documentation.
Log Views log messages for the selected job.

Job Group Scheduling tables Job
View JCL/Script Views the selected jobs JCL or job script statements.
Edit JCL/Script Edits the selected jobs JCL or job script statements.
Job
Why Determines why the selected job has not yet been executed.

Job Group Scheduling tables Job Group scheduling table
Enhanced Why Views the predecessors jobs and Group Scheduling table for a selected job or Group Scheduling table. For more information, see Enhanced Why on page 104

388
Table 97

Option Activate Application
Entity Jobs Group Scheduling tables Job Group Group Scheduling tables Set of jobs Group Scheduling tables Job Group Scheduling tables Set of jobs and Group Scheduling tables
Context Always available
Runs a third-party program using parameters supplied in an application activation definition. For more information, see Activating Applications on page 215. Find in Flowdiagram Locates and displays the node (as selected in the Navigation Tree) in the FlowDiagram. For more information, see Locating a node in a FlowDiagram using the Navigation Tree on page 94. Neighborhood Activates the neighborhood function, described in Neighborhood on page 109.
Can be performed on only one selected entity
Can be performed only on a set of selected entities Can be performed on a set of selected entities
Critical Path Activates the Critical Path function, described in Critical path on page 99.

Table 98
Option Toolbar Status Bar
View Menu options (Part 1 of 2)

Availability Description Displays or hides the CONTROL-M/EM toolbar. Displays or hides information at the bottom of the screen. From Menu bar Menu bar Menu bar Entity Toolbar Status bar Window Context Always available Always available Available when a ViewPoint is open Always available
Refresh Now Refreshes the display.
Messages
Menu bar Views messages describing general errors that occurred in CONTROL-M/EM, such as lack of available memory to perform a task. If no error occurred, the Messages dialog box is empty.
Messages dialog box
389
Table 98
Option Action Report Toggle Selection
View Menu options (Part 2 of 2)

Availability Description Displays errors that occurred when From Menu bar Entity Context Upon request or when an error occurs Available when multiple nodes are selected Available when multiple nodes are selected in a Viewpoint Available when a ViewPoint is open
actions were being performed. Changes the focus from node to node when several nodes are selected simultaneously in the Flow Diagram.
Menu bar
Job Action Report window

Selected nodes
View Selection
Allows viewing of only the selected nodes in the current, regular ViewPoint.
Menu Bar
Selected nodes
Select All
Selects all nodes visible in the flow diagram.
Menu bar
All nodes
Table 99
Option Global Conditions
Resources Menu options

Availability Description Views or modifies global conditions definitions. For more information, see Chapter 6, Displaying and defining resources and conditions. From Menu bar Entity Global conditions Context Available when a ViewPoint is open Available when a ViewPoint is open Available when a ViewPoint is open Available when a ViewPoint is open
Prerequisite Conditions
Views or modifies prerequisite conditions in Menu bar the active environment. For more information, see Chapter 6, Displaying and defining resources and conditions. Views or modifies Quantitative resources in Menu bar the active environment. For more information, see Chapter 6, Displaying and defining resources and conditions. Views or modifies Control resources in the active environment. For more information, see Chapter 6, Displaying and defining resources and conditions. Menu bar
Quantitative Resources
Quantitative conditions
Control Resources
Control resources
390
Table 100 Tools Menu options

Availability Option Order/Force Description Orders or forces a jobs or group scheduling tables. See Chapter 3, Defining a production environment: Introduction to CONTROL-M/Desktop. From Menu bar

Entity Jobs Group Scheduling tables
Context Always available
CONTROL-M/ Desktop
Views or modifies Scheduling tables Menu bar or job processing definitions. For more information, see the CONTROL-M/Desktop User Guide. Monitors and handles alerts. See Chapter 5, Monitoring alerts and errors. Menu bar
CONTROL-M/De Always sktop available
Alerts
Alerts
Always available Always available
Communications => Monitors communication status Status between each CONTROL-M and CONTROL-M/EM. For more information, see Chapter 7, Communication status. Communications => Creates or modifies CONTROL-M Administration definitions. For more information, see the CONTROL-M/Enterprise Manager Administrator Guide. Authorizations
Menu bar
Communication between CONTROL-M and CONTROL-M/ EM CONTROL-M definitions
Menu bar
Always available
Menu bar Specifies authorizations for CONTROL-M/EM users. For more information, see the Security chapter in the CONTROL-M/Enterprise Manager Administrator Guide. Changes password for logging in to CONTROL-M/EM. For more information, see Logging in on page 65. Menu bar
User authorizations
Always available
Change Password
User passwords
Always available
Menu bar Activate Defines or edits application Applications Editor activation definition parameters for a third-party program. For more information, see Activating Applications on page 215. Options Sets customization options. For more Menu bar information, see Chapter 10, Customization.
Applications
Always available
CONTROL-M /EM options
Always available
391
Table 101 Window Menu options

Option Cascade Tile Arrange Icons Split <window list> Description Shows all open windows in cascade format. Shows all open windows in tile format. Rearranges icons in the windows. Lets you move the split between the Net Overview and the upper part of the CONTROL-M/Enterprise Manager window. Lists the windows currently open, and lets you switch to any window in the list.
Table 102 Help Menu options

Option Tip of the Day Tutorial Description Displays the Tip of the Day, and lets you determine if you want the Tip of the Day to display automatically when CONTROL-M/EM is started. Displays the CONTROL-M/EM tutorial.
Help Contents and Displays help topics. Index About CONTROL-M/ Enterprise Manager Displays information about CONTROL-M/EM.
Table 103 Options of the FlowDiagram pop-up menu

Menu When you right-click outside any node in the FlowDiagram, a pop-up menu is displayed with these options. Option Arrange All Zoom In Zoom Out Step In Step Out Options Description Reorders the nodes in the flow diagram for clarity. Increases the percentage of magnification of the nodes displayed in FlowDiagram view by twenty-five percent. Decreases the percentage of magnification of the nodes displayed in FlowDiagram view by twenty-five percent. Changes the display in FlowDiagram view to display nodes a level lower than the current selected node. Changes the display in FlowDiagram view to display nodes a level higher than the current selected node. Opens the Options window to set customization options. See Chapter 10, Customization.
392
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Glossary
A
Active Jobs File The Active Jobs file lists all jobs scheduled for submission in the current day. Each job in the Active Jobs file is not submitted until all conditions in the job processing definition for the job are satisfied. The Active Jobs file is in the CONTROL-M database. Active Environment The Active Jobs files and the current status of all Quantitative and Control resources and all prerequisite conditions in all CONTROL-M installations that are currently connected to CONTROL-M/EM. Agent Platform Platform on which CONTROL-M/Agent runs. The Agent platform handles requests from CONTROL-M/Server to execute jobs or provide information. Application In a CONTROL-M/Enterprise Manager ViewPoint, jobs are organized into a hierarchy based on certain parameters in the job processing definition for each job. Application is one of these parameters. It is in the default hierarchy which is: CONTROL-M installation followed by application, group and job.
C
Calendar A collection of dates that are used by CONTROL-M to schedule the ordering of jobs. Calendar Manager A window where calendars are listed by name for viewing or modifying purposes. The Calendar Manager is accessed through CONTROL-M/Desktop. Collection A Collection defines which jobs in the enterprise are loaded into memory. Conditions Table A component of the CONTROL-M database that lists the current status of all prerequisite conditions in the CONTROL-M installation.
Glossary
393
CONTROL-M Software product that schedules, submits, tracks and follows up the execution of jobs in a specific installation. In certain releases, CONTROL-M functions are divided between two separate components: CONTROL-M/Server and CONTROL-M/Agent. CONTROL-M Database Repository of operational data relating to the functioning of the CONTROL-M installation. Contents of the database include the Active Jobs file, Scheduling tables (job processing definitions) and the Resources/Conditions table. The database is maintained by CONTROL-M using Sybase Adaptive Server. CONTROL-M Date Date used by CONTROL-M to assign the Scheduling date (Odate) to jobs. CONTROL-M Installation One or more computers controlled by a single installation of CONTROL-M. In older implementations of CONTROL-M, a CONTROL-M installation typically consists of a single computer. In the Server/Agent Technology implementation of CONTROL-M, a CONTROL-M installation consists of a Server platform and all the Agent platforms that it handles. In a CONTROL-M/Enterprise Manager ViewPoint, jobs are organized into a hierarchy based on certain parameters in the job processing definition for each job. CONTROL-M is one of these parameters. It is the highest level in the default hierarchy, followed by application, group and job. CONTROL-M Log Log containing a complete audit trail of every event occurring under the CONTROL-M production environment. CONTROL-M Platform Platform on which CONTROL-M runs. Under the Server/Agent Technology implementation of CONTROL-M, this is the platform on which CONTROL-M/Server runs. CONTROL-M/Agent Under the Server/Agent Technology implementation of CONTROL-M, the component of CONTROL-M that runs on each Agent platform. CONTROL-M/Agent submits jobs, performs requests from CONTROL-M/Server, and performs post-processing analysis of completed jobs. CONTROL-M/Desktop Application used to define and manage job processing definitions, Scheduling tables and Calendars. CONTROL-M/Desktop is a stand-alone application that can also be activated directly using the CONTROL-M/EM GUI. Creation and modification of job definitions, uploading and downloading tables, and forcing and ordering jobs are executed via CONTROLM/Desktop.
394
CONTROL-M/Server Under the Server/Agent Technology implementation of CONTROL-M, the component of CONTROL-M that runs on the Server platform. CONTROL-M/Server maintains the CONTROL-M database (including the Active Jobs file), schedules jobs, performs load balancing, sends job-handling requests to Agent platforms, and handles requests from CONTROL-M/EM. Control Resource User-defined physical or logical resource in a CONTROL-M installation. For each job the user specifies whether the job requires exclusive or shared access to the resource. CONTROL-M verifies that a job is not submitted for execution unless the Control resources required by the job are available in the required state (shared/exclusive). This prevents deadlock situations or contention between jobs for a given resource. Control resources are recorded in the Conditions/Resources table. CONTROL-M/Enterprise Manager or CONTROL-M/EM Software product that provides a central point of control for CONTROL-M installations. CONTROL-M/EM provides the GUI that allows users to graphically view the status of job schedules and execution in CONTROL-M installations, to issue requests for additional information, to make changes in the Active Jobs file, and to handle problems. CONTROL-M/EM also passes global conditions among CONTROL-M installations. CONTROL-M/Enterprise Manager Server or CONTROL-M/EM Server Process that handles communication between CONTROL-M/EM GUI workstations and other components of CONTROL-M/EM. The CONTROL-M/EM Server executes database queries, calculations and procedures for each GUI, thereby lessening its workload and streamlining productivity by enabling data-sharing between GUIs. Multiple CONTROL-M/EM Servers can be installed in a CONTROL-M/EM environment.
D
Download (of Active environment) Transmission of the Active environment of a given CONTROL-M installation to the CONTROL-M/EM database. This allows CONTROL-M/EM to display of the current situation in the CONTROL-M installation. Download occurs upon completion of the New Day procedure, after which updates are constantly issued to maintain the accuracy of the Active environment.
F
Filter A Filter defines which jobs loaded in the CONTROL-M/EM database are displayed in the CONTROL-M/Enterprise Manager ViewPoint window. Force To force a job is to instruct CONTROL-M to place the job in the Active Jobs file for possible submission, regardless of the scheduling parameters in the job processing definition for the job. See also Order.
Glossary
395
G
Gateway The process that handles communication between CONTROL-M and CONTROL-M/EM. There are gateway processes on both the CONTROL-M platform and on the CONTROL-M/EM workstation. General Daily Procedure See New Day Procedure. Global Alerts Server The process that identifies and distributes alerts between CONTROL-M installations and CONTROL-M/EM workstations. The Global Alerts Server connects to each CONTROL-M/EM gateway to receive alerts from CONTROL-M and transmit them to the CONTROL-M/EM GUIs. Global Condition A prerequisite condition that is passed between CONTROL-M installations via CONTROL-M/EM. Global conditions allow jobs in one CONTROL-M to be dependent on completion of a job in a different CONTROL-M. Global Conditions Server The process that identifies and distributes global conditions between CONTROL-M installations. The Global Conditions Server connects to each CONTROL-M/EM gateway to receive and transmit prerequisite conditions to the appropriate CONTROL-M. Group In a CONTROL-M/Enterprise Manager ViewPoint, jobs are organized into a hierarchy based on certain parameters in the job processing definition for each job. Group is one of these parameters. It is in the default hierarchy which is: CONTROL-M installation followed by application, group and job.
H
Hierarchy A hierarchy defines how the jobs selected by the Collection and Filter are displayed in the CONTROL-M/Enterprise Manager ViewPoint window.
J
Job Editing Form Used to view, specify, or modify job processing parameters for the job. The Job Editing Form is accessed through CONTROL-M/Desktop. Job Processing Definition Set of user-defined parameters for each job which provide CONTROL-M with detailed instructions on processing the job. job processing definitions are organized into Scheduling tables.
396
Job Processing Parameter Generic name for one of the user-defined parameters that comprise a job processing definition.
L
Load Balancing CONTROL-M mechanism for maximizing throughput of production jobs by automatic selection of the platform to execute each job, based on workload considerations.
M
MSSQL Server See SQL Server.
N
New Day Procedure Formerly General Daily Procedure. Daily scheduling and housekeeping procedures that run on the Server platform. The CONTROL-M date is advanced to the next day when this procedure runs. Node Group Under the Agent Technology implementation of CONTROL-M, a user-defined collection of Node IDs. A node group is specified in a job processing definition to indicate a group of Agent platforms from which CONTROL-M/Server can select a platform to execute the job. Node ID Under the Agent Technology implementation of CONTROL-M, name by which an Agent platform is identified to the Server platform. This is generally the Agent platforms host name.
O
Odate (Original Scheduling Date) Jobs managed by CONTROL-M are assigned a date at the time they are ordered (placed in the Active Jobs file). This date, referred to as the Odate, is the CONTROL-M date at the time the job is ordered and represents the date on which the job should be submitted for execution. Odate is also the default date assigned to prerequisite conditions at the time they are created. The variable ODAT (representing the Odate) is used when defining job dependencies to insure that a job waiting for completion of another job is only triggered by a job with the same working date. Order To order a job is to request that CONTROL-M review the scheduling parameters in the job processing definition for the job and, if the parameters are satisfied, place the job in the Active Jobs file for possible submission. See also Force.
Glossary
397
P
Prerequisite Conditions or Conditions A flag representing a user-specified situation or condition. Submission of a job for execution can be made dependent upon the existence of one or more prerequisite conditions. Prerequisite conditions are recorded in the Conditions/Resources table.
Q
Quantitative Resource User-defined variable representing a resource in the CONTROL-M installation. The user defines the total quantity of this resource in the CONTROL-M and, for each job, the quantity required/used by that job. CONTROL-M verifies that a job is not submitted for execution unless the Quantitative resources required by the job are available. Quantitative resources are recorded in the Conditions/Resources table.
R
Resources Table A component of the CONTROL-M database that lists the current status of all Control resources and Quantitative resources in the CONTROL-M installation.
S
Scheduling Table A collection of related job processing definitions. Scheduling tables are stored in the CONTROL-M database (and duplicated in the CONTROL-M/EM database). Scheduling tables are ordered by the New Day procedure or User Daily jobs. Scheduling Table Manager Used to define, maintain and control Scheduling tables in the CONTROL-M/EM database. The Scheduling Table Manager is accessed through CONTROL-M/Desktop. Server Platform Under the Agent Technology implementation of CONTROL-M, platform on which CONTROL-M/Server runs. The Server platform communicates with the CONTROL-M/EM workstation and with the Agent platforms. Sybase Adaptive Server Software product used by CONTROL-M/EM to maintain the CONTROL-M/EM database. The database can be maintained using either a dedicated instance of Sybase Adaptive Server (provided with CONTROL-M/EM for Unix) or an existing instance of a Sybase Adaptive Server (for Windows, provided by the user). The database can also be maintained using an Oracle Server or an MSSQL Server.
398
U
User Daily Job User-defined job that can be used to automate the ordering of production jobs.
V
ViewPoint The means for adapting the view of the enterprise to suit the users requirements. A ViewPoint defines which jobs are loaded into the database (Collection), which jobs are displayed (Filter), and how they are displayed (Hierarchy) in the CONTROL-M/Enterprise Manager ViewPoint window.
Glossary
399
400
Index
A
Action menu Group Scheduling tables 221 Job handling 204 Actions_Report 119 Activate Applications Editor buttons 217 description 216 fields 216 activating applications 215 Active environment description 27 updating 32 Active Group Errors report 310 Active Jobs file communication 273 downloading 33 Active Jobs report 309, 313 Active Links report 310 Active Loop Errors report 310 Active Manual report 310 Active Net description 316 Active Network Audit report 312 Active panel Group Editing form 224 Job Editing form 185 active report types 309 ADD control 346 Add Mask button Data Source panel 289 Add Mask dialog box Report Wizard 289 ADD RESOURCE command (MVS) 346 adding control resources 244 prerequisite conditions 214, 253 Adjust Condition parameter 348 Administration facility description 30 Agent platform description 35 Agents Administration facility 30 alerts adding notes 236 Alert Details window 237 Alerts window 232 color coded 234 CONTROL-M 231 defaults 334 filtering 236 flashing taskbar button 234 flow diagram 236 Global Alerts server 26, 232 handling 236 OPER message 351 OPER2 message 351 order ID of 0 239 OS/390 351 status 235, 238 troubleshooting 239 U-ECS message 351 Alerts panel Options dialog box 334 Alerts report 311 Alerts window actions 233 automatic opening 234 communication 232 description 231 field descriptions 238 filter criteria 235 opening 232 options 232 preferences 234 view 233 All Alerts report 313 All Jobs Collection default ViewPoint 130 All Jobs filter default ViewPoint 130 All Open ViewPoints Reconnection panel 336 Alternative Server Selection dialog box 337 Alternative Servers Reconnection panel 336 APPL job parameter 348 Application icons 82 Application Activation
Index
401
changing definition name 219 definition 215, 217 deleting definition 219 description 215 editor 216 Applications window 216 Apply button Control Resources window 243, 249, 257 Prerequisite Conditions window 253 Archived Background Flowdiagram-Colors panel 333 Archived Net description 316 Archived ViewPoint data center 317 date 317 description 315 displaying 316 duration 317 end time 317 net name 317 start time 317 Arrange All Environment-Display panel 327 Audit Operation field Audit report Filter panel 299 Audit report 311, 312 Filter panel 299 authorization displaying alerts 234 Auto Open Viewpoint Environment-General panel 326 Auto-Archive parameter OS/390 348 AutoEdit facility CTMCAES utility 347 online simulation 347 AutoEdit variables application specific 28 description 38 group jobs 227 Job Editing form 196 Automatic Refresh Environment-Display panel 327 Automatic transfer (download) description 33 Automatically connect to Global Alerts Server Alerts panel 334 Automatically open ViewPoint option ViewPoint wizard 122 Automatically reconnect Reconnection panel 336 Average Run Time field 187
B
background Flowdiagram-Colors panel 333 backup GUI server 335 basic scheduling parameters calendars 173 Best Fit option 72 BMC Batch Impact Manager job node state 86 BMC Software, contacting 2 Bring Alerts window to front Alerts panel 334 Browse button 217
C
Calendar Definition window opening 175 Calendar Manager window 174 calendars creating 173 defining 175 Modified field 164 periodic 173 relative 173 security 31 synchronization 163 Change option OS/390 346 Choose a Report Type New Report dialog box 300 Clear button Control Resources window 243, 249, 257 Prerequisite Conditions window 253 Close button Control Resources window 244, 249, 257 Prerequisite Conditions window 253 Codes parameter Job Editing form 201 Collections Collection window 124 creating 133 creating a filter 147 defining 133 deleting 135 description 90 editing 125 Include In/Exclude From criteria 138 modifying 134 modifying a filter 148 selection criteria 135 selection operators 137 colors communication status 272 high-level nodes 85 job nodes 84
402
communication Active Jobs file 273 Alerts panel settings 334 Alerts window 232 connection failure 274 CONTROL-M status 272 downloading 273 gateway route 272 initializing 273 net status 273 path inactive 272 problem resolution 274 Reconnect operations 275 Reconnect window 274 reconnecting 273 reconnecting to GUI Server 335 refreshing Status window 273 status colors 272 status window 271 synchronization 32, 272 Conditions Flowdiagram-Colors panel 333 conditions adding 347 erasing 347 identifying dependent jobs 109 Conditions panel Job Editing form 192 Conditions/Resources screen (MVS) 346 Confcal parameter OS/390 jobs 348 Confirm option Action menu 206 Group Scheduling tables 221 Confirm parameter OS/390 jobs 348 Confirmations panel Options dialog box 340 Report facility defaults 307 Connector Flowdiagram-Colors panel 333 Contexts tab Diagnostic panel 340 CONTROL parameter 348 Control resources automatic update 328 description 46 downloading 33 example 46 online management (MVS) 346 viewing jobs that share resources 245 window 242, 243 Control Resources report 310 CONTROL-M Archived ViewPoint 317 Communication Status window 272 components 39 database synchronizing 163 definition 34 disabled 272 job handling 51 message descriptions 353 Shout facility 238 submission criteria 45 CONTROL-M field Alerts window 237 Order/Force Job dialog box 170 CONTROL-M name Prerequisite Conditions window 252 CONTROL-M/Agent Node groups 55 CONTROL-M/Desktop description 25 CONTROL-M/EM communication 32 communication status 271 gateway connection 272 gateway representation 272 logging in 65 logging in from the command line 68 logging in to different GUI Server 66, 67 monitoring components 30 security 31 server name 66 CONTROL-M/EM database description 25 synchronizing with CONTROL-M 163 CONTROL-M/EM GUI description 25 CONTROL-M/EM ViewPoint window 27 CONTROL-M/EM window customization 323 description 69, 77 Flow Diagram view 79 navigation techniques 115 Net overview 80 refresh options 93 resizing 79 selection option 116 Step In/Step Out 96, 392 CONTROL-M/Server description 35 CONTROL-R Confirm Restart option 205 sysout viewing 213 converting old reports 313 Copy template button Report Template manager 304 counter Control Resources window 243 CPU job statistics 211 Create a New Report area
Index
403
New Report dialog box 300 overview 281 Create report from Template area 279 Create report using Report Wizard New Report dialog box 300 Create report with new template 281, 300 creating collection filters 147 Collections 133 scheduling tables 343 ViewPoint hierarchies 151 ViewPoints 130 critical parameter OS/390 348 critical path calculation 100 control resources 243 description 99 example 59 load balancing 59 required resources 248 Crystal Report application 277 ctmloadset utility 60 Current Status field group scheduling 224 customer support 3 customizing Alerts panel 334 CONTROL-M/EM window 323 reconnection defaults 335 Reporting facility defaults 304 CYCLIC job status 84 cyclic jobs holding 209 icon 82 Cyclic Jobs report 313 Cyclic Log file Diagnostic panel 339 Cyclic parameter OS/390 348 OS/390 348 Days Calendar parameter defining calendars 173 Days parameter defining calendars 173 OS/390 348 db_pass parameter emreportcli utility 309 db_user parameter emreportcli utility 309 DCAL parameter 348 D-CAT job processing parameter 348 Default Levels button hierarchy definition 152 defaults modifying 323, 324 Reporting facility 304 ViewPoints 130 Defined type Quantitative Resources window 248 defining Application Activation definition 217 calendars 175 CONTROL-M installations 34 fields to be in a report 292 Group By criteria 293 new jobs 343 one-time reports 300 report template 285 defining reports 284 DEFINITION ACTIVE FROM job processing parameter 348 DEFINITION ACTIVE TO job processing parameter 348 definition report types 310 Definitions Group Errors report 311 Definitions Loop Errors report 311 Delete button 217 Control Resources window 244, 249, 257 Prerequisite Conditions window 253 Delete option Action menu 206 Group Scheduling tables 221 Delete template button Report Template manager 304 Deleted (node state) 86 Deleted field Group Scheduling details 224 deleting Application Activation definition 219 Collections 135 control resources 244 job definitions 343 jobs 206 prerequisite conditions 253 scheduling tables 343 ViewPoint filters 149
D
data centers Archived ViewPoint 317 communication status 271 icons 82 Data Source panel 288 databases CONTROL-M/EM 25 DATEMEM parameter OS/390 348 dates Archived ViewPoint 317 Odate 45 Dates parameter
404
Viewpoint hierarchies 152 ViewPoints 132 DESC parameter OS/390 jobs 348 details Group Scheduling tables 221 Diagnostic Levels Diagnostic panel 340 Diagnostics panel Options dialog box 338 Discrete Value field Enter Parameter Values dialog box 280 Display refreshing 93 Viewpoints 93 Display condition nodes Flowdiagram Links panel 332 Display Do Conditions Flowdiagram Links panel 332 display language 65 Display links behind nodes Flowdiagram Links panel 332 Display n Jobs Actions in Report Environment-Display panel 328 Display n nodes in pack Flowdiagram-General panel 330 Display n nodes in separator Flowdiagram-General panel 330 Display Optional In Condition Flowdiagram Links panel 332 Display Options Environment-Display panel 327 Display Out Conditions with minus Flowdiagram Links panel 332 Display scheduling groups count Environment-Display panel 328 Display status colors in Tree View Environment-Display panel 328 displaying documentation 346 job details 345 prerequisite conditions 332 Report Template Manager 303 reports 282 statistics 345 Do Cond parameter OS/390 348 DO CTBRULE job processing parameter 348 Do Forcejob parameter OS/390 348 DO Ifrerun parameter OS/390 348 Do Mail parameter OS/390 348 Do NOTOK parameter OS/390 348 Do OK parameter OS/390 348 Do Rerun parameter OS/390 348 Do Set parameter OS/390 348 Do Shout parameter OS/390 349 Do statements Job Editing form 198 Do Stop Cyclic parameter OS/390 349 Do Sysout parameter OS/390 349 Doc Mem parameter viewing specified file 206 DOC parameter MVS 346 DOCLIB parameter OS/390 349 DOCMEM parameter OS/390 349 documentation Action menu option 206 Double click on item to Flowdiagram-Nodes panel 331 downloading active environment 32 scheduling tables 165 Due Out group scheduling 224 OS/390 job parameter 349 Duration Archived ViewPoint 317 Dynamic Filter Archived ViewPoint 318 dynamic report definition 278
E
Edit JCL/Script option Action menu 207 Edit option group scheduling tables 221 Edit Template button Report Template Manager 300 editing JCL 346 job scripts 207 Elapse field Group Scheduling details 224 elapsed time job statistics 211 EM_server parameter emreportcli utility 309 EMERGENCY parameter
Index
405
OS/390 349 emreportcli utility overview 283 parameters 309 report generation 308 Enable Diag Diagnostic panel 339 Enable JEF Undo Environment-General panel 326 Enable tooltip Flowdiagram-General panel 330 End Time Archived ViewPoint 317 playback 322 Ended Not OK status 84 Ended OK status forcing 208 forcing without post-processing 208 job nodes 84 Enter Parameter Values dialog box 280 Environment panel Reporting facility defaults 305 Environment-Display panel Options dialog box 327 Environment-General panel Options dialog box 325 error messages descriptions 353 notification 37 examples critical path 59 ctmloadset utility 60 load balancing resources 58 load balancing workflow 62 Exclude From Collection criteria 137 Exclusive control resources type 243 Executing job status 84 exits job ordering 52 Expand item Flowdiagram-Nodes panel (Options) 331 Export button Report Preview window 283 export file formats 284 Export to File option 72 exporting reports batch mode 308 overview 283 Files tab Diagnostic panel 340 Filter Definition window 149 Filter panel Audit report 299 Report Wizard 289 Filter presets Environment-General panel 326 Filter window ViewPoints wizard 127 filters alerts 236 creating 127 definitions 146 deleting 149 editing 127 multiple criteria 128 selection criteria 149 ViewPoints 127 Find button Report Preview window 283 Find/Highlight window 95 First field Flowdiagram-Nodes panel 331 Flash Alerts window on task bar Alerts panel 334 flow diagram description 79 displaying condition nodes 332 focusing on an alert 236 selecting nodes 109, 116 Step In/Step Out 386, 392 zooming 98 Flowdiagram Colors panel Options dialog box 333 Flowdiagram Links panel Options dialog box 332 Flowdiagram Nodes panel Options dialog box 331 Flowdiagram-General panel Options dialog box 329 Focused Item Flowdiagram-Colors panel 333 Force Into field Order/Force Job dialog box 172 Force OK no Post-processing option Action menu 208 Force OK option Action menu 208 forcing Force OK no Post-processing option 208 Force OK option 208 jobs 167 Order/Force Jobs dialog box 168 formats export files 284 Frames
F
Field Chooser option 71 Fields panel Report Wizard 291
406
Flowdiagram-Colors panel 333 Free node state 86 Free option Action menu 208 group scheduling tables 221 From Proc field, updating 187 From Step field, updating 187 defining 293 Group By panel Report Wizard 292 Group Editing form displaying 221 group scheduling tables description 40, 220 displaying details 220 flowchart 42 icons 82 workflow 41 Group Tree Report Preview window 283 groups icons 82 nodes 55 GRP MAXWAIT job processing parameter 349 GUI Server changing during login 66, 67 GUI server overview 25 reconnect settings 335
G
Gateway column Communication Status window 272 gateways communication 272 recovery 32 route 272 General panel Job Editing form 182, 184 Report Wizard 287 general report types 311 General settings Reconnection panel 336 Generate report button Report Template Manager 304 Generate Report from a Template option 281 Global Alerts server options 334 server name 334 Global conditions adding CONTROL-M 259 communication failure 262 deleting 259, 260 description 49, 255 from CONTROL-M 256 modifying 259 new 260 prefix 255, 256 security 255 slowing down the system 259, 264 to CONTROL-M 256 window 256 Global Conditions server description 26 Go button playback 322 Go To button Report Preview window 283 Go to End playback 322 Go to Start playback 322 Graph Placement Flowdiagram-General panel 330 group job processing parameter 349 Group By criteria
H
handling alerts 236 Held field group scheduling 224 Held node state 86 Hide empty scheduling groups Environment-Display panel 328 hierarchies creating 151 default ViewPoint 130 defining 124 definition window 151 deleting 152 existing 123 modifying 152 Hierarchy window ViewPoint wizard 123 high-level nodes displaying details 177 icons 82 status 84 Hold option Action menu 209 group scheduling tables 221 holding cyclic jobs 209
Index
407
I
Import Old Reports dialog box 314 In conditions indicator on job node 88 IN job processing parameter 349 In Use type Quantitative Resources window 248 Include In Collection criteria 137 Initial Dir field 215, 216 Interval parameter OS/390 349 IOABLCAL utility relative calendars 173 Item Count option 70
J
Japanese 64 JCL, viewing 212 Job Action Report window 119 Job Definitions report 310, 312 job dependency default radius 334 Job Editing form job details 181 Job field Order/Force Job dialog box 170 Job List screen OS/390 343 job nodes colors 84 displaying details 181 icons 82 job parameters OS/390 348 job processing definitions alert colors 234 deleting 343 description 39, 162 OS/390 346 updating 343 viewing 343 job statistics elapsed time 211 jobs archived output (sysout) 345 confirming 206 deleting 206 displaying documentation 206, 346 displaying reasons 344 editing a job script 207 editing JCL 346 field in Properties window 179 filtering 127
Force OK no post-processing option 208 Force OK option 208 forcing 167 freeing 208 graphic overview 345 group scheduling tables 40 holding 209 killing 209 listing 343 load balancing parameters 55 log 210 manual confirmation 345 Order/Force Jobs dialog box 168 ordering 51, 167, 347 output 213 post-processing 53 React option 210 rerunning 210, 345 Restart option (OS/390) 210 run statistics 345 scheduling 36 security authorization 31 status 84 tracking 343 undeleting 212 viewing a job script 212 viewing statistics 211 Why option 213
K
Kill option Action menu 209
L
languages display 65 Japanese 64 Last active ViewPoint Reconnection panel 336 Last Update column Communication Status window 273 description 71 Late node state 86 Library field Order/Force Job dialog box 170 LimitArchiveJobsInMem system parameter 318 Link Settings Flowdiagram Links panel 332 Links Definition report 310 list display adding fields 71 listing jobs 343
408
scheduling tables 343 load balancing critical-path 59 description 37, 54 Node ID/Group parameter 55 quantitative resources 56 workflow 62 Local View adjusting settings 240 alerts troubleshooting 239 Local ViewPoint default Radius 334 Log cyclic 339 group scheduling tables 221 Log Filename Diagnostic panel 339 logging in CONTROL-M/EM 65 logs message 344 viewing 210 migration old reports 313 Minimize 330 Minimize Graph Width Flowdiagram-General panel 330 Minimum parameter OS/390 349 modifying alert severity 236 alternative server list 337 collection filters 148 Collections 134 definition names 219 definition order 218 passwords 69 Viewpoint hierarchies 152 ViewPoints 132 monitoring CONTROL-M/EM components 30 Months parameter defining calendars 173 Move Entry Down button 217 Move Entry Up button 217
M
Main Menu OS/390 346 manual conditions adding 214 screen in OS/390 347 Manual Definitions report 311 Max reconnection retries Reconnection panel 337 Max Rerun OS/390 job parameter 349 Maximize Downward Flow Flowdiagram-General panel 330 MaxOldDay parameter 315 MaxOldTotal parameter 315 Maxwait group scheduling 224 job processing parameter 349 Mem Name alerts parameter 237 field in Alerts window 237 Memlib parameter OS/390 349 Memname parameter OS/390 349 Menu button 217 messages descriptions 353 OPER 351 OPER2 351 Shout 202 U-ECS 351
N
names CONTROL-M details 180 Properties window 179 navigation buttons Report Preview window 283 navigation techniques 115 Navigation tree colors 328 overview 78 selecting nodes 94 Step In/Step Out 96 Neighborhood identifying dependencies 109 selecting nodes 109 Net Name Archived ViewPoint 317 Net Overview 79, 80 Net Status column Communication Status window 273 network navigation techniques 115 searching 95 New Alert Notification Alerts panel 334 New button 217 Control Resources window 243, 249, 257 Prerequisite Conditions window 253 NEW COND description 347 New Day procedure
Index
409
description 43 download process after 33 New Report dialog box 281, 300 New Template button Report Template Manager window 285 New Template dialog box 285 New value Order/Force Job dialog box 172 Next Event playback 322 NJE field, updating 186 job processing parameter 349 NJE NODE parameter OS/390 349 node groups description 55 Node ID description 36 Node ID/Group parameter load balancing 55 Node Settings Flowdiagram-Colors panel 333 Node Title Flowdiagram-Colors panel 333 low resolution zoom 330 Nodes First Field Flowdiagram-Colors panel 333 nodes color 84 high-level 177 icons 82 job 181 locating 95 selecting 109, 118 selecting in Flow Diagram view 116 selecting in Navigation tree 94 selecting using Select All 118 state 86 status 84 Not in AJF job status 84 playback status 322 notes alerts 236 Notice or Handle option Alerts window 236 Number of Files Diagnostic panel 339 Number of messages per file Diagnostic panel 339 Order/Force Job dialog box 172 ON GROUP-END job processing parameter 349 On Request node state 86 On statements Job Editing form 198 Job Editing form (OS/390) 201 ON STEP/CODE job processing parameter 349 Open Existing Report list box 282 Open into Local View Alerts panel 334 Open this ViewPoint at the end of the wizard 122 Opening Existing Report area 279 OPER rollable OS/390 message 351 OPER2 unrollable OS/390 message 351 options reconnect 275 Order date field in group scheduling 224 Prerequisite Conditions window 252 order ID group scheduling 224 Order/Force Jobs dialog box description 168 ordering description 51 group scheduling tables 220 jobs 167 Order/Force Jobs dialog box 168 OS/390 CONTROL-M messages 353 OPER messages 351 OPER2 messages 351 parameter cross-reference 343 restarting a job 210 steps panel 199 sysout viewing 213 U-ECS messages 351 Out conditions indicator on job node 88 OS/390 job parameter 349 output viewing 213 Over Lib parameter OS/390 349 Owner parameter OS/390 349
O
Odate description 44
P
panels Report Wizard 286 parameters
410
report specification 278 Parameters field 215, 216 password change 69 password_ filename parameter emreportcli utility 309 pattern-matching strings 73 PDS parameter OS/390 349 periodic calendars description 173 PGMST parameter Job Editing form 201 Platform CONTROL-M details 180 CONTROL-M version 180 Playback description 315 End Time 322 Go 322 Go To End 322 Go to Start 322 Next Event 322 Not in AJF status 322 Play 322 Play Back 322 previous event 322 slider 322 speed 322 start time 322 stop 322 Time Display 322 units 322 POST_ODAT job status 84 PostProc panel Job Editing form 202 postprocessing Job Editing form 197 On statements 201 Shout messages 202 prerequisite conditions adding 253, 347 adding missing conditions 214 automatic update 328 Conditions/Resources screen 346 CTMJOBRQ utility 347 dependent jobs 109 description 48 displaying 332 downloading 33 examples 49 global conditions 255 Global Conditions server 26 Job Editing form 192 Main Menu 347 security authorization 31 viewing 81 Prerequisite Conditions report 309 Prerequisite Conditions window buttons 249, 253, 257 description 251 fields 252 Preset path Environment-General panel (Options) 326 Prevent-NCT2 parameter OS/390 jobs 349 preview printing a flow diagram 153 Previous Event playback 322 Print option 72 printing preview 153 priority Control Resources window 243 Critical Path parameter (OS/390) 349 OS/390 job parameter 349 PROCST parameter Job Editing form 201 Produce Global Links Report checkbox Filter panel 298 product support 3 Program field 215, 216 prompting facility screen 347 properties high-level nodes 177 job nodes 181
Q
quantitative resources automatic update 328 Conditions/Resources screen 346 deleting 250 description 47 downloading 33 examples 47 load balancing 56 priority 248 RBA 248 window 246 Quantitative Resources report 310 Quick scheduling screen 347
R
range Step Range for On statements 199 RBA Control Resources window 243 React option Action menu 210
Index
411
rebuild Flowdiagram reloading active net 327 recent value Order/Force Job dialog box 172 reconnecting to GUI Server manual mode 275 Reconnection panel 335 settings 275 Reconnection attempts Reconnection panel 337 Reconnection panel Options dialog box 335 redo Job Editing form 203 Refresh button Communication Status window 273 Control Resources window 244, 249, 257 Prerequisite Conditions window 253 Report Preview window 283 Refresh needed CONTROL-M details 180 Refresh options description 93 refresh Viewpoints display 93 Relationship parameter OS/390 349 Relative calendars 173 Reload active net Environment-Display panel 327 Reload resources list Environment-Display panel 328 Remarks column Communication Status window 273 Remove This Column option 71 Report 284 report definition criteria Report Wizard 286 report definitions 277 report generation emreportcli utility 308 overview 280 Report pane Report Preview window 283 report parameters dynamic specification 278 Report Preview window 282 report template selecting 281 Report Template Manager modifying templates 300 overview 303 Report Template Manager window 281, 285, 303 report templates modifying 300 overview 277 report types active 309 definition 310 general 311 overview 309 Report Wizard defining a report template 286 Fields panel 292 Filter panel 290, 299 Group By panel 293 overview 286 panels 287 Sort panel 294 special panels 297 Style panel 295 Summary panel 296 title bar 286, 301 Reporting facility Confirmations panel 307 customizing defaults 304 Environment panel 305 overview 277 starting 278 Viewer panel 306 Reporting Facility Start Page window 279 reports converting 313 definition 284 displaying 282 exporting 283 formats 311 migration of 313 one-time 300 previously run 282 templates 284 Requested control resources type 243 Required type Quantitative Resources window 248 Rerun Action menu 210 RERUNMEM job processing parameter 349 resequencing Application Activation definitions 218 Reset Levels button hierarchy definition 152 RESOURCE parameter OS/390 349 resources ctmloadset 60 description 29 security 31 Resources panel Job Editing form 194 Restart option Action menu 210 Restore ViewPoints options 336
412
Restore viewpoints Reconnection panel 336 restoring undeleting a job 212 Retro parameter OS/390 349 rows sorting 71 running applications 219 runtime statistics downloading to CONTROL-M/EM 33 Order/Force Job dialog box 172 selecting dependent nodes 109 multiple nodes 118 nodes in flow diagram 116 predecessor nodes 109 server platforms description 35 servers CONTROL-M/EM 66 Set Flowdiagram-Colors panel 333 Set panel Job Editing form 196 Set Settings Flowdiagram-General panel 330 SET VAR job processing parameter 350 severity modifying alerts 236 Shout parameter 238 Shape Flowdiagram-Nodes panel 331 Shared Control resources type 243 viewing jobs for a shared resource 245 Shift parameter OS/390 350 SHOUT job processing parameter 350 Shout destinations OS/390 351 overview 39 Shout messages alerts 234, 238 Job Editing form 202 level of urgency 238 Shouts panel Group Editing form 228 Show links between jobs Flowdiagram Links panel 332 Slider playback 322 Smooth display Flowdiagram-General panel 330 Sort Ascending option 71 Sort Descending option 71 Sort panel Report Wizard 294 Sort Presets by name Environment-General panel (Options) 326 sorting rows 71 specifying report definition criteria 286 speed playback 322 Standalone value
S
SAC job processing parameter 349 Save as Template button Report Preview window 283 Save settings for next run Diagnostic panel 340 Schedule tags OS/390 349 Scheduling Facility (OS/390) creating a job 343 entry panel 343 Scheduling Table Manager 166 Scheduling tables groups 40 jobs list 343 listing 343 Modified field 164 ordering 167 security 31 synchronization 163 uploading 165 scheduling tables creating 343 deleting 343 description 28 downloading 165 forcing 167 SCHENV job processing parameter 349 scripts editing 207 seconds between reconnection attempts Reconnection panel (Options) 337 security exits 52 mechanism, Author parameter 183 user authorizations 31 user exits 52 Select All 118 Select Servers Reconnection panel 337 Selected value
Index
413
Order/Force Job dialog box 172 Standard Deviation field 187 Start Time Archived ViewPoint 317 job statistics 211 playback 322 Start Zoom Level Flowdiagram-General panel 330 starting Reporting facility 278 Statistics option Action menu 211 group scheduling tables 221 status jobs 84 Status screen OS/390 345 status window communication 271 step codes OS/390 200 Step In/Step Out Navigation tree 97 Step Into item Flowdiagram-Nodes panel 331 step range Job Editing form 199 OS/390 350 stepping in and out description 96 in flow diagram 116 Steps panel Job Editing form 197 OS/390 199 Stop playback 322 stopping killing a job 209 Style panel Report Wizard 295 Summary panel report definition 302 Report Wizard 296 support, customer 3 Sync Communication Status window 272 CONTROL-M details 180 Synchronization communication 272 CONTROL-M/EM and CONTROL-M 163 Sysout viewing 213 Sysout handling Job Editing form 203 Sysout parameter OS/390 350 SYSTEM ID job processing parameter 350
T
Table field Order/Force Job dialog box 170 Table List (OS/390 343 tables forcing 344 ordering 344 tapes CTMPROMP utility 347 pull list screen 347 Task Type parameter OS/390 350 technical support 3 templates copying 304 defining 284 deleting 304 generating a report from 304 Report Template Manager 303 time Alerts window 237 group scheduling 224 OS/390 350 Time Display playback 322 Title Flowdiagram-Nodes panel 331 To Proc field 187 To Step field 187 toggle button Report Preview window 283 troubleshooting alerts 239 Type field Control Resources window 243 Quantitative Resources window 248
U
U-ECS shout message 351 Undelete option Action menu 212 group scheduling tables 221 undoing actions Job Editing form 203 UndoLevels General panel 326 Units playback 322 Unknown job status 84
414
Update button Control Resources window 249, 257 uploading definition 25 scheduling tables 165 Use Minimum Diag Level Diagnostic panel 339 Use of Radius Alerts panel 335 User Daily job description 43 utilities CTMCAES 347 ctmloadset 60 CTMOBRQ 347 CTMPROMP 347 CTMQUICK 347 IOACCND 347 ISPF 347 MVS menu 347
W
Wait between reconnection attempts Reconnection panel 337 Wait condition job status 84 Wait resource job status 84 Wait User job status 84 Wait User status job confirmation 206 WAIT_ODAT job status 84 WAITTIME job status 84 WCAL parameter OS/390 350 WDAYS parameter OS/390 350 Western European language characters 64, 65 Why option Action menu 213 group scheduling tables 221 workflow group scheduling tables 41 load balancing 62 Workstation column Communication Status window 272 Wrap field text in node Flowdiagram-Nodes panel 331
V
View field Alerts window 233 View JCL/Script option Action menu 212 View Jobs button Control Resources window 243 Viewer panel Reporting facility defaults 306 viewing JCL/scripts 212 job definitions 343 job documentation 206 job log 210 job output (sysout) 213 job statistics 211 jobs that share a control resource 245 print preview 153 ViewPoint Name Alerts panel 335 ViewPoint wizard 122 ViewPoints creating 130 default Radius 334 deleting 132 description 27, 90, 91 filter 127 modifying 132 restoring 336 security authorization 31 ViewPoints Manager 130 Wizard 121 Viewpoints display 93
X
XML_ arguments_file parameter emreportcli utility 309
Z
Zoom Level Flowdiagram-General panel 330 zooming Flow Diagram view 98 Status screen 345
Index
415
416
Notes
*50525* *50525* *50525* *50525*

*50525*

MEM620100UG50525

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MEM620100UG50525

Uploaded by

Copyright:

Available Formats

CONTROL-M/Enterprise Manager

Contacting BMC Software

United States and Canada

Outside United States and Canada

Restricted rights legend

Support by telephone or e-mail

Before contacting BMC Software

CONTROL-M/Enterprise Manager User Guide

CONTROL-M/Enterprise Manager User Guide

CONTROL-M (MVS) and CONTROL-M/EM cross-reference

343 343 346 346 347 347 348 351 353

CONTROL-M/Enterprise Manager User Guide

CONTROL-M/Enterprise Manager User Guide

CONTROL-M/Enterprise Manager User Guide

CONTROL-M/Enterprise Manager User Guide

CONTROL-M/Enterprise Manager User Guide

About this book

Chapter 3 Chapter 4 Chapter 5

About this book

Where to go from here

Chapter /Appendix Appendix A

Where to go from here

CONTROL-M/Enterprise Manager User Guide

About this book

The following conventions are used in this guide:

Menu => Option

CONTROL-M/Enterprise Manager User Guide

CONTROL-M/Agent CONTROL-M/eTrigger CONTROL-M/Control Modules CONTROL-M/ WebAccess

CONTROL-M product family

CONTROL-M/Enterprise Manager User Guide

Command Line Interface Utilities

Administration Facility Agent

CONTROL-M/Enterprise Manager User Guide

Managing your scheduling environment

Managing your scheduling environment

Viewing the production environment of the enterprise

Archive network environment Defining jobs and groups

Managing your scheduling environment

CONTROL-M/Enterprise Manager User Guide

Managing your scheduling environment

Handling system resources

CONTROL-M/EM administration tasks

Calculating critical path

CONTROL-M/EM administration tasks

Monitoring CONTROL-M/EM components

CONTROL-M/Enterprise Manager User Guide

CONTROL-M/EM administration tasks

Defining user authorizations

Elements for user authorization

Resources and conditions

Calendars and Scheduling tables ViewPoints Administrative responsibilities

CONTROL-M/EM administration tasks

Data from the CONTROL-M is downloaded to CONTROL-M/EM in the following ways.

CONTROL-M/EM administration tasks

CONTROL-M/EM administration tasks

Defining CONTROL-M installations

Root menu operations

CONTROL-M/Enterprise Manager User Guide

CONTROL-M Server/Agent technology

Automated job scheduling

CONTROL-M/Enterprise Manager User Guide

Allocation and monitoring of system resources

Tracking and monitoring job execution