Enabling DB2 Connect Unlimited

Donna Domovic

Enabling DB2 Connect Unlimited

Hello,

We're in the process of upgrading to DB2 v11 CM (I know we're late).  With that, some of our distributed applications that use the DB2 JDBC drivers or DB2 Connect have begun receiving errors similar to the following:

DSNT408I SQLCODE = -805, ERROR:  DBRM OR PACKAGE NAME DB2ELOC.DB2LIC.SY-

         SLIC.6F41366357454677 NOT FOUND IN PLAN DISTSERV. REASON 04   

DSNT418I SQLSTATE   = 51002 SQLSTATE RETURN CODE                       

DSNT415I SQLERRP    = DSNXEPM SQL PROCEDURE DETECTING ERROR            

DSNT416I SQLERRD    = -100  0  0  -1  0  0 SQL DIAGNOSTIC INFORMATION  

DSNT416I SQLERRD    = X'FFFFFF9C'  X'00000000'  X'00000000'  X'FFFFFFFF'

          X'00000000'  X'00000000' SQL DIAGNOSTIC INFORMATION           

 

We believe this is because they need a new license file to enable the JDBC driver and DB2 Connect to work with DB2 v11.  If you disagree, please let me know.

In the past, we've provided these files to the application teams and had them put the license file on their server along with the JDBC or DB2 Connect software.  With more and more applications using these things, however, this can become difficult and time consuming.

My understanding is that with the unlimited license, there's a way to enable these products on the mainframe side and then the apps would not have to worry about the license file.  Unfortunately, I've found various information on how to do this from the server side but not how to do it from the mainframe side.

Can someone please help and tell me how this can be done with DB2 v11 or where to look for this information? 

My preference is to be able to execute something on the mainframe for each DB2 data sharing group rahther than have to execute something on the server then have whatever apps use the JDBC drivers or DB2 Connect not have to include the license file on the server side.

Thanks in advance.

Donna Domovic

Jørn Thyssen

RE: Enabling DB2 Connect Unlimited
(in response to Donna Domovic)

Hi Donna,

If you upgrade the IBM data server drivers to a new version or release you generally need a new license file.

With the Unlimited license you can install the license on the z/OS side to avoid installing it on the client side.

  • Download the license activation kit from IBM Passport Advantage. Inside the zip file you will find a directory with db2connectactivate.bat
  • Run db2connectactivate.bat from your workstation https://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.1.0/com.ibm.db2.luw.licensing.doc/doc/r0057377.html
  • You can also run it from USS if you prefer: http://www-01.ibm.com/support/docview.wss?uid=swg21987569
  • This will generate a native stored procedure SYSIBM.DB2CON_LIC and a package DB2LIC.SYSLIC

 


In Reply to Donna Domovic:

Hello,

We're in the process of upgrading to DB2 v11 CM (I know we're late).  With that, some of our distributed applications that use the DB2 JDBC drivers or DB2 Connect have begun receiving errors similar to the following:

DSNT408I SQLCODE = -805, ERROR:  DBRM OR PACKAGE NAME DB2ELOC.DB2LIC.SY-

         SLIC.6F41366357454677 NOT FOUND IN PLAN DISTSERV. REASON 04   

DSNT418I SQLSTATE   = 51002 SQLSTATE RETURN CODE                       

DSNT415I SQLERRP    = DSNXEPM SQL PROCEDURE DETECTING ERROR            

DSNT416I SQLERRD    = -100  0  0  -1  0  0 SQL DIAGNOSTIC INFORMATION  

DSNT416I SQLERRD    = X'FFFFFF9C'  X'00000000'  X'00000000'  X'FFFFFFFF'

          X'00000000'  X'00000000' SQL DIAGNOSTIC INFORMATION           

 

We believe this is because they need a new license file to enable the JDBC driver and DB2 Connect to work with DB2 v11.  If you disagree, please let me know.

In the past, we've provided these files to the application teams and had them put the license file on their server along with the JDBC or DB2 Connect software.  With more and more applications using these things, however, this can become difficult and time consuming.

My understanding is that with the unlimited license, there's a way to enable these products on the mainframe side and then the apps would not have to worry about the license file.  Unfortunately, I've found various information on how to do this from the server side but not how to do it from the mainframe side.

Can someone please help and tell me how this can be done with DB2 v11 or where to look for this information? 

My preference is to be able to execute something on the mainframe for each DB2 data sharing group rahther than have to execute something on the server then have whatever apps use the JDBC drivers or DB2 Connect not have to include the license file on the server side.

Thanks in advance.

Donna Domovic



 

Best regards,

Jørn Thyssen

Rocket Software
77 Fourth Avenue • Waltham, MA • 02451 • USA
E: [login to unmask email] • W: www.rocketsoftware.com 

2018 IBM Champion.

Views are personal. 

Scott Goodell

RE: Enabling DB2 Connect Unlimited
(in response to Donna Domovic)

We have the BMC Apptune product and I regularly see this -805 reported but the client application never receives the error.  I just ran a couple of tests myself and on my client I have the current license file installed and using a simple db2 command window to run SQL I don't get any error reported but I see this -805 in Apptune.  I also ran the test using a JDBC connection with the db2jcc_license_cisuz.jar file and again the client program never received any error but Apptune showed the -805.  Notice mine is the same contoken as what yours shows.  

DSNT408I SQLCODE = -805, ERROR: DBRM OR PACKAGE NAME DBF3.DB2LI-
C.SYSLIC.6F41366357454677 NOT FOUND IN PLAN DISTSERV. REASON 04

It appears that DB2 tries to validate the license first on the z/OS side which in our case gets the -805 then the client side license must get validated since we never see the error on the client side.

It appears you would need a V11 client side license file or install the license on the z/OS side as Jørn mentioned.

Hope this helps a little anyway.

Scott

Donna Domovic

RE: Enabling DB2 Connect Unlimited
(in response to Scott Goodell)

Thanks to both of you for this information.  What Scott said fits with what we're seeing.

We'll work on getting the DB2 v11 license enabled on the z/OS side but it looks like we should be ok until that is done.

Thanks,

Donna Domovic