Hello

Our WebFOCUS applications is used by multiple users.
Does anybody know how to identify the user ID of the deferred query? Is any a specific file or data on the server which would show userID of the running query/report?

Thank you, Mila

Mila,

You can see the user who is executing a WF program in the WF console

(http://servername:port/cgiatt.exe)

This is under Workspace->Monitor->Data Services(Agents) in WF 7.6.2.

You will need to have IBI_REPORT_USER = &IBIMR_user in your ../client/wfc/etc/cgivars.wfs file. If it is not set currently, you will need to restart your Web server and WF processes after making the update.

Also, Resource Analyser tracks information about the reports that were run, who ran them, and other info. There are a series of SM* tables used to store this data.

Sean

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

Thak you, Sean

Thank you Sean

We have the following issue which sometimes causes our environment to collapse – one of the reports eats up all the space. Currently, Report Analyzer is not an option.
How to identify the user ID by just looking on the report files on the server? I believe the Console shows user by report name, but in these cases the report name is unknown. Can the console display the size of the hold files by report name and user? This would be helpfull.

Thank you, Mila

Mila,

I don't know what's available in 7.1, but in the 7.6 console, there is a column labelled State. I can right-click on the text in that column, then select View Statistics, and there is a window that displays. In that window, one of the items is Last MasterFile Name. This might tell you what you need to know.

Other than that, maybe someone else knows more info that will help.

Sean

Hold files are stored in EDATEMP and deleted when the report is done. The best you can do is monitor the agents and if you see one running a long time, log onto your Unix box and go to the directory under EDATEMP that has the agent id in it. You will be able to see the hold file being created.

If you were running self-service and the users logged on, the directory would be owned by the user but based on this post from you and another post, I think you are doing MRE. If that is the case and you are running a reporting server with OPSYS security and a default Unix id, all edatemp directories will be owned by that user.

I would do what smiths said and try to capture the MRE id so that you can track that back to the MRE user.

Thank you, Sean, very much

have a nice weekend, Mila

You could also just look back through the edaprint and you would be able to see which user(s) have connected just before the time when the problem occurs. Then give them 50 lashes.