1. If you use UCFCICS, then you will already have a working IDMSINTC interface because UCFCICS can only use INTC.
* But that INTC interface will have been assembled with a different CWADISP than the INTL interface you use for your CICS application pgms that issue IDMS DML..
2. Right now you will have in the CICS CSD a TRANSACTION definition that invokes your IDMSINTL interface program AND that IDMSINTL will have been assembled with a CWADISP that matches the CWADISP in the IDMSCINL stub that was linked with each CICS application program that issues IDMS DML.
* This interface module is probably defined to start as part of PLT processing at CICS startup.
3. To create an INTC that will service your existing CICS programs that issue IDMS DML you will need to assemble the CICSOPT with CWADISP that matches the CWADISP in the IDMSCINL stub currently linked with your user programs, AND if you already have an INTC used for UCFCICS, this new INTC interface module must have a unique name.
* There is no need to relink any application programs. The old IDMSCINL stub linked with them is fine, you just need to create a new INTC that matches the CWADISP in the IDMSCINL stub linked with the user programs.
4. Then delete the CICS CSD PROGRAM def for your old INTL interface, define the new INTC PROGRAM and be sure that the TRANSACTION invokes the new INTC instead of the old INTL.
So if you already have an INTC for UCFCICS, you should now have two unique transactions that invoke the two unique INTC Programs and delete the old INTL definition so you will not be starting two interfaces that use the same CWADISP.