Policy Definitions for Captured Messages
Messages of interest can be captured by making definitions in the policy using the Customization Dialog. If you only need to capture and display a message, but not to automate it, for APL and MVC you can list this message in the MESSAGES/USER DATA policy item and select Capture on the AT Status Specification panel to capture it.
Messages that have a CMD or REP action defined for them or that are defined as status messages are implicitly captured. There is no need to explicitly define these messages to be captured. In fact, doing so results in capturing them twice.
For example, to define message XYZ555I to be captured, enter AS option on the Message Automation Overview panel to display the AT Status Specification panel and select the Capture option.
COMMANDS HELP
------------------------------------------------------------------------------
AT Status Specification
Command ===>
View or change specifications for message: XYZ555I
Application / MVC Component status Monitor health status
_ ACTIVE Starting _ NORMAL Resource shows good results
_ UP Available _ WARNING Resource shows degradation
_ HALTED Degraded _ MINOR More severe than WARNING
_ Terminating Received STOP command _ CRITICAL More severe than MINOR
_ Terminated Terminated normally _ FATAL More severe than CRITICAL
_ ABENDING Going to end abnormally _ UNKNOWN Health status not available
_ Abended Ended abnormally _ Check Evaluate health status
_ BREAKING Non-recoverable abending Monitor status
_ BROKEN Non-recoverable abend FAILED Monitor failed
BROKEN Monitor finally failed
Capture specification
s Capture Capture Message
DOM . . . __________________________________
This definition leads to the creation of an AT entry for message XYZ555I using the AOFCPMSG command after the next configuration build process, as shown on the Message Automation Overview panel.
COMMANDS VIEW HELP
------------------------------------------------------------------------------
Message Automation Overview
AC AT condition MS MRT action selection MF MPFLSTxx specifications
AS AT status MO MRT override IG Ignore for AT, MRT, MPF
AO AT override
Message ID : XYZ555I
Generated AT entry :
IF MSGID = 'XYZ555I' THEN
EXEC(CMD('AOFCPMSG') ROUTE(ONE %AOFOPGSSOPER%));
Generated MRT entry :
UPON ( MSGID = 'XYZ555I' )
REVISE('Y' AUTOMATE)
Generated MPF entry :
XYZ555I as
At the same time, you can also delete (DOM, Delete Operator Message) an existing message by specifying its ID in the DOM field. In the example above, to delete message XYZ666I upon capturing XYZ555I, select the Capture option and specify XYZ666I in the DOM field.
Capture specification
S Capture Capture Message
DOM . . . XYZ666I
This definition leads to the creation of an AT entry for message XYZ555I using the AOFCPMSG command with parameter DOM=XYZ666I after the next configuration build process, as shown on the Message Automation Overview panel.
Generated AT entry :
IF MSGID = 'XYZ555I' THEN
EXEC(CMD('AOFCPMSG DOM=XYZ666I') ROUTE(ONE %AOFOPGSSOPER%));
For more information about AOFCPMSG, see AOFCPMSG in Programmer’s Reference.
Messages captured this way will always have a default severity of UNUSUAL. To overrule this default, you can use the so-called pseudo message CAPMSGS. See Pseudo message ID CAPMSGS.