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.
In DB2 V10 when Falling back to a previous mode, what tasks need to be done?
Article ID: 20026
RC Compare for DB2 for z/OSBind 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/OSDatabase Analyzer for DB2 for z/OSFast Unload for DB2 for z/OSFast Check for DB2 for z/OSFast Index for DB2 for z/OSFast Load for DB2 for z/OSRapid Reorg for DB2 for z/OSEndevor Software Change Manager (SCM)Endevor Software Change Manager - Natural Integration (SCM)Endevor Software Change Manager - ECLIPSE Plugin (SCM)Endevor Software Change Manager - Enterprise Workbench (SCM)
When running DB2 V10 NFM and falling back to a previous mode such as CM8, CM9, ENFM8 or ENFM9 what tasks need to be done for the DB2 Tools?
The following needs to be done when doing a fallback on a DB2 10:
Update the SSIDMODE in the SETUPxx member for the subsystem in fallback mode to the appropriate mode: CM8*, CM9*, ENFM8* OR ENFM9*. These modes were added in r15 thru PTF's: RO48520, RO48521, RO48522, and RO48523.
In Post Install generate and run the BIND job, ssid0002 for the subsystem in fallback mode.