CA IDMS Tools › Installation and Configuration Enhancements

Installation and Configuration Enhancements

Several changes to CA IDMS Tools make installation and maintenance easier. These changes separate user generated code from CA-distributed modules so you can apply maintenance without having to redo your customization.

The following changes make installation and maintenance easier:

• You now link the CA IDMS DML/Online (DMLO) user exit program as a separate load module. DMLO dynamically loads USDMLXIT during initial startup. For more information about implementing a DMLO user exit, see the DML Online User Guide.
• The CICS version of DMLO is now linked so that changes due to maintenance or a release upgrade are unlikely. For more information, see DMLO in a CICS Front-End.
• You now link the CA IDMS/DC Sort parameter module (TPSPARM) as a separate load module since it is loaded dynamically at runtime. For more information about generating a TPSPARM parameter module, see the DC Sort User Guide.
• You now link the CA IDMS Dictionary Migrator Assistant parameter module (XDMTPARM) as a separate load module, since it is loaded dynamically at runtime. For more information about creating a CA IDMS Dictionary Migrator Assistant parameter module, see comments in the installed version of the XDMTPARM module source.
• You no longer link your IDMS CALC exit program (IDMSCLCX) with GSSCALC. The tools products now invoke the CALC exit through the named user exit facility that is new in CA IDMS Version 18.0.
• A set of CSD definitions are provided for the CICS versions of CA IDMS/DC Sort and DMLO. These definitions reside in the installed source library members TPSCICS and USDCICS.
• Use of CA IDMS Task Analyzer, CA IDMS Masterkey and CA ADS Alive no longer require linking CA-supplied exit routines with RHDCUXIT. For more information, see Simplified Tools Exit Management. For more information, see Simplified Tools Exit Management.
• Use of CA IDMS Enforcer no longer requires linking special versions of the CA IDMS compilers. Instead, CA IDMS Enforcer is now invoked based on the presence of certain modules in your runtime library concatenation.For more information, see CA IDMS Enforcer Enablement.

DMLO in a CICS Front-End

The CICS front-end version of DMLO now consists of two components:

• A module that is created by linking an IDMSCINT interface module with the CA-supplied DMLO stub module USDTPIF5.
• A new site-independent module USDTPIFC containing only CA-supplied code.

Since user-generated code is linked only with the stub module, CICS DMLO will typically not need to be regenerated as a result of applying maintenance.

Before using the Version 18.0 runtime libraries in your CICS system, you must relink any modules that include USDTPIF5. The following shows the link-edit instructions.

Note: For more information about executing DMLO under CICS, see Implementing CA IDMS DMLO in Multiple CVs Under CICS in the Installation Guide.

z/OS Link

To link DMLO for a CICS environment in z/OS, execute the z/OS Link-Edit JCL inserting the following binder statements.

 ORDER   DFHEAI,USDTPIF5                      
 INCLUDE CAGJLOAD(USDTPIF5)                       
 INCLUDE CUSTLIB(idmscint)                       
 ENTRY   DFHEAI                               
 SETOPT PARM(AMODE=31,REUS=SERIAL,RMODE=ANY)    
 NAME usdtpifx(R)

idmscint

Specifies the name of your IDMSCINT program that interfaces with the target CA IDMS CV.

usdtpifx

Specifies the name of the program that your CICS DMLO transaction invokes.

Note: Do not use the names USDTPIF2, USDTPIF3, or USDTPIFC because these module names are reserved for CA-distributed programs.

Simplified Tools Exit Management

You no longer need to link CA-supplied exits with your RHDCUXIT module. All tools exit routines are loaded and managed independently from RHDCUXIT. This means you no longer need to relink your RHDCUXIT module if maintenance or release upgrades change one of the tools exit routines.

Another benefit of the simplified tools exit management in Version 18.0 is that you no longer need to tailor a USFUEXT module to identify exits to be invoked after the tools exits. Instead, you define your exits using the normal facilities for identifying numbered exits just as if no tools exits were involved. For information on how to define numbered exits, see the System Operations Guide.

As a result of this enhancement, you may need to change the startup JCL for one or more CVs:

• CA IDMS Task Analyzer users must specify a SYSIDMS parameter of TASK_ANALYZER_EXITS=ON in any CV in which CA IDMS Task Analyzer is to be used.
• CA IDMS Masterkey users must specify a SYSIDMS parameter of MASTERKEY_EXITS=ON in any CV in which CA IDMS Masterkey is to be used.

New SYSIDMS Parameters

New SYSIDMS parameters were introduced to indicate which CA IDMS tools exits you want to enable.

MASTERKEY_EXITS=ON|OFF

ON

Enables the CA IDMS Masterkey exits. ON must be specified if CA IDMS Masterkey is to be used in a CV.

OFF

Disables the CA IDMS Masterkey exits.

Default: OFF

TASK_ANALYZER_EXITS=ON|OFF

Controls whether CA IDMS Task Analyzer exits are enabled.

ON

Enables the CA IDMS Task Analyzer exits. ON is required if CA IDMS Task Analyzer is to be used in a CV.

OFF

Disables the CA IDMS Task Analyzer exits.

Default: OFF

CA IDMS Enforcer Enablement

The way you enable the use of CA IDMS Enforcer was enhanced to eliminate the need for linking special versions of the compilers. CA IDMS Enforcer is invoked based on the presence of the following modules in your STEPLIB or CDMSLIB library concatenation at runtime:

• ENFRXITO with an alias of ENFROXIT enables the use of CA IDMS Enforcer in an online environment
• ENFRXITB with an alias of ENFRBXIT enables the use of CA IDMS Enforcer in a batch environment

Note: If you indicate that Enforcer is to be used, these modules are placed in a special Enforcer load library during configuration.