Installation and Configuration › Separation of User-Configured Modules

Separation of User-Configured Modules

Starting with CA IDMS Version 18.0, user-configured modules and CA-distributed code are completely separated. To achieve this separation, management of the following items have been changed:

• Option modules
• Security modules
• User exits
• CA ADS built-in functions

The CA IDMS SVC is the only load module that still contains both CA-distributed common SVC code and user-configured code consisting of a customized SVCOPTS module and an optional user exit routine. Therefore you may need to reconfigure any instances of the IDMS SVC if maintenance is applied to the CA-supplied code.

Separation of Option Modules

In Version 18.0, option modules are no longer linked with the code that uses them. Instead, they are either dynamically loaded or linked with stub modules that rarely require maintenance updates.

Note: Option modules define a set of runtime options for a CA IDMS product or component. These modules are typically created by assembling a set of source code and linking the result with the code for which the options apply.

The Separation of Option Modules from CA-delivered code impacts the following situations:

• All CICS and UCF option modules are now linked with stub modules rather than the interface itself. For more information see Interface Configuration Enhancements.
• The startup parameter module (RHDCPARM) is no longer used, eliminating the need for linking a customized CA IDMS startup routine.
• All CA IDMS Tools options modules are now dynamically loaded. For more information see Installation and Configuration Enhancements.
• The CA IDMS exit routines are no longer linked with RHDCUXIT, eliminating the need for linking these CA modules with your customized RHDCUXIT routine. The CA ADS Alive exit feature is still supported in v18 and will be used if CA ADS Alive has been installed in the CV. No further action is required to use CA ADS Alive. For more information see Simplified Tools Exit Management.
• The CICS version of DMLO is now linked in a way that separates the DMLO application from the IDMSCINT interface module. See the section DMLO in a CICS Front-End.
• The COBOL and PL/I precompilers now dynamically load their parameter module. For more information see Precompiler Parameter Module.
• CA Culprit for CA IDMS now dynamically loads its parameter module. For more information see CA Culprit for CA IDMS Profile Module.

Precompiler Parameter Module

In Version 18.0, the COBOL and PL/I precompilers dynamically load a parameter module. This module lets you tailor the behavior of the precompilers without having to relink the precompilers when maintenance is applied.

In previous releases, you tailored default precompiler behavior by assembling an EDBPPARM module and linking the result with the precompiler. In Version 18.0, you create a parameter module in a similar way, but link the result into your custom load library as a stand-alone module called IDMSPPRM. The COBOL and PL/I precompilers dynamically load this module at runtime.

For more information about precompiler parameters, see the DML Reference – COBOL Guide or DML Reference - PL/I Guide.

z/OS assemble and link

To create a precompiler parameter module in z/OS, execute the z/OS Assemble and Link-edit JCL substituting the name of your IDMSPPRM source member and inserting the following binder statements:

 SETOPT PARM(AMODE=31,RMODE=ANY)    
 NAME IDMSPPRM(R)

CA Culprit for CA IDMS Profile Module

In Version 18.0, Culprit dynamically loads a profile module. As a result, you can tailor the behavior of Culprit without having to relink modules when applying maintenance..

In previous releases, you tailored default Culprit behavior by assembling a CULXPROF module using the CULMPROF macro and linking the result with various Culprit CUSTLIB programs. In Version 18.0, you create a profile module using the same macro, but link the result into your custom load library as a stand-alone module named CULPPROF. Culprit dynamically loads this module at runtime.

Note: For more information about profile parameters, see the CA Culprit for CA IDMS Reference Guide.

z/OS assemble and link

To create a Culprit profile module in z/OS, execute the z/OS Assemble and Link-edit JCL substituting the name of your CULPPROF source member and inserting the following binder statements.

 SETOPT PARM(AMODE=24,RMODE=24)    
 NAME CULPPROF(R)