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 APPLCOMPAT? Don't see any obvious option or command to set it. On Thu, 15 Dec 2022 08:50:53 +1100 Attila Fogarasi <fogar...@gmail.com> wrote: :>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 :>existing back-level driver. :> :>On Wed, Dec 14, 2022 at 9:42 PM Binyamin Dissen <bdis...@dissensoftware.com> :>wrote: :> :>> I am getting :>> :>> DSNL076I -DBCG DSNLXSVC DDF CONNECTION REJECTED DUE 794 :>> TO INCOMPATIBLE APPLCOMPAT VALUES. :>> LUWID=P3EBC7B8.H043.DC8D7A13DC85 :>> CLIENTAPPLCOMPAT=* :>> PACKAGEAPPLCOMPAT=V12R1M502 :>> PACKAGE=NULLID.SQLC2G13.41414141414E4758 :>> :>> I cannot figure out how to set the client level APPLCOMPAT or bind the :>> nullid :>> package to match. -- Binyamin Dissen <bdis...@dissensoftware.com> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
