Running multiple versions of FM/Db2
This topic explains how you can install multiple different versions of FM/Db2.
- Different (and unique) plan and package names are used for each FM/Db2 installation.
- The FM/Db2 plan and packages are bound using the appropriate DBRM modules for each version of FM/Db2.
- Each version of FM/Db2 uses a unique FMN2POPT module, and that module must specify the correct plan name for that version of FM/Db2.
- When FM/Db2 is used to access remote Db2® systems, the plan and packages for each FM/Db2 version must be bound on every Db2® system that might be accessed using FM/Db2.
The notes below cover the situation where an existing version (say version n) of FM/Db2 is installed. A new version (say n+1) of FM/Db2 is available and will be installed. The two versions are to be run concurrently while acceptance testing is completed for the newer version.
- FMN2PLAN
- FMN2GEN
- FMN2PLPK
- FMN2GNPK
- FMN2PLND (instead of FMN2PLAN)
- FMN2GEND (instead of FMN2GEN)
- FMN2PLPD (instead of FMN2PLPK)
- FMN2GNPD (instead of FMN2GNPK)
Any new names can be selected as long as they are different to all other FM/Db2 plan and package names that are already in use.
For the new version of FM/Db2, modify the sample bind jobs FMN2BNnP and FMN2BNnK as appropriate.
Run the modified bind jobs, both the bind plan and bind package, on every Db2® system. Ensure that the DBRM library specified in the new bind job is for the new version of FM/Db2.
FMN2SSDM SSID=XXXX,PLAN=FMN2PLND,PLAN2=FMN2GEND
Assemble the new FMN2POPT module, and ensure that this is available when a user runs the new version of Db2®.
For information about modifying FMN2POPT, see Changing the default options. For information about FMN2SSDM, see FMN2SSDM.