A good explanation is in apar PH08482
https://www.ibm.com/support/pages/apar/PH08482
On Thu, Dec 15, 2022 at 8:39 PM Binyamin Dissen
wrote:
> Perhaps I am missing something, but the V12R1M500 is the BIND APPLCOMPAT on
> the mainframe. The client doesn't need any V12 services (or V9, for that
>
forward with DB2 upgrades
Kevin
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Binyamin Dissen
Sent: Thursday, December 15, 2022 4:39 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DB2 V12 DB2 connect v9.5 problem
EXTERNAL EMAIL – USE CAUTION: This email is from
: Thursday, December 15, 2022 4:39 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DB2 V12 DB2 connect v9.5 problem
EXTERNAL EMAIL – USE CAUTION: This email is from an EXTERNAL source. Ensure
you trust this sender before clicking on any links or attachments.
Perhaps I am missing something
Perhaps I am missing something, but the V12R1M500 is the BIND APPLCOMPAT on
the mainframe. The client doesn't need any V12 services (or V9, for that
matter).
How can I bind the PACKAGE so that the client side APPLCOMPAT (of *) is
acceptable?
Or how can I tell IBM DB2 Client 9.5 to set
Normally this is due to a back-level client driver which doesn't support
M502. Installing a new driver on the client system is the usual remedy if
M502 is really needed (function used in the applications). Otherwise you
can rebind the package specifying V12R1M500 which should work with the
I am getting
DSNL076I -DBCG DSNLXSVC DDF CONNECTION REJECTED DUE 794
TO INCOMPATIBLE APPLCOMPAT VALUES.
LUWID=P3EBC7B8.H043.DC8D7A13DC85
CLIENTAPPLCOMPAT=*
