Hello friends,

I am currently working on

-> WebFOCUS version 7.7.03.

-> Websphere v 6.1 with WebFOCUS client on Linux x64-bit OS (Webserver/Application server).

-> WebFOCUS reporting server running on mainframe Z/OS 1.9.

-> Data source used is IDMS.

Whenever I run a report from Developer Studio or MRE, the report with 30 records also takes 5 minutes but finally gives the output. Is this because of too many tiers that are involved in the environment that are hitting the report performance?

Thanks for any assistance.

Thanks
Teju

This message has been edited. Last edited by: Kerry,

Can you run this directly on the WebFOCUS server ? to test how long it takes.

If I run the same report on Mainframe (Reporting server running on Mainframe), it runs instantaneously.

Thanks
Tejovathi

I mean, when I run the same report on RUMBA mainframe display, the output is instantaneous.

Please let me know if that is what you mean?

Thanks
Tejovathi

Yes, I guess the ontly thing you can do is to test each tier till it runs for 5 minutes.

The reporting server isn't the problem becasue its instantaneous.

What othere tiers do you have ?

Websphere with Webfocus client on Linux x64-bit OS is another tier.

Thanks
Tejovathi

Well you should be able to test the call from the WF Client.

All WF clients will have a test utility called RDAAPP

You can use this to call the reporting server and issue the request.

You may also want to look into tracing on the client as well.

Waz,

Is RDAAPP something on mainframe server using which I can execute the .fex file and check its performance? If not, please tell me how to logon to RDAAPP, test for performance from there?

I am asking this because this term RDAAPP is pretty much new to me.

Thanks
Tejovathi

Looks like things have changed since I used RDAAPP on a WebFOCUS Client Installation.

Its not there.

You may have to do this with tracing.

I can only guerss that there is a delay from a web or client call to the MF reporting server.

Waz,

Right now, we are using IDMS (Mainframe db) for reporting, which is also being accessed by many other users in the organization. Is it that the call made by the WF client to the WF reporting server is queued up because of the network traffic and hence causing the long response time?

Also, do you think that we can improve the response time of the report if we are going to migrate off the mainframe database to Oracle database and use Oracle database only for reporting purpose?

Need a quick suggestion from you because we are planning to implement that in the coming weeks.

Thanks
Tejovathi

If you are going direct against the DB there should be many gains.

It all comes down to the result set and pushing back any filtering, so the minimum number of records that can be returned, are.

This will hopefully solve the performance/network issues.

Waz,

Thanks a lot for the suggestion. I think I would ever be in touch with you to get my doubts cleared.

Thanks
Tejovathi