[Loadunner & DB2] Which protocol to use ?

[Dave Rabelink]

Finally the company here has started to perform load & stress tests using the tool Loadrunner from Mercury. This to compare the performance and stability between SQLHost connectivity to DB2 (mainframe) and IBM DB2 connect.

Another department is performing the tests, but they have trouble finding out which protocol to use to record the scenario's in Loadrunner.

I wonder if someone here has experience load testing TD applications using the Loadrunner product.

Basically the tests will be very simple. Just record a predefined set of SQL statements like connect, select from some tables and disconnect.
The scenarios will be performed using SQLHost connectivity and using IBM DB2 connect.

The database is DB2 on mainframe.

My questions are :

- Which protocol is used in connectivity using SQLHost to DB2 mainframe at client side. What is the best module to choose in Loadrunner to record and execute performance tests ?

- The same question, but now when using IBM DB2 connect.

Here a small piece from SQL.ini where the settings for SQLHost are defined. Maybe someone here can indicate which protocol is used in these settings :

Code: Select all

[win32client]
clientname=Win32Client
connecttimeout=5
setzerolengthstringstonull=on

[win32client.dll]
comdll=sqlws32

[win32client.ws32]
serverpath=DB2SERVB,ap01.eur.tld,3001/SQLHPRDB

Any help or hints are very welcome.

[Dave Rabelink]

Maybe I should narrow my question down a bit, so a little kick of this thread.

Does anyone here has experience using Mercury Loadrunner for testing database connections (any, eg SqlBase) from TD build applications ?

[Dave Rabelink]

For anyone interested in the answer.

After some experimenting, the protocol which is used in communication to SQLHost to DB2/Mainframe is Windows Sockets.

In Loadrunner, select the WinSocks protocol and the TD application involved.
Loadrunner records all WinSock commands and is stored in a Loadrunner script which shows all fired SQL statements (and the resulting data), which can be parameterized and replayed.