Determines whether CICS messages that are trapped by the XTDOUT CICS exit may be deleted from the appropriate CICS transient data queue by AOF rules.
Note: When you are writing rules for CICS messages and the COF interface is active, you can determine the exit type by using the OPS/REXX OPSINFO function as follows:
var = OPSINFO('EXITTYPE')
This function returns the type of the exit in which the AOF captured the event that triggered the rule. If the exit type is CICS, the message is from the COF interface. If the exit type is MVS, either CICS issued the message through a WTO, or the COF interface issued a WTO because the WTOCICS parameter is set to YES. When the exit type is CICS and the CICSDELETE parameter is set to YES, an AOF message rule return value of SUPPRESS or DELETE has the same effect, deleting the message from the CICS transient data queue. If CICSDELETE is set to NO, the SUPPRESS or DELETE value is ignored. When the exit type is MVS, the SUPRESS and DELETE return values operate as with any z/OS message and have no effect on the CICS transient data queue.
NO
CA OPS/MVS will not allow suppression of transient data queue messages by AOF rules. CA OPS/MVS will not honor a return value of either SUPPRESS or DELETE from an AOF rule, and the CICS message appears in the CICS transient data queue.
YES
CA OPS/MVS will allow suppression of transient data queue messages by AOF rules. CA OPS/MVS honors the return value from the AOF rule.
Anytime
Example: CICSDELETE
This function permits AOF suppression of transient data queue messages:
OPSPRM('SET','CICSDELETE','YES')
|
Copyright © 2014 CA.
All rights reserved.
|
|