DFHAC2236 error with abend code S014 can occur in an MRO CICS environment in some situations. Resolving this may require use of the BRIDGE=YES parm in the #UCFCICZ macro, even though the CICS 3270 Bridge Facility may not be explicitly in operation.
This situation can occur in any operating system, when CICS is used to invoke UCF as a way to communicate with the IDMS region.
There is a feature in CICS called 3270 Bridge Facility. CA IDMS supports this via the BRIDGE=YES parm in the #UCFCICZ macro. The term BRIDGE=YES was intended to refer to Bridge Facility Terminals. However, in IDMS, as the APAR QI85071 states, a bridge terminal is any terminal that is not considered a permanent terminal in a CICS region, for example a surrogate terminal defined in the AOR of a MRO environment.
Some shops run with a specific TOR/AOR setup in their MRO environment as follows:
With this environment, if a terminal session aborts in a TOR, then DFHZNEP is invoked in both the TOR and the associated AOR. The terminal in the TOR will be considered a surrogate terminal since it is not in the same AOR where UCFCICS and UCFCICZ are executing. Thus, for communication with this terminal to be handled correctly, the BRIDGE=YES parm in the #UCFCICZ macro must be coded in this situation also. Failure to do so can result in a DFHAC2236 error with abend code S014.
When a shop is using CICS & UCF to invoke CA IDMS, then if:
1- they are using the CICS feature called 3270 Bridge Facility;
2- the shops runs with a specific TOR/AOR setup in their MRO environment as follows:
a- DFHZNEP, programs that issue a START TRANSID and LINK to UCFCICZ, UCFCICS and UCFCICZ all execute in the same AOR CICS region; and
b- terminal sessions may run in a TOR.
In either of the two cases outlined above, the BRIDGE=YES parm in the #UCFCICZ macro must be coded. Failure to do so can result in a DFHAC2236 error with abend code S014.
Technical Note APAR QI85071 describes when a terminal is considered a bridge terminal.