In DB2 V10 when Falling back to a previous mode, what tasks need to be done?

book

Article ID: 20026

calendar_today

Updated On:

Products

CA RC/Migrator CA Endevor SCM Interface DB2 Administration CA RC Compare for DB2 for z/OS CA RC Extract for DB2 for z/OS CA RC/Query CA RC Secure for DB2 for z/OS CA RC Update for DB2 for z/OS CA Bind Analyzer for DB2 for z/OS CA Detector CA SQL-Ease for DB2 for z/OS CA Sysview Performance Management Option for DB2 for z/OS CA Database Detector for DB2 for z/OS CA Plan Analyzer for DB2 for z/OS CA Subsystem Analyzer for DB2 for z/OS CA Database Analyzer for DB2 for z/OS CA Fast Unload for DB2 for z/OS CA Fast Check for DB2 for z/OS CA Fast Index for DB2 for z/OS CA Fast Load for DB2 for z/OS CA Rapid Reorg for DB2 for z/OS CA Endevor Software Change Manager (SCM) CA Endevor Software Change Manager - Natural Integration (SCM) CA Endevor Software Change Manager - ECLIPSE Plugin (SCM) CA Endevor Software Change Manager - Enterprise Workbench (SCM)

Issue/Introduction

Description:

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?

Solution:

The following needs to be done when doing a fallback on a DB2 10:

  1. 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.

  2. In Post Install generate and run the BIND job, ssid0002 for the subsystem in fallback mode.

Environment

Release:
Component: ENDBAS