Re: DB2 V12 DB2 connect v9.5 problem
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 > 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 > 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 > 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 > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DB2 V12 DB2 connect v9.5 problem
We just went from DB2 v9 to v12 M500. Had to upgrade clients to 11.5. Doug . On Dec 15, 2022, at 08:35, Clark, Kevin wrote: Looks like you'll need to be at least V11.1.??? for Data Sever Client https://www.ibm.com/docs/en/db2-for-zos/12?topic=aclid-v12r1mnnn-application-compatibility-levels-data-server-clients-drivers V9.5 reach EOS many years ago. We just ran a scan to locate software version and still have a few 9.5 versions out there after upgrading to V11.5 Client. It's worth the effort to upgrade everywhere as soon as possible , to avoid these type of road blocks going 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 an EXTERNAL source. Ensure you trust this sender before clicking on any links or attachments. 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 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 :>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 https://urldefense.com/v3/__http://www.dissensoftware.com__;!!EwdynJtshnZ7iu3ntw!mBf5f2W_JigNcVHMOLqhTM86-k5x_toZh3jvLl_OuUmDUFrK7qXje1qQMsDdzasPcfYf2S5d4w6SQFc1sXoaetg$ 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 *** Unauthorized interception of this communication could be a violation of Federal and State Law. This communication and any files transmitted with it are confidential and may contain protected health information. This communication is solely for the use of the person or entity to whom it was addressed. If you are not the intended recipient, any use, distribution, printing or acting in reliance on the contents of this message is strictly prohibited. If you have received this message in error, please notify the sender and destroy any and all copies. Thank you. ATENCIÓN: Si habla español, tiene a su disposición servicios gratuitos de asistencia lingüística. Llame al 855-258-6518 注意：如果您使用繁體中文，您可以免費獲得語言援助服務。請致電 855-258-6518 CareFirst BlueCross BlueShield, CareFirst BlueChoice, Inc. and all of their corporate affiliates comply with applicable federal civil rights laws and do not discriminate on the basis of race, color, national origin, age, disability or sex. *** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DB2 V12 DB2 connect v9.5 problem
Looks like you'll need to be at least V11.1.??? for Data Sever Client https://www.ibm.com/docs/en/db2-for-zos/12?topic=aclid-v12r1mnnn-application-compatibility-levels-data-server-clients-drivers V9.5 reach EOS many years ago. We just ran a scan to locate software version and still have a few 9.5 versions out there after upgrading to V11.5 Client. It's worth the effort to upgrade everywhere as soon as possible , to avoid these type of road blocks going 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 an EXTERNAL source. Ensure you trust this sender before clicking on any links or attachments. 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 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 :>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 https://urldefense.com/v3/__http://www.dissensoftware.com__;!!EwdynJtshnZ7iu3ntw!mBf5f2W_JigNcVHMOLqhTM86-k5x_toZh3jvLl_OuUmDUFrK7qXje1qQMsDdzasPcfYf2S5d4w6SQFc1sXoaetg$ 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 *** Unauthorized interception of this communication could be a violation of Federal and State Law. This communication and any files transmitted with it are confidential and may contain protected health information. This communication is solely for the use of the person or entity to whom it was addressed. If you are not the intended recipient, any use, distribution, printing or acting in reliance on the contents of this message is strictly prohibited. If you have received this message in error, please notify the sender and destroy any and all copies. Thank you. ATENCIÓN: Si habla español, tiene a su disposición servicios gratuitos de asistencia lingüística. Llame al 855-258-6518 注意：如果您使用繁體中文，您可以免費獲得語言援助服務。請致電 855-258-6518 CareFirst BlueCross BlueShield, CareFirst BlueChoice, Inc. and all of their corporate affiliates comply with applicable federal civil rights laws and do not discriminate on the basis of race, color, national origin, age, disability or sex. *** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DB2 V12 DB2 connect v9.5 problem
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 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 :>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 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
Re: DB2 V12 DB2 connect v9.5 problem
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 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 > 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 > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
DB2 V12 DB2 connect v9.5 problem
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 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
