Good Morning,

is there any solution to retrieve who ran an interactive program at a 
specific date (iSeries V6R1) ?

Merci
-- 
Pat

On 3/24/11 5:53 AM, Patrick Tonnerre wrote:
>
> is there any solution to retrieve who ran an interactive program at
> a specific date (iSeries V6R1) ?
>

   Setup auditing to include audit of object-level detail, then for the 
interactive program PgnName in library PgmLib issue the following:

    CHGOBJAUD OBJ(PgmLib/PgmName) OBJTYPE(*PGM) OBJAUD(*ALL)

   To retrieve who ran the program on a specific date issue a DSPJRN 
QAUDJRN RCVRNG(*CURCHAIN) FROMTIME(&theday '00:00:00') TOTIME(&theday 
'23:59:59') for that specific date &theday to list either [not sure of 
which] of the T-ZR "Audit read access" or T-ZM "Object method access" 
entries with whatever means to filter the data [e.g. directed by the 
DSPJRN command to a named output file].

Regards, Chuck

"Patrick Tonnerre" <nospam@nospam.org> wrote in message 
news:imferl$1ka3$1@obelix.gegeweb.org...
| Good Morning,
|
| is there any solution to retrieve who ran an interactive program at 
a
| specific date (iSeries V6R1) ?
|
| Merci
| -- 
| Pat


Is their a relationship between the workstation name and the program 
at issue?  If yes you can search for the job name which equals the 
workstation name in QHIST or in the job accounting journal.

If not, do you have journaling running on files updated by the 
program?  If yes you can dump the journal receiver to a file and 
search for updates and program name at the time in question and find 
the job name and user name from that.

If the answer is no to both I think you are out of luck for past 
events.  However, if this is very important and likely to be an issue 
in the future, you should consider controlling program access with 
security or place it in a menu process that will write a log of 
invocations for future retrieval.

Finally, if the problem is not really who ran the program but that 
someone did at a time when some other job needed to run, you can add 
object locking and checks for conflicting locks as part of the 
programs and or job streams in question.

Mike Sicilian 

Thank You Mike and Chuck for your answers
I will check it soon

Pat