Use of use APPLCOMPAT for Bind when migrating to DB2 v.11 NFM

book

Article ID: 40566

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

Issue/Introduction

 

Question: 

CA DB2 tools required to bind all the products Packages and Plans when migrating from one release to another of DB2.

When we migrating from DB2V10  to v.11 NFM, should the we bind packages use APPLCOMPAT(V11R1)? If so, how can it be accomplished?

 

Answer: 

CA DB2 tools products SQL are expected to function just fine with users's APPLICATION COMPATIBILITY default ZPARM value.  There is no compatibility issues with our applications that would require us to use the APPLCOMPAT option on the binds. Therefore, this bind parameter is currently not present in our bind statements. If we ever decide to use this option it will be per product package and internal rather than user controlled.

Environment

Release:
Component: GEN