Customized DFHXCOPT module is not being picked up for EXCI calls

Cause

The options module is not linked properly. APAR PK17426 added a new option to DFHXCOPT called ABENDBKOUT to CICS TS V3.1. As part of the design, an ALIAS was created for DFHXCOPT called DFHXCOPE. The EXCI driving module DFHXCPRH that does the MVS LOAD for the options table was changed to FIRST load DFHXCOPE, and if that was not found, then try loading DFHXCOPT. Because you have not re-established the alias properly, DFHXCPRH does indeed find DFHXCOPE, which is still an alias for the old copy of DFHXCOPT. Your new options are never loaded.

The CICS TS information center under Using the EXCI options table, DFHXCOPT mentions that the format of the DFHXCOPT options table has changed since it was first introduced. In CICS TS for z/OS®, Version 3.2 (and, by APAR, also in CICS TS 2.1, CICS TS 2.2, and CICS TS 3.1) the table now includes a version number, which is intended to allow more flexibility for future extensions.

The JCLIN shipped with the PTF for APAR PK17426 had JCLIN that changed the SMP environment so that SMP knew about the ALIAS. However, if you have assembled and linked your customized DFHXCOPT module outside of SMP, you might not have linked it properly to re-establish the alias.

The full JCLIN is:

//DFHXCOPT JOB
//L#XCOPT EXEC PGM=IEWL,
// PARM='LIST,XREF,NCAL,RENT,REFR'
//SYSPRINT DD SYSOUT=*
//SYSLMOD  DD DISP=SHR,DSN=XXXXXXXX.SDFHEXCI
//SYSUT1   DD UNIT=SYSDA,
// DISP=(NEW,DELETE),
// SPACE=(1700,(400,400))
//ADFHMOD  DD DISP=SHR,DSN=XXXXXXXX.ADFHMOD
//SYSLIN   DD *
 INCLUDE ADFHMOD(DFHXCOPT)
 MODE AMODE(31),RMODE(ANY)
 ENTRY DFHXCOPT
 ALIAS DFHXCOPE
 NAME DFHXCOPT(R) RC=0
/*