How to define the SETUP parameters in a DB2 Data Sharing Environment in Coexistence Mode.

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

Introduction:

When installing the products into a Data Sharing Environment it is recommended to define all DB2 subsystems to each SETUPxx CDBAPARM Parmlib member.

This particular Data Sharing Environment contains the following subsystems:

SYS0 - Group Attach Name only
SYS1 - DB2 10 CM8
SYS2 - DB2 v8 NFM

As this Data Sharing Environment is in Coexistence Mode, how should the SETUP subsystem parameters for the DB2 Load Libraries be defined?

Instructions:

The definition for the Group SSID should reflect the version that has been migrated. In this example, DB2 10 CM8.

This would be defined as follows:

 

   SYS0   
   SSIDVER (V10)   
   SSIDMODE (CM8)   
   
   LOADLIBS(   
   DB2 10 CM8 Exit and Load Libraries   
   ) 

 

The definition for the migrated member, SYS1, should contain the DB2 10 CM8 definitions:

 

   SYS1   
   SSIDVER (V10)   
   SSIDMODE (CM8)   
   
   LOADLIBS(   
   DB2 10 CM8 Exit and Load Libraries   
   ) 

 

The definition for the member that has not yet been migrated, SYS2, should contain the old version definitions for DB2 v8 NFM:

 

   DBT2   
   SSIDVER (V8)   
   SSIDMODE (NFM)   
   
   LOADLIBS( 

 	DB2 V8 NFM Exit followed by DB2 10 CM8 Exit libraries, then DB2 V8 NFM Load Library 	
 	) 

Environment

Release:
Component: ENDBAS