This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
8.1 and up
MainView AutoOPERATOR version 8.1.00 introduced the ability to perform delayed automation for WTOs issued when AutoOPERATOR isn’t active. Can you give me a little more information on how this is done?
This is the statement in the Release Notes that someone might have seen.
You can now perform delayed automation for write to operator messages (WTOs)
that are issued while MainView AutoOPERATOR was not active. When you
enable this feature, the Rules Processor sees these historical WTOs as HWTO
MainView AutoOPERATOR sees the captured WTOs as HWTO (Historical WTO) events. You can use Rules to perform delayed automation with these events. HWTO event Rules are similar to MSG events. MSG events are WTOs that occur while MainVIew AutoOPERATOR is active. The Rule Processor sees WTOs that are collected when MainView AutoOPERATOR is briefly inactive as history (or HWTO) events.
- After IPL but before MainView AutoOPERATOR is started. These are called early WTOs.
- While MainView AutoOPERATOR is not active (such as when you restart MainView AutoOPERATOR with a WARM start). These are called interim WTOs.
This requires that you have BMC MainView Automation (product code MVN) active in the MainView AutoOPERATOR BBI-SS PAS.
A new event type was created called HWTO - Historical WTO
The event type HWTO is for early and interim WTOs that were issued when MainView AutoOPERATOR was inactive.
The HWTO event type is available only when you have the BMC MainView Automation Solution active in the MainView AutoOPERATOR BBI-SS PAS. For more information, see theMainView AutoOPERATOR Customization Guide.
HWTO events are WTOs that were issued when MainView AutoOPERATOR was inactive. There are two kinds of HWTOs:
- Early WTOs that are issued during IPL until MainView AutoOPERATOR starts
- Interim WTOs that are issued during brief planned outages of MainView AutoOPERATOR
When MainView AutoOPERATOR initializes, these saved early WTOs are available to the Rule Processor as HWTO events. The HWTO events are processed immediately after the PAS starts and do not retain the timing of the original WTO messages.
When you specify WTOINTRM=Y in BBPARM member AAOPRMxx and stop the PAS, the Rule Processor keeps running to record interim WTOs in an extended CSA table. When a WTO occurs, the WTO control block (WQE) is copied to the extended CSA table. Later when MainView AutoOPERATOR initializes, these WQEs are available to the Rule Processor as HWTO events.
This table can contain about 10,000 WQEs. Note that many WQEs may be associated with a multi-line WTO.
HWTO events are similar to MSG events because they represent WTOs. However fewer Rule actions are available and fewer Rule and EXEC variables are valid for HWTO Rules as compared with MSG Rules.
See List of variables for HWTO-initiated Rules for a list of variables that are valid in a HWTO Rule. For a list of variables that are valid in an EXEC scheduled by an HWTO Rule, see the MainView AutoOPERATOR Advanced Automation Guide
You would need to create new rules with this new event type, existing rules would not fire. You could copy an existing rule and give it the HWTO event type.
Please note the Historical WTOs facility requires special planning in order to obtain the best results. Other types of events (CIC, etc) are not captured - only WTOs (MSG) events.
For example, the HWTO events are replayed 'at full speed' with no pauses.
There is also a slight gap in time, between when the AutoOPERATOR is shutdown to when our exit starts collecting WTOs and storing them in our data space.
This is a fully supported IBM exit. Our code in the exit will collect the messages as passed to the exit and collect them in a dataspace associated with the CONSOLE address space. When the PAS starts up, our PAS code will process those control blocks, passing each in turn to the SSI processing for Rules as HWTO (held WTO) events.