convert from IDMSINTL to IDMSINTC for CICS programs accessing IDMS

Products

• IDMS
• IDMS - Database

Issue/Introduction

What is the procedure for changing from IDMSINTL to IDMSINTC for CICS programs that issue IDMS DML?

Environment

Release: All supported releases.

Resolution

1. If using UCFCICS, then there must already be a working IDMSINTC interface because UCFCICS can only use IDMSINTC. However, that IDMSINTC interface will have been assembled with a different CWADISP than the IDMSINTL interface being used for CICS application programs that issue IDMS DML.
   
   
2. In the CICS CSD, there must already be a TRANSACTION definition that invokes the 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 IDMSINTC that will service the existing CICS programs that issue IDMS DML, assemble the CICSOPT with CWADISP that matches the CWADISP in the IDMSCINL stub currently linked with the user programs, AND if there is already an IDMSINTC used for UCFCICS, then this new IDMSINTC 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, just create a new IDMSINTC that matches the CWADISP in the IDMSCINL stub linked with the user programs.
   
   
4. Then delete the CICS CSD PROGRAM definition for the old INTL interface, define the new IDMSINTC PROGRAM and be sure that the TRANSACTION invokes the new IDMSINTC instead of the old IDMSINTL. If there is already an IDMSINTC for UCFCICS, there will now be two unique transactions that invoke the two unique IDMSINTC programs, and delete the old IDMSINTL definition so there will not be two interfaces started with the same CWADISP.
   

Additional Information

Standard CICS Interface