Migration actions required for each release

This topic describes common activities and considerations that are typically required when you migrate from one release of Language Environment to another:

  1. Update the CICS® System Definition (CSD) file using the program definitions in the CEECCSD member and CEECCSDX member found in the SCEESAMP data set. Language Environment may have changed (added or deleted) load modules in this release.
  2. Update the Language Environment load modules that were placed in the link pack area (LPA). Sample members found in the SCEESAMP data set, which can be used to move load modules into LPA, should be reviewed with every release migration. See the table “Language Environment sample IEALPAnn or PROGxx members in CEE.SCEESAMP” for the list of sample members and their changed content in z/OS Language Environment Customization.
  3. If any Language Environment user exits were used at the previous release and you plan to use them with the new release, they must be re-linked using the new release of Language Environment.
  4. In z/OS® V1R7, a new parmlib member, CEEPRMxx, was added for Language Environment. You can use it to specify Language Environment runtime options for the system. Operator commands are also provided to allow you to query and update the active runtime options for the system. This simplifies the management of Language Environment options, particularly in multisystem environments. For more information, see z/OS Language Environment Customization.
Parent topic: Migrating from another Language Environment release