Interim WTOs
Interim WTOs are collected from the time when the MainView AutoOPERATOR PAS ASID terminates through shortly after the MainVIew AutoOPERATOR BBI-SS PAS re-starts. This includes about 5 WTOs at the very start of the MainView AutoOPERATOR BBI-SS PAS initialization. You cannot trap 100% of the messages during termination through initialization of the BBI-SS PAS that is collecting interim WTOs. The Rule Processor sees these interim WTOs as HWTO events.
WTOINTRM=Y must be specified before the BBI-SS PAS shuts down and it must also be specified before the BBI-SS PAS starts up.
Automating interim HWTO events can help manage situations which you know might occur during planned MainView AutoOPERATOR outages. For example, suppose you plan a brief planned outage where MainView AutoOPERATOR is recycled to pick up new maintenance. When WTOINTRM=Y is specified, you can perform delayed automation on WTOs that are issued while MainView AutoOPERATOR was not active
The BBI-SS PAS issues the following message indicating that it will collect interim WTOs:
AA3002I WILL CAPTURE INTERIM WTOS FOR LATER HISTORICAL PROCESSING
The CSA table that collects interim WTOs can collect about 100,000 WTOs. When the table is full, no more WTOs are collected and the following message is issued:
DX0100I MainView AutoOPERATOR INTERIM WTO TABLE IS FULL xxxx
The CSA table is deleted after the BBI-SS PAS is restarted and the HWTOs are passed to the Rule Processor. The following message is issued:
AU0320I REPLAYED nnnn INTERIM WTOS
Note
If you specify a COLD start, the captured interim WTOs are lost. The COLD start frees CSA (including CSA used to store interim WTOs). A COLD start may also be forced by applying certain BMC PTFs.
In addition, if the MainView AutoOPERATOR BBI-SS PAS terminates abnormally, the interim WTO feature is not available. The ability to save interim WTO runs as part of a normal BBI-SS PAS termination.
Comments
Log in or register to comment.