Hi,

I want to create a report which can give me information as which user has run which report and number of hits or number of times user has run the report along with timestamp.

so , for example:

userid, reportname, hits,timestamp

Does anyone has done similar before?

Thanks
Abhi

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

This has been asked before, and from memory, several answers were given.

We here have a fex included, effectivly in each report that writes the required info, who/what/when, into a db, that can then be reported on.

Here's the fex we use:

-* File outcmusr.fex
 FILEDEF OUTCMUSR DISK &&BASEAPP..outcmusr.txt ( LRECL 80 RECFM V APPEND
-RUN
-SET &NOW=HHMMSS('A8');
-SET &DTLPGM=EDIT(&FOCFOCEXEC,'$99999999');
-WRITE OUTCMUSR &DATEYYMD &NOW &DTLPGM &OUTPUT &RUSER &&STAFF_NAME
-RUN

We just do a -INCLUDE of this program wherever we need it. Obviously those items that are not system variables (&RUSER, &&STAFF_NAME and &OUTPUT) have to be established prior to the -INCLUDE.

Of course, the downside of appending a file is thta if two users try to update the file at precisely the same time, there is a chance of one of the updates not being performed.

You'd be better off creating a FOCUS DB on a sync machine or using an RDBMS like MS SQL for your repository.

T

An example of what T proposes is what I use at one of my clients:

-SET &RUSER = UPCASE(8, &RUSER, 'A8');
SQL SQLMSS
INSERT INTO DBO.DS_LOG ( FEX_NAME,  USER_ID,  SERVER_ID,  LOG_DATE, LOG_TIME )
                VALUES ( '&WEBRPC', '&RUSER', '&&SERVER', '&YYMD',  '&TOD'   );
END
SQL SQLMSS
COMMIT;
END

&WEBRPC contains the name of the fex which is being set in the report or maintain itself. &&SERVER is being set in the edasprof.prf.

What ever the destination of the info, there is a level of infrastructure that needs to be put in place.

My suggestionnis to have one generic fex that is included in all fexes, and this one can then include any other peices of code that needs to be set for all fexes.

An example of this would be stats gathering, and generic constants.

You can have a sink machine process that writes to a database, but instead of -INCLUDing the code in each focexec, you can insert a run entry into DEFAULT.WFS before the target focexec is executed. In this way, you can also have a piece that runs after the focexec that can capture the run time into the same usage auditing database via the sink machine. The nice part about this approach is that the usage database can also accommodate a record of run parameters or other relevant statistics.

If you have purchased the WebFOCUS Pro Server you already have a component called "Resource Analyser". Just turn it on and you get all kinds of reports about who is using what and when. Plus you can do your own reports from the data file of all usage that is kept.