The following table describes the available Control‑M/Analyzer exits:
Table 287 Control‑M/Analyzer Exits
Exit |
Description |
---|---|
CTBX001 |
Receives control for every mission order that must be placed in the Active Balancing file. For further details, see the INCONTROL for z/OS Security Guide. |
CTBX003
|
Control‑M/Analyzer database exit. Controls all access (for read, write, or update) to Control‑M/Analyzer database files (group file, basic variable definitions files and variable generation files). |
CTBX004
|
Control‑M/Analyzer Rule Activity file selection exit. This exit controls which users can see Control‑M/Analyzer invocations on the Rule Activity screen. |
CTBX008
|
This exit is used to control access to the Active Balancing file. For example, the exit checks if a user is authorized to delete a mission using the Active Balancing Environment screen. For further details, see the INCONTROL for z/OS Security Guide. |
CTBX009
|
This exit receives control for every message issued by the Control‑M/Analyzer Shout facility. It can modify the message text, change its destination or suppress it. It can also be used for special purposes, such as an interface to InfoMan or to Electronic Mail Systems. |
CTBX010
|
Extract user-defined processing exit. This exit is used to process extracted information according to user-defined specifications during processing of a DO EXTRACT statement. For more information on extract processing, see the DO EXTRACT statement in the rule definitions chapter of the Control‑M/Analyzer User Guide, and member CTBX010 in the IOA SAMPEXIT library. |
CTBX011 |
This exit processes each line outputted by the Control‑M/Analyzer DO PRINT statement before its contents are actually written as output. |
CTBX014
|
This exit is invoked by Control‑M/Analyzer during WHEN statement processing. It receives control for each line scanned by the STRING search string before the search is performed. The search criteria of the exit can be changed according to user needs. |
Parent Topic |