DB2 z/OS: db2cli.ini File and DB2 Connect Gateways

Bill Gallagher

DB2 z/OS: db2cli.ini File and DB2 Connect Gateways
Good morning list,

Hopefully a simple question this morning.

First, our environment: DB2 z/OS v11, with a number of DB2 Clients connecting though a handful of DB2 Connect gateway servers

I'm looking to make a change to our client/server application which will involve adding a parameter to the "db2cli.ini" file to enable a particular behavior for the application on DB2 z/OS.

This is a "classic" 20+ year old client/server application, with the app running on a Windows PC with a DB2 Client, going through a DB2 Connect gateway server to access the DB2 z/OS database on the backend.

We have hundreds of clients scattered throughout the state at a number of regional offices (around 15 or so). I believe each regional office is configured to go through a different DB2 Connect gateway, all of which are located in a single data center.

My question is: when deploying the necessary change to the "db2cli.ini" file, do we have to roll it out to the PC's of each of the hundreds of clients throughout the state, or can we just apply it at the 15 or so DB2 Connect gateway servers, and all clients going through each gateway will see the benefit of the change?

Thanks in advance.

Bill Gallagher
DB2 Database Administrator
State of Connecticut

Philip Nelson

DB2 z/OS: db2cli.ini File and DB2 Connect Gateways
(in response to Bill Gallagher)
Bad news I'm afraid Bill. This will need to go out to all the clients.

If you are making a change, you might want to look at deploying the changes
in db2dsdriver.cfg rather than db2cli.ini. Also into doing direct
connections rather than going through a gateway. The need for a gateway
is virtually redundant nowadays - at best it manages the DB2 Connect
license if you haven't installed the license at the mainframe side. But
all the other stuff it used to do, such as connection concentration and
protocol transformations are all done at either the client or the server
(mainframe) these days. By putting it direct you will save yourself a
needless network hop. If you don't have the mainframe license installed
(the best option) you'd need to deploy a license file to each client, but
if you are making a change to the client anyway that should not be a big
deal.

HTH

Phil

On 19 February 2018 at 13:37, GALLAGHER, WILLIAM <[login to unmask email]>
wrote:

> Good morning list,
>
>
>
> Hopefully a simple question this morning.
>
>
>
> First, our environment: DB2 z/OS v11, with a number of DB2 Clients
> connecting though a handful of DB2 Connect gateway servers
>
>
>
> I’m looking to make a change to our client/server application which will
> involve adding a parameter to the “db2cli.ini” file to enable a particular
> behavior for the application on DB2 z/OS.
>
>
>
> This is a “classic” 20+ year old client/server application, with the app
> running on a Windows PC with a DB2 Client, going through a DB2 Connect
> gateway server to access the DB2 z/OS database on the backend.
>
>
>
> We have hundreds of clients scattered throughout the state at a number of
> regional offices (around 15 or so). I believe each regional office is
> configured to go through a different DB2 Connect gateway, all of which are
> located in a single data center.
>
>
>
> My question is: when deploying the necessary change to the “db2cli.ini”
> file, do we have to roll it out to the PC’s of each of the hundreds of
> clients throughout the state, or can we just apply it at the 15 or so DB2
> Connect gateway servers, and all clients going through each gateway will
> see the benefit of the change?
>
>
>
> Thanks in advance.
>
>
>
> Bill Gallagher
>
> DB2 Database Administrator
>
> State of Connecticut
>
>
>
> -----End Original Message-----
>

Bill Gallagher

DB2 z/OS: db2cli.ini File and DB2 Connect Gateways
(in response to Philip Nelson)
Phil,

Thanks for the response.

We’re about to commence a project which will ultimately retire the current application over the next 3-5 years, and replace it with a shiny new one. While I can (and have) gotten buy-in on the need to make the change that I’ve proposed, I don’t want to go near the idea of changing from gateways to direct connections (in the spirit of “knowing when to pick your battles”), especially for an application that is going to be retired. The gateways are currently used to easily shut down access to the application whenever there are upgrades or code deployments. I’m not about to rock that boat (though I 100% agree that direct connections are the way to go).

Bill Gallagher
DB2 Database Administrator
State of Connecticut


From: Philip Nelson [mailto:[login to unmask email]
Sent: Monday, February 19, 2018 8:42 AM
To: [login to unmask email]
Subject: [DB2-L] - RE: DB2 z/OS: db2cli.ini File and DB2 Connect Gateways

Bad news I'm afraid Bill. This will need to go out to all the clients.

If you are making a change, you might want to look at deploying the changes in db2dsdriver.cfg rather than db2cli.ini. Also into doing direct connections rather than going through a gateway. The need for a gateway is virtually redundant nowadays - at best it manages the DB2 Connect license if you haven't installed the license at the mainframe side. But all the other stuff it used to do, such as connection concentration and protocol transformations are all done at either the client or the server (mainframe) these days. By putting it direct you will save yourself a needless network hop. If you don't have the mainframe license installed (the best option) you'd need to deploy a license file to each client, but if you are making a change to the client anyway that should not be a big deal.

HTH

Phil

On 19 February 2018 at 13:37, GALLAGHER, WILLIAM <[login to unmask email]<mailto:[login to unmask email]>> wrote:
Good morning list,

Hopefully a simple question this morning.

First, our environment: DB2 z/OS v11, with a number of DB2 Clients connecting though a handful of DB2 Connect gateway servers

I’m looking to make a change to our client/server application which will involve adding a parameter to the “db2cli.ini” file to enable a particular behavior for the application on DB2 z/OS.

This is a “classic” 20+ year old client/server application, with the app running on a Windows PC with a DB2 Client, going through a DB2 Connect gateway server to access the DB2 z/OS database on the backend.

We have hundreds of clients scattered throughout the state at a number of regional offices (around 15 or so). I believe each regional office is configured to go through a different DB2 Connect gateway, all of which are located in a single data center.

My question is: when deploying the necessary change to the “db2cli.ini” file, do we have to roll it out to the PC’s of each of the hundreds of clients throughout the state, or can we just apply it at the 15 or so DB2 Connect gateway servers, and all clients going through each gateway will see the benefit of the change?

Thanks in advance.

Bill Gallagher
DB2 Database Administrator
State of Connecticut


-----End Original Message-----

Roy Boxwell

DB2 z/OS: db2cli.ini File and DB2 Connect Gateways
(in response to Bill Gallagher)
Just wondering which flag you are wishing to set... as changing thousands of ini files is a right royal PITA it might be easier to do the changes on the Mainframe side of the fence...

Roy Boxwell

SOFTWARE ENGINEERING GMBH and SEGUS Inc.
-Product Development-

Heinrichstrasse 83-85
40239 Duesseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: [login to unmask email]<mailto:[login to unmask email]>
http://www.seg.de http://www.seg.de

Software Engineering GmbH
Amtsgericht Düsseldorf, HRB 37894
Geschäftsführung: Gerhard Schubert

From: GALLAGHER, WILLIAM [mailto:[login to unmask email]
Sent: Monday, February 19, 2018 2:37 PM
To: '[login to unmask email]' <[login to unmask email]>
Subject: [DB2-L] - DB2 z/OS: db2cli.ini File and DB2 Connect Gateways

Good morning list,

Hopefully a simple question this morning.

First, our environment: DB2 z/OS v11, with a number of DB2 Clients connecting though a handful of DB2 Connect gateway servers

I'm looking to make a change to our client/server application which will involve adding a parameter to the "db2cli.ini" file to enable a particular behavior for the application on DB2 z/OS.

This is a "classic" 20+ year old client/server application, with the app running on a Windows PC with a DB2 Client, going through a DB2 Connect gateway server to access the DB2 z/OS database on the backend.

We have hundreds of clients scattered throughout the state at a number of regional offices (around 15 or so). I believe each regional office is configured to go through a different DB2 Connect gateway, all of which are located in a single data center.

My question is: when deploying the necessary change to the "db2cli.ini" file, do we have to roll it out to the PC's of each of the hundreds of clients throughout the state, or can we just apply it at the 15 or so DB2 Connect gateway servers, and all clients going through each gateway will see the benefit of the change?

Thanks in advance.

Bill Gallagher
DB2 Database Administrator
State of Connecticut


-----End Original Message-----

Bill Gallagher

DB2 z/OS: db2cli.ini File and DB2 Connect Gateways
(in response to Roy Boxwell)
Adding the following:

STMTCONCENTRATOR=WITHLITERALS

Our DB2 subsystem is shared with another state agency, so we pretty much need to make a change like this at the client/application level. Otherwise, we could be impacting the other agency's application. Another can of worms that I'm not willing to open.

Bill Gallagher
DB2 Database Administrator
State of Connecticut


From: Boxwell, Roy [mailto:[login to unmask email]
Sent: Monday, February 19, 2018 9:27 AM
To: [login to unmask email]
Subject: [DB2-L] - RE: DB2 z/OS: db2cli.ini File and DB2 Connect Gateways

Just wondering which flag you are wishing to set... as changing thousands of ini files is a right royal PITA it might be easier to do the changes on the Mainframe side of the fence...

Roy Boxwell

SOFTWARE ENGINEERING GMBH and SEGUS Inc.
-Product Development-

Heinrichstrasse 83-85
40239 Duesseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: [login to unmask email]<mailto:[login to unmask email]>
http://www.seg.de http://www.seg.de

Software Engineering GmbH
Amtsgericht Düsseldorf, HRB 37894
Geschäftsführung: Gerhard Schubert

From: GALLAGHER, WILLIAM [mailto:[login to unmask email]
Sent: Monday, February 19, 2018 2:37 PM
To: '[login to unmask email]' <[login to unmask email]<mailto:[login to unmask email]>>
Subject: [DB2-L] - DB2 z/OS: db2cli.ini File and DB2 Connect Gateways

Good morning list,

Hopefully a simple question this morning.

First, our environment: DB2 z/OS v11, with a number of DB2 Clients connecting though a handful of DB2 Connect gateway servers

I'm looking to make a change to our client/server application which will involve adding a parameter to the "db2cli.ini" file to enable a particular behavior for the application on DB2 z/OS.

This is a "classic" 20+ year old client/server application, with the app running on a Windows PC with a DB2 Client, going through a DB2 Connect gateway server to access the DB2 z/OS database on the backend.

We have hundreds of clients scattered throughout the state at a number of regional offices (around 15 or so). I believe each regional office is configured to go through a different DB2 Connect gateway, all of which are located in a single data center.

My question is: when deploying the necessary change to the "db2cli.ini" file, do we have to roll it out to the PC's of each of the hundreds of clients throughout the state, or can we just apply it at the 15 or so DB2 Connect gateway servers, and all clients going through each gateway will see the benefit of the change?

Thanks in advance.

Bill Gallagher
DB2 Database Administrator
State of Connecticut


-----End Original Message-----

-----End Original Message-----