When writing AOF rules you need to be aware that CA MIC imported messages have the following attributes:
CA MIC presents imported messages to CA OPS/MVS using the above standards, regardless of any CA MIC message editing parameter values in effect on any system. In other words, CA MIC consistently presents CA OPS/MVS with original message data regardless of the CA MIC message editing that may have taken place on a given system based on the CA MIC MIMINIT EDITMESSAGE, SYSNAME, SYSTYPE, and JOBID parameters.
When the local CA MIC subsystem is directing imported messages to the local CA OPS/MVS subsystem, it is important that AOF rules interrogate the MSG.SYNA, the MSG.REISSUE environmental variables, or both to identify the systems from which messages are originating. Otherwise, these rules may misinterpret CA MIC imported messages as being from the local system, which may result in unpredictable or incorrect actions.
The following sample AOF MSG rule allows imported CA MIC messages to be easily identified in OPSLOG. Filtering on the USER column with a value of MIC limits the display to CA MIC imported messages. The display can also be limited to those messages imported from a particular system by filtering on the COLOR column.
Note: This logic colorizes all imported messages from systems XE13, XE12, and XE07. If you only want to colorize the CA MIC imported messages, the select statement needs to be subject to the MSG.MIC = 1 condition. If you decide to implement this rule, we suggest that you merge the rule logic into any existing MSG * rules that you may have.
)MSG * )PROC if MSG.MIC = 1 then MSG.USER = "MIC" select when MSG.SYNA = "XE13" then MSG.COLOR = OPSCOLOR("TURQ") when MSG.SYNA = "XE12" then MSG.COLOR = OPSCOLOR("YELLOW") when MSG.SYNA = "XE07" then MSG.COLOR = OPSCOLOR("PINK") otherwise nop end
Copyright © 2014 CA Technologies.
All rights reserved.
|
|