Hi all,

I would like to know if we should be using any special commands or system settings when running WebFocus reports over our AS400 files.

From what I understand when we submit a report in WebFocus we can see an active job on the AS400 'TSCOM3', under the WebFocus user id 'IADMIN'. However when viewing this job on the AS400 we can see that the job has many files open, including ones that aren't actually being used in our current report. It has been suggested that these files could be 'left overs' from previous reports that have run and that they should have been closed. Possible reference to Activation
Groups?

If this 'rings a bell' with anyone please let me know

Cheers

Mark

We have the same on our AlphaVax.
What I did is automatically start and stop the service on that machine during the night.
Not specially for these "left overs" but more to let the back-up process on the Vax do its work without any problem. The unclosed processes kept sometimes files locked and the back-up process did not like that.
So at the beginning of the back-up we did an EDASTOP and at the end an EDASTART.
If you have to have the WF system available for 7*24 this is not your solution.

Thanks Frank. This is something we can try.

However, I still think we have an issue that can be hopefully be identified.

This morning the three active TSCOM3 jobs were showing no files active/open. I ran a WebFocus report and all the files used in this report then appeared (and still remain) as open on the last TSCOM3 job. However I then ran a different WebFocus report and the files that were used in this report were not left open in the job, only the ones from the first report??

I have been through the source for both reports and I cannot spot a difference that would explain this?

I have noticed that both reports have the commands:

SQL DB2 SET OPTIMIZATION ON
SQL DB2 SET SQLJOIN OUTER ON

Can someone explain the effect of these commands or point me to where I can find more on these commands.

Thanks again

Mark.

Hi Mark,
Both of these commands instruct the DB2 adapter to create SQL statements that take advantage of RDBMS join, sort, and aggregation capabilities.
Search the ibi techsupport site (http://techsupport.informationbuilders.com) for optimization to get started.
The actual worker processes for requests are known as agents or tscom3 processes (tscom3 is the actual program name).
You will probably meed to turn on the server traces to get a better idea of whats happening under the covers.
Rich