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
FULL
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
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.
Chapter 4 Administrator tasks 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 CONTROL-M/Control Module for SAP Administrator Guide
Modifying the default event-based rule file
Table 23 SAP Event Based Scheduling Configuration file
Parameter Description
EXTRACT_EVENT_FROM_SAP Enables the monitoring of specified events in SAP, when the value is set to Y.
Valid values:
■
Y
■
N
(default)
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 .
Modifying the default event-based rule file
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.)
Chapter 4 Administrator tasks 133
Modifying the default event-based rule file
134
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 *
CONTROL-M/Control Module for SAP Administrator Guide
Modifying the default event-based rule file
[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 Rule File parameters (Part 1 of 3)
Parameter
[Condition]
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
.
Indicates account as defined by the CONTROL-M/CM for SAP account utility.
Valid characters:
Alphanumeric
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]
The SAP event ID.
Valid characters:
Alphanumeric and the asterisk (*) wildcard.
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
.
Chapter 4 Administrator tasks 135
Modifying the default event-based rule file
Table 24 Rule File parameters (Part 2 of 3)
Parameter
JOBNAME
Description
Mandatory CTMORDER parameter.
Name of the job to be ordered.
SCHEDTAB
GROUP_ID
AutoEdit variable
ODATE
[CTMCONTB]
Note:
The job specified in this parameter value should be defined in
CONTROL-M/EM before the SAP Event Based Scheduling utility is run.
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.
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
.
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.
136 CONTROL-M/Control Module for SAP Administrator Guide
