Need to track what programs users are accessing, like in the PIBS file.
Has anyone ever worked on this issue? I am working on a D3 pick
machine.

Write a subroutine like:

subroutine filetracker(Param)
' param contains program ID (and anything else you want to track [time,
date, etc])
open pibs then
read pRec from system(22) then
locate(param,prec,21;vx) then ;* I picked an attr at random
prec<22,vx> += 1
end else
prec<21,-1> = param
prec<22,-1> = 1
end
end
end
return

Then in each of the programs you want to track:

x = oconv(ProgramName,"call filetracker")


Mark Brown

"AlRoda" <alfred (AT) alroda (DOT) com> wrote

I have given this some thought about this subject. I would like to at
least offer these suggestions on the matter.

a. Personally, I would stay away from the PIBS file. The PIBS file is
to be considered a "system" file that one should not fuss with except
for attributes 001 and 002. PIBS gets updated by the system for logons,
logoffs and LOGTO's. My advice: use your own file.

b. Mark's code looks like it would work for Pick/Basic programs. But,
how about PROCS, macros, TCL commands and so on? For this to be
meaningful data, it seems to me that EVERY Basic program and EVERY
PROCedure needs to be identified, and, at the least, know if the user
is at the TCL level.

c. It seems to me that, depending on the structure of the application
"menu system", this might be a place to start. Each menu option could
record the program/proc/etc. name in the user's file. Using the "menu
system" as the "driver" would greatly reduce the number of programs
that would need to be touched to implement this project.

d. I'll bet the data required are already available within the bowels
of D3. I could be wrong, of course. But, I have no idea where to start
looking for those data.

My 2-cents worth.
Dave Weaver, Weaver Consulting



Mark Brown wrote: