The RTA external notifications
An RTA external notification is generated when the status of a CICS® resource is not as expected. The notification can take the form of either an external message or an SNA generic alert, or both.
External messages
External messages are operator messages that are written to the MVS console by default. External messages can also be viewed from the CICSPlex® SM RTA outstanding events view (EVENT object) while a condition is active.
When a condition has been resolved, it disappears from the RTA outstanding events view (EVENT object). (However, external messages written to the RTA outstanding events view (EVENT object) view are also written to the CICSPlex SM EYULOG to provide a record of the contents of the RTA outstanding events view (EVENT object).) In the RTA outstanding events view (EVENT object), external messages are sorted in order of urgency, with the message about the most urgent condition at the top of the list. The urgency of a condition is user-defined.
External messages are issued in pairs: one message is issued at the start of a condition, and
another is issued when the condition ends. The messages all have the prefix EYUPN
. External
messages can be intercepted by automation products, such as NetView, AOC/MVS, and AOC/MVS
CICS Automation.
SNA generic alerts
CICSPlex SM can construct SNA generic alerts and transmit them, via the NetView program-to-program interface (PPI), to NetView for processing.
NetView can trap SNA generic alerts in its automation table, which can either take action itself to resolve the problem, or start some automation code from a command list (CLIST) or command processor.