Changing the NoDup(CICSFAST) option

Typically, an IDIOPTS DD statement is used in CICS® procedures to facilitate changes to options without the need to cycle CICS®. However, as far as the NoDup(CICSFAST) option is concerned, a limitation exists. The actual processing of the IDIOPTS data set is performed by the main Fault Analyzer module, IDIDA. This module is the main program that runs in the MVS™ attached subtask. The NoDup(CICSFAST) processing is done in the IDIXCX53 exit code before the subtask is attached. The value used for NoDup(CICSFAST) is whatever the value was set to on the previous full run of Fault Analyzer in that CICS® region (IDIDA attach). When a CICS fast duplicate fault suppression occurs (message IDI0066I), the attach of IDIDA and the reading of the options data set does not occur. Another IDIDA attach must happen before the NoDup(CICSFAST) option change is reflected down to the exit for NoDup(CICSFAST) action. This means either waiting for another unique fault (forced by creating a new abend with CECI to perform an EXEC CICS® ABEND) or the NoDup(CICSFAST) time-out to occur.

Alternatively, you can cause changes to this option to take effect immediately by using the CFA transaction to uninstall and reinstall all CICS invocation exits. See Controlling CICS transaction abend analysis.