Running multiple versions of ZDT/Db2
This topic explains how you can install multiple different versions of ZDT/Db2.
- Different (and unique) plan and package names are used for each ZDT/Db2 installation.
- The ZDT/Db2 plan and packages are bound using the appropriate DBRM modules for each version of ZDT/Db2.
- Each version of ZDT/Db2 uses a unique HFM2POPT module, and that module must specify the correct plan name for that version of ZDT/Db2.
- When ZDT/Db2 is used to access remote Db2® systems, the plan and packages for each ZDT/Db2 version must be bound on every Db2® system that might be accessed using ZDT/Db2.
The notes below cover the situation where an existing version (say version n) of ZDT/Db2 is installed. A new version (say n+1) of ZDT/Db2 is available and will be installed. The two versions are to be run concurrently while acceptance testing is completed for the newer version.
- HFM2PLAN
- HFM2GEN
- HFM2PLPK
- HFM2GNPK
- HFM2PLND (instead of HFM2PLAN)
- HFM2GEND (instead of HFM2GEN)
- HFM2PLPD (instead of HFM2PLPK)
- HFM2GNPD (instead of HFM2GNPK)
Any new names can be selected as long as they are different to all other ZDT/Db2 plan and package names that are already in use.
For the new version of ZDT/Db2, modify the sample bind jobs HFM2BNnP and HFM2BNnK 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 ZDT/Db2.
HFM2SSDM SSID=XXXX,PLAN=HFM2PLND,PLAN2=HFM2GEND
Assemble the new HFM2POPT module, and ensure that this is available when a user runs the new version of Db2®.
For information about modifying HFM2POPT, see Changing the default options. For information about HFM2SSDM, see HFM2SSDM.