ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
About the fall back for the Data sharing ENV.
Article ID: 132524
Bind Analyzer for DB2 for z/OSSQL-Ease for DB2 for z/OSSYSVIEW Performance Management Option for DB2 for z/OSPlan Analyzer for DB2 for z/OSSubsystem Analyzer for DB2 for z/OS
Prerequisite scenario; The DB2 will be upgraded V10(NFM) to V11(CM). In a data sharing group, there are two subsystems(DB2V and DB2W) exist in as follows. Lpar AI09 AI0A DB2SSID DB2V DB2W
In both subsystem, SYSVIEW for DB2 R19.0 is being used and post-installation processes for the SYSVIEW for DB2 will be performed based on the DB2 upgrade for V11(CM). After that, only one subsystem of them will be fallbacked to DB2 V10(CM). That situation is as follows. Lpar AI09 AI0A DB2SSID DB2V DB2W DB2 V11(CM) V10(NFM)
When the one of the subsystems will be fallbacked to DB2 V10(NFM), the post-installation processes will be performed for the fallbacked subsystems. If the ssid0002 job will be run for the fallbacked subsystems, the PLANs for the CA-DB2 tools in the subsystem will be rebound in DB2V10. In this situation, can the DB2V(V11) subsystem be monitored appropriately even if the PLANs for the CA-DB2 tools is rebound in DB2V10?
Yes. both subsystems can be monitored appropriately. As the SQL functionalities will not change, the Bind job (ssid0002 job) isn't needed to run after the fallback. From DB2 11 CM to DB2 10 NFM becasue Plan/Packages will be bound with same SQL functionalities and any problems should not occur. However, the SETUPxx member must be updated accordingly but you do not have to run again the Bind Job.
For CA SYSVIEW for DB2 you have to be careful with DB2VER parameter, there are only two possible values for this parameter, DB2VER=10.1 and DB2VER=11.1, it does not matter CM or NFM, you have to update the parameter in the fallback to DB2 10 NFM.
In a Data Sharing group, the DB2 Catalog is shared for all the DB2 members (DB2 Subsystems) in the group, the SQL functionalities to access this DB2 Catalog have to be the same in all the members in the group. The SQL functionalities in DB2 10 NFM are exactly the same ones as in DB2 11 CM, this is the reason you can run DB2 11 NFM and DB2 11 CM in the same group. For example, the DB2 11 CM and DB2 11 NFM cannot be run in the same Data Sharing group, this is not supported IBM, SQL functionalities in DB2 11 NFM will change after the migration from CM to NFM. The same apply for DB2 10 NFM and DB2 11 NFM, they cannot run together in same Data Sharing group.