Installation and Configuration › Key Changes from Previous Releases

Key Changes from Previous Releases

CA IDMS Version 18.0 introduces several enhancements in the installation and configuration process to conform to CA’s software delivery standards. These enhancements both simplify the installation process and make applying maintenance and upgrading to new releases easier. However, these new enhancements may also have an impact on some of the procedures you have used in the past to configure CA IDMS.

The following enhancements apply to all CA IDMS Version 18.0 installations regardless of operating system or the tools used to do installation and configuration:

• The entire CA IDMS family of products is installed at all sites. Identification of the specific products to be used in an operational environment takes place during configuration. For more information about how products are identified, see Product Intent Declaration.
• Site-specific customizations such as option modules and exits are either linked independently or with stub modules that will rarely, if ever, require maintenance updates. For more information about what this enhancement means and how it impacts your configuration procedures, see Separation of User-configured Modules.
• Tailored load and source modules created during configuration are placed in libraries separate from those libraries that are populated during installation and deployment. These libraries are referred to as custom libraries. For more information about CA IDMS libraries and their use, see the Installation Guide.
• Optional APARs are no longer used to tailor CA IDMS behavior. In Version 18.0, optional APARs are replaced either with syntax or numbered options implemented through flag settings in the RHDCOPTF module. For a list of the optional APARs that have been eliminated and how to achieve equivalent Version 18.0 functionality, see Optional APAR Replacement.

The preceding changes make applying maintenance and upgrading to new releases easier because most customizations need not be redone. If maintenance or release upgrade impact a customization, the preceding strategy makes reimplementing the customization easier.