Re: of job logs, auditing and such ...

[Rob Berendt <rob@xxxxxxxxx>]

Try doing the following:
DSPLOG OUTPUT(*PRINT) MSGID(CPF1124)
CRTPF QTEMP/SPOOL RCDLEN(150)
CPYSPLF FILE(QPDSPLOG) TOFILE(QTEMP/SPOOL) SPLNBR(*LAST)

A sample CPF1124 message is:
Job 702536/TROYM/REENROLL started on 09/27/99 at 09:00:23

There are slicker ways to do things, but this is a start.

Rob Berendt




clarke@teri.org on 09/27/99 01:28:55 PM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     midrange-l@midrange.com@Internet
cc:      
Fax to: 
Subject:        of job logs, auditing and such ...


I need help understanding an AS/400 concept that I have not previously   
been exposed to, but is now wreaking havoc on my work day.  My question   
is:  To what level of detail is 'job logging' available, and what   
controls the existence and/or level of logging?  Recently we have had a   
situation where a process has not run correctly.  We suspect that the   
user involved missed running a job.  However there is no output for this   
user's interactive sessions in QEZJOBLOG.  And when I have been able to   
find output, it contained no useful information.  The default for the   
signoff command is '*list'.  However in at least some cases the user(s)   
may be selecting an option within a proprietary menu (JDE, for instance)   
to sign off.  Ultimately I'd like to have the ability to look back for   
any given day and see what any user did on that day, right down to   
keystrokes if possible.  I'd settle though for at least having a record   
of what jobs they ran, be it by command line or menu option.  Can anyone   
help me to better understand this?  Or can someone point me to   
appropriate documentation?  Any help would be most appreciated.  Thanks   
in advance!

Regards,

Bob Clarke

WINMAIL.DAT