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?

book

Article ID: 20026

calendar_today

Updated On:

Products

RC Compare for DB2 for z/OS Bind Analyzer for DB2 for z/OS SQL-Ease for DB2 for z/OS SYSVIEW Performance Management Option for DB2 for z/OS Plan Analyzer for DB2 for z/OS Subsystem Analyzer for DB2 for z/OS Database Analyzer for DB2 for z/OS Fast Unload for DB2 for z/OS Fast Check for DB2 for z/OS Fast Index for DB2 for z/OS Fast Load for DB2 for z/OS Rapid Reorg for DB2 for z/OS Endevor 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)

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
Powered by Wolken Software