Cognos, ODBC and Progress Question

[jsingleton]

We currently use Openlink V5.1 to connect Cognos (Windows) to Progress 9.1D (Unix Tru-64 V 5.1B). This works fine for the normal 2 databases we want to connect to. We have been able to connect to 4 databases at various times, but now need to connect to 6. I understand that 5 is the normal limit, and to achieve connectivity to more the -h parameter needs to be set. The start up parameters are held in a pfcontrol file, but I am unable to see where to put the -h in this file.

The Progress Knowledge Base is not very helpful, saying you need to remove the -h from a startup parameter file as it will be ignored, so what options do I have?

Any ideas will be much appreciated.

 

[RealHeavyDude]

The -h parameter is only applicable for connection Progress 4GL clients to databases. You don't give much information as to how you connect your Cognos application to the Progress databases and I don't know anything about Cognos. But since you posted this in DataServers and ODBC forum I'll take it that you connect to with an ODBC/JDBC driver to the SQL engine of the database. If that is true, then it's a issue of Cognos handling many concurrent database connection.

On a note: In order to have this work successfully you need to set up the database accordingly. You should set up a secondary login broker so that you have two brokers, each dedicated to a type of clients, 4GL or SQL. The spooling of remote clients on the remote servers will not work if both type of clients connect to the same login broker. Just look up secondary login broker in the Progress knowledge base and you fill find the information you need to set it up correctly.

And, last but not least, 9.1D is of course 10 years old software: Buggy, limited and unsupported.

Heavy Regards, RealHeavyDude.

 

[jsingleton]

Thanks, RealHeavyDude. Sorry I have not replied before, but I got distracted by other matters considered more important by management. We have only got to keep Progress 91D goung for another 5 months, when it will be replaced by an SQL Server system. We've actually rejigged things so we now only need to look at 2 databases at a time, but your comments are appreciated.