For installations with multiple databases, you should migrate all your databases to the current level. All users have the same features available to them, and future database migrations are easier.
Applications at any supported release level can access application servers at any supported release level. However, if an application requester and application server are at different release levels, any functions used must be available in both release levels. That is, you cannot use any new release facilities from ISQL, DBS Utility, or application programs when the application server is running a different level of DB2 Server for VSE & VM than the application requester.
All existing applications that accessed a database before the database was migrated to another release level continue to work after migration.
| Note: | Changes were required in Version 7 Release 1 to handle file
I/O correctly when using CMS 15 and later. These changes affect the
format of data that is unloaded and reloaded by the UNLOAD and RELOAD commands
of the DBS Utility. If you use the DBS Utility's UNLOAD and RELOAD
commands with databases at different release levels, you must ensure that the
code changes have been applied at all release levels. For releases
prior to Version 7 Release 1, you must apply the following
APARs:
|
See Appendix H, Incompatibilities Between Releases for incompatibilities that exist between each release and the next release.