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

If you really  want to see everything happening on your system you can do
the following.  It will, however, cost you a great deal of disk space.

First, you want all  your job descriptions set to generate the lowest level
messages possible (leave IBM's alone).  You do this by changing the job
description parameters shown below.

     Message logging:
        Level  =  4
        Severity =  0
       Text = *SECLVL

    Log CL program command = *YES

Second, ensure all your CL program are created with the Log commands
parameter set to *YES.

Third, ensure anywhere the SBMJOB command is used that the Message logging
and Log CL program commands  are set up the same as stated above for job
descriptions.

You probably don't have to go any further than this to see if a job is being
skipped.  At this point you will be able to see what job path a user
followed by reviewing job logs.

Fourth, start  journaling on all your physical files.  You can review
journal receivers to see how your data was accessed, added, changed, or
deleted,

Lastly, start Auditing on all objects.   You can find the specifics on
auditing in the Security Reference manual.

-----Original Message-----
From: Bob Clarke 3rd x4502 <clarke@teri.org>
To: midrange-l <midrange-l@midrange.com>
Date: 27 September 1999 11:29
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


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---