Current release to previous release support

This support enables objects (such as programs and files) that are created and saved on the current release to be restored and used on a previous release.

Object compatibility is provided for in many languages and most object types are supported on both release levels if the objects use only functions from a previous release.

You can enable current release-to-previous release support by using the target release (TGTRLS) parameter on create and save commands.

Table 1 illustrates the TGTRLS parameter and values available for the current and previous releases. Refer to this table to determine the valid values for the release currently on your system.

The TGTRLS values must use the form VvRrMm.

Table 1. Values for TGTRLS parameter
Current IBM i release *CURRENT *PRV Other valid values
Start of changeV7R6M0End of change Start of changeV7R6M0End of change Start of changeV7R5M0End of change Start of changeV7R4M0End of change
V7R5M0 V7R5M0 V7R4M0 V7R3M0
V7R4M0 V7R4M0 V7R3M0 V7R2M0
V7R3M0 V7R3M0 V7R2M0 V7R1M0
V7R2M0 V7R2M0 V7R1M0 V6R1M0
V7R1M0 V7R1M0 V6R1M0 V5R4M0
V6R1M0 V6R1M0 V5R4M0 V5R3M0
V5R4M0 V5R4M0 V5R3M0 V5R2M0

This support is useful to the following situations:

  • A network enterprise with some current release systems and previous release systems.
  • An application development business with a single system on the current release that supports customers who might still be on the previous release.

Current release-to-previous release support provides great savings and productivity improvements to application developers. By using this support, most network enterprises and application development businesses no longer need to maintain two development systems. (For example, two development systems might contain a previous-release system that contains previous-release objects, or a current-release system that contains current-release objects.) Usually this support enables previous release and current release objects to exist on one development system.