Re: Alternatives to ODBC Connections

I'm not familiar with ASP. But tou might want to double check to make sure all programs are using connection pooling to get connection from iseries and they are releasing the connection once done with it.

"Brian Piotrowski" <bpiotrowski@xxxxxxxxxxxxxxx> wrote in message news:<mailman.5124.1355774918.10847.rpg400-l@xxxxxxxxxxxx>...
Hi All,

Does anyone know if there are any alternatives to an ODBC connection through ASP code or a dot.net program? We're noticing an increased problem with our programs and the dreaded QZDASOINIT job (many of them!) monopolizing the CPU usage quite often.

Right now most of the programs use code similar to this:

Set adoCon400 = Server.CreateObject("ADODB.Connection")
adoCon.Open "Provider=IBMDA400.DataSource.1;Persist Security Info=False;User ID=<Ourid>;Password=<ourpassword>;Data Source=<ourAS400>"
Set recordset = Server.CreateObject("ADODB.Recordset")
strSQL = "<our SQL statement>"
recordset.open strSQL, adoCon400
....do something with the results....
Recordset.close
Set recordset = nothing

That might have been fine and dandy when we didn't have many web applications, but now we have a lot more web applications running through IIS (Server 2008R2 64bit) and it appears to impact the system's performance.

Any helpful ideas or advice would be most appreciated.

Thankee-sai!

/b;

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Brian Piotrowski
Manager - I.T.
Simcoe Parts Service, Inc.
Ph: 705-435-7814 x343
Fx: 705-435-5029
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
http://www.simcoeparts.com<http://www.simcoeparts.com/>

Please consider the environment. Don't print this e-mail unless you really need to.

The information contained in this communication is confidential and intended only for the use of those to whom it is addressed. If you have received this communication in error, please notify me by telephone (collect if necessary) and delete or destroy any copies of it. Thank you!

----------