70028

CONTROL-M/Control Module for SAP
Administrator Guide
Supporting
CONTROL-M/CM for SAP 6.3.01
October 2007
www.bmc.com
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 2007 BMC Software, Inc. BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners. DB2 is a registered trademark of International Business Machines Corporation. IBM is a registered trademark of International Business Machines Corporation. ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Oracle is a registered trademark of Oracle Corporation. SAP, SAP R/3, and SAP NetWeaver are trademarks or registered trademarks of SAP AG in Germany and in several other countries. UNIX is a registered trademark of The Open Group. 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 BMC Software Customer Support website or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, see Before contacting BMC.
Support website
You can obtain technical support from BMC 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 offers find the most current information about BMC products search a database for issues similar to yours and possible solutions order or download product documentation download products and maintenance report an issue or ask a question subscribe to receive proactive e-mail alerts when new product notices are released find worldwide BMC 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 customer_support@bmc.com. (In the subject line, enter SupID:<yourSupportContractID>, such as SupID:12345). Outside the United States and Canada, contact your local support center for assistance.
Before contacting BMC

Have the following information available so that Customer Support can begin working on your issue 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 issue 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
License key and password information

If you have questions about your license key or password, contact BMC as follows:
(USA or Canada) Contact the Order Services Password Team at 800 841 2031, or send an e-mail message to ContractsPasswordAdministration@bmc.com. (Europe, the Middle East, and Africa) Fax your questions to EMEA Contracts Administration at +31 20 354 8702, or send an e-mail message to password@bmc.com. (Asia-Pacific) Contact your BMC sales representative or your local BMC office.
CONTROL-M/Control Module for SAP 6.3.01 Administrator Guide
Contents
Chapter 1 Introduction 11 12 14 14 15 17 18 21 22 25 28 28 32 34 36 37 37 38 38 38 41 42 43 44 45 45 46 48 51 60 73 75 75 76 76
5
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . More about CONTROL-M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP Job Scheduling in CONTROL-M. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining and scheduling jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTROL-M solution for Business Information Warehouse . . . . . . . . . . . . . . . . CONTROL-M solution for Data Archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 2 Installation
Step 1 - Installation and upgrade requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP authorizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2 - Installing or upgrading CONTROL-M/CM for SAP . . . . . . . . . . . . . . . . . . . . Installing and upgrading CONTROL-M/CM for SAP on UNIX . . . . . . . . . . . . . . Installing and upgrading CONTROL-M/CM for SAP on Microsoft Windows . Downloading the RFC library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3 - Importing the SAP panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4 - Importing the CONTROL-M/CM for SAP utilities to the CONTROL-M Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing the functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5 - CONTROL-M function modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing CONTROL-M function modules to SAP Unicode systems . . . . . . . . . CONTROL-M/CM for SAP and the SAP XBP interface . . . . . . . . . . . . . . . . . . . . . CONTROL-M/CM for SAP and SAP Business Information Warehouse . . . . . . . Installing the CONTROL-M FMs in the SAP system . . . . . . . . . . . . . . . . . . . . . . . . Installing the Conversion utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling CONTROL-M/CM for SAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 3 Defining and monitoring SAP jobs in CONTROL-M
Creating a template for a job definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a job skeleton for SAP jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating and monitoring SAP R/3 jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP panel parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selecting job steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring and managing SAP jobs in CONTROL-M . . . . . . . . . . . . . . . . . . . . . . Data archiving jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data archiving with XBP 1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Data Archiving session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
Configuring the environment to work with Data Archiving Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 SAP panel parameters for data archiving. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Business Information Warehouse jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Creating a Business Information Warehouse job . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 SAP panel parameters for SAP-BW jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Monitoring and managing Business Information Warehouse jobs . . . . . . . . . . . . 94 Chapter 4 Administrator tasks 97
Account Management Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Accessing the Account Management utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Configuring general parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Accessing the Configuration Management utility . . . . . . . . . . . . . . . . . . . . . . . . . 107 Configuring parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Configuring and working with the Extractor Management utility. . . . . . . . . . . . . . . 111 Accessing the Extractor Management utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 General configuration of the Extractor Management utility . . . . . . . . . . . . . . . . . 114 Job interception and control with the Extractor Management utility . . . . . . . . . 115 Extracting and monitoring SAP CCMS jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Initiating a mass parallel process (detecting spawned jobs) . . . . . . . . . . . . . . . . . 127 Defining a user exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Activating the Extractor Management utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 SAP Event Based Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Modifying the default configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Modifying the default event-based rule file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Import SAP Calendar utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Requesting SAP actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Displaying a list of variants for a program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Altering parameter values in a variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Displaying variant details within a program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Raising a SAP event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Deleting a job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Defining a new job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Modifying a job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Converting CONTROL-M Option for R3 account definitions. . . . . . . . . . . . . . . . . . . 150 Converting CONTROL-M Option for R/3 jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Appendix A Extracting and monitoring jobs 159
Defining a rule file with the ctmextract utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Monitoring SAP jobs with the ctmextract utility. . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Extracting job definitions with the ctmextract utility . . . . . . . . . . . . . . . . . . . . . . . 166 Appendix B Index Related SAP Notes 169 173
CONTROL-M/Control Module for SAP Administrator Guide
Figures
SAP panel, Job Editing form (Job Definition mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Add ABAP dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Change variant dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 External command dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 External program dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 SAP panel, Job Editing form (Active Job mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 SAP panel for Data Archiving, Job Editing form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Job Editing form, SAP panel, Original mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 SAP panel for BW - InfoPackage, Job Editing form . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 SAP panel for BW - Process Chain, Job Editing form . . . . . . . . . . . . . . . . . . . . . . . . . . 90 SAP-BW panel - InfoPackage (Active Job mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Accounts Management window (CONTROL-M Configuration Manager) . . . . . . . . 99 Update Account options (CONTROL-M Configuration Manager) . . . . . . . . . . . . . . 100 Account Adding Wizard (first screen) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 New Account dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Configuration management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Add/Update CONTROL-M Interception Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Extractor Management utility - Extraction Criteria tab . . . . . . . . . . . . . . . . . . . . . . . . 122 Example of event-based rule file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Import SAP Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Figures
Tables
SAP authorizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 RFC library details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 XBP BAPIs versus CONTROL-M function modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 SAP-BW BAPIs versus CONTROL-M function modules . . . . . . . . . . . . . . . . . . . . . . . 41 SAP Event Based Scheduling AutoEdit variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 SAP panel parameters - Job Definition mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Add ABAP dialog box parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Change Variant subparameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Variant options for selection and range types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 External Command dialog box parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Add External Program dialog box parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Additional SAP panel parameters - Active Job mode . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Data-archiving SAP panel parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 SAP-BW job panel parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Additional SAP-BW panel parameters - Active Job Mode . . . . . . . . . . . . . . . . . . . . . . 95 CONTROL-M/CM for SAP Account Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Configuration Management utility parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 CTM interception rules parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Parameters for avoiding discarded intercepted jobs . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Job Extraction Criteria parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Extraction Rules parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 User Exit script parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 SAP Event Based Scheduling Configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Rule File parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Import SAP Calendar parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Parameters for var_mon action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Parameters for var_edit action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Parameters for var_show action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Parameters for raise_event action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Parameters for job_delete action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Parameters for job_define action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Parameters for job_modify action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 ctmr3req interrupt parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Conversion utility parameter descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Problem parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Rule file AutoEdit parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Mandatory parameters for ctmcreate and ctmdefine . . . . . . . . . . . . . . . . . . . . . . . . . 163 Parameters for monitoring a job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Known SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Tables
10
Chapter
Introduction
CONTROL-M/CM for SAP provides a complete and SAP-certified interface between the worlds of CONTROL-M and the specific SAP environments. Using BMC CONTROL-M/Control Module for SAP you can manage both the traditional SAP, planned and automated processes, and the unpredicted real-time, event-driven dynamic job submission. The CONTROL-M/CM for SAP user interface is designed to be based on SAP native terminology, using a similar look and feel. This is in order to make the CONTROL-M/CM for SAP interface an easy-to-use tool for SAP users, and therefore minimize end-user training needs. CONTROL-M/CM for SAP also greatly increases batch processing and existing scheduling capabilities in SAP as follows:
the ability to integrate and manage large quantities of jobs advanced scheduling and monitoring capabilities between different SAP systems, and between SAP and non-SAP systems advanced high level networking between jobs a user-friendly GUI, in which you can easily view the job flow the ability to control the workload using logical or real resource availability integration between mySAP (non R/3) and R/3 components
Using CONTROL-M/CM for SAP, you can perform the following actions:
define, schedule, and store SAP jobs in the CONTROL-M database submit SAP jobs using the CONTROL-M/Enterprise Manager (CONTROL-M/EM) GUI monitor and control SAP jobs from within CONTROL-M/EM
Chapter 1
Introduction
11
Terminology
intercept jobs in SAP, then control and monitor them in CONTROL-M create and monitor mass parallel processes (spawned jobs) archive and delete older data as required, using the CONTROL-M solution for SAP Data Archiving monitor and control SAP-Business Warehouse business processes in CONTROL-M, using the CONTROL-M solution for SAP-BW use SAP advanced load-balancing mechanism, such as Logon Groups and Job Server Group control advanced job submission options from within CONTROL-M, such as Spool list recipients for a job, and advanced parameter management dynamically trigger both SAP and non- SAP (CONTROL-M-managed) jobs, as a result of SAP events
Other SAP-related functionality is described later in the book, including defining new SAP jobs and raising events, among others.
Terminology
The following table lists abbreviations and terms used in this document:
Term ABAP SAP Server SAP Client SAP Note BAPI Description Language used within the SAP system (ABAP Reports). Also referred to as ABAP/4. Computer on which the SAP Application server runs. This can also be the same computer on which CONTROL-M/Agent runs. Computer on which the SAP GUI runs. A SAP-produced document that details a specific problem in the SAP system, and a suggested solution. Business Application Programming Interface. A set of ABAP/4 function modules accessible through RFC technology (Remote Function Calls). BAPIs are an open interface for integrating with SAP products, assuring their stability and compatibility with current and future releases.
12
Terminology
Term BC-XBP (External Interface for Job Background Processing)
Description A set of SAP-created and certified BAPIs that enable CONTROL-M to control, start and monitor jobs outside SAP R/3. Through this interface, SAP R/3 Computer Center Management System (CCMS) supports CONTROL-M integration with existing administration tools. XBP 2.0: The new certified version of SAP BC-XBP. XBP 2.0 is an enhancement of XBP 1.0, and can be installed without changing current functionality. The primary advantages are:

New Parent/Child (spawned) job functionality New interception capabilities Triggering events and additional help functions. New and enhanced ways of working with jobs: defining, monitoring, modifying, starting and deleting jobs
For more information about the XBP 2.0 interface, see SAP Note 604496. CONTROL-M function modules CONTROL-M extended functionality installed in SAP. For more information see Step 4 - Importing the CONTROL-M/CM for SAP utilities to the CONTROL-M Configuration Manager on page 37. A job created by another job that is monitored by CONTROL-M. A job that created one or more spawned jobs.
Spawned job Parent job
Business Warehouse SAP Business Information Warehouse (BW) is a data warehouse (BW) solution for SAP R/3. However, it is a separate application, independent of SAP R/3. P/C I/P Administrator Workbench CONTROL-M/EM FixPack XBP A Business Information Warehouse Process Chain A Business Information Warehouse InfoPackage The Administrator Workbench is a GUI-based tool for BW implementation, maintenance, customization, scheduling, and monitoring and is a part of the SAP front-end. CONTROL-M/Enterprise Manager. A CONTROL-M bug resolution. Official certified SAP interface for batch processing management.
Chapter 1
Introduction
13
More about CONTROL-M
More about CONTROL-M

CONTROL-M/CM for SAP, together with the CONTROL-M products described below, are included in the CONTROL-M scheduling solution.
Product CONTROL-M/Enterprise Manager CONTROL-M/Server Description 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 drive scheduling 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 is used to execute CONTROL-M jobs.
CONTROL-M/Agent
Additional products are available for interfacing between the CONTROL-M scheduling solution and other systems management products. For more information, contact your BMC Software sales representative.
SAP Job Scheduling in CONTROL-M

A job in SAP is comprised of a list of steps. Each step should be either an ABAP/4 program, an external program, or an external command. Jobs in the SAP system are executed in background processes, which are defined on the SAP servers. All CONTROL-M capabilities are available to SAP jobs, including advanced scheduling criteria, complex dependencies, Quantitative and Control resources, and AutoEdit variables.
14
Defining and scheduling jobs

SAP jobs can be managed in any of the following ways:
A new SAP job is defined, stored, and submitted using CONTROL-M. When defining a new SAP job, you select job steps. Each step should include at least one of the following step parameters: ABAP program External command External program Select the Create option in the CONTROL-M/CM for SAP panel of the Job Editing form. For more information, see Selecting job steps on page 60. An original SAP job is run. Select the Original option in the CONTROL-M/CM for SAP panel of the Job Editing form. An SAP job is copied and run, enabling multiple runs of identical jobs. Select the Copy option in the CONTROL-M/CM for SAP panel of the Job Editing form. An SAP job is monitored from within CONTROL-M, by creating a mirror-image of the job in CONTROL-M. Post-processing actions can also be performed on the job. Select the External option in the CONTROL-M/CM for SAP panel of the Job Editing form. A predefined SAP Batch Input procedure is scheduled and submitted using CONTROL-M. Select the Batch Input option in the CONTROL-M/CM for SAP panel of the Job Editing form.
For more information about how to define a SAP job, see Chapter 3, Defining and monitoring SAP jobs in CONTROL-M. When defining a new SAP job, you select job steps. This means all job parameters, including ABAP program, External command, and External program step parameters. The job is submitted and monitored as if it were a regularly defined SAP job. Jobs can also be defined, stored in the CONTROL-M database, and saved for submission at a later date. For more information, see Selecting job steps on page 60.
Monitoring and controlling SAP jobs

Jobs defined, scheduled, and submitted in SAP are monitored by CONTROL-M, using SAP-produced data. This data is obtained by searching for job-specific selection criteria. CONTROL-M creates a mirror image of the job. This mirror image is not submitted for execution, but is used by CONTROL-M to track and monitor the job.
Chapter 1
Introduction
15
After the job starts to run, CONTROL-M/CM for SAP monitors the SAP system to check the status of the job. As the job progresses, its status is updated in the CONTROL-M database and in CONTROL-M/EM viewpoint. In addition to monitoring the running job, CONTROL-M can also cancel it in SAP, if necessary. When the job ends, CONTROL-M/CM for SAP provides CONTROL-M/EM with the SAP job output for each request. The SAP job log and the SAP job spool are copied to the job sysout or to files if required. Post-processing mechanisms can then be activated in CONTROL-M/EM. SAP jobs are monitored in SAP using SAP transaction SM37. This transaction displays all jobs and their associated status. During the run time of a job, the job status is reflected differently in CONTROL-M and SAP databases, as described in the following table.
CONTROL-M job status Executing SAP job status Scheduled Released Ready Active Finished Canceled
Ended OK Ended NOTOK
The SAP job status can be seen in CONTROL-M/EM, in the SAP panel of the Job Editing form, in the SAP Job Status field. For more information, see Extracting and monitoring SAP CCMS jobs on page 121.
Enhanced Batch Processing management

CONTROL-M/CM for SAP is integrated with the SAP XBP 2.0 interface functionality. This means that many features are now provided that were previously available only through CONTROL-M function modules, when CONTROL-M/CM for SAP was configured to Extended mode (that is, when the Use Extended parameter was set). These features now work through SAP-created and certified BAPIs, that are an integral part of the CONTROL-M/CM for SAP solution.

track spawned jobs intercept SAP jobs activate intercepted jobs create mirror image (Extractor Management) load parameters lists control ABAP program variants
16
CONTROL-M solution for Business Information Warehouse
Monitoring mass parallel processes

Mass parallel processes (spawned jobs) are created by SAP jobs that were either created or monitored in CONTROL-M. CONTROL-M/CM for SAP detects the spawned jobs of the SAP parent job and creates a mirror image of them in CONTROL-M. Through these mirror images, the spawned jobs are tracked and monitored. For more information, see Initiating a mass parallel process (detecting spawned jobs) on page 127.
Intercepting and controlling jobs

Job interception and control is a two-stage process. Using the Extractor Management utility to determine which jobs should be intercepted by SAP and how the Extractor should handle the various intercepted jobs. For more information, see Job interception and control with the Extractor Management utility on page 115.
CONTROL-M solution for Business Information Warehouse

CONTROL-M solution for BW InfoPackages
CONTROL-M can be used to schedule, monitor, and post-process existing InfoPackages from SAP-BW. Therefore, you should first create and test the InfoPackages using SAP-BW tools provided by SAPGUI. For more information on how to create and test SAP-BW InfoPackages, refer to SAP documentation. After you create an InfoPackage in SAP, you can create a CONTROL-M job to run it. Running this CONTROL-M job starts the InfoPackage in SAP and enables you to monitor it. The monitoring procedure in CONTROL-M does not monitor a specific CCMS job, since an InfoPackage run in SAP-BW usually includes several CCMS jobs and other operations. Instead, it uses SAP BAPIs to start and monitor the InfoPackage as a logical unit that is not limited to one specific CCMS job. The Sysout of the CONTROL-M job includes information similar to that displayed on the SAP-BW status panel of the monitoring screen of an InfoPackage specific run (transaction RSA1), including error messages. You can define post-processing rules in CONTROL-M based on this information. For information on how to create InfoPackage jobs in CONTROL-M, see Creating a Business Information Warehouse job on page 88.
Chapter 1
Introduction
17
CONTROL-M solution for Data Archiving
CONTROL-M solution for BW Process Chains

CONTROL-M can be used to schedule, monitor, and post-process existing Process Chains from SAP-BW. Therefore, you should first create and test the Process Chains using SAP-BW tools provided by SAPGUI. For more information on how to create and test Process Chains, refer to the SAP documentation. After you create a Process Chain in SAP, you can create a CONTROL-M job that is used to run it. Running this CONTROL-M job starts the Process Chain in SAP and enables you to monitor it. The monitoring procedure in CONTROL-M does not monitor a specific CCMS job in SAP-BW, since a Process Chain in SAP-BW includes several CCMS jobs. Instead, it uses BAPIs to start and monitor the Process Chain as a logical unit, not limited to a specific process or CCMS job. This means that the entire Process Chain, the details of which can be displayed in SAPGUI as many processes, are represented in CONTROL-M as one job. The Sysout of the CONTROL-M job includes information about the updated status of each process in the chain and the number of Records transferred and requested. You can define post-processing rules in CONTROL-M based on this information. For more information about how to create Process Chain jobs in CONTROL-M, see Creating a Business Information Warehouse job on page 88.

The CONTROL-M solution for SAP Data Archiving involves the creation of a Data Archiving session, which is a group scheduling table of Data Archiving jobs. Such a session can
automate all phases of Data Archiving, including SAP-owned jobs and other business processes manage, schedule, and monitor individual archiving jobs schedule archiving jobs according to business requirements and available resources
Data Archiving sessions are monitored and managed from the CONTROL-M/EM GUI. Each session is a separate entity in itself. Prerequisites and post-processing instructions can be set for each session. A Data Archiving session can be scheduled to run periodically, by assigning it specific scheduling parameters.
18
Working with Data Archiving

The Job Interception and Spawned Jobs functionalities help simplify the Data Archiving scheduling table in CONTROL-M.
Job Interception makes it possible to prevent CCMS from releasing Delete jobs and Store jobs. These jobs can, therefore, be controlled from CONTROL-M. Spawned Jobs functionality makes it possible to automatically detect Delete jobs and Store jobs, and for the SAP CM Extractor process to automatically extract them during run time, into the CONTROL-M active environment.
For more information on the Extractor Interception and Spawned Jobs functions, see page 111.
Data Archiving session

Each Data Archiving session in CONTROL-M consists of one Write job and two templates:
The Write job creates a Write job in SAP. When this job runs, it spawns Delete jobs in the SAP system. These Delete jobs then spawn Store jobs. The template for Delete jobs - The Delete jobs that were created by the Write job in SAP are ordered automatically into CONTROL-M by the Extractor process using this template. You can, therefore, control these jobs in CONTROL-M using CONTROL-M tools, such as conditions and resources. The template for Store jobs - The Store jobs that were created by the Delete jobs in SAP are ordered automatically into CONTROL-M by the Extractor process using this template. You can, therefore, control these jobs in CONTROL-M using CONTROL-M tools, such as conditions and resources.
NOTE
If you use a store-before-delete, instead of a delete-before-store, configuration (defined using the SARA transaction in SAP), you must switch between the Store and Delete templates in CONTROL-M.
Chapter 1
Introduction
19
Sample Data Archiving session

A sample Data Archiving session, containing all the components described above, is provided in a CONTROL-M/Desktop draft file, named Data_Archiving_example_XBP20.DRF. This draft is located in the FORMS directory on the CONTROL-M/CM for SAP installation CD. To run this session, certain customer-specific details must be adjusted (for example, Account and Node Group).
NOTE
The templates for Delete and Store jobs should only be created as templates, and should not be ordered and submitted.
Quantitative Resources are defined for the templates in the draft. To run the sample session successfully, you must add these logical resources in your CONTROL-M. In addition, you must configure the Extractor process to fit this procedure. For detailed information, see Data archiving on page 76 and Configuring the environment to work with Data Archiving Sessions on page 83.
Data Archiving workflow

Use the following workflow as a guideline.
20
Chapter
Installation
This chapter describes how to install CONTROL-M/CM for SAP at your site. Instructions are also provided for upgrading a previous version of CONTROL-M/CM for SAP, and for uninstalling the current version of CONTROL-M/CM for SAP.
NOTE
If a version of CONTROL-M Option for R/3 is installed on the Agent computer on which you plan to install CONTROL-M/CM for SAP, it is not necessary to uninstall CONTROL-M Option for R/3. The two products can function simultaneously, using the same Agent. However, to use the new features of the current product, convert Option jobs using the CONTROL-M/CM for SAP conversion utility. Instructions for installing this utility can be found in Installing the Conversion utility on page 43.
The following steps are provided for installing or upgrading CONTROL-M/CM for SAP:

Step 1 - Installation and upgrade requirements Step 2 - Installing or upgrading CONTROL-M/CM for SAP Step 3 - Importing the SAP panel Step 4 - Importing the CONTROL-M/CM for SAP utilities to the CONTROL-M Configuration Manager Step 5 - CONTROL-M function modules
Following this are instructions on Installing the Conversion utility and Uninstalling CONTROL-M/CM for SAP.
Chapter 2
Installation
21
Step 1 - Installation and upgrade requirements

Before installing CONTROL-M/CM for SAP, ensure that the following requirements are met:
Requirements CONTROL-M/Agent Version 6.3.01 6.2.01 Fix Pack 1 or later Notes: Requirements for CONTROL-M Configuration Manager, and for CJK support can be seen below. 6.3.01 6.2.01 6.3.01 6.2.01 CONTROL-M/EM 6.3.01, with Fix Pack 4 or later. CONTROL-M/Server 6.3.01 FP 2 or later CONTROL-M/Agent 6.3.01 FP 2 or later. CONTROL-M/EM 6.3.01 CONTROL-M/Server 6.3.01 CONTROL-M/Agent 6.3.01 See the release notes for a detailed list of the operating systems that are compatible with CONTROL- M/CM for SAP 6.3.01. Note: For the most current operating system compatibility information for this version, see http://www.bmc.com/supportu/PAC_utility/index.cfm. SAP Basis Release: 4.5B, 4.6C, 4.6D, 6.10, 6.20, 6.40, and 7.0 (NetWeaver). If you are working with SAP Basis 7.0, SAPKB70012 (Support Package 12) should be installed, as a minimum requirement. Kernel version Due to SAP changes in the RFC libraries, a minimum kernel for your SAP system is required. The minimum kernel is detailed in SAP note 792850 and 903329. Warning: Failing to fulfill this requirement prevents CONTROL-M/CM for SAP from working and the following connection error is displayed: You are not authorized to logon to the target system (error code 1) Connect to SAP gateway failed partner not reached (host <...>, service 33<nn>) Note: SAP recommends that you always have the most updated version of Kernel installed.
CONTROL-M/Server CONTROL-M/EM For the CONTROL-M Configuration Manager utilities For CJK support
Supported platforms
SAP
22
Requirements SAP continued
Version XBP interface Your SAP system must include the XBP 2.0 interface in order for the majority of the features of this release to work. Some of the features are available without XBP 2.0, if you use CONTROL-M Function Modules. For more information see, Step 5 - CONTROL-M function modules on page 38 and the comparison table Table 3 XBP BAPIs versus CONTROL-M function modules on page 39. According to SAP documentation, the XBP 2.0 interface is included in the following SAP Basis Support Packages.

4.6C - SAPKB46C41 (Support Package 41) 4.6D - SAPKB46D35 (Support Package 35) 6.10 - SAPKB61028 (Support Package 28) 6.20 - SAPKB62017 (Support Package 17) 6.40 - No support package needed 7.0 - No support package needed
For information provided by SAP on XBP 2.0, see SAP Note 604496 (Composite SAP note XBP 2.0) and http://service.sap.com/job-scheduling. Data archiving If you are using XBP 1.0 on SAP 4.6C and you plan to implement CONTROL-M support for Data Archiving, you must apply SAP Note 458670 to your SAP system. Follow instructions provided in the SAP note. When using XBP 2.0, this note is not necessary. For more information, see Data archiving jobs on page 75. SAP Business Information Warehouse Releases: 2.0B, 2.1C, 3.0B, 3.1 Content, 3.1 Content with BI CONT 3.20, 3.5, 7.0. If you plan to use the CONTROL-M/CM for SAP-BW functionality, the following BW Support Packages must be installed:

BW 2.0B - SAPKW20B35 (release details in SAP Note 601001) BW 2.1C - SAPKW21C27 (release details in SAP Note 601023) BW 3.0B - SAPKW30B27 (release details in SAP Note 723258) BW 3.1 - SAPKW31021 (release details in SAP Note 723263) BW 3.5 - SAPKW35012 (release details in SAP Note 986892) BW 7.0 - SAPKW70014 (release details in SAP Note 991094)
Chapter 2
Installation
23
Version If you plan to use the CONTROL-M/CM for SAP Interrupt functionality, for BW 3.0 and 3.5, SAP Note 786748 must be installed manually. For more details about Interrupts see Interrupts - Removing a process chain from schedule on page 149. Related SAP Notes Certain SAP Notes exist that resolve problems which can occur when using CONTROL-M/CM for SAP. For a full list of these Notes, see Appendix B, Related SAP Notes. In order to avoid installing each note separately, you can also install the following SAP Basis Support Packages:

4.6C -- SAPKB46C52 (Support Package 52) 4.6D -- SAPKB46D43 (Support Package 43) 6.10 -- SAPKB61046 (Support Package 46) 6.20 -- SAPKB62059 (Support Package 59) 6.40 -- SAPKB64017 (Support Package 17)
The following SAP Business Warehouse Support Packages can also be installed. These Support Packages include SAP Note 1059049, which correct a previous SAP problem.

BW 7.0 - SAPKW70015 (release details in SAP Note 991095) BI 7.1 - SAPKW71001 (release details in SAP Note 1011773)
Note: Information regarding the availability of the above support packages and other related data should be verified directly with SAP. Import SAP Calendar If you plan to use the Import SAP Calendar utility, your SAP system version should be PI_BASIS 2002_2_620 or later. SAP Event Based Scheduling SAP Basis Release: 7.0
24
SAP authorizations
Version Open ports The gateway port in the SAP host should always be open. If you are using a firewall, you must ensure that this port is open. The port is typically 33<SYSNR>, where SYSNR represents the System number of the computer on which the SAP Gateway Server is running. For example, port 3335 is used when System number is 35. If you are using Logon Groups, you must ensure that the Message Server port you are using is open. For details regarding the port number, see Table 18 on page 119.
Java Runtime Environment (JRE)
1.4.2 or later JRE is not delivered with the CONTROL-M/CM for SAP and must be installed separately. For details, see http://www.java.com. You must ensure that the Java Binaries Directory is in the path environment variable.
Minimum RAM Required disk space RFC library
256 MB 20 MB The RFC library is not delivered with the CONTROL-M/Control Module for SAP. It must be installed separately. For more information, see Downloading the RFC library on page 34.
SAP authorizations
SAP users of this product must have the following authorizations: Table 1 SAP authorizations (part 1 of 3)
Authorization JOBACTION JOBGROUP BTCADMIN Values * * *
Authorization Object S_BTCH_JOB Object class: BC_A (Basis: Administration) S_BTCH_ADM Object class: BC_A (Basis: Administration) S_BTCH_NAM Object class: BC_A (Basis: Administration)
BTCUNAME
Note: For an explanation on restricting this authorization see the Owner parameter on page 64.
Chapter 2
Installation
25
SAP authorizations
Table 1
S_RFC
SAP authorizations (part 2 of 3)

Authorization ACTVT RFC_NAME RFC_TYPE EXTCOMPANY EXTPRODUCT INTERFACE ACTVT Values * * * BMC Software Control-M XBP *
Authorization Object
Object class: AAAB (Cross-application) S_XMI_PROD Object class: BC_A (Basis: Administration) S_RZL_ADM Object class: BC_A (Basis: Administration)
Note: To prevent other SAP users (not the CONTROL-M account user) from releasing Intercepted Jobs manually using SAP transaction SM37, BMC Software recommends removing the '01' value for ACTVT in the S_RZL_ADM Authorization Object. For further restriction of this authorization, see SAP note 605483 in Appendix B, Related SAP Notes.
S_LOG_COM Object class: BC_A (Basis: Administration) S_SPO_DEV Object class: BC_A (Basis: Administration) S_USER_GRP Object class: BC_A (Basis: Administration) S_RS_ADMWB Object class: RS (Business Information Warehouse) S_RS_ISOUR Object class: RS (Business Information Warehouse)
COMMAND HOST OPSYSTEM SPODEVICE
* * * *
ACTVT CLASS ACTVT RSADMWBOBJ ACTVT RSAPPLNM RSISOURCE RSTSRCOBJ
* * 03, 16, 23, 66 * 03, 23, 49 * * *
26
SAP authorizations
Table 1
SAP authorizations (part 3 of 3)

Authorization ACTVT RSAPPLNM RSTSRCOBJ RSOSOURCE Values 23 * * * * * * 03, 16, 23
Authorization Object S_RS_ISRCM Object class: RS (Business Information Warehouse)
S_RS_PC - (Data Warehousing Workbench Processchains) Object class: RS (Business Information Warehouse)
RSPCCHAIN RSAPPLNM RSPCPART ACTVT
Note: All BW authorizations under the RS Object Class are required only if you work with CONTROL-M/CM for SAP solution for BW. S_ARCHIVE Object class: BC_A (Basis: Administration) S_DATASET Object class: BC_A (Basis: Administration) ACTVT APPLIC ARCH_OBJ ACTVT FILENAME PROGRAM * * * * * *
Note: The S_ARCHIVE and S_DATASET authorizations are required only if you use CONTROL-M/CM for SAP solution for Data Archiving.
NOTE
There is a transport that includes a user role with all the authorizations (with the exception of S_RS_PC) needed for working with the SAP CM. The role is named 'BMCCTRLM_CM_USER '. Use this role in your CONTROL-M user. For details on how to install the Transport, see Installing the CONTROL-M FMs in the SAP system on page 42.
You may need to add additional authorizations to the above if your jobs require them. The authorization checks for the job run are done in SAP using the Owner of the job step. However, if you do not set an Owner for the job step, the Owner set in the account is used and must have the required authorizations.
Chapter 2
Installation
27
Step 2 - Installing or upgrading CONTROL-M/CM for SAP
NOTE
The User Type, as defined in the SAP User maintenance transaction (SU01), can be either System or Dialog. Different User Types may cause errors in connection.
Step 2 - Installing or upgrading CONTROL-M/CM for SAP

This step consists of the following two options:
Installing and upgrading CONTROL-M/CM for SAP on UNIX (see page 28). Installing and upgrading CONTROL-M/CM for SAP on Microsoft Windows (see page 29).
Installing and upgrading CONTROL-M/CM for SAP on UNIX

Choose the appropriate installation procedure in this section. If you already have CONTROL-M/CM for SAP version 6.1.03 or version 6.2.01 installed, you can choose to upgrade. After running the installation procedure, you must define at least one account profile before you can use CONTROL-M/CM for SAP to define jobs. For instructions on defining an account profile, see Account Management Utility on page 98.
To install CONTROL-M/CM for SAP on Unix NOTE

Before beginning the installation procedure, ensure that all jobs are ended and all CONTROL-M/Agent processes are shut down. For more information, see the CONTROL-M/Agent for Unix Administrator Guide.
1 On your CONTROL-M/Agent computer, log on as the root user and run the
shut-ag command to shut down CONTROL-M/Agent.
2 Mount the installation CD. 3 Log on as the CONTROL-M/Agent user. 4 On the command line, enter
<CDROM_path>/Unix/setup.sh
28
Various messages detailing file extraction are displayed. Follow the on-screen instructions.
5 A message regarding account definition and the SAP RFC library is displayed. You
must download the RFC library to the locations indicated in the message. For details on downloading the RFC library see Downloading the RFC library on page 34. The installation is complete.
6 To restart CONTROL-M/Agent, log on as the root user, and run the start-ag
command.
To upgrade CONTROL-M/CM for SAP on Unix NOTE

Before beginning the installation procedure, ensure that all jobs are ended and all CONTROL-M/Agent processes are shut down. For more information, see the CONTROL-M/Agent for Unix Administrator Guide.
1 On your CONTROL-M/Agent computer, log on as the root user, and run the
2 Log on as the CONTROL-M/Agent user. 3 Run the shut-xt command to shut down the Extractor process. 4 Back up your existing installation of CONTROL-M/CM for SAP. 5 Mount the installation CD. 6 On the command line, enter <CDROM_path>/Unix/setup.sh; an Upgrade
installation message is displayed.
7 Enter I. NOTE
If a version of CONTROL-M/CM for SAP that cannot be upgraded is detected, you need to uninstall that version and perform a new installation procedure (see To install CONTROL-M/CM for SAP on Unix on page 28).
The upgrade procedure is performed.
8 Download the RFC library, and copy it to the following two locations:
<home directory>/ctm/cm/SAP/exe <home directory>/ctm/exe
Chapter 2 Installation 29
For more information see Downloading the RFC library on page 34.
9 To restart the Extractor process, run the start-xt command. 10 To restart the CONTROL-M/Agent, log on as the root user, and run the start-ag
command.
Silent installation or upgrade on UNIX

The silent installation or upgrade procedure can be used instead of the interactive installation procedure. This procedure requires placing the parameters that you would normally enter in interactive mode into a file that is accessed by the silent installation or upgrade procedure. The silent installation or upgrade procedure can be used to install or upgrade CONTROL-M/CM for SAP on a single computer or on many computers throughout a network. Silent installation or upgrade involves two stages: 1. Prepare of an installation or upgrade parameters file. This stage is only run once. The installation parameters file is prepared by running the standard interactive installation in silent installation or upgrade mode. The prepared installation parameters file can now be used to install CONTROL-M/CM for SAP where necessary. CONTROL-M/CM for SAP is not installed in this stage. Instead, a file is created with the specified parameter values. 2. Run the CONTROL-M/CM for SAP installation using the parameters file prepared in the previous step. This stage is run for each silent installation of CONTROL-M/CM for SAP.
To prepare and run a CONTROL-M/CM for SAP silent installation or upgrade 1 Prepare the installation parameters file: A Log on as an Agent user. B Set the BMC_SILENT_INSTALL environment variable to Y, as follows:
For sh, ksh, and bash shell users:
BMC_SILENT_INSTALL=Y export BMC_SILENT_INSTALL
For csh or tcsh shell users:

30 CONTROL-M/Control Module for SAP Administrator Guide
setenv BMC_SILENT_INSTALL Y
C Activate the installation script with the following command:

<cd_path>/Unix/setup.sh
D Follow the interactive menu instructions. The installation parameters are saved
to ${HOME}/BMCINSTALL/PRODUCTS.CTL
E The installation parameters file should be copied to a network location that is

accessible to all computers on which a silent installation will be performed.
NOTE
At the end of the silent installation or upgrade procedure, the parameters file is saved in the BMCINSTALL/installed/cm_sap directory as PRODUCTS.CTL.DRRMC.6.3.01, on each Agent where the procedure is performed.
2 Install or upgrade CONTROL-M/CM for SAP in silent mode: A Log on as the root user and run the shut-ag command to shut down
CONTROL-M/Agent.
B Log on as an Agent user. C Use the following command to run the installation script:
<cd_path>/Unix/setup.sh -respond <respond file>
where <cd_path> is the path of the mounted CD <respond file> is the full path to the parameter file that was created in Step 1.
3 If you are performing a new installation, run the Account Management utility to
create at least one account. For information about creating accounts, see Account Management Utility on page 98.
4 To restart the CONTROL-M/Agent, log on as the root user, and run the start-ag
command. The installation is complete.
Chapter 2
Installation
31
Installing and upgrading CONTROL-M/CM for SAP on Microsoft Windows

Choose the appropriate installation procedure in this section. If you already have CONTROL-M/CM for SAP version 6.1.03 or version 6.2.01 installed, you can choose to upgrade. After running the installation procedure, you must define at least one account profile before you can use CONTROL-M/CM for SAP to define jobs. For instructions on defining an account profile, see Account Management Utility on page 98.
To install CONTROL-M/CM for SAP on Microsoft Windows

Before beginning this procedure, ensure that all jobs are ended.
1 Insert the installation CD. 2 Choose Start => Run, and enter the following command:
<CDROM_drive>:\Windows\setup.bat
3 Choose an agent from the multi-agent list. Follow the instructions given in each
window.
4 Click Finish and follow the instructions in the Installation Complete dialog box. 5 Download the RFC library to the appropriate locations. For details on
downloading the RFC library see Downloading the RFC library on page 34.
6 Restart the CONTROL-M/Agent services. To upgrade CONTROL-M/CM for SAP on Microsoft Windows NOTE
Before beginning the upgrade procedure, ensure that all jobs are ended.
1 Back up your existing installation of CONTROL-M/CM for SAP. 2 Insert the installation CD. 3 Choose Start => Run and enter the command:
<CDROM_drive>:\Windows\setup.bat
32
The installation application identifies that a version of CONTROL-M/CM for SAP that can be upgraded is installed on your computer. A dialog box opens telling you the identified version of CONTROL-M/Control Module for SAP, and asking you if you wish to continue with the upgrade.
4 Click Yes to continue. NOTE

If a version of CONTROL-M/CM for SAP that cannot be upgraded is detected, a confirmation message to uninstall is displayed.
5 The installation is complete. Follow the instructions in the Installation Complete

dialog box, and download the RFC library to the appropriate locations. For details on downloading the RFC library see Downloading the RFC library on page 34.
6 You can now restart the CONTROL-M/Agent and CONTROL-M/CM for SAP
Extractor services.
Silent installation or upgrade on Windows

The silent installation procedure can be used to install CONTROL-M/CM for SAP using a batch procedure instead of using the interactive installation procedure.
NOTE
Silent installation and silent upgrade of CONTROL-M/CM for SAP is not supported for Microsoft Windows cluster environments.
1 Prepare the installation parameters: A Log on using a user ID that has Administrator privileges on the current
computer.
B Insert the Installation CD. C In the Windows subdirectory of the CD, run the Prep_silent.bat file. D After entering all the parameters, select Save & Exit.
The parameters are saved in the %TEMP%\DRRMC.6.3.01_silent.bat file.
2 Run the installation procedure:
Chapter 2
Installation
33
Downloading the RFC library
A Ensure that the installation CD is still in the CD-ROM drive. B Enter the following command:
%TEMP%\DRRMC.6.3.01_silent.bat
C Check the %TEMP%\DRRMC.6.3.01_silent_log.txt to confirm that the

installation ended successfully.
3 If you are performing a new installation, run the Account Management utility
(ctmaftacc) to create at least one account. For information about creating accounts, see either Adding new accounts on page 67 or Using the Account Management utility in Silent mode on page 75.
NOTE
The same batch file can be copied to other computers and used to create several identical installations. Modify the <AGENT_NAME> parameter in the DRRMC.6.3.01_silent.bat file to the name of the CONTROL-M/Agent on which you want to install this CM. If necessary, you can modify the CD source mapping by altering the Auto_CD_ Image variable in the DRRMC.6.3.01_Silent.bat file. UNC mapping can also be used.
Where to go from here

The following table describes tasks that you should perform after you complete the installation procedure.
Subject Defining an account Altering CONTROL-M/CM for SAP default configuration. Configuring the Extractor process. Activating the Extractor process. Location See Account Management Utility on page 98. See Configuring general parameters on page 107. See Configuring and working with the Extractor Management utility on page 111. See Activating the Extractor Management utility on page 130.

The RFC library must correspond to the computer and the operating system where the CONTROL-M/CM for SAP is installed. The RFC library can be either 32 or 64 bit and it must match the CM for SAP compilation environment. However, in most cases, the CM for SAP requires the 32 bit version of the RFC library.
34
WARNING
If you download an incorrect RFC library, CONTROL-M/CM for SAP may not work.
Use Table 4 to help you decide which library version to download. The Paths to librfc downloads are available in solution SLN000000212332 in the Knowledge Base, accessible from the Customer Support website at http://www.bmc.com/support_home. SAP Note 413708 provides updated details regarding the RFC libraries. For more SAP information on the RFC library, go to http://service.sap.com/rfc-library. When selecting a download path, always select non-unicode. Table 2 RFC library details
Kernel version 6.40 6.40 6.40 6.40 6.40 6.40 6.40 6.40 6.40 6.40 6.40 32-bit or 64-bit 32-bit 64-bit 64-bit 32-bit 32-bit 32-bit 64-bit 32-bit 32-bit 64-bit 64-bit Library file name librfc32.dll librfc32.dll librfc32.dll librfccm.so librfccm.o librfccm.sl librfccm.so librfccm.so librfccm.so librfccm.so librfccm.so
Agent operating system Windows Windows Server on x86 64-bit Windows 2003 EE Itanium Solaris 32-bit/64-bit AIX 32-bit/64-bit HP-UX 32-bit/64-bit HP-UX Itanium Red Hat or SuSE Linux Red Hat or SuSE Linux on X86 64bit Red Hat or SuSE Linux Itanium Compaq TRU64 Unix
NOTE
When connecting to SAP Basis 7.00, the Kernel version value should be 6.40 and not 6.20.
After downloading the RFC library, extract it from the SAR file using the sapcar (Unix) or SAPCAR.exe (Windows) executable. For more information, see SAP Note 413708. You must then copy the RFC library to the following locations: In Unix
<Agent home directory>/CM/SAP/EXE/ <Agent home directory>/EXE/ Chapter 2 Installation 35
Step 3 - Importing the SAP panel
NOTE
For Unix, the file permission needs to be set to 755.
In Windows
<Agent home directory>\CM\SAP\EXE\ <Agent home directory>\EXE\
Checking the version of an RFC Library

Check the version of your current RFC library using the following procedure. On Unix, run the following command:
strings librfccm.<lib extension according to specific OS> | grep LIBRFC
On Windows, open an MS-DOS window, and run the following command:

find "LIBRFC" librfc32.dll
Step 3 - Importing the SAP panel

The following procedure ensures that SAP job parameters (the SAP panel) are displayed in the Job Editing form in CONTROL-M/EM and CONTROL-M/Desktop.
Before you begin

Ensure that the CONTROL-M/CM for SAP CD is mounted or easily accessible through your network.
To import the SAP panel

This procedure must be performed on every computer that has CONTROL-M/Enterprise Manager client components installed.
1 In CONTROL-M/Desktop, choose Tools => Import Applications Forms. 2 In the browse window, navigate to the Forms directory on the installation CD.
Select the SAP1.xml, SAP_DA.xml, and SAP_BW.xml files, and click Import.
36
Step 4 - Importing the CONTROL-M/CM for SAP utilities to the CONTROL-M Configuration Manager
3 Shut down CONTROL-M/Enterprise Manager GUI, and then restart it. This
enables the newly imported SAP panel functionality (see Figure 1 on page 49). For more information about the Job Editing form, refer to the CONTROL-M/Enterprise Manager User Guide.
NOTE
If you are upgrading an existing installation of CONTROL-M/CM for SAP, jobs that were defined and stored in CONTROL-M 6.1.03 or 6.2.01 can still be used with the new installation of CONTROL-M/CM for SAP.
Step 4 - Importing the CONTROL-M/CM for SAP utilities to the CONTROL-M Configuration Manager
The following procedure enables you to activate CONTROL-M/CM for SAP utilities from the CONTROL-M Configuration Manager.
NOTE
This feature is supported only for CONTROL-M/Agent 6.3.01 FP2, CONTROL-M/Server 6.3.01 FP2 and CONTROL-M/EM 6.3.01 FP4 or later.
Importing the functionality

NOTE
This procedure must be performed on every computer that has CONTROL-M Configuration Manager installed.
1 Close the CONTROL-M Configuration Manager. 2 Log on using a user ID that has Administrator privileges on the specific computer. 3 Insert the CONTROL-M/CM for SAP CD. 4 From the CCM subdirectory of the CD, run the CCMinstall.cmd file. 5 Restart the CONTROL-M Configuration Manager.
Chapter 2 Installation 37
Step 5 - CONTROL-M function modules
NOTE
In order to use the CONTROL-M/CM for SAP utilities in the CONTROL-M Configuration Manager, you must ensure that the ctmgetcm utility has been run in CONTROL-M/Server. For more information, see the Utilities chapter in the CONTROL-M/Server Administrator Guide.
Step 5 - CONTROL-M function modules

CONTROL-M Function Modules (FMs) are required in order to perform tasks that are not provided by the SAP standard BAPIs. They are CONTROL-M/CM for SAP-specific APIs that enhance the functionality of SAP. A set of predefined CONTROL-M FMs is provided together with CONTROL-M/CM for SAP.
NOTE
If you do not want to install CONTROL-M Function Modules, ensure that the Use Extended check box in the configuration utility is cleared. For more information, see Configuring general parameters on page 107.
Importing CONTROL-M function modules to SAP Unicode systems

When importing CONTROL-M Function Modules to a SAP system 6.10 or later, contact your SAP administrator to determine whether it is a Unicode system. If it is, you must follow the instructions provided in SAP Note 330267, in the section entitled "Transports from 4.6 to 6.10/6.20/6.30", regarding actions to be performed during the import procedure. Otherwise, CONTROL-M Function Modules may not work in the SAP Unicode system.
CONTROL-M/CM for SAP and the SAP XBP interface

XBP 2.0 was created by SAP to work with external scheduling applications. XBP 2.0 replaces and upgrades many functionalities previously provided by the CONTROL-M FMs in earlier versions of CONTROL-M/CM for SAP. CONTROL-M/CM for SAP version 6.3.01 works integrally with the XBP interface and its latest improved functionality in version 2.0. To work with CONTROL-M/CM for SAP XBP 2.0 functionality, you must set the value of the XBP Version account parameter to XBP2.0. For more information, see Account Management Utility on page 98.
The XBP 2.0 interface is integrated in the SAP system as part of the standard Support Package supplied by SAP. To see which Support Package includes the XBP 2.0 interface, see XBP interface on page 23. To verify whether your SAP system includes the XBP 2.0 interface, see XBP Version on page 101. The following table describes the major differences in actions performed with XBP 1.0, XBP 2.0, and CONTROL-M FMs. If, to perform a specific action, either XBP BAPIs or CONTROL-M FMs can be used, CONTROL-M always uses XBP BAPIs. For example, if you want to copy a variant on a SAP system with XBP 1.0 installed, CONTROL-M FMs must be installed. However, if your SAP system has XBP 2.0 installed, the variant is copied using the XBP BAPIs (2.0). Table 3
Action Parent/Child (mass parallel) functionality Intercept functionality Enhanced Extract functionality Basic Extract functionality (ctmextract) Raise SAP events Submit an event-based job Batch Input functionality Submitting Data Archiving jobs Detecting and Releasing Data Archiving jobs X X (Using the Parent/Child and the Interception functions) Job Class (A, B) in Create mode Preventing duplication in extracting jobs from SAP X X X X X X X X X
XBP BAPIs versus CONTROL-M function modules (part 1 of 3)

XBP 1.0 BAPIs XBP 2.0 BAPIs X X X X (Works partially without CONTROL-M FMs) X CONTROL-M Function Modules
Chapter 2
Installation
39
Table 3
Action

XBP 1.0 BAPIs XBP 2.0 BAPIs X X X X CONTROL-M Function Modules
Support for External Command Spool List Recipient in Create job mode Additional Print and Archiving Job Step parameters Improved faster mechanism for tracking jobs in SAP Configure Joblog retrieval Opersys cover page parameter CP and NP options in variant selection Parameters for time of printing (Print immediate, Print later or Send to SAP spooler) Use Logon Groups Load and Action requests: ABAP Programs list Variants list Show Variant Variant Copy Variant Change Output devices (printers) list Layouts (print formats) list Load Job Server Groups Load External Command Load for distribution list X X X
X X X X
X X X X X X X X X X
X X X X
40
CONTROL-M/CM for SAP and SAP Business Information Warehouse
Table 3
Action Load owner

XBP 1.0 BAPIs XBP 2.0 BAPIs X Note: Supported when working with SAP 6.20 or later. CONTROL-M Function Modules
Load event
CONTROL-M/CM for SAP and SAP Business Information Warehouse

When working with SAP-BW there are several actions that cannot be performed by the SAP standard BAPIs. These are performed by CONTROL-M Function Modules. The following table describes the major differences in actions performed by BW 2.x BAPIs, BW 3.x or later BAPIs, and CONTROL-M Function Modules. Table 4
Action Start I/P Monitor I/P I/P Sysout Get Background Job Name/Count Set Background Job Name Display the number of records transferred and requested of an I/P run Start P/C Monitor P/C Restart P/C P/C Sysout Not relevant Not relevant Not relevant Not relevant X X X X X
SAP-BW BAPIs versus CONTROL-M function modules

BW 2.x BAPIs X X BW 3.x or later CONTROL-M Function BAPIs Modules X X X X X X X
NOTE
Process Chains (P/C) capabilities are only available in SAP-BW 3.x or later systems.
Chapter 2
Installation
41
Installing the CONTROL-M FMs in the SAP system
Installing the CONTROL-M FMs in the SAP system

CONTROL-M FMs are packed in SAP Transports, and are located on the installation CD:

On Unix: <CDROM_path>/Transports On Microsoft Windows: <CDROM_path>:\Transports
To install the FMs in the SAP system, you must import the containing transport into the SAP system. Copy the transport files into the transport directory of the SAP system. Ensure that you remove the read-only attribute of the transport files copied from the CD. Otherwise, the import to the SAP system may fail. Use the SAP Transport Management System (transaction STMS) or the operating system executable program tp to import the required transport. For information about the Transport Management System and the tp program, refer to SAP documentation. Each of the following subfolders under the Transports folder contains transports as follows: SAP_R3
This transport must be installed in order to use any of the CONTROL-M FMs, and it must be installed before installing any other transports.
BW
This transport contains the BW-related FMs. Install it only after the SAP_R3 transport is installed.
DA
Install this transport if you use the CONTROL-M Data Archiving functionality. Install it only after the SAP_R3 transport is installed. Do NOT install this transport on SAP release 4.5B.
AUTH
Install this transport if you want to use the CONTROL_M authorization-role.
42
Installing the Conversion utility
The authorization transport contains a role that includes all of the minimum authorization needed for CONTROL-M users. This transport must be imported into Client 000 and then the role must be copied to the specific client by creating a local transport and importing it to the target client. BMC Software recommends defining SAP users for CONTROL-M with the SAP System user type.
Installing the Conversion utility

The conversion utility (ctmr3con) converts CONTROL-M Option for R/3 jobs, and jobs created by the CONTROL-M/Desktop Job Editing form, to CONTROL-M/CM for SAP jobs. For more information about this utility, see Converting CONTROL-M Option for R/3 jobs on page 152.
NOTE
The conversion utility can only be run if you are using a Windows operating system.
To install the Conversion utility 1 Log on to the CONTROL-M/EM computer. 2 Extract the sap_cm_conv_ut.zip zip file from the <cdrom_path>\conversion folder to
a temporary folder on the computer.
To uninstall the Conversion utility

When you finish using the conversion utility, you can remove it by deleting the temporary directory and all its contents.

The following table describes where to find information related to this task.
Subject What can be converted and how to convert jobs Location See Converting CONTROL-M Option for R/3 jobs on page 152.
Chapter 2
Installation
43
Uninstalling CONTROL-M/CM for SAP
Uninstalling CONTROL-M/CM for SAP

To uninstall from Unix NOTE
Before beginning the uninstall procedure, ensure that all jobs are ended.
1 On your CONTROL-M/Agent computer, log on as the root user, and run the
2 Log on as the CONTROL-M/Agent user, and run the shut-xt command to shut
down the Extractor process.
3 Run the following command to uninstall CONTROL-M/CM for SAP.

$HOME/BMCINSTALL/uninstall/cmsap_uninstall.sh
4 Type Y, and press <Enter> to confirm the uninstall procedure; a message detailing
what is being removed is displayed. The uninstallation procedure is complete. CONTROL-M/CM for SAP has been successfully removed from your computer. To restart CONTROL-M/Agent, log on as the root user again, and run the start-ag command.
To uninstall from Microsoft Windows NOTE

Before beginning the uninstall procedure, ensure that all jobs are ended.
1 From the Start menu, choose Settings => Control Panel, and double-click
Add/Remove Programs.
2 Select CONTROL-M/Control Module for SAP under the relevant agent, and click
Add/Remove.
3 Select Uninstall your Current Version and click OK. The uninstallation procedure is
complete.
44
Chapter
Defining and monitoring SAP jobs in CONTROL-M

3
A CONTROL-M/CM for SAP job is a job definition to be used for defining and monitoring SAP jobs. These jobs are defined using the Job Editing form in CONTROL-M/Desktop. The Job Editing form contains a series of panels, including the SAP panel, as shown in Figure 1 on page 49. The following tasks are described in this chapter:

Creating a template for a job definition Creating a job skeleton for SAP jobs Creating and monitoring SAP R/3 jobs Data archiving jobs Business Information Warehouse jobs
NOTE
For more information about the Job Editing form and Job parameters, see the CONTROL-M/ Guide and the CONTROL-M Job Parameter and Variable Reference Guide.
Creating a template for a job definition

NOTE
This section is for users of CONTROL-M/Enterprise Manager 6.3.01 or later. If you are using CONTROL-M/Enterprise Manager 6.2.01 or earlier, please proceed directly to Creating a job skeleton for SAP jobs on page 46.
Chapter 3
45
Creating a job skeleton for SAP jobs
To create or modify a template 1 In CONTROL-M/EM, create a template, as described in the

CONTROL-M/Enterprise Manager Administrator Guide.
2 Select the required CONTROL-M from the list of available CONTROL-M/Servers. 3 Select one of the following Job Types from the current JOB TYPES list:

SAP R3 SAP Data Archiving SAP Business Warehouse
4 Select the Execution tab of the Job Editing form to display the Execution panel. 5 In the Node Id/Group field of the Execution panel, specify the name of the
CONTROL-M/Agent on which you want to define and run jobs.
NOTE
You can manually enter the name of the Agent, or click Load to generate a list of available Agents. If you want to utilize CONTROL-M node groups with CONTROL-M/CM for SAP, ensure that the ctmgetcm utility has been run in CONTROL-M/Server. For more information about defining a Node Group, see the CONTROL-M/Server Administrator Guide.

NOTE
This section is for users of CONTROL-M/Enterprise Manager 6.2.01. If you are using CONTROL-M/Enterprise Manager 6.3.01 or later, please proceed directly to Creating and monitoring SAP R/3 jobs on page 48
46
Using the task described in this section, you prepare a skeleton for SAP jobs in CONTROL-M/Desktop.
Before you begin
Select an existing skeleton from the Current Skeleton list and make a copy of it, giving it a new, logical name. BMC Software recommends that you use the WINDOWS_SKELETON for this purpose. If you want to utilize CONTROL-M node groups with CONTROL-M/CM for SAP, ensure that the ctmgetcm utility has been run in CONTROL-M/Server. For more information, see the Utilities chapter in the CONTROL-M/Server Administrator Guide.
NOTE
You must create separate job skeletons for SAP R/3 jobs, SAP Data Archiving jobs, and SAP BW jobs.
To create or modify a skeleton 1 Click Edit Skeleton on the toolbar. 2 Choose the required CONTROL-M from the list. 3 Click Application. Additional fields of the Skeleton Editor are displayed. 4 In the Application Node Group field, specify the name of the
CONTROL-M/Agent on which you want to define and run jobs. You can either manually enter the name of the Agent, or click Load to generate a list of available Agents. For information about defining a Node Group, see the CONTROL-M/Server Administrator Guide.
5 In the Application field
if you specified the Application Node Group field manually, you must specify an applicable set of values from the list if you chose the Application Node Group field from the Load list, this field is automatically specified according to your selection
Chapter 3
47
Creating and monitoring SAP R/3 jobs
6 In the Form Name field:

choose SAP R3 to load the SAP job panel designed to work with SAP R3 jobs choose SAP Data Archiving to load the SAP job panel designed to work with Data Archiving jobs choose SAP Business Warehouse to load the SAP job panel designed to work with SAP-BW jobs
NOTE
If none of these are displayed in the Form Name field, the SAP panel was not imported properly. For more information, see Step 3 - Importing the SAP panel on page 36.
7 Click OK. NOTE

For more information about defining a skeleton, see the CONTROL-M/ Guide.

Subject Defining a Skeleton Creating a Job Specify Parameter Values Location For more information about defining a template or a skeleton, see the CONTROL-M/ Guide. See Creating and monitoring SAP R/3 jobs on page 48. For more information about parameter values, see the CONTROL-M Job Parameter and Variable Reference Guide.

Use the following task to create a CONTROL-M/CM for SAP job.
Before you begin

For CONTROL-M/EM 6.2.01 or earlier: Ensure that you have a job skeleton defined for CONTROL-M/CM for SAP jobs, as described in Creating a job skeleton for SAP jobs on page 46, and select this skeleton from the Current Skeleton list in CONTROL-M/Desktop
48
To Create a SAP R3 job 1 For CONTROL-M/EM 6.3.01 or later, choose Edit => New Job.
For CONTROL-M/EM 6.2.01 or earlier, choose Edit => Job => New.
2 For CONTROL-M/EM 6.3.01 or later, select the SAP template from the Template
list. For more information about creating a template, see Creating a template for a job definition on page 45. For CONTROL-M/EM 6.2.01, proceed directly to step 3.
NOTE
For descriptions of all panels in the Job Editing form, see the CONTROL-M/ Guide.
3 Click the SAP tab of the Job Editing form to display the SAP panel, as shown in
Figure 1 on page 49. Figure 1 SAP panel, Job Editing form (Job Definition mode)
Chapter 3
49
4 Choose the required job mode. There are five options:
Choose Create to create and run a new job in SAP. At least one step must be selected in order to define a SAP job in CONTROL-M. For explanations about setting Job steps, see Selecting job steps on page 60. Choose Original to run an existing job in SAP. Choose Copy to copy an existing job in SAP and run the new job. Choose External to monitor an existing job in SAP, submitted by a user, or by another entity other than CONTROL-M. This can also be used for monitoring and post-processing. Choose Batch Input to run a Batch Input session.
The appropriate parameters are enabled for the selected job mode. For descriptions of all SAP panel parameters, see Table 6 on page 52.
5 For CONTROL-M/Desktop 620 or earlier, click Save to Draft when you are
satisfied with the data in the SAP panel. The job is added to the current CONTROL-M Scheduling table. For CONTROL-M/Desktop 6.3.01 or later, when you are satisfied with the data in the SAP panel, click one of the following:

Save: The job is added to the current CONTROL-M Scheduling Table. Save and Close: The job is added to the current CONTROL-M Scheduling Table and job definition window will be closed Save & Order: The job is added to the current CONTROL-M Scheduling Table and can be ordered immediately. Save as Template: The job definition is saved as a template for further SAP job definitions.

Subject Data Archiving Jobs SAP-BW Jobs Location See Data archiving jobs on page 75. See Business Information Warehouse jobs on page 88.
Using the SAP Event Based Scheduling functionality to trigger a job

If you want a job to be triggered by a SAP Event, you can use the SAP Event Based Scheduling functionality.
50
SAP panel parameters
During the time a job is ordered, this functionality adds certain AutoEdit variables to the job, when the CTMORDER action is submitted. These AutoEdit variables are read-only and their values are displayed in the Set panel in the Job Editing form. Their definitions are described in Table 5 : Table 5 SAP Event Based Scheduling AutoEdit variables
Description Name of the event Corresponds to the value of the Event parameter in your SAP system. Value is always SAP Name of the SAP server that raised the event In the format: yyyymmddhhmmss (GMT)
AutoEdit Variable %%EVENT_ID %%EVENT_PARM %%EVENT_TYPE %%EVENT_SOURCE %%EVENT_TIMESTAMP
%%EVENT_CM_ACCOUNT Name of CONTROL-M/CM for SAP account
For more information, see SAP Event Based Scheduling on page 131.

The CONTROL-M/CM for SAP fields in the SAP panel of the Job Editing form are described in Table 6 .
NOTE
For a more detailed description of each parameter, see the SAP Parameters chapter in the CONTROL-M Job Parameter and Variable Reference Guide. Clicking the Load buttons in the SAP panel generates a list in real time that satisfies relevant criteria. To enter a value in a specific field, select the item from this list and click OK. The asterisk * can be used as a wildcard to filter parameters such as account names, Job names, and so on. For example, entering *DE* in the Account field generates a list of all accounts that contain the string DE.
Chapter 3
51
Table 6
Parameter Account
SAP panel parameters - Job Definition mode (part 1 of 8)

Definition Account name. Mandatory. Uppercase only, no blank spaces permitted. The account is a profile. The remaining parameters are predefined according to the account, when the account is created. Account is mapped to the CONTROL-M/EM Owner parameter. Click the account Load button to display a list of accounts that comply with the generic name you enter. The asterisk * can be used as a wildcard to filter account names. For information about defining an account, see Adding a new account on page 102.
Copy From Step
Indicates from which Job step in the original job to begin the copying procedure. Mandatory for Copy job mode. Disabled for other job modes. Valid values are: 1-99. Default: 1
Detect Spawned Jobs A spawned job is a job created by another (parent) job, and monitored by CONTROL-M. This parameter indicates whether to detect and monitor jobs that were spawned by the current SAP job. The following options are available:
Start Spawned Job: start any detected spawned job that has a status of Scheduled. No Detection needed: Do not detect spawned jobs of the current job. Detect and Create According to: Parent (current) job definition: Detect spawned jobs of the current job and extract these jobs to CONTROL-M, with identical properties to the parent job. A specific job definition: A field is displayed, in which you enter a specific SAP-type job name. Detected spawned jobs of the current job are extracted to CONTROL-M with identical properties to the selected (not the current) job. Note: The selected job must exist in the same scheduling table as the current job.
For detailed information about detecting spawned jobs, see Initiating a mass parallel process (detecting spawned jobs) on page 127. Event The event ID that indicates the event name of the After Event start condition. Text box. Mandatory for the After Event start condition. Valid values are: 1-32 characters.
52
Table 6
Parameter

Definition The event parameter for a specific ID. Text box. Optional. Valid values are: 1-64 characters.
Event parameter
Job Class
Job submission priority (in SAP). Mandatory for Create job mode only. Disabled for every other job mode value. Valid values are:

A (most urgent) B (urgent) C (least urgent) (Default)
Note: The A and B values only work if you use XBP 2.0 functionality or the Extended functionality in an XBP 1.0 system with the CONTROL-M Function Modules installed. Job Count Unique SAP job ID number Mandatory when Job Mode value is Copy, Original, or External. 8-digit number (specific job) or special values (string). Special values:

FIRST FIRST_SCHEDULED LAST LAST_SCHEDULED
When the job mode value is Copy, the parameter can contain digits or any of the special values. When the job mode value is Original, the parameter can contain digits, FIRST_SCHEDULED, or LAST_SCHEDULED. When the job mode value is External, the Special Values are not applicable and an 8-digit number must be entered. Job Mode Determines the task that the job performs. Mandatory. Valid values are:

Create: Create a new job. Copy: Copy an existing job. Original: Run a previously defined job. External: Monitors a job that runs in the SAP Server. Batch Input: Process a Batch Input session.
Chapter 3
53
Table 6
Parameter Job Name

Definition Job name to be monitored or submitted. Mandatory. Mapped to the CONTROL-M/EM Job Name parameter. In any job mode other than Create you can load a list of available jobs using a Job Status and Owner filter. Click Filter to display the Job Status Filter window and select criteria for choosing jobs by Job Status and Owner. Click Load to display a list of job names that meet the criteria defined in the Job Status Filter window.

The Filter and Load options are not available in Create job mode. In Original job mode, when you open the Job Status Filter dialog box only Scheduled is selected and cannot be modified. All other statuses are disabled. In Copy and External job modes, when you open the Job Status Filter dialog box, all statuses are enabled. In Batch Input job mode, the Filter option is not available. Click Load to display a list of available Batch Input sessions. In Batch Input job mode the Job Name field is also called Map Name.
The asterisk * can be used as a wildcard to filter jobs. Note: This parameter is case-sensitive (for a generated Load list). For example, if you entered JOBD* as criteria, the generated Load list would display all jobs beginning with the characters JOBD, but not jobs beginning with Jobd. New Job Name New job name for Copy mode only. Optional. Mapped to the CONTROL-M/EM Job Name parameter.
54
Table 6
Parameter

Definition
Output Management When you click the Output Management button the Output Management dialog box opens. The field formerly known as Copy spool to is included in this dialog box. Manage and control the output of your job, Optional. The Spool of the job and its Joblog are both created in SAP. You can customize the way CONTROL-M handles them by selecting one of the following options for each output type:
Do not copy. (Default for Spool) Copy to Sysout - the Spool or Joblog is copied to the same location as the job output. (See Sysout Handling in the CONTROL-M Job Parameter and Variable Reference Guide). (Default for Joblog). Copy to file - name and path of the file to which the Spool or Joblog is copied. Case sensitive, no blank spaces permitted.
QID
Batch Input Session Queue ID number. Optional. Only enabled if the job mode is set to Batch Input Default: None Filled automatically when you click the Job Name Load button and select a specific Batch Input session. If left unset, the oldest defined session is scheduled. Note: Batch Input jobs that are deleted after they run are not monitored. The status of jobs marked for deletion is not displayed.
Chapter 3
55
Table 6
Parameter

Definition When you click the Spool List Recipient button, the Spool List Recipient dialog box opens. Optional. Recipient type - Select the recipient type from the list. Note: The following Recipient types are supported: SAP user name External address Shared distribution list Private distribution list Other Recipient types are not fully supported. Recipient name - Name of the recipient of the job. Click Load to generate and display a list of all recipients. The list of recipients is displayed according to the selected recipient type. The asterisk * can be used as a wildcard to filter the search. The Load action is available for the following recipient types: SAP user name Shared distribution list Private distribution list Other recipient types can be entered manually.

Spool List Recipient
Attributes: The following attributes are available. By default these are not selected. Copy and Blind copy cannot be selected at the same time.

Copy Express Blind copy No forwarding
Note: This only works if you use XBP 2.0 functionality or the Extended functionality in an XBP 1.0 system with the CONTROL-M Function Modules installed.
56
Table 6
Parameter

Definition When you click the Start Condition button the Start Condition dialog box opens.The field formerly known as Submit Job with ASAP Option is included in this dialog box. In this dialog box, you can set whether the job runs with the ASAP option immediately or after event. Valid values are:
Start Condition
ASAP - Submit with ASAP option. (Default) If ASAP is selected the job runs as soon as a background work process is available for it in SAP. If the job cannot start immediately, it is transformed in SAP into a time-based job. Immediate - Start immediately. If Immediate is selected, the job either runs immediately, or fails in case there are no work processes available to run it. After Event - The job is submitted and waits for an event to be triggered. This option is supported only if SAP Note 833777 is implemented. If you selected the After Event option in the Start Condition window you must enter the following information:
Event: Event name. Maximum 32 characters. Mandatory for event-based jobs. Upper case only. Click Load to generate and display a list of available events. The asterisk * can be used as a wildcard to filter the search. Parameter: Event parameter. Maximum 64 characters. Optional.
Jobs submitted with the After Event start condition, remain in Released status in SAP until the event occurs. A message indicating this is displayed in the CONTROL-M SYSOUT. Note: The event-based job functionality only works if you use XBP 2.0 functionality. Load action for Events only works if you use the Extended functionality of the CONTROL-M Function Modules.
Chapter 3
57
Table 6
Parameter Steps

Definition Step (action) to be performed as part of the SAP job. At least one step must be defined in Create job mode. Disabled for every other job mode. Between 1-99 steps can be selected. ABAP program: Add an ABAP program. External command: Add an external command. External program: Add an external program. The following control buttons can be used for each step: Move up Move down Delete Edit Duplicate step
58
Table 6
Parameter

Definition Job server group on which the job runs. Optional. Case sensitive, no blank spaces permitted. Click Load to generate and display a complete list of available Job server groups. If this parameter is left unspecified, the SAP system decides on which server to run the job. See also, Target Server below in this table. The Job server groups are defined in the SAP SM61 transaction. They contain a list of Application Server names. If you set a group name in the Target group field of the job definition, the job is submitted using a Background work process, on the most available Application Server from the list included in this group. Note: this functionality only works if your SAP system is release 6.10 or later and you have SAP Note 729317 installed. The Load action for the Target Group list only works if you use XBP 2.0 functionality. For information about load-balancing during logon time, see Account Management Utility on page 98.
Target Group
Target Server
Application Server on which the job runs. Optional. Case sensitive, no blank spaces permitted. Click Load to generate and display a complete list of available application servers. If this parameter is left unset, the SAP system decides itself on which application server the job is to be carried out. This is the normal procedure recommended by SAP, because the system can then carry out its own load balancing. BMC Software recommends that you only select the target server if that server has particular resources necessary for the job processing. Note: If manually set, the following (full) format must be used: hostname_SYSID_sysnumber
Chapter 3
59
Selecting job steps
Selecting job steps

There are three different kinds of job steps that you can add to a job:

ABAP program External command External program
To select a job step 1 In the SAP panel of the Job Editing form, ensure that the Create job mode is
selected.
2 Click the Add step button corresponding to the type of job step you want to add
(ABAP Program, External command, or External program). The appropriate dialog box opens.
3 Set the parameter values in the dialog box, as described in

Add ABAP dialog box parameters on page 61 External Command dialog box parameters on page 69 External Program dialog box parameters on page 71
4 Click OK to add the job step to the SAP job, and to return to the SAP panel of the
Job Editing form. Use the control buttons to edit and manipulate selected program steps.
60
Selecting job steps
Add ABAP dialog box parameters

The Add ABAP dialog box parameters are described in Table 7 on page 62. For more information about these parameters, see the CONTROL-M Job Parameter and Variable Reference Guide. Figure 2 Add ABAP dialog box
WARNING
CONTROL-M/CM for SAP supports CJK language functionality. However, while the program itself supports CJK languages, the name and the description of the ABAP should not contain any CJK language characters. If the following message is displayed ("The CONTROL-M response is invalid."), when you click the ABAP Program Load button, it is likely that this is the reason.
Chapter 3
61
Selecting job steps
Table 7
Parameter
Add ABAP dialog box parameters (part 1 of 5)

Description The name of the ABAP program. Mandatory. Uppercase only, blank spaces permitted, special characters (for example, &, * or ?) not permitted. Either Enter a specific ABAP program manually, or
ABAP Program
Click Load to generate and display a list of all ABAP programs. If there are more entries than the number you entered in the Max List Entries parameter, select Additional Results to see more results. For more information on configuring the Max List Entries parameter, see Configuring general parameters on page 107.
Tip: Narrow the search parameters by entering at least one character in the field, before clicking Load. The asterisk * can be used as a wildcard. Note: The Load button only works if you use XBP 2.0 functionality or the Extended functionality in an XBP 1.0 system with the CONTROL-M Function Modules installed. Archive ID SAP ArchiveLink Storage system ID. Case sensitive, only trailing blank spaces permitted. Default: ZZ. Note: This only works if you use XBP 2.0 functionality or the Extended functionality in an XBP 1.0 system with the CONTROL-M Function Modules installed. Only enabled if Print Archive Mode is set to Archive or Print & Archive. Archive Text Free text description of the archive location. Optional. Case sensitive, no blank spaces permitted. Note: This only works if you use XBP 2.0 functionality or the Extended functionality in an XBP 1.0 system with the CONTROL-M Function Modules installed. Only enabled if Print Archive Mode is set to Archive or Print & Archive. Authorization Columns User with print authorization. Optional. Case sensitive, blank spaces permitted. Maximum number of characters on an output line. Mandatory. Valid values are: An integer between 1-255, or select the Use ABAP program default check box to indicate that the number of characters is obtained from the ABAP program code. Default: 80. Delete After Print Indicates if report is deleted after printing. Optional. Valid values are:

Selected = delete after printing Cleared = do not delete after printing (Default)
62
Selecting job steps
Table 7
Parameter

Description Spool department. Optional. Case sensitive. Blank spaces permitted. Note: This only works if you use XBP 2.0 functionality or the Extended functionality in an XBP 1.0 system with the CONTROL-M Function Modules installed.
Department
Document Type Archive object document type. Optional. Case sensitive, blank spaces permitted. Only enabled if Print Archive Mode is set to Archive or Print & Archive. Information Field Archive information. Optional. Free text string. Case sensitive, blank spaces permitted. Only enabled if Print Archive Mode is set to Archive or Print & Archive. Job Name Language A read-only field that displays the job name. Language. One character. Case sensitive. Optional. Example: E for English; D for German; d for Serbo-Croatian. If left unset, the value is taken from the account language field. Layout Print Layout format. Optional. Uppercase only, no blank spaces permitted. Click Load to generate and display a list of all layouts. The asterisk * can be used as a wildcard to filter the search. Note: The Load button only works if you use XBP 2.0 functionality. Name Spool list name. Optional. Uppercase only, blank spaces permitted. Note: This only works if you use XBP 2.0 functionality or the Extended functionality in an XBP 1.0 system with the CONTROL-M Function Modules installed. New Spool Request New spool request. Optional. Valid values are:

Selected = Request new spool (Default) Cleared = Do not request
Note: This only works if you use XBP 2.0 functionality or the previous Extended functionality in an XBP 1.0 system with the CONTROL-M Function Modules installed. Number of Copies Object Type Number of copies to be printed. Mandatory. Valid values are: 1 - 255. Default: 1 Archive object type. Optional. Case sensitive, blank spaces permitted. Only enabled if Print Archive Mode is set to Archive or Print & Archive.
Chapter 3
63
Selecting job steps
Table 7
Parameter

Description Type of cover sheet for output. Optional. Drop down list format. Valid values are:

OS Cover Sheet
Default Setting Print Do Not Print
Output Device
Designated printer logical name. Optional. Uppercase only, no blank spaces permitted. Click Load to generate and display a list of all output devices. The asterisk * can be used as a wildcard to filter the search. Notes: The Load button only works if you use XBP 2.0 functionality. If the device does not exist, SAP adds a $ sign before the device name.
Owner
R/3 user whose authorizations the Job Step uses during processing. Optional. Uppercase only, no blank spaces permitted. If left unset, the value is taken from the account owner field. Click Load to generate and display a list of all owners. Note: The load functionality works only in SAP 6.20 or later, and only with a specific Basis SP installed. For more details, see SAP note 753559. The asterisk ("*") can be used as a wildcard to filter the search. Note: To prevent users from running job steps with a different user, use authorization restrictions in SAP. To do this, give the authorization object S_BTCH_NAM a specific value for BTCUNAME. For details, see SAP documentation.
Print Archive Mode
Print archive mode. Optional. Valid values are:

Print (Default) Archive Print & Archive
Print Expiration The number of days after which print job expires. Optional. Range: 1-8 or Do Not Delete. Recipient Name of recipient of step output. Optional. Case sensitive, blank spaces permitted.
64
Selecting job steps
Table 7
Parameter Rows

Description Maximum number of rows per page. Mandatory. Valid values are: An integer between 1-90, or select the Use ABAP program default check box to indicate that the number of rows is obtained from the ABAP program code. Default: 65.
SAP Cover Page Type of cover page for output. Optional. Valid values are:

Default Setting Print Do Not Print
SAP Job Step Selection Cover Page
A read-only field that indicates the step number in the job. Indicates whether a selection cover page should be used. Optional. Valid values are:

Selected Use cover page Cleared Do not use cover page (Default)
Time of Print
Indicates whether to print job output immediately. Optional. Valid values are:

Print out immediately Print Later Send to SAP spooler (Default)
Note: the default value Send to SAP spooler can only be used in SAP release 6.10 or later. If you do not change this value in SAP releases lower than 6.10, the SAP system uses its default value. Titles Spool list titles. Optional. Case sensitive, blank spaces permitted. Note: This only works if you use XBP 2.0 functionality or the Extended functionality in an XBP 1.0 system with the CONTROL-M Function Modules installed.
Chapter 3
65
Selecting job steps
Table 7
Parameter

Description
Use ABAP This parameter exists for both the Rows and the Columns parameters. Program Default Select it if you want to use the ABAP program default for either the maximum number of rows per page (Rows), or the maximum number of characters on an output line (Columns). Valid values are:

Selected - Use the ABAP program default Cleared - Do not use the ABAP program default. Use the number entered in the Rows or Columns box.
Variant Name
Variant name. Optional. Only enabled if the ABAP program parameter is selected. Click Load to generate and display a list of variants available for the selected ABAP program. The asterisk * can be used as a wildcard to filter the search. Uppercase only, blank spaces permitted, special characters are permitted according to SAP guidelines. (For more information, please refer to the SAP documentation). When a variant is set for an ABAP program, the following buttons are enabled:
Copy. Enables the creation of a new variant based on the properties of an existing variant. The new variant is created as soon as you confirm its name. Show. Displays the variant values in a separate window (see Figure 3 on page 67). Change. Enables you to modify the values of the various variant parameters, see Figure 3 on page 67. To apply these parameter values click OK. To keep the variants original parameter values, click Undo Changes. Note: The changes in the values of the variant parameters are only performed during job run time.
Note: The Copy, Show and Change buttons only work if you use XBP 2.0 functionality or the Extended functionality in an XBP 1.0 system with the CONTROL-M Function Modules installed.
66
Selecting job steps
Variant subparameters
Figure 3 Change variant dialog box
The following subparameters are displayed in the Change Variant dialog box: Table 8
Parameter Description # Modify Name Type
Change Variant subparameters (part 1 of 2)

Description The Variant description This field can be changed in the Change variant window. A read-only field that indicates the index number of the Variant parameter Checkbox. Select to indicate that the parameter should be changed. a read-only field that indicates the name of the Variant parameter There are three variant types: Simple - Enter a specific value in the Value field. Other fields are disabled. Selection - Enter a specific value in the Value field. Set values for the Sign and Option fields. Range - Enter Low and High values. Set values for the Sign and Option fields. free text value; used for Simple and Selection parameter types. the lower limit value; used only for Range parameter type upper limit value; used only for Range parameter type
Value Low High
Chapter 3
67
Selecting job steps
Table 8
Parameter Sign
Change Variant subparameters (part 2 of 2)

Description used for Selection and Range parameter types; specifies whether the condition is inclusive (applies) or exclusive (does not apply). Valid values are:

I - inclusive E - exclusive
Option
used for Selection and Range parameter types; contains the operator for the elementary condition. See Table 9 Variant options for selection and range types below.
Table 9
Option BT NB EQ NE GT LT GE LE CP NP
Variant options for selection and range types

Type Range Range Selection Selection Selection Selection Selection Selection Selection Selection Description Between - used with lower and upper limits Not Between - used with lower and upper limits. Equal - used with the Value field Not equal - used with the Value field Greater than - used with the Value field Less than - used with the Value field Greater or equal - used with the Value field Less than or equal - used with the Value field Contains pattern - used with wildcards in the Value field Does not contain the pattern - used with wildcards in the Value field
For more information about select options, see SAP documentation.
68
Selecting job steps
External Command dialog box parameters

The External Command dialog box parameters are described in Table 10 . For more information about these parameters, see the CONTROL-M Job Parameter and Variable Reference Guide. Figure 4 External command dialog box
Table 10
Parameter
External Command dialog box parameters (part 1 of 2)

Description Indicates whether a trace is activated. Optional. Valid values are:

Activate trace
Selected - activate Cleared - not activated (Default)
Name
External Command name. Mandatory. Upper-case only; blank spaces are permitted. Click Load to generate and display a list of all external commands. When you select a line from the list, this field, and the Operating System fields are inserted with the selected values. The asterisk * can be used as a wildcard to filter the search.
Job name
A read-only field that displays the job name.
Chapter 3
69
Selecting job steps
Table 10
Parameter
External Command dialog box parameters (part 2 of 2)

Description Indicates whether SAP waits for the external command to end before starting the next step, or exiting. Optional.Valid values are:

Job waiting for external termination
Selected Waits (Default) Cleared Does not wait
Log external errors in job log
Indicates whether to write errors to the job log. Optional. Valid values are:

Selected - write to log (Default) Cleared - do not write
Log external Indicates whether to write output to the job log. Optional. Valid values output in job log are:

Operating System
Operating system type for the command as defined in SAP. Use the Load button of the Name field. Enter value manually, or click the "..." button to select a value from the list.
Owner
Authorized step owner. Optional. Uppercase only, blank spaces not permitted. If left unset, the value is taken from the account owner field. Click Load to generate and display a list of all owners. The asterisk * can be used as a wildcard to filter the search.
Parameters Step number Target Server
Parameters for the external command. Optional. Case sensitive, blank spaces are permitted. A read-only field that indicates the step number in the job. Host computer where the external command runs. Mandatory. Case sensitive, blank spaces are not permitted. Click Load to generate and display a list of all target servers Note: If manually set, the short format must be used: hostname
70
Selecting job steps
External Program dialog box parameters

The External Program dialog box parameters are described in Table 11 . For more information about these parameters, see the CONTROL-M Job Parameter and Variable Reference Guide. Figure 5 External program dialog box
Table 11
Parameter
Add External Program dialog box parameters (part 1 of 2)

Description Indicates whether a trace is activated. Optional. Valid values are:

Activate trace
Selected - activate Cleared - not activated (Default)
Name Job name Job waiting for external termination
External program name. Mandatory. Case sensitive, blank spaces are permitted. A read-only field that displays the job name. Indicates whether SAP waits for the external program to end before starting the next step, or exiting. Optional. Valid values are:

Selected Waits (Default) Cleared Does not wait
Log external errors in job log
Indicates whether to write errors to the job log. Optional. Valid values are:

Chapter 3
71
Selecting job steps
Table 11
Parameter
Add External Program dialog box parameters (part 2 of 2)

Description
Log external Indicates whether to write output to the job log. Optional. Valid values output in job log are:

Owner
Authorized step owner. Optional. Uppercase only, blank spaces not permitted. If left unset, the value is taken from the account owner field.
Parameters Step number Target host
Parameters for the external program. Optional. Case sensitive, blank spaces are permitted. A read-only field that indicates the step number in the job. Host computer where the external program runs. Mandatory. Case sensitive, blank spaces are not permitted. Note: If manually set, the short format must be used: hostname
72
Monitoring and managing SAP jobs in CONTROL-M

You can monitor SAP jobs using CONTROL-M. This includes both original SAP CCMS jobs, and jobs in SAP that were created using CONTROL-M.
Before you begin

Ensure that you can see the required SAP job in CONTROL-M/EM.
To monitor SAP jobs

In CONROL-M/EM, double-click the CONTROL-M/CM for SAP job. The Job Editing form, SAP panel, is displayed in Active Job mode. Figure 6 SAP panel, Job Editing form (Active Job mode)
All fields that are set in Creating and monitoring SAP R/3 jobs on page 48 now have read-only status. Additional fields are also displayed when a job has been created and scheduled. Key fields are described in Table 12 on page 74.
Chapter 3
73
Table 12
Parameter Job Type
Additional SAP panel parameters - Active Job mode

Description This shows the nature of the SAP job. Indicated if the check box is selected. Only relevant for jobs extracted by the Extractor process.
Extracted: A SAP job extracted from SAP to CONTROL-M by the Extractor process for monitoring and managing purposes. Intercepted: A job that was intercepted by SAP, extracted to CONTROL-M by the Extractor process, activated by CONTROL-M/CM for SAP and is now being monitored in CONTROL-M. Spawned: A job that was created in SAP by a job created or monitored in CONTROL-M, extracted from SAP by the Extractor process and is now being monitored in CONTROL-M. - Parent Name: If the job type is Spawned, the name of the parent job is displayed in this field. - Parent Id: If the job type is Spawned, the SAP job count of the parent job is displayed in this field.
Notes: For jobs that were not extracted by the Extractor process, no information is displayed in any of these fields. A job can fit more than one job type criteria. For example, it can be both spawned and intercepted. If this is the case, the job type assigned the higher priority is the actual job type, and is indicated by a bold ring around the check box. For more information about priorities and job detection criteria, see Configuring and working with the Extractor Management utility on page 111. These fields are only enabled if you are using XBP 2.0 functionality. SAP Job Status Classification for the job. Displays the actual status of the job in SAP. Important: This is updated when the Job Editing form is opened. However, the status is not refreshed automatically. Note: This field is active only if you are using XBP 2.0 functionality.
For more information about monitoring jobs in CONTROL-M, see the CONTROL-M/Enterprise Manager User Guide. For information about viewing and updating job details, see the CONTROL-M/Enterprise Manager User Guide.
To cancel a SAP job

Right-click the required job, and select Kill. The job is cancelled in SAP. This action is possible as long as the job is still active in SAP
74
Data archiving jobs
NOTE
The Kill action does not work for SAP BW jobs.
To view a SAP job step list

Right-click the required job, and select View JCL/Script. The job steps are displayed.
Data archiving jobs

CONTROL-M/CM for SAP can archive information in the SAP database, using Data Archiving jobs that are created using the CONTROL-M/Desktop. A Data Archiving session is created to perform Data Archiving jobs, using the CONTROL-M group scheduling table functionality. To work with Data Archiving jobs, you must install CONTROL-M Function Modules. For more information, see Step 4 - Importing the CONTROL-M/CM for SAP utilities to the CONTROL-M Configuration Manager on page 37.
Data archiving with XBP 1.0

A typical Data Archiving session in XBP 1.0 includes a Write job and two Detect jobs.
A (Data Archiving) Write job copies data from the SAP database to archive files. A Detect job detects either Delete or Store jobs that are created in SAP during the Write job process. A Delete job reads information from an archive file, verifies that this information is the same as in the SAP database, and deletes it from the database. A Store job copies archive files to a storage system. As a Detect job discovers a Delete or Store job, a new job is created in CONTROL-M. This job runs the Delete or Store job in SAP, enabling you to monitor it from CONTROL-M. The Detect job continues to search for Delete or Store jobs, according to session specifications. It runs cyclically until all Delete or Store jobs are detected and run. For more information, see Creating a Data Archiving session on page 76.
Chapter 3
75
Data archiving
Data archiving
A typical Data Archiving session includes a Write job and two job definition templates, one for Delete jobs and another for Store jobs.
The Write job copies data from the SAP database to archive files and spawns the Delete jobs in SAP. The Write job is defined in CONTROL-M as a parent job (meaning, the Detect Spawned Jobs option is selected). The job definition template for Delete jobs is used when Delete jobs are detected as spawned by the Write job. Each Delete job spawns one Store job, so the template for Delete jobs should also be defined as a parent. Store jobs are spawned by Delete jobs in SAP. The job definition template for Store jobs is used when they are detected as spawned by Delete jobs. For more information, see Creating a Data Archiving session.
Creating a Data Archiving session

The following procedures describe how to create a Data Archiving session.
NOTE
A pre-prepared draft for a Data Archiving session can be found on the CONTROL-M/CM for SAP installation CD, in <CD_ROM>\Forms. You can use it either as an example of a typical Data Archiving session, or as a template for new Data Archiving sessions. For more information, see Sample Data Archiving session on page 20.
Before you begin

For CONTROL-M/EM 6.2.01 or earlier: Ensure that you have a job skeleton defined for CONTROL-M/CM for SAP Data Archiving jobs, as described in Creating a job skeleton for SAP jobs on page 46, and select this skeleton from the Current Skeleton list in CONTROL-M/Desktop.
To create a group scheduling table 1 For CONTROL-M/EM 6.3.01 or later, choose Edit => New Scheduling Group.
For CONTROL-M/EM 6.2.01 or earlier, choose Edit => Scheduling Group => New.
76
2 For CONTROL-M/EM 6.3.01 or later, select the SAP (group) template from the
Template list. For more information about creating a template, see Creating a template for a job definition on page 45. For CONTROL-M/EM 6.2.01, proceed directly to step 3.
3 Set the Group Editing form parameters according to your requirements. NOTE
For more information about the Group Editing form, see the CONTROL-M/ Guide.
4 For CONTROL-M/EM 6.3.01 or later, click OK to open the group scheduling table
in CONTROL-M/Desktop. For CONTROL-M/EM 6.2.01 or earlier, click Save to Draft to open the group scheduling table in CONTROL-M/Desktop. You can now create a Data Archiving job, directly into the group scheduling table and Data Archiving session.
To create a Data Archiving write job 1 For CONTROL-M/EM 6.3.01 or later, choose Edit => New Job.
2 For CONTROL-M/EM 6.3.01 or later, select the SAP Data Archiving template from
the Template list. For more information about creating a template, see Creating a template for a job definition on page 45. For CONTROL-M/EM 6.2.01, proceed directly to step 3.
NOTE
For descriptions of all panels in the Job Editing form, see Chapter 3 of the CONTROL-M/ Guide.
3 Click the SAP tab of the Job Editing form to display the SAP panel, as shown in
Figure 7.
4 For Job Mode, select Write job.
Chapter 3
77
Figure 7
SAP panel for Data Archiving, Job Editing form
5 Click Detect Spawned Jobs to open the Detect Spawned Job dialog box.
6 Select A specific job definition, and for Job Name enter the name of the Delete
template to use as a template for creating spawned jobs. Click OK to close the dialog box.
7 Define other parameters for the job, as required. For descriptions of these
parameters, see Table 13 on page 84.
8 To set additional print parameters for the job, click Print Parameters to open the
Print Parameters dialog box. The fields in the Print Parameters dialog box are described in Table 7 Add ABAP dialog box parameters on page 62.
satisfied with the data in the SAP panel. The job is added to the group scheduling table of the Data Archiving session.
78
For CONTROL-M/Desktop 6.3.01 or later, when you are satisfied with the data in the SAP panel, click one of the following:
Save: The job is added to the group scheduling table of the Data Archiving session. Save and Close: The job is added to the group scheduling table of the Data Archiving session and the job definition window will be closed Save & Order: The job is added to the group scheduling table of the Data Archiving session and can be ordered immediately. Save as Template: The job definition is saved as a template for further SAP Data Archiving job definitions.
To create the Job Definition template for Delete jobs 1 For CONTROL-M/EM 6.3.01 or later, select the SAP template from the Template
list. For more information about creating a template, see Creating a template for a job definition on page 45. Ensure that you select the regular SAP R3 template and not the SAP Data Archiving template. For CONTROL-M/EM 6.2.01, select the skeleton for CONTROL-M/CM for SAP jobs from the Current Skeleton list in CONTROL-M/Desktop. Ensure that you select a regular SAP R3 skeleton and not a SAP Data Archiving skeleton.
2 For CONTROL-M/EM 6.3.01 or later, choose Edit => New Job.

NOTE
3 Click the SAP tab of the Job Editing form to display the SAP panel. 4 For Job Mode, select Original.
Chapter 3
79
Figure 8
Job Editing form, SAP panel, Original mode
5 Click Detect Spawned Jobs to open the Detect Spawned Job dialog box.
6 Select A specific job definition, and for Job Name, enter the name of the Store
template to use as a template for creating spawned jobs. Click OK to close the dialog box
7 Define the parameters for the job definition template for Delete jobs as appropriate.
For descriptions of the parameters, see Table 13 on page 84.
satisfied with the data in the SAP panel. The job is added to the group scheduling table of the Data Archiving session.
80
To Create the Job Definition Template for Store Jobs 1 For CONTROL-M/EM 6.3.01 or later, select the SAP Data Archiving template from
the Template list. For more information about creating a template, see Creating a template for a job definition on page 45. Ensure that you select the regular SAP R3 template and not the SAP Data Archiving template. For CONTROL-M/EM 6.2.01, select the skeleton for CONTROL-M/CM for SAP Data Archiving jobs from the Current Skeleton list in CONTROL-M/Desktop. Ensure that you select a regular SAP R3 skeleton and not a SAP Data Archiving skeleton.
2 For CONTROL-M/EM 6.3.01 or later, choose Edit => New Job.

NOTE
3 Click the SAP tab of the Job Editing form to display the SAP panel.
Chapter 3
81
4 For Job Mode, select Original.
5 Define the parameters for the job definition template for Store jobs as appropriate.
For descriptions of these parameters, see Table 13 on page 84.
satisfied with the data in the SAP panel. The job is added to the group scheduling table of the Data Archiving session. For CONTROL-M/Desktop 6.3.01 or later, when you are satisfied with the data in the SAP panel, click one of the following:
NOTE
The templates for Delete and Store jobs should only be created as templates, and should not be ordered and submitted.

Configuring the environment to work with Data Archiving Sessions
Subject Defining a group scheduling Table for Data Archiving Defining other Job Editing form parameters.
Location For information about defining a group scheduling table for Data Archiving, see CONTROL-M/ Guide. For more information about all CONTROL-M job parameters, see the CONTROL-M Job Parameter and Variable Reference Guide.
Configuring the Environment For more information, see Configuring the environment to to Work with Data Archiving work with Data Archiving Sessions. Sessions in XBP 2.0
Configuring the environment to work with Data Archiving Sessions

The system environment must be properly configured to use Data Archiving.
1 Ensure that the Job Interception and Spawned Jobs functionalities are activated in
the relevant SAP system. See Activating Interception and Parent/Child functions in SAP on page 113 and the relevant SAP documentation.
2 Use the Extractor Management utility to set the following priorities for the
Extractor process:

Spawned jobs - first priority Intercepted jobs - second priority
Setting first priority for spawned jobs in the Extractor process ensures that Delete jobs and Store jobs are created (ordered) according to the template definition of their parent jobs, and NOT according to CONTROL-M interception rules. For more information, see To set job type priorities from the CONTROL-M Configuration Manager on page 114.
3 Use the SAP Interception Criteria panel of the Extractor Management utility to
configure your SAP system to intercept Data Archiving Delete jobs and Store jobs. This can be done using a rule that is similar to the following:
EXAMPLE
JOB NAME: ARV_EXAMPLE_DEL* USER NAME: CONTROLM
For more information on extraction management, see Configuring and working with the Extractor Management utility on page 111.
Chapter 3
83
SAP panel parameters for data archiving

The SAP panel parameters for Data Archiving are described in Table 13 . For further information about these parameters, see the CONTROL-M Job Parameter and Variable Reference Guide. Table 13
Parameter Account
Data-archiving SAP panel parameters (part 1 of 5)

Definition Account name. Mandatory. Uppercase only, no blank spaces permitted. The account is a profile. The remaining parameters are predefined according to the account, when the account is created. Mapped to the CONTROL-M/EM Owner parameter. Clicking the account Load button displays a list of accounts that comply with the generic name you enter. The asterisk * can be used as a wildcard to filter account names. For information about defining an account, see Account Management Utility on page 98.
Archiving Object
Archiving object in SAP. Mandatory. Free text string. Click Load to generate and display a list of all archiving objects. The asterisk * can be used as a wildcard. Note: The Load button only works if you are using Extended functionality.
Check Sessions
Only available for Write jobs. Enables the user to check if an incomplete archiving session exists for a specific archiving object. Note: An incomplete archiving session is one for which not all Delete jobs ended successfully. Valid values are: Selected = Perform a check Cleared = Do not perform a check (Default) If an incomplete archiving session is found, a message is displayed, and a Data Archiving write job is not created.
84
Table 13
Parameter

Definition Only available for Write jobs. Enables the user to check if a Write job already exists with the specific variant for the archiving object defined for this job. Valid values are:

Check Variant
Selected = Perform a check Cleared = Do not perform a check (Default)
If such a Write job is found, a message is displayed, and a new Write job is not created. Copy Spool To Name and path of the file to which the spool should be copied. Optional. Case sensitive, no blank spaces permitted. Note: If *SYSOUT is set, the spool is copied to the same location as the job output. (See Sysout Handling in the CONTROL-M Job Parameter and Variable Reference Guide). Detect Spawned Jobs Only available for Write jobs. A spawned job is a job created by another (parent) job, and monitored by CONTROL-M. This parameter indicates whether to detect and monitor jobs that were spawned by the current SAP job. The following options are available:
No Detection needed: Do not detect spawned jobs of the current job. Detect and Create According to: Parent (current) job definition: Detect spawned jobs of the current job and extract these jobs to CONTROL-M, with identical properties to the parent job. A specific job definition: A field is displayed, in which you enter a specific SAP-type job name. Detected spawned jobs of the current job are extracted to CONTROL-M with identical properties to the selected (not the current) job. Important: The selected job must exist in the same scheduling table as the current job.
For more information, see Initiating a mass parallel process (detecting spawned jobs) on page 127
Chapter 3
85
Table 13
Parameter Job Class

Definition Job submission priority (in SAP). Mandatory for Write job mode only. Disabled for both Detect Delete and Detect Store job mode values. Valid values are:

A - most urgent B - urgent C - least urgent (Default)
Note: The A and B values only work if you use XBP 2.0 functionality or the Extended functionality in an XBP 1.0 system with the CONTROL-M Function Modules installed. Job Mode Determines the task that the job performs. Mandatory. Valid values are:

Write: Creates and runs a Data Archiving write job. Detect Delete: Detects a Data Archiving delete job created in SAP (only used in data archiving with XBP 1.0). Detect Store: Detects a Data Archiving store job created in SAP (only used in data archiving with XBP 1.0).
Job Name
Job name to be monitored or submitted. Mandatory. Mapped to the CONTROL-M/EM Job Name parameter.
Print Parameters Session Number
See Table 7 Add ABAP dialog box parameters on page 62. Available for Detect jobs only. Indicates the archiving session number in SAP. Click Load to generate and display a complete list of session numbers. This parameter must be set when either of the following occur: The Write job was not created by CONTROL-M The Write job and the Detect job are not part of the same group scheduling table. This parameter should not be set if the Write job and the Detect job are part of the same group scheduling table.
86
Table 13
Parameter

Definition Specifies whether the job should run with the ASAP option or immediately. Check box format. Valid values are:

Submit Job with ASAP Option
Selected - submit with ASAP option Cleared - start immediately (Default)
When this parameter is selected the job runs as soon as a background work process is available for it in SAP. If the job cannot start immediately, it is transformed in SAP into a time-based job. If this parameter is cleared, the job either runs immediately, or fails if there are no work processes available to run it. Target Server Application Server on which the job runs. Optional. Case sensitive, no blank spaces permitted. Click Load to generate and display a complete list of available application servers. If this parameter is left unset, the SAP system determines which application server will execute the job. This is the normal procedure recommended by SAP, because the system can then carry out its own load balancing. You should only select the target machine if that server has particular resources necessary for the job processing. Note: If manually set, the following (full) format must be used: hostname_SYSID_sysnumber
Chapter 3
87
Business Information Warehouse jobs
Table 13
Parameter Variant

Definition Variant name. Mandatory. Only enabled if the Archiving Object parameter is set. Only available for Write jobs. Click Load to generate and display a complete list of variants available for the selected Archiving Object. Uppercase only, blank spaces permitted, special characters are permitted according to SAP guidelines. (For more information, refer to the SAP documentation). When a variant is set for an Archiving Object, the following buttons are enabled:
Copy. Enables the creation of a new variant based on the properties of an existing variant. The new variant is created as soon as you confirm its name. Show. Displays the variant values in a separate window (see Figure 3 on page 67). Change. Enables you to modify the values of the various variant parameters (see Figure 3 on page 67). To apply these parameter values click OK. To keep the variants original parameter values, click Undo Changes. Note: The changes in the values of the variant parameters are only performed during job run time.
Note: The Copy, Show, and Change buttons only work if you use XBP 2.0 functionality or the Extended functionality in an XBP 1.0 system with CONTROL-M Function Modules installed.
Business Information Warehouse jobs

The following section describes how to create, monitor, and manage SAP-BW jobs using CONTROL-M. For an introductory overview, see CONTROL-M solution for Business Information Warehouse on page 17.
Creating a Business Information Warehouse job

The following procedures describe how to create a Business Information Warehouse (SAP-BW) Job in CONTROL-M.
88
Before you begin
For CONTROL-M/EM 6.2.01 or earlier: Ensure that you have a SAP Business Information Warehouse skeleton defined, as described in Creating a job skeleton for SAP jobs on page 46, and select this skeleton from the Current Skeleton list in CONTROL-M/Desktop. Ensure that the required InfoPackages (I/P) or Process Chains (P/C) are already defined in the SAP BW system.
NOTE
When defining a P/C in the SAP BW system, ensure that you choose Start Using Meta Chain or API as the start condition for the trigger process (Start Process) of the P/C. If you do not do this, the job fails in CONTROL-M. You can access this parameter from the SAP transaction RSPC; right-click the Trigger process and select Maintain Variant.
To create a SAP BW job 1 For CONTROL-M/EM 6.3.01 or later, choose Edit => New Job.
2 For CONTROL-M/EM 6.3.01 or later, select the SAP Business Information

Warehouse template from the Template list. For more information about creating a template, see Creating a template for a job definition on page 45. For CONTROL-M/EM 6.2.01, proceed directly to step 3.
NOTE
3 Click the SAP tab of the Job Editing form to display the SAP-BW panel.
The fields in the SAP panel are described in Table 14 on page 92.
4 Choose the required SAP BW/Business Process Type to enable the appropriate
parameters. There are two options:

InfoPackage (see Figure 9, below) Process Chain (see Figure 10, below)
Chapter 3
89
Figure 9
SAP panel for BW - InfoPackage, Job Editing form
Figure 10
SAP panel for BW - Process Chain, Job Editing form
5 Select the required InfoPackage or Process Chain.
InfoPackage - Enter the specific InfoPackage information, or click Load to generate a list of available InfoPackages from which you can make a selection. Process Chain - Enter the specific Process Chain information, or click Load to
generate a list of available Process Chains.
6 Set additional parameters as required. 7 For CONTROL-M/Desktop 620 or earlier, click Save to Draft when you are
satisfied with the data in the SAP panel. The job is added to the scheduling table of the Business Information Warehouse.
90
SAP panel parameters for SAP-BW jobs
Save: The job is added to the current Business Information Warehouse Scheduling Table. Save and Close: The job is added to the current Business Information Warehouse Scheduling Table and job definition window will be closed Save & Order: The job is added to the current Business Information Warehouse Scheduling Table and can be ordered immediately. Save as Template: The job definition is saved as a template for further SAP Business Information Warehouse job definitions.
8 The job is added to the scheduling table of the Business Information Warehouse. Where to go from here
Subject Defining other Job Editing form parameters. Location For more information about all CONTROL-M job parameters, see the CONTROL-M Job Parameter and Variable Reference Guide.

The SAP panel parameters for BW jobs are described in Table 14 . For further information about these parameters, see the CONTROL-M Job Parameter and Variable Reference Guide.
NOTE
The asterisk can be used as a wildcard to filter parameters such as account names and Job names. For example, entering *DE* in the Account field generates a list of all accounts that contain the DE string.
Chapter 3
91
Table 14
Parameter Account
SAP-BW job panel parameters (part 1 of 2)

Definition Account name. Mandatory. Uppercase only, no blank spaces permitted. The account is a profile. The remaining parameters are predefined according to the account, when the account is created. Mapped to the CONTROL-M/EM Owner parameter. Clicking the account Load button displays a list of accounts that comply with the generic name you enter. The asterisk * can be used as a wildcard to filter account names. For information about defining an account, see Accessing the Account Management utility on page 98.
Background Job Name
Valid when InfoPackage Business Process Type is selected. Name of the InfoPackage's background job name. Optional. The BI_BTCH prefix is preset and cannot be changed. If no value is entered, SAP-BW generates a name for the background job.
CONTROL-M Job Name
The name under which the job is submitted in CONTROL-M. Mandatory. Mapped to the CONTROL-M/EM Job Name parameter.
InfoPackage Description
Valid when InfoPackage Business Process Type is selected. InfoPackage Description. Mandatory. Free text Can be used as a filter before loading a list of InfoPackages, or you can enter a specific InfoPackage name. Tip: Before clicking Load, narrow the search parameters by entering at least one character in the field. The asterisk * can be used as a wildcard. Note: The Load button generates data for both this parameter and InfoPackage Tech. Name.
92
Table 14
Parameter
SAP-BW job panel parameters (part 2 of 2)

Definition Valid when InfoPackage Business Process Type is selected. InfoPackage Technical Name, a unique BW-generated InfoPackage ID. Mandatory. Uppercase only, no blank spaces permitted. The value of this parameter can be defined by

InfoPackage Tech. Name
entering a specific InfoPackage technical name clicking Load and selecting the required InfoPackage
Note: The Load button generates data for both this parameter and InfoPackage Description. Process Chain Description Valid when Process Chain Business Process Type is selected. Optional. Free text. Describes a Process Chain. Can be used as a filter before loading a list of Process Chains, or you can enter a specific Process Chain name. Tip: Before clicking Load, narrow the search parameters by entering at least one character in the field. The asterisk * can be used as a wildcard. Note: The Load button generates data according to data set in this parameter and in Process Chain ID. Process Chain ID Valid when Process Chain Business Process Type is selected. Mandatory. Uppercase only, no blank spaces permitted. A unique BW-generated ID of a Process Chain. Can be used as a filter before loading a list of Process Chains, or you can enter a specific Process Chain name. Tip: Before clicking Load, narrow the search parameters by entering at least one character in the field. The asterisk * can be used as a wildcard. Note: The Load button generates data according to data set in this parameter and in Process Chain Description. SAP-BW/Business Process Type Determines the task that the job performs. Mandatory. Valid values are:

Process Chain (Default) InfoPackage
Note: Parameters are described further on in this table.
Chapter 3
93
Monitoring and managing Business Information Warehouse jobs

You can handle SAP-BW jobs using CONTROL-M/CM for SAP. CONTROL-M/CM for SAP jobs monitor and manage SAP-BW Business Processes (InfoPackages or Process Chains) that were pre-defined in a SAP-BW system.
Before you begin

Ensure that you can see the required SAP-BW job in CONTROL-M/EM.
To Monitor SAP-BW Jobs

Double-click the SAP-BW job to open the Job Editing form in CONTROL-M/EM, in Active Job mode. Figure 11 SAP-BW panel - InfoPackage (Active Job mode)
All fields that were set in Creating a Business Information Warehouse job on page 88 now have read-only status. Additional fields are also displayed. These are described in Table 15 on page 95. The parameters described in Table 15 are available when a job is created and scheduled, and can be seen in the Job Editing form, in CONTROL-M/EM.
94
Table 15
Parameter
Additional SAP-BW panel parameters - Active Job Mode

Description A BW-generated unique ID for the InfoPackage's running session. The InfoPackage's background job count. A BW-generated unique ID for the Process Chain running session. If a job fails, select an option to indicate how the Process Chain should be rerun. Valid values are:

Additional InfoPackage Parameters InfoPackage RNR Background Job Count Process Chain Log ID Rerun options
Additional Process Chain Parameters
Restart from point of failure (Default) Rerun from start
Note: Only available while job is in Hold status.
For more information about monitoring jobs in CONTROL-M, see the CONTROL-M/Enterprise Manager User Guide.
Interrupting SAP-BW Jobs

To remove your process chain from the schedule (interrupt), run the request utility (ctmr3req) with PC_STOP_SCHEDULE action. The job is removed from the schedule, and you receive an alert from the EM alert mechanism. The job stays active in CONTROL-M until it is finished in SAP. For more information, see Interrupts Removing a process chain from schedule on page 149.
Chapter 3
95
96
Chapter
Administrator tasks
This chapter describes tasks that can be performed using the CONTROL-M/CM for SAP utilities. These are described under the following topics:

Account Management Utility on page 98 Configuring general parameters on page 107 Configuring and working with the Extractor Management utility on page 111 SAP Event Based Scheduling on page 131 Import SAP Calendar utility on page 137 Requesting SAP actions on page 140 Converting CONTROL-M Option for R3 account definitions on page 150 Converting CONTROL-M Option for R/3 jobs on page 152
NOTE
CONTROL-M/CM for SAP functionality using CONTROL-M Configuration Manager is available to you, only if you are using the following:

CONTROL-M/EM 6.3.01 fix pack 4 or later CONTROL-M/Server 6.3.01 fix pack 2 or later CONTROL-M/Agent 6.3.01 fix pack 2 or later
The utilities that are available are:

Account Management Configuration Management Extractor Management Import SAP Calendar
Note: The utilities listed above can also be accessed from your local computer, as previously, with the exception of the Import SAP Calendar utility. The functionality of utilities that can be accessed from both the CONTROL-M Configuration Manager and the Java GUI is the same, except if specified otherwise. Screenshots displayed in this chapter show the utilities as accessed from the CONTROL-M Configuration Manager.
Chapter 4
Administrator tasks
97
Account Management Utility
Account Management Utility

This section describes how to create, modify and delete CONTROL-M/CM for SAP accounts. You can use the Account utility to define user accounts that are authorized to work with the SAP server. An account is a set of parameters that must be defined in order to connect to the SAP system, using a specific SAP server or specific Logon Group (see step 3 on page 104). The following topics are included: Accessing Account Management from the CONTROL-M Configuration Manager on page 98 Accessing Account Management from the Java GUI on page 98
NOTE
Before operating CONTROL-M/CM for SAP for the first time, you must define at least one account.
Accessing the Account Management utility

Accessing Account Management from the CONTROL-M Configuration Manager
To manage CONTROL-M/CM for SAP accounts from within the CONTROL-M Configuration Manager, navigate to the required CONTROL-M/Agent, right-click the specific CONTROL-M/CM for SAP, and select Account Management.
Accessing Account Management from the Java GUI
On Unix, ensure that you are logged in as the CONTROL-M/Agent user, and that the Unix DISPLAY environment variable is set correctly. Run ctmag, select the SAP tab, and select Account management. On Microsoft Windows, go to Start => Programs => CONTROL-M/Agent <agent>. Select the SAP tab, and select Account Management to open the CONTROL-M/CM for SAP Account Management window.
For more information about account management, see Account Management Utility on page 98.
98
The Account Management window is displayed (see Figure 12). Figure 12 Accounts Management window (CONTROL-M Configuration Manager)
You can use the buttons in the toolbar to perform the following actions:

Add a new account Update an existing account Copy an existing account to create a new one Delete an existing account Test the validity of an account
You can also update accounts by double-clicking a line in the Accounts Management window. The Account details window is displayed (see Figure 13). For a detailed description of the parameters in the Accounts Management and the Accounts Details windows, see Table 16 on page 100.
Chapter 4
Administrator tasks
99
Figure 13
Update Account options (CONTROL-M Configuration Manager)
Table 16
Parameter
CONTROL-M/CM for SAP Account Parameters (Part 1 of 3)

Description Name of the CONTROL-M/CM for SAP account. Free text string. Maximum length: 30 characters. Uppercase only. No blank spaces permitted.
Account Name
Application Server hostname System Number
Host name of the computer running the SAP Application Server. This parameter is disabled if Use Logon Group is selected. The number of the SAP instance, for example: 03 Format: Two-digit. This parameter is disabled if Use Logon Group is selected. SAP client, for example: 100 Format: Three-digit.
Client
Login
SAP login user name. See Table 3 on page 39 for details about required authorizations.
Password Confirm Password Language
password for the SAP login user. confirmation of the password SAP language indication. Default: English Note: To use the CJK functionality, one of the CJK languages must be selected.
100
Table 16
Parameter

Description Defines the SAP XBP interface version installed on the SAP server. Valid values are:

XBP Version
XBP1.0 XBP2.0 (Default)
To check if XBP 2.0 exists in your system, look in the SAP transaction SA38 for the ABAP program INITXBP2. If this is there, XBP 2.0 exists in your system. SAP Application Version Valid values are:

R/3 (Default) BW 2.x BW 3.x or later
System ID
Three alpha-numeric characters that represent the SAP System ID. This parameter is enabled only if Use Logon Group is selected. Host name of the computer on which the SAP System Message Server is running. This parameter is enabled only if Use Logon Group is selected. For Java GUI only. Checkbox. See Message Server Hostname parameter. The Group name as defined in the SAP SMLG transaction. This parameter is enabled only if Use Logon Group is selected. Specifies how many times the program should try to reconnect to the SAP system after either

Message Server Hostname
Logon Group Group
RFC Max Retry
a connection failure a Function Call error
Valid values are: 1 - 20. Default: 10
Chapter 4 Administrator tasks
101
Table 16
Parameter

Description Specifies the number of seconds the program should wait, after a Function Call error is encountered, before trying to reconnect to the SAP system. Valid values are: 1 - 120. Default: 5
RFC Retry Interval
Use Extended
Specifies whether the extended functionality of CONTROL-M/CM for SAP should be used. Valid values are:

Cleared = No (Default) Selected = Yes
Note: If you select this option, the CONTROL-M Function Modules must be installed on the SAP server on which you are working. For more information about extended functionality, see Step 5 - CONTROL-M function modules on page 38.
Adding a new account

Use this procedure to define a new CONTROL-M/CM for SAP account.
To add an account from within the CONTROL-M Configuration Manager

If you add an account from within the CONTROL-M Configuration Manager, an automatic Wizard guides you through the process. Specify the account parameters as required. These parameters are described in Table 16 on page 100. Figure 14 displays the first screen of the Wizard. The manner in which the Wizard runs is dependent on your choice of Logon Type, and the parameters are displayed accordingly. At the end of the Wizard, a summary screen is displayed, providing a Check Account option, for you to verify your account definition.
102
Figure 14
Account Adding Wizard (first screen)
To add an account using the Java GUI, follow the procedure below.
To add an account using the Java GUI 1 Access the account utility, as described in Accessing the Account Management
utility on page 98. The Account Management utility is displayed.
2 Click Add to open the New Account dialog box.
103
Figure 15
New Account dialog box
For a detailed description of the parameters in the Accounts Management utility and the New Account dialog box, see Table 16 on page 100.
3 Enter account-configuration parameters. The account can be defined either:

as a regular connection (direct) or by using logon groups
4 If your account uses a logon group connection, select Use Logon Group.
If you are entering a direct-connection account, ensure that Use Logon Group is not selected. In either case, specify the appropriate information for all available account configuration parameters.
NOTE
All enabled parameters are mandatory.
104
5 If your account uses a direct connection, proceed directly to step 6. If you are using
logon groups, you must add a new line to the services file on the computer on which CONTROL-M/Agent is running, as follows: sapms<SID> 36<SYSNR>/tcp
SID represents the System ID, and SYSNR represents the System number of the computer on which the SAP Message Server is running.
EXAMPLE
sapmsDEV 3619/tcp
The services file can be found in the following folders:

On Unix: /etc/ On Windows: <system drive>:\WINNT\system32\drivers\etc On Windows 2003 or later: <system drive>:\Windows\system32\drivers\etc
This should be done for each System ID for which you defined a logon group. For more information about Logon Groups and load balancing, go to the BMC Software Customer Support web site at http://www.bmc.com/support_home ==> Resolution Knowledge Database and see Resolution 192593.
6 Click OK to save the new account. The New Account dialog box closes, and the
new account information is added to the CONTROL-M/CM for SAP Account Management utility window.
NOTE
If you just defined an account for the first time since installing CONTROL-M/CM for SAP, the Copy, Edit, and Remove buttons in this window are now enabled. You can use these buttons to add accounts, or edit or delete existing accounts.
7 Click Save to save the Accounts list. NOTE

When deleting an existing account you must ensure that all Rules defined for this account in the Extractor Management utility are removed. You should also ensure that you do not use ctmextract with Rules for deleted accounts.
105
To check an account configuration 1 Select the required account in the CONTROL-M/CM for SAP Account
Management window.
2 Click Check Account. The Account utility checks whether a connection can be
established with the SAP server, using the specific account parameters, and displays a message, according to the result of the check.
To configure an Administrator password

Use the following procedure to configure an Administrator password. This password prevents unauthorized users from using or modifying the Account utility.
WARNING
This functionality is only available when using this utility in the Java GUI.
1 Click Administrator Password in the CONTROL-M/CM for SAP Account

Management window.
2 Choose Add/Change Administrator Password, and click OK. NOTE

Select Delete if you want to delete an Administrator Password.
3 Enter and confirm the password as required, and click OK.

After an Administrator password is set, the CONTROL-M/CM for SAP Account utility cannot be activated without entering this password.
NOTE
The Administrator password is also used to open the Extractor Management utility. For more information, see Configuring and working with the Extractor Management utility on page 111.
106
Configuring general parameters
CONTROL-M/CM for SAP support for CJK Languages

CONTROL-M/CM for SAP 6.3.01 now supports CJK when viewing the Sysout file.
Configuring CONTROL-M/CM for SAP for CJK Support

To enable CJK support, the following criteria must be fulfilled:
The Foreign Language Support parameter in CONTROL-M/Agent must have CJK specified. One of the CJK languages in the Account Management utility must be selected.
NOTE
CJK languages must also be installed on the SAP system itself.
For more information regarding the use of CJK functionality, see Add ABAP dialog box parameters on page 61.
CONTROL-M/EM User privileges required for the Account Management utility:

User Privilege BROWSE UPDATE FULL Ability View already defined accounts Update an existing account Test Account Add new account Delete account
Configuring general parameters

This section describes how to access and use the Configuration Management utility.
Accessing the Configuration Management utility

The following topics are included: Accessing Configuration Management from the CONTROL-M Configuration Manager on page 108
Chapter 4 Administrator tasks 107
Configuring parameters
Accessing Configuration Management from the Java GUI on page 108
Accessing Configuration Management from the CONTROL-M Configuration Manager

To configure CONTROL-M/CM for SAP parameters from within the CONTROL-M Configuration Manager, navigate to the required CONTROL-M/Agent, right-click the specific CONTROL-M/CM for SAP, and select Configuration Management. The Configuration Management utility is displayed (see Figure 16):
Accessing Configuration Management from the Java GUI
On Unix, ensure that you are logged in as the CONTROL-M/Agent user, and that the Unix DISPLAY environment variable is set correctly. Run ctmag, select the SAP tab, and select Configuration Management. On Microsoft Windows, go to Start => Programs => CONTROL-M/Agent <agent>. Select the SAP tab, and select Configuration Management to open the CONTROL-M/CM for SAP Configuration Management window.
The CONTROL-M/CM for SAP configuration utility is used to change the default operating parameters of CONTROL-M/CM for SAP.
To change the CONTROL-M/CM for SAP operating parameters 1 Access the Configuration utility, (see Accessing the Configuration Management
utility on page 107). The Configuration Management window is displayed (see Figure 16).
108
The Configuration Management utility parameters are described in Table 17 Figure 16 Configuration management window
Table 17
Parameter
Configuration Management utility parameters (Part 1 of 3)

Description Sets the audit level for the current session. Valid values are:

Audit Level
0: No additional audit level information to be added to the SAP server 1: Add audit level 1 information to the SAP server 2: Add audit level 2 information to the SAP server 3: Add audit level 3 information to the SAP server
Default: 0 Note: Additional audit level information can be viewed in the RZ15 SAP transaction. Max List Entries Max Wait for SAP Recovery Specifies the maximum number of rows to be produced for a Load list. Valid values are: 1-1000. Default: 250 The Max Wait for SAP Recovery (minutes) parameter enables you to maintain an Executing status for CONTROL-M/CM for SAP jobs running in a SAP system even when the connection to the SAP system is lost. Range: 0-1500 Default: 0 (minutes). An alert is sent to CONTROL-M/EM when the connection to SAP is lost or reconnected. Note: If the connection is still lost after the set number of minutes has elapsed, the job fails and is assigned a status of Disappeared.
109
Table 17
Parameter

Description Indicates which job should be copied if Copy mode is set without a JOBCOUNT value. Valid values are:

Run Copy Mode
LAST_SCHEDULED: Last job with scheduled status LAST: Last job (any status) FIRST_SCHEDULED: First job with scheduled status FIRST: First job (any status)
Default: LAST_SCHEDULED Run Org Mode Indicates which job should be released if Original mode is set without a JOBCOUNT value. Valid values are:

LAST_SCHEDULED: Last job with scheduled status FIRST_SCHEDULED: First job with scheduled status
Default: LAST_SCHEDULED Sysout file name Name of the Sysout file. You can assign a specific prefix to this file name. Valid values are:

JOBNAME: as defined in the CONTROL-M/EM job definition MEMNAME: as defined in the CONTROL-M/EM job definition None (default)
Mixed Case Job Name Allow mixed case job name for External Mode jobs. (For job (External Jobs) monitoring purposes only.) Valid values are:

Cleared = No (Upper case only) (Default) Selected = Yes (Mixed case permitted)
Note: When this parameter is cleared, searches only find job names with all uppercase characters, regardless of how information was entered. When this parameter is selected, all searches are run exactly specific to the character information entered. Applicable for the External job mode only. Mixed Case Job Name Allow mixed case job name for other CONTROL-M jobs. (For (Other CTM Jobs) creating or submitting jobs.) Valid values are:

Cleared = No (Upper case only) (Default) Selected = Yes (Mixed case permitted)
Note: When this parameter is cleared, searches only find job names with all uppercase characters, regardless of how information was entered. When this parameter is selected, all searches are run exactly specific to the character information entered. Applicable for Create, Copy, and Original job modes.
110
Configuring and working with the Extractor Management utility
Table 17
Parameter

Description Sets the maximum size of the spool log that CONTROL-M/CM for SAP can read, in MB. Valid values: 0 - 1000. Options: Unlimited maximum size (default) Set Maximum size
Log Spool Maximum size
2 Modify the Configuration parameters, if necessary. 3 Click OK to save your choices. NOTE
If you are working in the Java GUI on Microsoft Windows, you must restart CONTROL-M/Agent after modifying any CONTROL-M/CM for SAP operating parameters, in order for the changes to take effect.
CONTROL-M/EM User privileges required for the Configuration Management utility:

User Privilege BROWSE UPDATE Ability View already defined configuration parameters Update configuration parameters

The Extractor Management utility mechanism

intercepts and controls SAP CCMS jobs detects running SAP CCMS jobs detects spawned jobs
Each of these functions is a separate procedure. All three are managed by the Extractor Management utility, to coordinate these functions to work simultaneously and without conflicts.
111
These functions, plus the various options for general configuration of the Extractor Management utility, can be configured from the Extractor Management utility. When the Extractor process is running, you can also use another function, that enables you to schedule jobs, and to raise conditions in CONTROL-M, according to SAP events. For more information, see SAP Event Based Scheduling on page 131. If you are working in a Unix environment, ensure that you are logged in as the CONTROL-M/Agent user.
The following topics are included: Configuring the Extractor Management utility, as described in General configuration of the Extractor Management utility on page 114 SAP Interception Criteria and CTM Interception Rules, as described in Job interception and control with the Extractor Management utility on page 115 Extraction Rules, as described in Extracting and monitoring SAP CCMS jobs on page 121
The configuration for detecting spawned jobs is performed separately, using the Job Editing form. For more information, see Initiating a mass parallel process (detecting spawned jobs) on page 127.
NOTE
The Extractor Management utility uses the CONTROL-M ctmorder utility to create jobs in CONTROL-M. Therefore, you may need to adjust the security settings in CONTROL-M/Server.
CONTROL-M job confirmation in SAP

Each SAP job that is submitted in CONTROL-M, regardless of whether it was created or copied by CONTROL-M/CM for SAP, or whether it was extracted or intercepted, or handled by the SAP Based Event Scheduling utility is marked in SAP as Confirmed. This procedure enables the Extractor process to work cyclically according to predefined rules, so that only new jobs, that have not yet been submitted in CONTROL-M, are created in CONTROL-M, and duplication is prevented.
112
Accessing the Extractor Management utility
Activating Interception and Parent/Child functions in SAP

The following functionalities must be enabled in SAP before using them with the CONTROL-M Extractor Management utility.

Interception of SAP jobs Detection of spawned jobs (Parent/Child functionality)
To activate these functions, run the INITXBP2 ABAP program in your SAP system and switch on the required actions.
Accessing the Extractor Management utility

Accessing Extractor Management from the CONTROL-M Configuration Manager
To configure CONTROL-M/CM for SAP parameters from within the CONTROL-M Configuration Manager, navigate to the required CONTROL-M/Agent, right-click the specific CONTROL-M/CM for SAP, and select Extractor Management. The Extractor Management utility is displayed.
Accessing the Extractor Management utility from the Java GUI
On Unix, ensure that you are logged in as the CONTROL-M/Agent user, and that the Unix DISPLAY environment variable is set correctly. Run ctmag, select the SAP tab, and select Extractor Management. On Microsoft Windows, go to Start => Programs => CONTROL-M/Agent <agent>. Select the SAP tab, and select Extractor Management to open the CONTROL-M/CM for SAP Extractor Management window.
NOTE
If you defined an Administrator password for the Account Management utility, you are prompted to enter it now. (See To configure an Administrator password on page 106.)
113
General configuration of the Extractor Management utility
General configuration of the Extractor Management utility

The Extractor Management utility enables you to set priorities for job types to be detected in SAP. This is because SAP jobs can be identified with more than one criterion.
EXAMPLE
A job could be a spawned job and fulfill interception criteria.
However, CONTROL-M can only create a job with one job type, and, therefore, you must set job type priorities. This is to indicate to the Extractor Management utility how a job should be handled when it matches more than one rule. You must ensure that potential rule overlapping is avoided wherever possible, or handled if necessary.
WARNING
You should not use more than one Extractor Management utility on the same system and client, since this may cause unexpected results. If you have two accounts configured to work with the same system and client (for a different user), you must ensure that no more than one of them is configured to work with the Extractor.
NOTE
Extracted jobs cannot have a higher priority than Intercepted or Spawned jobs.
To set job type priorities from the CONTROL-M Configuration Manager 1 Access the Extractor Management Utility, (see Accessing the Extractor
Management utility on page 113). The Extractor Management window is displayed.
2 In the General Configuration section, at the top of the window, select the priority
from the list for each job type field. You can set first, second, or third priority to a job type, and you can also select not to have a job type detected.
NOTE
If Intercepted Jobs is assigned a priority, you must ensure that at least one CTM Interception Rule is selected, as described on page 117.
114
Job interception and control with the Extractor Management utility
3 Select the Activity Log check box, to have a log created and saved in the
CONTROL-M/Agent proclog directory. This log has the following name structure: xt_log_<YYMMDD>.
4 In the Interval Time field, enter the required number of seconds between loops
cycles of the Extractor.
5 Click Apply. To set job type priorities from the Java GUI 1 Access the Extractor Management Utility, (see Accessing the Extractor
Management utility on page 113).
2 The Extractor Management window is displayed, overlaid with the Select SAP
Account dialog box. Select the required SAP Account.
3 In the Extractor Management window, select the priority for each job type from the
dropdown list. You can set first, second, or third priority to a job type. You can also select not to have a job type detected.
NOTE
If Intercepted Jobs is assigned a priority, you must ensure that at least one CTM Interception Rule is selected, as described on page 117.
4 Select the Activity Log check box, to have a log created and saved in the
CONTROL-M/Agent proclog directory. This log has the following name structure: xt_log_<YYMMDD>.
5 In the Interval Time field, enter the required number of seconds between loops
cycles of the Xtractor.
6 Click Save.

Job interception and control is a two-stage process. You set all job interception criteria using the Extractor Management utility. Stage 1: Which jobs should be intercepted by SAP? You must set rules to determine which jobs in SAP should be intercepted.
115
An intercepted job is a job created in SAP, that fulfills the interception criteria as set by the Extractor Management utility. Once intercepted by SAP, these jobs are put on hold in Scheduled status, until they are released by CONTROL-M. Stage 2: How should the Extractor Management utility handle these jobs? You must define sets of rules to be applied to these intercepted jobs. These rules are constructed according to Job Names and User Names. For each rule, an action must be set. These actions indicate how the Extractor should handle these jobs.
NOTE
All intercepted jobs must be processed by CONTROL-M to avoid jobs being stuck in Scheduled status forever.
Before you begin
Ensure that the Interception function is enabled in your SAP system (see Activating Interception and Parent/Child functions in SAP on page 113). Assign a priority to Intercepted jobs in the Extractor General Configuration tab (see General configuration of the Extractor Management utility on page 114). Activate the Extractor Management utility (see Activating the Extractor Management utility on page 130).
To define SAP interception criteria from within the CONTROL-M Configuration Manager 1 Access the Extractor Management utility (see Accessing the Extractor
Management utility on page 113). The Extractor Management utility window is displayed .
2 Select an account from the drop-down list. The tabs section is now enabled. 3 Select the SAP Interception Criteria tab. 4 Click Load to download all available SAP interception criteria from the SAP
server.
5 Select whether to Add, Edit, Copy or Delete any of the downloaded SAP
interception criteria.
6 Click Apply and select the CTM Interception Rules tab.
116
7 Click Add (or Edit, Copy or Delete as required) to display a dialog box similar to
the one shown in Figure 17. The parameters in this dialog box are described in Table 18. Figure 17 Add/Update CONTROL-M Interception Rule
8 Click OK. The data is saved in the Extractor Management utility, but no
information is passed to the Extractor process until you click Apply. The Copy, Edit, and Remove buttons are now enabled.
9 When you are satisfied that all criteria in the CTM Interception Rules panel are set
according to your requirements, click Apply.
NOTE
All criteria in this tab is representative of the corresponding selected account. Changing the account will alter all previously defined criteria.
WARNING
Carefully consider how you set Job Name and User Name criteria. Anything too general (for example, entering * in both fields), could cause system or other user jobs to be intercepted. Additionally, you should ensure that you have no more than one account that uses Interception rules using the same system and client.
117
To define SAP interception criteria from the Java GUI 1 Access the Extractor Management utility (see Accessing the Extractor
Management utility on page 113). The Extractor Management utility window is displayed .
2 The Extractor Management window is displayed, overlaid with the Select SAP
Account dialog box.
NOTE
The Change Account button can be used at any time to open the Select SAP Account dialog box and configure a different account.
Click Load to load the Interception Criteria table from SAP. The Add, Copy, Edit, and Remove buttons are now enabled.
3 To add new Interception criteria, click Add. 4 Set the Job Name criteria (for example BTC_*) and the User criteria (for example,
DEB*), and click OK. The * symbol can be used as a wildcard filter for both
parameters.
5 When you are satisfied that all criteria in the SAP Interception Criteria panel are set
according to your requirements, click Save. Information is sent to SAP, and all jobs that match the Interception Criteria are intercepted by SAP.
WARNING
Carefully consider how you set Job Name and User Name criteria. Anything too general (for example, entering * in both fields), could cause system or other user jobs to be intercepted. Additionally, you should ensure that you have no more than one account that uses Interception rules using the same system and client.
6 Click the CTM Interception Rules tab, and click Add to display the following dialog
box:
7 Set the parameters, as described in Table 18.

8 Click OK. The data is saved in the Extractor Management utility, but no
information is passed to the Extractor process until you click Save. The Copy, Edit, and Remove buttons are now enabled.
9 When you are satisfied that all criteria in the CTM Interception Rules panel are set
according to your requirements, click Save. Table 18
Parameter Job Name User Program Template Job Name
CTM interception rules parameters (Part 1 of 2)

Description Intercepted SAP job name, to be extracted from SAP to CONTROL-M. The *wildcard can be used. SAP user that created the job. The *wildcard can be used. LEAVE AS DEFAULT (*) Name of existing SAP-type CONTROL-M job (not submitted) to be used as a template for creating the job in CONTROL-M. Mandatory unless User Exit is selected.
Template Scheduling Table
Existing CONTROL-M scheduling table to which the Template Job Name belongs. Mandatory, unless User Exit is selected.
User Exit
Path to an executable or script file that includes user-specific definitions about how to create the intercepted jobs in CONTROL-M. Mandatory, unless Template Job Name is selected. If User Exit is selected, you must do one of the following:

Enter a valid path to a pre-defined executable or script file. Click Select to select an existing file.
Note: If you access this file from the CONTROL-M Configuration Manager, it has to exist in the USER_EXIT directory. This is located in the CONTROL-M/Agent directory, under CM/SAP. For more information about User Exits, see Defining a user exit on page 129.
119
Table 18
Parameter
CTM interception rules parameters (Part 2 of 2)

Description Set into which CONTROL-M group scheduling table the job should be submitted. Valid values are:

Into Group
None (Default) - use when the job template does not belong to a group scheduling table Recent - add the job to the group scheduling table that was most recently ordered Standalone - order the job with adding it to a group scheduling table New Group - order the job to a new group scheduling table Specific - set a group scheduling table Order ID to which to add the job
The last four options are similar to the Force Into options of CONTROL-M/EM. For more information about CONTROL-M group scheduling tables and Force Into parameters, see the CONTROL-M/EM User Guide.
Preventing intercepted jobs from being discarded in SAP

This procedure describes how to avoid a situation in which jobs are intercepted, but remain in SAP in scheduled status and are never acquired by the Extractor Management utility. A special interception rule must be defined to prevent this. Additionally, a default job that is associated with a specific scheduling table must be predefined and stored in CONTROL-M. These should be set as part of the following procedure. Click the CTM Interception Rules tab, and click Add. Set the parameters, as described in the following table: Table 19
Parameter Job Name User Program Template Job Name Template Scheduling Table User Exit
Parameters for avoiding discarded intercepted jobs

Value * * * Default SAP-type job Default scheduling table Can be defined instead of a Template Job Name and Template Scheduling Table
120
Extracting and monitoring SAP CCMS jobs
NOTE
If you do not follow this procedure, a predefined User Exit is used by the Extractor. For more information, see Pre-defined User Exit for the Extractor Management utility on page 130.
Example of job interception with the Extractor Management utility

Previously, to supervise the background job load in SAP, the SAP administrators removed users Release Authorizations, and released these jobs manually, according to the overall load in the system. The Extractor Intercept functionality now enables SAP administrators to provide users with Release Authorizations, and then manage the background job load by creating intercept rules and scheduling these jobs through CONTROL-M. Following is an example of how you can use the job interception functionality to control Background Work Process (WP) availability in your SAP system.
1 Define SAP interception criteria to intercept all jobs created by a specific group of
users.
2 In CONTROL-M/EM, define Quantitative Resources as WP_emp with a value of

eight units. Eight is the number of WPs to be available for this group of users.
3 In CONTROL-M/Desktop, define a job (to be used as a template) that requires one

unit of WP_emp.
4 In the CTM Interception Rules panel, set the job that you just defined as the
Template Job Name.
In this example, if your system has ten Background WPs available, the selected group of users cannot use more than eight, and, therefore, the system always leaves two WPs available for other purposes.

The CONTROL-M/CM for SAP Extractor Management utility can be used to create one or more mirror-image jobs by using criteria identical to that of specific jobs already running in SAP. These are then monitored (but not submitted), enabling CONTROL-M to track the progress of the actual job in SAP. This mirror image is stored in the Active Jobs file in the CONTROL-M/Server database.
121
NOTE
The functionality available in previous versions of CONTROL-M/CM for SAP using the ctmextract utility is still supported. For details, see Appendix A, Extracting and monitoring jobs.
Before you begin
Assign a priority to Extracted jobs in the Extractor General Configuration tab (see General configuration of the Extractor Management utility on page 114). Activate the Extractor Management utility (see Activating the Extractor Management utility on page 130).
To extract running SAP CCMS jobs from within the CONTROL-M Configuration Manager 1 Access the Extractor Management utility, as described in Accessing the Extractor
Management utility on page 113.
2 Select the Extraction Criteria tab.

Figure 18 Extractor Management utility - Extraction Criteria tab
This tab is divided into two sections: Job Extraction Criteria and Extraction Rules [for specific criteria].
122
In the Job Extraction Criteria section, you can define extraction criteria for the kinds of SAP job that CONTROL-M will extract. All jobs that have these criteria will be extracted from SAP and mirrored in CONTROL-M.
NOTE
Jobs will only be mirrored in CONTROL-M if they meet the criteria of an extraction Rule.
Once you have specified Job Extraction criteria, the Extraction Rules section is enabled. You can define specific extraction rules that will affect which SAP jobs are extracted and how they will be represented in CONTROL-M.
3 In the Job Extraction Criteria section, click Add to display the Add Extraction
Criteria dialog box. The parameters in this dialog box are described in Table 20 on page 124.
4 Specify the parameters as required, and click OK. The Extraction Rules section is
now enabled.
5 In the Extraction Rules section, click Add to display the Add Extraction Rule
dialog box. The parameters in this dialog box are described in Table 21 on page 125. You can click Advanced Parameters to display a list of extra job parameters that can be used to filter the extracted jobs.
6 Specify the parameters as required, and click OK. NOTE

All criteria in this tab is representative of the corresponding selected account. Changing the account will alter all previously defined criteria.
To extract running SAP CCMS jobs using the Java GUI 1 Access the Extractor Management utility, as described in Accessing the Extractor
Management utility on page 113.
2 The Extractor Management dialog box is displayed, overlaid with the Select SAP
Account dialog box.
NOTE
The Change Account button can be used at any time to display the Select SAP Account dialog box and configure a different account.
123
Click the Extraction Criteria tab, and click Add.
3 An Add dialog box is displayed, in which you can set values for the Extraction
Criteria parameters. These criteria set which jobs should be extracted from SAP. The available fields and definitions are described in Table 20 on page 124.
4 Click Rules to display the Rules Viewer. 5 Click Add in the Rules Viewer to display another Add dialog box where you can
assign sub-rules to jobs or sets of jobs. These rules determine how jobs are created and monitored in CONTROL-M, and are described in Table 21. This step can be repeated to add additional rules in the Rules Viewer.
6 Click OK. The data is saved. The Rule Viewer is re-displayed, with the Copy, Edit,
and Remove buttons enabled. You can either add additional rules or proceed to step 7.
7 Click OK. All of the information that you set during this procedure is displayed as
one entry in the Extraction Criteria panel. The Copy, Edit, Rules, and Remove buttons are enabled.
NOTE
Click Rules to directly access the Rules Viewer of a specific extraction criterion, in the Extraction Criteria panel. You can now modify the existing rules, or add new ones.
8 When you are satisfied that all criteria in the Extraction Criteria panel are set
according to your requirements, click Save. Table 20
Field Name JOBNAME
Job Extraction Criteria parameters (Part 1 of 2)

Field Description Name of the job in SAP. Can be either a specific or generic name. Valid values are: any generic value, for example: JOB_* Mandatory. Free text. Note: In a Job Name, SAP perceives an underscore _ and a space to be the same character. This means that two jobs, named respectively JOB GOLD and JOB_GOLD, for example, would be recognized as one and the same job. This is a known SAP problem.
JOBCOUNT JOBGROUP
CCMS job number. 8-digit number. Optional. Group to which the jobs belong. Free text. Optional
124
Table 20
Field Name
Job Extraction Criteria parameters (Part 2 of 2)

Field Description Owner of the job in SAP. Mandatory. Valid values are: any generic value, for example: *Y*
USERNAME
FROM_DATE
Scheduled start date for CCMS job. Optional. Valid format: YYYYMMDD
FROM_TIME
Scheduled start time for CCMS job. Optional. Valid format: HHMMSS Note: This parameter depends on the specification of both FROM_DATE and TO_DATE for the same day.
TO_DATE TO_TIME
Scheduled end date for CCMS job. Optional. Valid format is: YYYYMMDD Scheduled end time for CCMS job. Optional. Valid format: HHMMSS Note: This parameter depends on the specification of both FROM_DATE and TO_DATE for the same day.
NO_DATE WITH_PRED EVENTID EVENTPARAM PRELIM SCHEDULED READY RUNNING FINISHED ABORTED
Selection flag for jobs with no start date. Optional. Valid values are: X/N Selection flag for jobs with start after predecessor. Optional. Valid values are: X/N Background event ID. Free text. Optional Background Event parameter. Free text. Optional. Status of CCMS job. Valid values are: X/N (Default: X). Optional.
Table 21
Field Name
Extraction Rules parameters (Part 1 of 3)

Field Description SAP job name. Mandatory Can be either a specific or a generic name.
JOBNAME
Note: The following parameters are used to set how the job should be created in CONTROL-M. You can define either according to a predefined job and scheduling table (Template Job Name and Template Scheduling Table), or according to a user-defined script (User Exit). Template Job Name Name of an existing CONTROL-M job (not submitted) to be used as a template for creating a SAP-type job in CONTROL-M. Mandatory, unless User Exit is selected.
125
Table 21
Field Name

Field Description An existing CONTROL-M scheduling table to which the Template Job Name belongs. Mandatory, unless User Exit is selected. The path to an executable or script file, that includes user-specific definitions about how to create the extracted jobs in CONTROL-M. Mandatory, unless Template Job Name is selected.
Template Scheduling Table
User Exit
If User Exit is selected, you must enter a valid path to a pre-defined executable or script file or
Click Select to select an existing file. Note: If you access this file from the CONTROL-M Configuration Manager, it has to exist in the USER_EXIT directory. This is located in the CONTROL-M/Agent directory, under CM/SAP.
For more information about User Exits, see Defining a user exit on page 129. All the following parameters are optional. Note: From the CONTROL-M Configuration Manager, these parameters are available when you click Advanced Parameters. JOBCOUNT STEPCOUNT SDLSTRTDT SDLSTRTTM BTCSYSTEM SDLDATE SDLTIME SDLUNAME LASTCHDATE LASTCHTIME LASTCHNAME RELDATE RELTIME RELUNAME STRTDATE STRTTIME ENDDATE Job ID. Optional. 8-digit number. Job step ID number. Optional. Scheduled start date for background job. Optional. Scheduled start time for background Job. Optional. Target system to run background job. Optional. Date of job or step scheduling. Optional. Time of a scheduled job or step. Optional. Initiator of job or step scheduling. Optional. Date of last job change. Optional Time of last job change. Optional Name of user who made last job change. Optional. Release date for background schedule. Optional. Release time of scheduled background job. Optional. User that released scheduled batch job. Optional. Job start date. Optional. Batch job start time. Optional. Job start date. Optional.
126
Initiating a mass parallel process (detecting spawned jobs)
Table 21
Field Name ENDTIME PERIODIC STATUS

Field Description Batch job start time. Optional. Periodic jobs indicator ('X'). Optional. Status of background job. Optional. Background user name for authorization check. Optional. Background client for authorization check. Optional. Number of successor jobs. Optional. Number of previous jobs. Optional. Latest run date for batch job. Optional. Latest run time for batch job. Optional. Work process number. Optional. Work process ID. Optional. Background event ID. Optional. Background Event parameters (for example, Jobname/Jobcount). Optional. Job classification. Optional. Factory calendar ID for background processing. Optional. Server name. Optional. Server name. Optional.
AUTHCKNAM AUTHCKMAN SUCCNUM PREDNUM LASTSTRTDT LASTSTRTTM WPNUMBER WPPROCID EVENTID EVENTPARM JOBCLASS CALENDARID EXECSERVER REAXSERVER

A spawned job is a job created by another (parent) job, and monitored by CONTROL-M. The Extractor Management utility can detect and extract spawned jobs into CONTROL-M.
Before you begin
Ensure that the Parent/Child function is enabled in your SAP system (see Activating Interception and Parent/Child functions in SAP on page 113). Assign a priority to Spawned jobs in the Extractor General Configuration tab (see General configuration of the Extractor Management utility on page 114). Activate the Extractor Management utility (see Activating the Extractor Management utility on page 130).
127
Detecting the spawned jobs of a parent job

1 Define a regular SAP-type job in CONTROL-M. (For more information see
Creating and monitoring SAP R/3 jobs on page 48.)
2 In the SAP panel, click Detect Spawned Jobs to display the Detect Spawned Jobs
dialog box.
3 Select your choice, according to the available options:

Parameter Start Spawned Job Description If you select Start Spawned Job, CONTROL-M/CM for SAP checks the status of each spawned job and starts any spawned job with Scheduled status. No spawned jobs are detected. Parent (current) job definition: Detect spawned jobs of the current job, and extract these jobs to CONTROL-M, with identical properties to the parent job. Notes: This means that if the spawned jobs create spawned jobs of their own, they are also detected. Additionally, all generations of spawned jobs are created in the scheduling table to which the original parent job belongs. A specific job definition: A field is displayed, in which you can enter a specific SAP-type job name. Detected spawned jobs of the current job are extracted to CONTROL-M with identical properties to the selected (not the current) job. Important: The selected job must exist in the same scheduling table as the current job. Note: To detect further generations of spawned jobs, select the Detect Spawned Jobs option in the Job Editing form of the selected set job.
No Detection Needed Detect and Create According to:
128
Defining a user exit
For more information about the Job Editing form and defining a CONTROL-M job, see the CONTROL-M/Enterprise Manager User Guide.
4 Click OK. The Extractor Management utility detects spawned jobs, according to
the priority set in the General Configuration panel of the Extractor Management utility. For more information see General configuration of the Extractor Management utility on page 114.
Defining a user exit

When processing intercepted or extracted jobs, you can either extract them to the CONTROL-M environment, as described in the earlier part of this section, or you can assign a different manner in which these jobs should be processed. A user exit is a user-defined script (or executable) that can be used for this purpose. For each intercepted or extracted job, the Extractor Management utility runs the script, and passes a list of parameters with values of the specific intercepted or extracted job. The parameters are described in Table 22 on page 129. Table 22
1 2
User Exit script parameters

Parameter value <SAP Job Name> <Job count>
Parameter number
A successful return value of the script is 0 (zero). Any other return value causes the job to be intercepted or extracted again, at the next iteration of the Extractor Management utility. The User Exit script can run a user-defined action, and can use other CONTROL-M utilities (for example, ctmorder and ctmcreate) to handle the Extracted or Intercepted job.
NOTE
When using the CONTROL-M Configuration Manager, the User Exit script can only exist in the following location: <Agent_dir>/cm/SAP/USER_EXIT
129
Activating the Extractor Management utility
Pre-defined User Exit for the Extractor Management utility

Extractor Management automatically defines a default CTM Interception Rule that meets the conditions described in Table 19 on page 120. This Interception Rule calls a pre-defined User Exit script with the following name and location:

On Unix: <Agent_homedir>/ctm/cm/SAP/exe/default_order On Microsoft Windows: <Agent home directory>\CM\SAP\EXE\default_order.bat
This User Exit script is called by the default Interception Rule if the intercepted job has not met the conditions of any preceding rule. This script submits the job using the CONTROL-M ctmcreate command. You can use this script as one example of how to create a User Exit.
Activating the Extractor Management utility

NOTE
The Extractor Management utility should not be activated before configuring its parameters. For more information, see Configuring and working with the Extractor Management utility on page 111.
To activate and stop the Extractor Management utility in Unix

To activate the Extractor Management utility mechanism for CONTROL-M/CM for SAP, use the following procedure: At the command prompt enter start-xt. To stop the Extractor Management utility, enter shut-xt.
NOTE
If the computer on which CONTROL-M/Agent is installed is rebooted while the Extractor process is active, CONTROL-M/Agent automatically restarts the Extractor Management utility. (A similar procedure occurs with CONTROL-M/Tracker.)
To activate and stop the Extractor Management service in Microsoft Windows

If the computer has not been restarted since the installation of CONTROL-M/CM for SAP, you must restart it before activating the Extractor Management service.
130
SAP Event Based Scheduling
1 Select Start => Settings => Control Panel => Administrative Tools => Services to
display the Services dialog box.
2 Select CONTROL-M SAP CM XT, and either
click Start to start the Extractor Management service or click Stop to stop the Extractor Management service
CONTROL-M/EM User privileges required for the Extractor Management utility:

User Privilege BROWSE Ability View extractor general configuration View SAP Interception Criteria View CTM Interception Rules View Extraction Criteria and Rules Change extractor general configuration Change SAP Interception Criteria Change CTM Interception Rules Change Extraction Criteria and Rules
FULL
SAP Event Based Scheduling

The SAP Event Based Scheduling utility is a CONTROL-M/CM for SAP feature that enables jobs to be triggered in a specific order, and conditions to be raised or deleted, based on events within the SAP system.
NOTE
The Extractor Management service (for UNIX, read process) must be running for you to use the SAP Event Based Scheduling functionality.
WARNING
No more than one Extractor service (process) can be running at one time.
131
Modifying the default configuration file
To work with SAP Event Based Scheduling, you must create and define a configuration file, and an event-based rule file. See:

Modifying the default configuration file on page 132 Modifying the default event-based rule file on page 133
Default examples of both of these files are provided with CONTROL-M/CM for SAP, and are installed on your computer during the Installation process. For more information about the installation process, see Chapter 2, Installation.
Before you begin

Before using the SAP Event Based Scheduling utility, you should go into your SAP system and ensure that all events in the event history have a status of Confirmed. This is to ensure that action items are not triggered by previous events when you run the SAP Event Based Scheduling utility. If the event history has not yet been configured, events will not be displayed in the Event History tab. Use the SAP transaction sm62 to add appropriate entries in the Criteria and Reorganization tabs, which ensures that events are included in the Event History.
Modifying the default configuration file

1 Navigate to the following file location, on the computer on which
CONTROL-M/CM for SAP is installed:
<CM SAP directory>/data/event_cfg.dat
2 Open the event_cfg.dat file in a text editing application. 3 Configure the parameters according to your requirements. The parameters in the
event_cfg.dat file are described in Table 23.
132
Modifying the default event-based rule file
Table 23
Parameter
SAP Event Based Scheduling Configuration file

Description Enables the monitoring of specified events in SAP, when the value is set to Y. Valid values: Y N (default)
EXTRACT_EVENT_FROM_SAP
ORDER_MAX_RETRY <number> The maximum number of times the SAP Event Based Scheduling utility retries an unsuccessful action. Valid values: Any integer between 0 - 255. Default: 3.
4 Close and save the event_cfg.dat file. NOTE

Since the SAP Event Based Scheduling utility is embedded in the Extraction Manager service/process, the specified general parameters in the Extractor Management utility (Interval time in seconds, and Activity log) are also effective. For more information, see General configuration of the Extractor Management utility on page 114.

Rules for how the SAP Event Based Scheduling utility runs are defined in a specific event-based rule file. A default version of this file (event_rules.dat) is provided and installed during the installation process. The file can be found in the following location:
<CM SAP directory>/DATA/event_rules.dat
NOTE
The event-based rule file follows the same conventions as the intercept_rules.dat file. (Each condition is followed by at least one Action.)
133
To create a rule file 1 Open the event_rules.dat file, in a text editing application. 2 Configure the parameters according to your requirements. The file is structured as
displayed in Figure 19. The parameters are described in Table 24.
NOTE
If either type of action (CTMORDER or CTMCONTB) fails, they will retry again as many times as specified according to the value of the ORDER_MAX_RETRY parameter in the event_cfg.dat configuration file. Once the maximum number of retries is reached, a message is displayed in the Activity log (if active), and an Alert is sent to CONTROL-M/EM.
Figure 19
Example of event-based rule file
[CONDITION_1] SAPR3-ACCOUNT MYDXI SAPR3-EVENT_ID ER1 SAPR3-EVENT_PARM [CTMORDER] JOBNAME Job1 SCHEDTAB Table1_erez [CTMORDER] JOBNAME Job2 SCHEDTAB Table2_erez [CONDITION_2] SAPR3-ACCOUNT MYDXI SAPR3-EVENT_ID ER1 SAPR3-EVENT_PARM * [CTMORDER] JOBNAME Job1 SCHEDTAB Table1_erez %%gili %%shok1 ok %%shok2 ok [CTMCONTB] [CTMCONTB] COND_ACTION ADD [CONDITION_3] SAPR3-ACCOUNT MYDXI SAPR3-EVENT_ID SAP_END_OF_JOB SAPR3-EVENT_PARM *
134
[CTMORDER] JOBNAME Job1 SCHEDTAB Table1_erez %%lego go for it! [CONDITION_4] SAPR3-ACCOUNT DJGH3 SAPR3-EVENT_ID * SAPR3-EVENT_PARM * [CTMCONTB] COND_ACTION DELETE
COND_DATE ****
The rule file consists of Conditions and Actions, described in Table 24. As soon as all the criteria of a condition are met by an event, the actions specified within that condition are performed.
NOTE
Any further conditions for which the event could have matching criteria are ignored.
Table 24
Parameter
Rule File parameters (Part 1 of 3)

Description A section of the rule file which must contain at least one action. There is no limit to the number of actions that be contained within a condition. Note: Two valid action types exist. CTMORDER and CTMCONTB.
[Condition]
SAPR3-ACCOUNT
Mandatory condition parameter. Indicates account as defined by the CONTROL-M/CM for SAP account utility. Valid characters: Alphanumeric Mandatory condition parameter. The SAP event ID. Valid characters: Alphanumeric and the asterisk (*) wildcard.
SAPR3-EVENT_ID
SAPR3-EVENT_PARM Mandatory condition parameter. The SAP event parameter. Valid characters: Alphanumeric and the asterisk (*) wildcard. Can also be left blank, since this parameter value is optional in SAP. [CTMORDER] Valid type of action. This is a CONTROL-M utility that orders a job. Note: CTMORDER is always run with a parameter value of FORCE -Y.
135
Table 24
Parameter JOBNAME

Description Mandatory CTMORDER parameter. Name of the job to be ordered. Note: The job specified in this parameter value should be defined in CONTROL-M/EM before the SAP Event Based Scheduling utility is run.
SCHEDTAB
Mandatory CTMORDER parameter. Indicates the scheduling table of the job to be ordered. Note: The job specified in this parameter value should exist in this scheduling table before the SAP Event Based Scheduling utility is run.
GROUP_ID
Optional CTMORDER parameter. Indicates defined group of jobs to be ordered. Valid values: LAST Corresponds to the Recent parameter in the Intercept functionality. ALONE Corresponds to the Standalone parameter in the Intercept functionality. NEWG Corresponds to the New Group parameter in the Intercept functionality. Free text string (alphanumeric characters). Corresponds to the Specific parameter in the Intercept functionality. Note: All of the above Intercept functionality parameters are described in Table 18 on page 119 Optional CTMORDER parameter. Valid values: AutoEdit Name AutoEdit Value (Blank spaces permitted) Structure: %%<autoedit name> <autoedit value> Note: Certain AutoEdits exist within the SAP Event Based Scheduling utility, and can be used when defining CONTROL-M/CM for SAP jobs, in connection with SAP events. For more information, see Using the SAP Event Based Scheduling functionality to trigger a job on page 50.
AutoEdit variable
ODATE
CTMORDER parameter. Any ctmorder date value. Default value: ODAT Valid type of action. This is a utility that adds or deletes conditions from CONTROL-M. See the Notes section at the end of this table.
[CTMCONTB]
136
Import SAP Calendar utility
Table 24
Parameter

Description Name of the condition. Optional. Maximum length: 255 characters Optional parameter that specifies the action for a CTMCONTB condition. Valid values: ADD DELETE DELETENOWILD Note: When not specified, the default is ADD. Optional parameter that represents the CTMCONTB date value. Maximum length: 4 characters Note: When not specified, the default is ODAT.
COND_NAME
COND_ACTION
COND_DATE
Notes If the COND_NAME parameter is not specified for CTMCONTB, the condition created in CONTROL-M has the following template-like structure: sap_<Event_ID>_<Event_Param> 1. In such a condition, if the Event Param value is empty, the name of the condition name has the following structure: sap_<Event_ID> 2. In such a condition, if the Event_ID is SAP_END_OF_JOB, the Event_Param value is truncated, resulting in the job count number being omitted from the condition. 3. In such a condition, if there are spaces in the Event Param value, they are automatically converted to underscores.

In addition to the current CONTROL-M/EM calendars, you can now import SAP calendars, using CONTROL-M/CM for SAP. Using the Import SAP calendar utility, you can import the calendars from your SAP machine to your CONTROL-M environment, in order to use them when defining your batch jobs.
NOTE
The Import SAP Calendar utility can only be accessed from the CONTROL-M Configuration Manager. Only SAP factory calendars can be imported.
137
To access the Import SAP Calendar utility 1 In the CONTROL-M Configuration Manager, locate the required iteration of
CONTROL-M/CM for SAP, and right-click.
2 Select Import SAP Calendar. The following dialog box is displayed:

Figure 20 Import SAP Calendar
The parameters are inter-dependent. Most are disabled until you have defined an account and then a calendar associated with that account. The parameters in this dialog box are described in Table 25.
NOTE
All fields in Table 25 are mandatory.
Table 25
Parameter
Import SAP Calendar parameters

Description Name of the CONTROL-M/CM for SAP account. The SAP calendar. Note: Disabled until an account is specified.
Calendar to Import Account Name SAP Calendar Name
SAP Calendar year
The SAP calendar year. Note: Disabled until an account is specified.
CONTROL-M Definitions
138
Table 25
Parameter
Import SAP Calendar parameters

Description Enables the SAP calendar to be imported to all online instances of CONTROL-M/Server. Default. Enables the SAP calendar to be imported to a specific instance of CONTROL-M/Server. When selected, a drop-down list of all online instances of CONTROL-M/Server is enabled. Enabled when the SAP calendar name and year have been selected. Automatically displays the default <SAP calendar name>_<SAP calendar year>. Free text. Enabled when the SAP calendar name and year have been selected. Automatically displays the default <SAP calendar name>_<SAP calendar year>. Free text.
Import to all CONTROL-M/Servers Import to a specific CONTROL-M/Server
Calendar name
Calendar description
NOTE
This utility is closely associated with the CONTROL-M defcal utility. For more information about this utility, see the CONTROL-M/Enterprise Manager Administrator Guide.
The result is written as the following file: BMC_importedSAPcalendar_<account name>_<SAP calendar name>_<SAP calendar year>.xml.
3 Access this file by selecting Start => Run => %temp%. 4 Copy this file to the computer on which the CONTROL-M/EM server is located. 5 Run the CONTROL-M/EM defcal utility using this file. 6 Upload the result of the defcal utility to the required CONTROL-M server. NOTE
If you plan to use the Import SAP Calendar utility, your SAP system version should be PI_BASIS 2002_2_620 or later.
CONTROL-M/EM User privileges required for the Import SAP Calendar utility:
User Privilege BROWSE UPDATE Ability View existing calendars on the SAP system Import a calendar
139
Requesting SAP actions
Requesting SAP actions

The CONTROL-M/CM for SAP Request utility (ctmr3req) can be used to request that SAP perform certain actions, using information from the SAP database. The ctmr3req utility can request that SAP perform the following actions:
Display a list of defined variants for a specific program, as described on page 140. Alter the value of a specific variant in a program, as described on page 141. Display the details of a specific variant, as described on page 143. Enable a SAP background processing event to be raised (triggered), as described on page 144. Delete a job from the SAP database, as described on page 145. Define a new job, as described on page 146. Modify an existing job, as described on page 147. Remove process chain from schedule on page 149.
NOTE
This utility can be used within ctmcreate or ctmdefine. However if it is used this way, the command is limited to 512 characters.
Displaying a list of variants for a program

Use this procedure to request that SAP display a list of defined variants for a specific ABAP program. (The program is set in the SAPR3-PROGRAM parameter.)
Before you begin
If you are working in a Microsoft Windows environment, open a new DOS prompt window. If you are working in a Unix environment, ensure that you are logged in as the CONTROL-M/Agent user.
140
Altering parameter values in a variant
To display a list of variants

Enter the following command, with the parameters set according to the values described in Table 26, and press <Enter>. on Unix
ctmr3req -SAPR3-ACTION var_mon -SAPR3-ACCOUNT <account_name> -SAPR3-PROGRAM <program_name>
on Windows
<Agent home directory>\CM\SAP\EXE\ctmr3req -SAPR3-ACTION var_mon -SAPR3-ACCOUNT <account_name> -SAPR3-PROGRAM <program_name> [-Agent <agent_name>]
Table 26
Parameter
Parameters for var_mon action

Description The action that classifies the nature of this version of the ctmr3req utility. (var_mon) Mandatory. Name of a specific SAP account. Mandatory. Maximum length: 30 characters. Name of the ABAP program in SAP, if such a program has been indicated. Mandatory.
SAPR3-ACTION SAPR3-ACCOUNT SAPR3-PROGRAM
Below is an example of the ctmr3req utility when used to display a list of variants, using the DGOLDHAD account, for the prog1 program:
D:\Program files\BMC Software\CONTROL-M aGENT\David\ctmr3req -SAPR3-ACTION var_mon -SAPR3-ACCOUNT DGOLDHAD -SAPR3-PROGRAM prog1 -Agent Default

Use this procedure to alter the value of set parameters in a variant.
Before you begin
141
To alter parameter values

ctmr3req -SAPR3-ACTION var_edit -SAPR3-ACCOUNT <account_name> -SAPR3-PROGRAM <program_name> -SAPR3-VAR <variant_name> -SAPR3-VAR_PARAM<nnn> <variant_parameter_name>=<variant_parameter_value> [-SAPR3-VAR_TEXT <variant_text>]
on Windows
<Agent home directory>\CM\SAP\EXE\ctmr3req -SAPR3-ACTION var_edit -SAPR3-ACCOUNT <account_name> -SAPR3-PROGRAM <program_name> -SAPR3-VAR <variant_name> -SAPR3-VAR_PARAM<nnn> <variant_parameter_name>=<variant_parameter_value> [-SAPR3-VAR_TEXT <variant_text>] [-Agent <agent_name>]
Table 27
Parameter
Parameters for var_edit action

Value Action that classifies the nature of this version of the ctmr3req utility. (var_edit) Mandatory. Name of a specific SAP account. Maximum length: 30 characters. Mandatory. Name of the ABAP program in SAP, if such a program has been indicated. Mandatory. This parameter specifies the name of the variant for a specific program in SAP. Mandatory. The parameter of the variant. Mandatory. nnn is a three-digit number that represents the parameter count number.
-SAPR3-ACTION -SAPR3-ACCOUNT -SAPR3-PROGRAM -SAPR3-VAR -SAPR3-VAR_PARAM<nnn>
-SAPR3-VAR_TEXT
Description of the variant. Optional
In the following example, the ctmr3req utility is used to alter parameter values, using the DGOLDHAD account, for the prog1 program, with the var1 variant, when the Airline value is an integer between 5 and 9, and the text is This is a test variant. All parameters are mandatory, except the -SAPR3-VAR_TEXT parameter, as indicated by the square brackets.
ctmr3req -SAPR3-ACTION var_edit -SAPR3-ACCOUNT DGOLDHAD -SAPR3-PROGRAM prog1 -SAPR3-VAR var1 -SAPR3-VAR_PARAM001 "AIRLINE=I,BT,5 => 9" [-SAPR3-VAR_TEXT "This is a test var"]
142
Displaying variant details within a program
Displaying variant details within a program

Use this procedure to display the details of a specific variant within a program.
Before you begin
To display variant details in a program

ctmr3req -SAPR3-ACTION var_show -SAPR3-ACCOUNT <account_name> -SAPR3-PROGRAM <program_name> -SAPR3-VAR <variant_name>
on Windows
<Agent home directory>\CM\SAP\EXE\ctmr3req -SAPR3-ACTION var_show -SAPR3-ACCOUNT <account_name> -SAPR3-PROGRAM <program_name> -SAPR3-VAR <variant_name> [-Agent <agent_name>]
Table 28
Parameter
Parameters for var_show action

Description Action that classifies the nature of this version of the ctmr3req utility. (var_show) Mandatory. Name of a specific SAP account. Maximum length: 30 characters. Mandatory. Name of the ABAP program in SAP, if such a program has been indicated. Mandatory. The variant of the SAP program. Mandatory.
-SAPR3-ACTION -SAPR3-ACCOUNT -SAPR3-PROGRAM -SAPR3-VAR
In the following example, the ctmr3req utility is used to display variant details in a program, searching for var1 variants, using the DGOLDHAD account, for the RSAAA02 program. All parameters are mandatory.
ctmr3req -SAPR3-ACTION var_show -SAPR3-ACCOUNT DGOLDHAD -SAPR3-PROGRAM prog1 -SAPR3-VAR var1
143
Raising a SAP event
Raising a SAP event

Use this procedure to enable a specific SAP background processing event to be raised (triggered).
Before you begin
To raise a SAP event

ctmr3req -SAPR3-ACTION raise_event -SAPR3-ACCOUNT <account_name> -SAPR3-EVENT_ID <event_ID> -SAPR3-EVENT_PARAM <event_parameter>
on Windows
<Agent home directory>\CM\SAP\EXE\ctmr3req -SAPR3-ACTION raise_event -SAPR3-ACCOUNT <account_name> -SAPR3-EVENT_ID <event_ID> -SAPR3-EVENT_PARAM <event_parameter> [-Agent <agent_name>]
Table 29
Parameter
Parameters for raise_event action

Description Action that classifies the nature of this version of the ctmr3req utility. (raise_event) Mandatory. Name of a specific SAP account. Maximum length: 30 characters. Mandatory. Name of SAP background processing event Mandatory. Additional parameters for a SAP background processing event. Optional.
-SAPR3-ACTION -SAPR3-ACCOUNT -SAPR3-EVENT_ID -SAPR3-EVENT_PARAM
In the following example, the ctmr3req utility is used to raise the ev1 event, with the parameter value of evparm1, using the DGOLDHAD account. All parameters are mandatory.
ctmr3req -SAPR3-ACTION raise_event -SAPR3-ACCOUNT DGOLDHAD -SAPR3-EVENT_ID ev1 -SAPR3-EVENT_PARAM evparm1
144
Deleting a job
Deleting a job
Use this procedure to delete a specific job from the SAP database.
Before you begin
To delete a job
ctmr3req -SAPR3-ACTION job_delete -SAPR3-ACCOUNT <account_name> -SAPR3-JOBNAME <job_name> -SAPR3-JOBCOUNT <job_count>
on Windows
<Agent home directory>\CM\SAP\EXE\ctmr3req -SAPR3-ACTION job_delete -SAPR3-ACCOUNT <account_name> -SAPR3-JOBNAME <job_name> -SAPR3-JOBCOUNT <job_count> [-Agent <agent_name>]
Table 30
Parameter
Parameters for job_delete action

Description Action that classifies the nature of this version of the ctmr3req utility. (job_delete) Mandatory. Name of a specific SAP account. Maximum length: 30 characters. Mandatory. Job name in SAP to be deleted. Mandatory. Unique ID number for the job in SAP. Mandatory
-SAPR3-ACTION -SAPR3-ACCOUNT -SAPR3-JOBNAME -SAPR3-JOBCOUNT
In the following example, the ctmr3req utility is used to delete a job. All parameters are mandatory.
ctmr3req -SAPR3-ACTION job_delete -SAPR3-ACCOUNT DGOLDHAD -SAPR3-JOBNAME job1 -SAPR3-JOBCOUNT 12344321
145
Defining a new job
Defining a new job

Use this procedure to define a new job in SAP database.
Before you begin
To define a job
ctmr3req -SAPR3-ACTION job_define -SAPR3-ACCOUNT <account_name> -SAPR3-JOBNAME <job_name> -SAPR3-STEP-S<nn>-STEP_TYPE {A|C|E} -SAPR3-STEP-S<nn>-PROGRAM <program_name>
on Windows
<Agent home directory>\CM\SAP\EXE\ctmr3req -SAPR3-ACTION job_define -SAPR3-ACCOUNT <account_name> -SAPR3-JOBNAME <job_name> -SAPR3-STEP-S<nn>-STEP_TYPE {A|C|E} -SAPR3-STEP-S<nn>-PROGRAM <program_name> [-Agent <agent_name>]
NOTE
The remainder of the syntax for this action depends on the value of the -SAPR3-STEP-S<nn>-STEP_TYPE parameter, and subsequent parameter values.
Table 31
Parameter
Parameters for job_define action (Part 1 of 2)

Description Action that classifies the nature of this version of the ctmr3req utility. (job_define) Mandatory. Name of a specific SAP account. Maximum length: 30 characters. Mandatory. Job name in SAP to be defined. Mandatory.
-SAPR3-ACTION -SAPR3-ACCOUNT -SAPR3-JOBNAME
146
Modifying a job
Table 31
Parameter
Parameters for job_define action (Part 2 of 2)

Description Step type. Mandatory. Valid values are: A = ABAP program C = External command E = External program nn is a two-digit number that represents the step number.
-SAPR3-STEP-S<nn>STEP_TYPE
-SAPR3-STEP-S<nn>PROGRAM
The name of the job step program. Mandatory. nn is a two-digit number that represents the step number.
NOTE
The Target Group and Target Server parameters are not supported by the ctmr3req utility in
job define mode.

For information about additional parameters for use when defining a new job, see the CONTROL-M Parameters and Variables Reference Guide.
In the following example, the ctmr3req utility is used to define a new job. The first five parameters are mandatory, including -SAPR3-STEP-S01-STEP_TYPE. The following step types can be selected:

A = ABAP program C = External command E = External program
The remaining parameters are defined according to both the step type and your specifications. There can be more than one step type, and not all step types require the same specification.
ctmr3req -SAPR3-ACTION job_define -SAPR3-ACCOUNT DGOLDHAD -SAPR3-JOBNAME job1 -SAPR3-STEP-S01-STEP_TYPE A -SAPR3-STEP-S01-PROGRAM ZQA_WITH_VARIANTS -SAPR3-STEP-S01-VAR-NAME MOMO -SAPR3-STEP-S01-PRINT_COPIES 030
Modifying a job
Use this procedure to modify an existing job in the SAP database.
147
Modifying a job
Before you begin
To modify a job
The procedure for modifying an existing job using the ctmr3req utility is very similar to the procedure for defining a new job using this utility. Enter the following command, with the parameters set according to the values described in Table 32, and press <Enter>. on Unix
ctmr3req -SAPR3-ACTION job_modify -SAPR3-ACCOUNT <account_name> -SAPR3-JOBNAME <job_name> -SAPR3-JOBCOUNT <job_count> -SAPR3-STEP-S<nn>-STEP_TYPE {A|C|E} -SAPR3-STEP-S<nn>-PROGRAM <program_name>
on Windows
<Agent home directory>\CM\SAP\EXE\ctmr3req -SAPR3-ACTION job_modify -SAPR3-ACCOUNT <account_name> -SAPR3-JOBNAME <job_name> -SAPR3-JOBCOUNT <job_count> -SAPR3-STEP-S<nn>-STEP_TYPE {A|C|E} -SAPR3-STEP-S<nn>-PROGRAM <program_name> [-Agent <agent_name>]
NOTE
The remainder of the syntax for this action depends on the value of the -SAPR3-STEP-S<nn>-STEP_TYPE parameter, and subsequent parameter values.
Table 32
Parameter
Parameters for job_modify action (Part 1 of 2)

Description Action that classifies the nature of this version of the ctmr3req utility. (job_modify) Mandatory. Name of a specific SAP account. Maximum length: 30 characters. Mandatory. Job name in SAP to be modified. Mandatory. Unique ID number for the job in SAP. Mandatory.
-SAPR3-ACTION -SAPR3-ACCOUNT -SAPR3-JOBNAME -SAPR3-JOBCOUNT
148
Modifying a job
Table 32
Parameter
Parameters for job_modify action (Part 2 of 2)

Description Step type. Mandatory. Valid values are:

-SAPR3-STEP-S<nn>STEP_TYPE
A = ABAP program C = External command E = External Program
nn is a two-digit number that represents the step number. -SAPR3-STEP-S<nn>PROGRAM The name of the job step program. Mandatory. nn is a two-digit number that represents the step number.
NOTE
For information about additional parameters for use when defining a new job, see the CONTROL-M Parameters and Variables Reference Guide.
In the following example, the ctmr3req utility is used to modify an existing job. As with the procedure for defining a new job (see page 146), the first five parameters are mandatory. In this example, the second step is being modified. Even if the step type is the same as it was previously, it must still be set in the utility.
ctmr3req -SAPR3-ACTION job_modify -SAPR3-ACCOUNT DGOLDHAD -SAPR3-JOBNAME job1 -SAPR3-JOBCOUNT 13292201 -SAPR3-STEP-S02-STEP_TYPE A -SAPR3-STEP-S02-PROGRAM ZQA_WITH_VARIANTS -SAPR3-STEP-S02-VAR-NAME KUKU
Interrupts - Removing a process chain from schedule

To remove a process chain from schedule, use the following procedure:
Before you begin
149
Converting CONTROL-M Option for R3 account definitions
To remove a process chain from schedule

Enter the following command, with the appropriate parameters set (for more details see Table 33, and press <Enter>. on Unix
ctmr3req -SAPR3-ACTION PC_STOP_SCHEDULE -SAPR3-ACCOUNT <account_name> -SAPR3-PROCESSCHAIN_ID <chain_id>
on Windows
<Agent home directory>\CM\SAP\EXE\ctmr3req -SAPR3-ACTION PC_STOP_SCHEDULE -SAPR3-ACCOUNT <account_name> -SAPR3-PROCESSCHAIN_ID <chain_id> [-Agent <agent_name>]
Table 33
Parameter
ctmr3req interrupt parameters

Description The action that classifies the nature of this version of the ctmr3req utility. (pc_stop_schedule) Mandatory. Name of a specific SAP account. Mandatory. Maximum length: 30 characters.
SAPR3-ACTION SAPR3-ACCOUNT
SAPR3- PROCESSCHAIN_ID Name of Process Chain in SAP. Mandatory.
Below is an example of the ctmr3req utility when used to remove a process chain from schedule, using the DGOLDHAD account, and pc1 as processchain_id:
ctmr3req -SAPR3-ACTION PC_STOP_SCHEDULE -SAPR3-ACCOUNT DGOLDHAD -SAPR3-PROCESSCHAIN_ID pc1
NOTE
CONTROL-M/CM for SAP does not support the Kill Job functionality for SAP BW jobs.

The CONTROL-M/CM for SAP Conversion utility (conr3acc) is used to create new account definitions for CONTROL-M/CM for SAP based on existing accounts in CONTROL-M/Option for R/3.
NOTE
This utility is specific to users who have a previous installation of CONTROL-M/Option for R/3. Both CONTROL-M/CM for SAP and CONTROL-M option for R/3 can exist and run concurrently on your computer.
Before you begin
If you are working in a Microsoft Windows environment, open a new DOS prompt window. If you are working in a Unix environment, ensure that you are logged in as the CONTROL-M/Agent user. Before running this utility, you must use the ctm_r3_acc_man utility of CONTROL-M option for R/3 to modify the R/3 Language account fields to single-letter values. Note that single-letter language values are case sensitive. For example, D stands for German, while d stands for Serbo-Croatian. The single-letter values for languages can be found in the SPRAS field of SAP table T002. For more information on using one or two letters to represent languages, refer to SAP documentation and SAP Note 92012.
To convert an account definition 1 Enter the conr3acc command and the full path and filename of the account file that
you want to convert, on the command line, as shown in the syntax example below:
conr3acc $HOME/r3/data/acc_file
2 Press <Enter>. CONTROL-M/CM for SAP takes the information from the
CONTROL-M/Option for R/3 account file, and creates a new file, based on this information, located with all CONTROL-M/CM for SAP accounts file. The account definition is automatically saved.

The following table describes where to find information about tasks related to this one.
Subject Adding a new account. Location Adding a new account on page 102
151
Converting CONTROL-M Option for R/3 jobs

The Conversion utility (ctmr3con) enables you to convert jobs defined previously for CONTROL-M Option for R/3 into jobs that can be run and monitored using CONTROL-M/CM for SAP.
NOTE
This utility can convert both command line jobs, and jobs that use the Grid functionality in Enterprise Controlstation 6.0.0x. For more information regarding which jobs can be converted, see What can be converted? on page 154.
Before you begin
You must use CONTROL-M/EM version 6.2.01 or later. This means that scheduling tables that were created using earlier Grid functionality must first be migrated to CONTROL-M/EM 6.2.01 and then exported, as described in Step 1, below. Open a new DOS prompt window.
NOTE
The conversion utility can only be run if you are using a Windows operating system.
To convert jobs 1 In CONTROL-M/EM, export the scheduling table that you want to convert, using
the exportdeftable utility. For more information about the exportdeftable utility, see the CONTROL-M/Enterprise Manager Utility Guide.
2 Run the conversion utility from the temporary directory using the following
command:
ctmr3con [-IN_FILE <input_file>] [-OUT_FILE <output_file>] [-JOB_MAN_DEF_MODE {CREATE|DEFINE|MODIFY|RUN_ COPY|RUN_ORG|WAITONLY}] [-RUN_COPY_MODE {LAST|FIRST|LAST_SCHEDULED| FIRST_SCHEDULED}] [-HELP]
NOTE
This syntax is applicable for both Microsoft Windows and Unix operating systems. However, in Unix you may need to add ./ before ctmr3con (for example, ./ctmr3con -IN_FILE abc.xml -JOB_MAN_DEF_MODE RUN_ORG).
152
Table 34
Parameter -IN_FILE
Conversion utility parameter descriptions

Description and default value Input file. Default name: db_out.xml Note: <input_file> in the above syntax represents the exported scheduling table file.
-OUT_FILE
Output file. Default name: <input_file>_conv_output.xml For example, if the input file name is em_out_file.xml, the output file would be em_out_file_conv_output.xml.
-JOB_MAN_DEF_MODE
Specifies the default function to be performed by the Job Manager utility. Default value is RUN_COPY. Note: For more information, see the CONTROL-M for R/3 Administrator Guide.
-RUN_COPY_MODE
Indicates which instance of the job should be copied if the -run_copy parameter is set without a specific -cnt (count) number. Default value is LAST_SCHEDULED. Note: For more information, see the CONTROL-M Option for R/3 Administrator Guide.
The conversion utility should be run only from the directory in which it is located.
3 Before importing the new scheduling table into CONTROL-M/EM, either delete
the original scheduling table (using the Local Delete functionality), or rename it.
4 In CONTROL-M/CM for SAP, the SAP Job Name (SAP panel) and CONTROL-M
Job Name (General panel) parameters are linked and dependent upon each other. When running the Conversion utility, if the value of the -job parameter (from CONTROL-M Option for R/3) is not the same as the CONTROL-M Job Name, the linkage described above can lead to problematic results. The following workaround can be performed in order to disconnect the two parameters:
A Close the CONTROL-M/Enterprise Manager GUI and the CONTROL-M

Desktop.
B On the computer that is running CONTROL-M/Desktop, back up the SAP1.xml

file from the following location: for versions of CONTROL-M/EM earlier than 6.3.01
%programfiles%\BMC Software\CONTROL-M EM <version>\Data\ ECSApplicationForms
153
for versions of CONTROL-M/EM 6.3.01 and later

%programfiles%\BMC Software\CONTROL-M EM <version>\ <EM instance>\Data\ECSApplicationForms
C Delete the following lines from this file:

<PAIR> <AEV>SAPR3-JOBNAME</AEV> <DB>DBF_DEF_JOB_JOB_NAME</DB> </PAIR>
NOTE
1. This will disable linkage for all CONTROL-M/CM for SAP jobs. 2. If you define Extraction or Interception rules in the Extractor utility, ensure that the Template Job Name relates to the CONTROL-M Job Name parameter, not to the SAP Job Name parameter.
5 Run the deftable utility on the output file (converted scheduling table). The output
file name is displayed at the end of the conversion utilitys output (see Step 2 on page 152). The jobs in the selected scheduling table are converted. For more information about the deftable utility, see the CONTROL-M/Enterprise Manager Utility Guide.
What can be converted?

Jobs for the following CONTROL-M Option for R/3 utilities can be converted, using this patch:

ctm_r3_xjob_man ctm_r3_job_man ctm_r3_bi_mon ctm_r3_xvar_mon ctm_r3_var_man (except the copy variant function) ctm_r3_xutils (for raise event functionality only)
Jobs for the following CONTROL-M Option for R/3 utilities cannot be converted:

ctm_r3_job_mand ctm_r3_xjob_mand ctm_r3_job_mon ctm_r3_xjob_mon ctm_r3_xutils (for all functionality except raise event)
154
NOTE
The ctm_r3_job_mand and ctm_r3_xjob_mand utilities are not converted because CONTROL-M/Control Module for SAP has a built-in tracking facility, rendering these utilities redundant. If you are no longer using CONTROL-M Option for R/3, you can stop using jobs containing these utilities or delete these jobs.
Standard versus extended mode operations

Standard and Extended modes are defined in CONTROL-M/Control Module for SAP on a global level during run time. Standard mode or Extended mode is selected using the Account Management utility. This is different from CONTROL-M Option for R/3, in which you could define Standard or Extended mode at the job definition level. Converted jobs acquire the selected mode during run time, according to what is defined with the Account Management utility.
Known issues
The following table describes special considerations and limitations for conversion of certain parameters or utilities: Table 35 Problem parameters
Clarification / remarks The Copy Variant function is not supported. Not supported. Not supported for creating new steps (not existing steps) Mandatory, unless the -pass parameter is entered. For jobs without the -acc parameter that are based on parameters in the configuration file, see the explanation of the -pass parameter, below. The account name (as represented by the -acc parameter) is left as is. The assumption is that the account conversion utility (conr3acc) was used successfully and that the new account name is identical to the original one. -pass This parameter is ignored if an -acc parameter is indicated. (See the explanation of the -acc parameter above.) If this parameter exists, the user must create an account called DEFAULT, as jobs are converted using enter an account named DEFAULT. -cancel -debug Not supported. This parameter is ignored. Debugging information is recorded by CONTROL-M/Control Module for SAP according to the debug level configured in CONTROL-M/Agent. For more information, see the section describing the Configuration Management utility in the CONTROL-M/Agent Administrator Guide.
Parameter / feature ctm_r3_var_man -list -modify -acc
155
Table 35
Problem parameters
Clarification / remarks Only jobs with a -start value of Y are converted. The -wait parameter is ignored.
Parameter / feature ctm_r3_bi_mon
-rfc_trace Any unknown parameter Redirection (> or >>)
Not Supported. Job is not converted and an error message is issued. Redirection symbols at the end of a command line of a job are left as is. However, this is only when jobs are converted to a command line. Redirection symbols are removed from the command line of jobs that are converted to CONTROL-M/Control Module for SAP jobs, with a tasktype of JOB.
Output command line Not supported. length greater than 512 characters MemLib and MemName When migrating from CONTROL-M Option for R/3 to CONTROL-M/CM for SAP, the MemLib and MemName parameters are overwritten, even when the values of the parameters are not empty. For more information, see The MemLib (Path) field on page 156.
The MemLib (Path) field

During conversion, the MemLib and MemName fields maintain their original values if the fields are not empty. The conversion utility enters a default value if the fields are empty. However, the MemLib field is still overwritten when you open the job editing form unless you perform the following steps:
1 Close the CONTROL-M/Enterprise Manager GUI and the CONTROL-M Desktop. 2 On the computer that is running CONTROL-M/Desktop, back up the SAP1.xml file
from the following location: for versions of CONTROL-M/EM earlier than 6.3.01
%programfiles%\BMC Software\CONTROL-M EM <version>\Data\ ECSApplicationForms
for versions of CONTROL-M/EM 6.3.01 and later

%programfiles%\BMC Software\CONTROL-M EM <version>\ <EM instance>\Data\ECSApplicationForms
3 Remove the following lines from the SAP1.xml file:
156
<PAIR> <AEV>SAPR3-PATH</AEV> <DB>DBF_DEF_JOB_MEM_LIB</DB> </PAIR>
4 Save the SAP1.xml file. 5 The MemLib field is mandatory for all Product Short jobs. After the changes
described above, the default value will no longer be entered automatically. Therefore, you must ensure that the MemLib field in the SAP Skeleton contains a non-empty value, for example, Not in use for Sap jobs. Failing to do this will cause new SAP jobs to fail if the Memlib field value is not specified.
157
158
Appendix
Extracting and monitoring jobs

This appendix describes the CONTROL-M Extraction utility (ctmextract), with which you can monitor and extract SAP jobs to CONTROL-M. While this functionality has been surpassed for the most part by the Extractor Management utility (as described in Configuring and working with the Extractor Management utility on page 111), there are still instances when you need to use the ctmextract utility, including the following:

if the XBP 2.0 interface is not installed on your SAP system when extracting job definitions
The ctmextract utility can be used to
create one or more mirror-image jobs by using criteria identical to that of specific jobs already running in SAP These are then monitored using the CONTROL-M ctmcreate utility (but are not submitted). This enables CONTROL-M to track the progress of the actual job in SAP. This mirror image is stored in the Active Jobs file in the CONTROL-M/Server database. For more information, see Monitoring SAP jobs with the ctmextract utility on page 164.
define one or more jobs in CONTROL-M, by using criteria identical to that of specific jobs defined in the SAP database It does this and uses the CONTROL-M ctmdefine utility to store these jobs in the CONTROL-M definition environment. For more information, see Extracting job definitions with the ctmextract utility on page 166.
To perform either of these actions, you must create a rule file, as described in Defining a rule file with the ctmextract utility on page 160.
Appendix A Extracting and monitoring jobs
159
Defining a rule file with the ctmextract utility

Use this procedure to create a rule file. A rule file is required in order to use the ctmextract utility to either monitor SAP jobs with ctmcreate, (Monitoring SAP jobs with the ctmextract utility on page 164) or to extract job definitions to CONTROL-M using ctmdefine, (Extracting job definitions with the ctmextract utility on page 166).
Before you begin
If you are working in a Microsoft Windows environment, ensure that you have a DOS window running. If you are working in a Unix environment, ensure that you are logged in to a CONTROL-M/Agent account.
To create a rule file 1 Open a new text file, in a text editor program. A rule file should be structured in
two sections, as described in the following example:
The first section indicates which job definitions are to be monitored or extracted, by setting the selection criteria for the job (described below). The second section specifies whether to monitor the job (ctmcreate), or extract its definition to CONTROL-M (ctmdefine), described on page 163.
[CONDITION1] %%SAPR3-JOBNAME SH_CR15 %%SAPR3-ACCOUNT CM2 %%SAPR3-OWNER SH*
2 In the first section of your rule file, set AutoEdit variables under the [CONDITION1]
string. The AutoEdit variables available are described in Table 36 on page 161. Type the required AutoEdit variables, and save.
160
Table 36
Rule file AutoEdit parameters (part 1 of 2)

Description Name of account (connection for this query). Mandatory. Free text
AutoEdit Variable %%SAPR3-ACCOUNT
%%SAPR3-JOBNAME
Name of the job in SAP. Can be either a specific or generic name. Note: If a SAP job name contains spaces, (for example, JOB GOLD1) the corresponding CONTROL-M job name is the same, with underscores replacing the spaces (for example, JOB_GOLD1). Mandatory. Free text Note: In a Job Name, SAP perceives an underscore _ and a space to be the same character. This means that, two jobs, named respectively JOB GOLD and JOB_GOLD, for example, would be recognized as the same job. This is a known SAP problem.
%%SAPR3-OWNER
Owner of the job in SAP Valid values are any generic value. Example: * Mandatory
%%SAPR3-JOBCOUNT
CCMS job number Free text
%%SAPR3-JOBGROUP
Summary of jobs for a group Free text
%%SAPR3-FROM_DATE
Scheduled start date for CCMS job Valid format is: YYYYMMDD
%%SAPR3-FROM_TIME
Scheduled start time for CCMS job Valid format is: HHMMSS Note: This parameter depends on the specification of both %%SAPR3-FROM_DATE and %%SAPR3-TO_DATE for the same day.
161
Table 36
Rule file AutoEdit parameters (part 2 of 2)

Description Scheduled end date for CCMS job Valid format is: YYYYMMDD
AutoEdit Variable %%SAPR3-TO_DATE
%%SAPR3-TO_TIME
Scheduled end time for CCMS job Valid format is: HHMMSS Note: This parameter depends on the specification of both %%SAPR3-FROM_DATE and %%SAPR3-TO_DATE for the same day.
%%SAPR3-EVENT_ID
Background event ID Free text
%%SAPR3-EVENT_PARAM
Background event parameter Free text
%%SAPR3-RELEASED
Status of CCMS job Valid values are: X/N (default X)
%%SAPR3-READY
%%SAPR3-ACTIVE
%%SAPR3-FINISHED
%%SAPR3-CANCELED
162
Following is an example of the second section of a rule file:

{[CTMCREATE]|[CTMDEFINE]} NODEGRP TLVW2K065 GROUP SAP1 %%SAPR3-ACCOUNT CM2
The second section depends on whether you want to monitor or extract job definitions. As indicated in the example, you must choose either [CTMCREATE] or [CTMDEFINE], as required:
Choose [ctmcreate] to create one or more jobs that monitor identical jobs already running in SAP. For more information, see Monitoring SAP jobs with the ctmextract utility on page 164. Choose [ctmdefine] to extract job definitions from SAP into the CONTROL-M/Server database. For more information, see Extracting job definitions with the ctmextract utility on page 166.
3 Set the parameters for the second section. See Table 37 for a full list of parameters.
All parameters are mandatory, regardless of whether you choose to monitor or extract job definitions.
NOTE
All parameters described in Table 37 exist in both utilities, except where otherwise indicated.
Table 37
Parameter NODEGRP
Mandatory parameters for ctmcreate and ctmdefine

Description Node group. Valid value: Agent name. Mandatory when CONTROL-M/Server and CONTROL-M/Agent are not installed on the same computer.
%%SAPR3ACCOUNT GROUP TABLE
Account name (where the connection parameters to the SAP server are set). Relevant CONTROL-M/Server group name (for ctmdefine-set actions). Relevant CONTROL-M/Server table name (for ctmdefine-set actions).
NOTE
You can define any CONTROL-M parameter accepted by either the ctmcreate or ctmdefine utilities. For a detailed description of all CONTROL-M job parameters, see the CONTROL-M Job Parameter and Variable Reference Guide.
163
Monitoring SAP jobs with the ctmextract utility

Subject Monitoring SAP jobs using the rule file you have just created. Location See Monitoring SAP jobs with the ctmextract utility on page 164
Extracting Job Definitions using the rule See Extracting job definitions with the ctmextract file you have just created. utility on page 166

Use this procedure to create one or more mirror-image jobs by using criteria identical to that of specific jobs already running in SAP. You can monitor them using the CONTROL-M ctmcreate utility, although they were not submitted by CONTROL-M. This enables you to track the progress of the actual job in SAP. The mirror image is stored in the Active Jobs file in the CONTROL-M/Server database.
NOTE
Mirror images are only created for jobs that do not have scheduled status.
Before you begin
To monitor the job 1 Create a rule file as described in Defining a rule file with the ctmextract utility on
page 160.
2 Enter the following command:

ctmextract -CM_APPL_TYPE SAP -RULETABLE <rule file name and path>
164
NOTE
This command line can be used as part of a CONTROL-M regular job (command line), or cyclic job. By using a cyclic job, you can repeat the job extraction according to the selected rule file.
The parameters in this command are described in Table 38 on page 165.
NOTE
To make a ctmextract instance re-extract all jobs, add -IGNORE_DUP Y to the original command, and repeat the procedure described above.
The utility runs according to the specifications in the rule file. Table 38
Parameter -CM_APPL_TYPE
Parameters for monitoring a job

Description Represents SAP as an external application. Valid value: SAP
-RULETABLE
Used to set the name and path of the rule file. Valid value is the selected rule file.
-IGNORE_DUP
Causes a ctmextract instance to re-extract all jobs, regardless of whether they were already extracted. Valid value: Y

Subject Defining a rule file to be used when monitoring jobs or extracting job definitions. Location See Defining a rule file with the ctmextract utility on page 160
Extracting Job Definitions using the rule See Extracting job definitions with the ctmextract file (as described above) that you have utility on page 166 just created.
165
Extracting job definitions with the ctmextract utility

Use this procedure to extract a job definition from the SAP database to CONTROL-M, and manage this job from CONTROL-M.
NOTE
Only jobs that have scheduled status can have their definition extracted.
Before you begin
To extract job definitions 1 Create a rule file (as described in Defining a rule file with the ctmextract utility
on page 160).
2 Enter the following command:

ctmextract -CM_APPL_TYPE SAP -RULETABLE <rule file name and path>
The parameters in this command are described in Table 38 on page 165.
NOTE
To make a ctmextract instance re-extract all jobs, add -IGNORE_DUP Y to the original command, and repeat the procedure described above.
The utility runs according to the specifications in the rule file.

166
Subject Defining a rule file to be used when monitoring jobs or extracting job definitions. Monitoring SAP jobs using the rule file (as described above) that you have just created.
Location See Defining a rule file with the ctmextract utility on page 160 See Monitoring SAP jobs with the ctmextract utility on page 164
167
168
Appendix
Related SAP Notes

The information contained in Table 39 below describes known SAP Notes that resolve problems which could occur using CONTROL-M/CM for SAP. For more information about these SAP Notes, access either the SAPNet - R/3 Frontend (previously called OSS), or the SAP Service Marketplace, at http://service.sap.com/notes.
NOTE
This may require you to install later support packages on your SAP system.
Table 39
1003941
Known SAP Notes

Description SAP BW, Process Chain: On the agent tracker process, an error occurs that the chain is not continued despite the fact that the process was completed successfully. SAP BW, Process Chain: On the agent tracker process, In very quick parallel asynchronous processes, even though one or more processes may be successful, the process chain log may not contain any instances. As a result, the chain does not continue after the successful process
SAP Note number
1005481
706292
DB2 database system. A function that checks or reads the status of a job report, and understands that the job does not exist, even though it clearly does. As 706292, for the DB6 database system. As 706292, for the SQL Server Microsoft database. Kernel corrections.
888681 756201 792850 903329
Appendix B
Related SAP Notes
169
Table 39
1030158
Known SAP Notes

Description The FKJO_SCHEDULE report prepares jobs for a mass activity run for external job schedulers. Jobs should be created in "Scheduled" status. However, these jobs exist in 'Released' status for a short time during the report runtime before their status is changed to 'Scheduled'. This can be a problem for some external job schedulers. When an external job scheduler reads child jobs of the FKJO_SCHEDULE report, no results are shown, because scheduled jobs are not child jobs. In this situation, the jobs must have "Released" status, released and the external job scheduler must intercept these jobs. (This is a continuation of the note 1030158)
SAP Note number
1048051
1004083
This SAP note relates to the Restart from Point of Failure option in the SAP panel of the CONTROL-M/EM active environment. Process Chain jobs do not restart. CONTROL-M/CM for SAP reports that Process Chain jobs ended NOTOK, when they have actually completed successfully. This is due to an internal SAP problem. CONTROL-M/CM for SAP reports that R/3 jobs ended NOTOK, when they have actually completed successfully. This is due to an internal SAP problem. Load ABAP fails with error 101 - Call back function with events called. When you activate the process chain using the RSPC_API_CHAIN_START function, the E_LOGID parameter is empty but no exception is triggered. BP_JOB_SELECT: Optimizing the job selection (See also SAP Note 715355; After you import SAP Note 715355, jobs may not be selected correctly.) See the following Flash: "BMPM009945 Jobs in Copy mode end in failure after updating the SAP Basis SP level". If you want to create jobs with the After Event start condition, this note must be installed in your SAP system. Due to an internal SAP problem, jobs intercepted by SAP fail to start running and are assigned a status of NOTOK in CONTROL-M. See the following Flash: "CONTROL-M fails to start Intercepted jobs, and displays an error message". Intercepted jobs are released and started by SAP just after being intercepted. As a result, the Interception functionality is unusable. See the following Flash: "Intercepted jobs are released by SAP". BAPI_XBP_REPORT_SEARCH: Empty report names in output In XBP 2.0, Load ABAP does not provide the full list of ABAP programs. This is a SAP problem. Job count cannot be created. When restarting a Process Chain from point of failure using CONTROL-M, irrelevant processes are also started.
1059049
1016441
856780 790615 839526
835846
833777 782127
756901
732350
728947 699144
170
Table 39
677081
Known SAP Notes

Description Data Archiving: Delete and Store jobs may not be recognized as children of the Write job. This SAP Note must be implemented when working with the CONTROL-M solution for Data Archiving with XBP 2.0 functionality. Severe problems when working with Business Information Warehouse. This SAP Note must be applied to your SAP system when working with CONTROL-M solution for Business Information Warehouse. Jobs become stuck in "Released" status instead of being executed. When copying a job, the Spool List Recipient is not copied. Short dump with BAPI_XBP_REPORT_SEARCH This SAP Note relates to bug number BMPM008968 (No support of comma as decimal point in numeric fields). For more information, see the CONTROL-M/CM for SAP Release Notes, FD5311. Jobs are created with the wrong job class. Slow reaction of certain BAPI functions can affect the Extractor Management utility performance, and the loading of job names in the Job Editing form. Incorrect print parameters for XBP (Version 2.0) In XBP 2.0, the Use ABAP Program default does not work properly. This is aSAP problem Authorization checks are not performed when releasing intercepted jobs. A composite SAP Note on XPB 2.0. When a parent job name contains a period ("."), the child job is not always registered as such, causing the parent job to finish without waiting until the child job has finished. Spool list recipient is lost when you use XBP. Data Archiving: This SAP Note should be implemented when using XBP 1.0 on SAP 4.6C. Importing CONTROL-M Function Modules to Unicode SAP systems. See also Step 4 - Importing the CONTROL-M/CM for SAP utilities to the CONTROL-M Configuration Manager on page 37. Due to CONTROL-M usage, the SAP table TXMILOGRAW rapidly increases in size. To resolve this problem:
SAP Note number
664830
654802 641175 635095 628917
612564 610480
609462
605483 604496 602683
487374 458670 330267
182963
Follow general instructions for configuring Standard Jobs, as described in SAP Note 16083. If this does not resolve the problem, configure SAP_REORG_XMILOG to delete XMI logs more frequently. When using SAP releases earlier than 4.6C, follow the instructions in SAP Note 182963.
Appendix B
Related SAP Notes
171
Table 39
101146 16083
Known SAP Notes

Description Problems with background processing authorizations A review of Standard Jobs and Reorganization jobs. See also SAP Note 182963.
SAP Note number
172
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
Index
A
ABAP description 12 ABAP Program parameter Add ABAP window 62 Account Management window 98, 108, 113 Account parameter Data Archiving 84 SAP panel 52 SAP-BW 92 Account parameters 100 Accounts checking configuration 106 converting definitions 150 defining 28, 32, 102 handling 98 Activating Extractor process 130 Add ABAP window parameters 62 Add External Program window parameters 69, 71 Altering variant parameter values 141 Archive ID parameter Add ABAP window 62 Archive Mode parameter Add ABAP window 64 Archive Text parameter Add ABAP window 62 Archiving Object parameter Data Archiving 84 Audit Level parameter 109 Authorization 25 SAP user 100 Authorization parameter Add ABAP window 62 creating 88
C
Check Sessions parameter Data Archiving 84 Check Variant parameter Data Archiving 85 Client parameter ctmr3acc utility 100 Columns parameter Add ABAP window 62 Configuration management utility 107 Configuring environment XBP 2.0 83 conr3acc utility 150 CONTROL-M Function Modules 38 CONTROL-M functionality 11 CONTROL-M Job Name parameter SAP-BW 92 CONTROL-M/Option for R/3 existing installation 21 conversion 43 Conversion utility installing 43 uninstalling 43 conversion utility 43 Conversion Utility parameters 153 Converting account definitions 150 Converting R/3 jobs 152 Copy From Step parameter SAP panel 52 Copy Spool To parameter Data Archiving 85 Creating template 46 creating 46 creating a job 48 CTM interception rules 120 CTM interception rules parameters 119 ctmcreate parameters 163 ctmdefine parameters 163 ctmextract utility 159 ctmr3cfg utility 155 ctmr3req utility 140, 148
B
Background Job Count parameter SAP-BW 95 Background Job Name parameter SAP-BW 92 BMC Software, contacting 2 Business Warehouse 88 Business Warehouse job
Index
173
customer support 3 activating on Windows 130
D
DA transport 42 Data Archiving 18 workflow XBP 2.0 20 Data archiving 75 creating a session with XBP 2.0 76 defining a job 79, 81 Data archiving sessions, drafts 76 Defining accounts 102 Data Archiving job 79, 81 Data Archiving session with XBP 2.0 76 job skeleton 47 jobs 146 rule file 160 SAP-BW job 88 user exit 129 Delete After Print parameter Add ABAP window 62 Delete job 75 Delete job template 76 XBP 2.0 19 Deleting jobs 145 Department parameter Add ABAP window 63 Detect job 75 Detect Spawned Jobs button SAP panel 52 Detect Spawned Jobs parameter Data Archiving 85 Detecting spawned jobs 127 Displaying variant details 143 Displaying variants 140 Document Type parameter Add ABAP window 63 Drafts, Data Archiving sessions 76
F
Features 11 Form Name parameter 48 Function Modules 38 installing 42
G
Group Scheduling table 76
I
Import SAP calendar utility 137 Importing SAP panel 36 transports 42 InfoPackage Description parameter SAP-BW 92 InfoPackage RNR parameter SAP-BW 95 InfoPackage Tech. Name parameter SAP-BW 93 Information Field parameter Add ABAP window 63 INITXBP2 101, 113 Installation function modules 42 importing SAP panel 36 importing transports 42 requirements 22 Intercepted jobs preventing discarding 120 Into Group parameter 120
E
Event, raising 144 Existing jobs scheduling 14 exportdeftable utility 152 Extended and Standard mode 155 Extended mode 38 Extracting job definitions 166 Extracting SAP CCMS jobs 121 Extraction rules parameters 124 Extractor 121 Extractor Management utility 111, 112 Extractor service activating on Unix 130
J
Java Runtime Environment 25 Job Class parameter Data Archiving 86 SAP panel 53 Job Count parameter SAP panel 53 Job definitions, extracting 166 Job Editing form illustration 49 Job interception XBP 2.0 19 Job Mode option buttons SAP panel 53 Job Mode parameter Data Archiving 86
174
Job Name parameter 119 Data Archiving 86 SAP Panel 54 Job skeleton defining 47 job_define action parameters 146 job_delete action parameters 145 job_modify action parameters 148 Jobs cancelling 74 controlling 15 converting 152 defining 146 deleting 145 extracting 121, 159 modifying 147 monitoring 15 running 15 scheduling 14 spawned 127 statuses 16 jobs creating 48
O
Object Type parameter Add ABAP window 63 Output Device parameter Add ABAP window 64 Owner parameter Add ABAP window 64 Add External Program window 70, 72
P
Parameters 70, 72 Add External Program window 69, 71 avoiding discarded intercepted jobs 120 Client 100 conversion utility 153 CTM Interception Rules 119 ctmcreate and ctmdefine 163 Extraction Rules panel 124 for monitoring a job 165 job_define action 146 job_delete action 145 job_modify action 148 problems 155 raise_event action 144 rule file autoedit 161 rules viewer 125 SAP panel Active Job mode 74 SAP panel, Data Archiving 84 SAP-BW Job panel 92 spawned jobs 128 user exit script 129 var_edit action 142 var_mon action 141 var_show action 143 XBP version 101 Parameters parameter Add External Program window 70, 72 Parameters, Add ABAP window 62 Parameters, SAP panel Job Definition mode 52 Platforms 22 Preventing discarding intercepted jobs 120 Print Expiration parameter Add ABAP window 64 Problem parameters 155 Process Chain Description parameter SAP-BW 93 Process Chain ID parameter SAP-BW 93 Process Chain Log ID parameter SAP-BW 95 product support 3 Products 14 Program parameter 119
K
Known issues 155
L
Language parameter 100 Add ABAP window 63 Layout parameter Add ABAP window 63
M
Mass parallel process 17, 127 Max List Entries parameter 109 Mixed Case Job Name parameter 110 Modifying jobs 147 Monitoring jobs 15 Monitoring mass parallel processes 17 Monitoring SAP-BW jobs 94
N
Name parameter Add ABAP window 63 New Spool Request parameter Add ABAP window 63 Number of Copies parameter Add ABAP window 63
Index
175
Q
QID parameter SAP panel 55
R
R/3 jobs converting 152 raise_event action parameters 144 Raising SAP event 144 Recipient parameter Add ABAP window 64 Request utility 140 Rerun options parameter SAP-BW 95 RFC Max Retry parameter 101 RFC Retry Interval parameter 102 Rows parameter Add ABAP window 65 Rule file defining 160 Rules viewer parameters 125 Run Copy Mode parameter 110 Run Org Mode parameter 110 Running jobs 15
S
SAP account, defining 28, 32 SAP authorization 25 SAP CCMS jobs extracting and monitoring 121 SAP Cover Page parameter Add ABAP window 65 SAP Event based scheduling 131 SAP event, raising 144 SAP jobs cancelling 74 skeleton 47 status 74 SAP language 100 SAP panel illustration, Active Job mode 73 illustration, BW InfoPackage 90 illustration, BW Process Chain 90 illustration, Data Archiving 78 illustration, Job Definition mode 49 importing functionality 36 parameters, Active Job mode 74 parameters, BW 92 parameters, Data Archiving 84 parameters, Job Definition mode 52 SAP system number 100 SAP-BW jobs 88
monitoring 94 SAP-BW panel illustration, InfoPackage 94 parameters 92 parameters, Active Job mode 95 SAP-BW/Business Process Type parameter SAP-BW 93 Scheduling jobs 14 Selection Cover Page parameter Add ABAP window 65 Session Number parameter Data Archiving 86 silent installation on UNIX 30 on Windows 33 Skeleton SAP jobs 47 Skeleton Editor 47 Application Node Group field 47 Application Type field 47 SM37 transaction 16 Spawned jobs 17, 127 XBP 2.0 19 Standard and Extended mode 155 Statuses 16 Steps buttons SAP panel 58 Store job 75 Store job template 76 XBP 2.0 19 Submit Job with ASAP Option parameter Data Archiving 87 support, customer 3 Supported platforms 22 System Number 100
T
Target Host parameter Add External Program window 70, 72 Target Server parameter Data Archiving 87 SAP panel 59 technical support 3 Template 46 Template Job Name parameter 119 Template Scheduling Table parameter 119 Titles parameter Add ABAP window 65 transactions SM37 16 Transport facility 42 Transports, importing 42
176
U
Uninstalling conversion utility 43 on Unix 44 on Windows 44 Unix uninstallation 44 Upgrading 29, 30, 32, 33 on Unix 29 Use ABAP Program Default parameter Add ABAP window 66 Use Extended parameter 102 Use_Extended 38 User exit 129 User Exit parameter 119 User parameter 119 Utilities, configuration management accessing from the CONTROL-M Configuration Manager 108 accessing from the Java GUI 108 Utilities, Extractor management 111 accessing from the CONTROL-M Configuration Manager 113 accessing from the Java GUI 113 activating 130 Activating Interception and Parent/Child functions in SAP 113 CONROL-M Job confirmation 112 defining a user exit 129 detecting spawned jobs 127 extracting and monitoring SAP CCMS jobs 121 general configuration 114 initiating a mass parallel process 127 job interception and control 115 preventing intercepted jobs from being discarded in SAP 120 Utilities, Import SAP calendar 137
Windows silent installation 33 Write job 75, 76 XBP 2.0 19
X
XBP 1.0 75 XBP 2.0 76 configuring environment 83 workflow 20 XBP 2.0 functionality 38 XBP version, specifying 101
V
var_edit action parameters 142 var_mon action parameters 141 var_show action parameters 143 Variant altering parameters 141 displaying details 143 displaying list of values 140 Variant Name parameter Add ABAP window 66 Data Archiving 88
W
Wait for Termination parameter Add External Program window 70, 71
Index
177
178
Notes
*70028* *70028* *70028* *70028*

*70028*

70028

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

70028

Enviado por

Direitos autorais:

Formatos disponíveis

CONTROL-M/Control Module for SAP

Contacting BMC Software

United States and Canada

Outside United States and Canada

Restricted rights legend

Support by telephone or e-mail

Before contacting BMC

License key and password information

CONTROL-M/Control Module for SAP 6.3.01 Administrator Guide

CONTROL-M/Control Module for SAP Administrator Guide

CONTROL-M/Control Module for SAP Administrator Guide

CONTROL-M/Control Module for SAP Administrator Guide

CONTROL-M/Control Module for SAP Administrator Guide

Term BC-XBP (External Interface for Job Background Processing)

Spawned job Parent job

More about CONTROL-M

More about CONTROL-M

SAP Job Scheduling in CONTROL-M

CONTROL-M/Control Module for SAP Administrator Guide

Defining and scheduling jobs

Defining and scheduling jobs

Monitoring and controlling SAP jobs

Defining and scheduling jobs

Ended OK Ended NOTOK

Enhanced Batch Processing management

CONTROL-M/Control Module for SAP Administrator Guide

CONTROL-M solution for Business Information Warehouse

Monitoring mass parallel processes

Intercepting and controlling jobs

CONTROL-M solution for Business Information Warehouse

CONTROL-M solution for Data Archiving

CONTROL-M solution for BW Process Chains

CONTROL-M solution for Data Archiving

CONTROL-M/Control Module for SAP Administrator Guide

CONTROL-M solution for Data Archiving

Working with Data Archiving

Data Archiving session

CONTROL-M solution for Data Archiving

Sample Data Archiving session

Data Archiving workflow

CONTROL-M/Control Module for SAP Administrator Guide

Step 1 - Installation and upgrade requirements

Step 1 - Installation and upgrade requirements

CONTROL-M/Control Module for SAP Administrator Guide

Step 1 - Installation and upgrade requirements

Requirements SAP continued

Step 1 - Installation and upgrade requirements

Requirements SAP continued

CONTROL-M/Control Module for SAP Administrator Guide

Requirements SAP continued

Java Runtime Environment (JRE)

Minimum RAM Required disk space RFC library

SAP authorizations (part 2 of 3)

COMMAND HOST OPSYSTEM SPODEVICE

ACTVT CLASS ACTVT RSADMWBOBJ ACTVT RSAPPLNM RSISOURCE RSTSRCOBJ

* * 03, 16, 23, 66 * 03, 23, 49 * * *

CONTROL-M/Control Module for SAP Administrator Guide

SAP authorizations (part 3 of 3)

Authorization Object S_RS_ISRCM Object class: RS (Business Information Warehouse)

RSPCCHAIN RSAPPLNM RSPCPART ACTVT

Step 2 - Installing or upgrading CONTROL-M/CM for SAP

Step 2 - Installing or upgrading CONTROL-M/CM for SAP

Installing and upgrading CONTROL-M/CM for SAP on UNIX

To install CONTROL-M/CM for SAP on Unix NOTE