This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
We would like to force CONTROL-M jobs directly from MainView AutoOPERATOR Rules. Is this possible without using CONTROL-O?
With AutoOPERATOR 7.2, a change was made to the Rule Processor panels that have new actions where you can now directly set condition codes and force jobs running under the control of CONTROL-M.
The event type panels support two new fields that you can use in a Rule to send a FORCE JOB or a SET COMMAND command to the primary CONTROL-O or CMEM region. The new field names are:
CTM Force Job
CTM Set Cond.
If you have already implemented the AOSIVTBL sample table in your CONTROL-M environment, you must copy the new AOSIVTBL table into the existing AOSIVTBL table. For further details on field descriptions for the Rules Processor see the MainView AutoOPERATOR Basic Automation Guide, Volume 1: Using Rules - Table listing Action Specification fields and event types.
The steps required to implement the MainView AutoOPERATOR interface to CONTROL-O and CMEM are detailed in the MainView AutoOPERATOR Customization Guide (Implementing the MainView AutoOPERATOR interface to CONTROL-O and CMEM). The instructions apply to both CONTROL-O and CMEM.
Some customers have reported an error (IOAE12E ERROR IN DEFINITION, DEFINITION SCREEN CANNOT BE BUILT) when viewing the AOSIVTBL rule table using CMEM and not CONTROL-O. CMEM is a reduced version of CONTROL-O and only CONTROL-O supports setting IOA variables from AutoOPERATOR. The AOSIVTBL rule table cannot be viewed as a CMEM table, only as a CONTROL-O table. However, it can be ordered when running CMEM.
The following command initializes the AutoOPERATOR interface from CTMCMEM.
This will give a response as shown below:
CTO83AI INITIALIZATION OF AUTOOPERATOR SUPPORT STARTED
CTO83EI SUBSYSTEM REGISTERED WITH AUTOOPERATOR INTERFACE
CTO83FI INITIALIZATION OF AUTOOPERATOR SUPPORT ENDED SUCCESSFULLY
CTO357I COMMAND ENDED SUCCESSFULLY
For further details, see the INCONTROL for z/OS Administrator Guide.
With CMEM, a CONTROL-M job can be ordered, a CONTROL-M condition can be given but adding a CONTROL-M variable with result in an error (this is supported by CONTROL-O).