Re: of job logs, auditing and such ... -- MIDRANGE-L

If you go to a job description (CHGJOBD or through WRKJOBD) you
will find a parameter for LOG.  This takes 3 values.  The first value is the
Level.  Hitting F1 on this field there are descriptions for each (0 through 4)
with 4 being the most logging.  The next value is the severity.  This specifies
what message severity a message must be before it is logged.  And, the
last value is text, which can be *NOLIST, *MSG or *SECLVL.  *NOLIST
means don't produce a job log if the job ends normally.  *MSG means
just give me the messages in the job log, and *SECLVL means also give
me the second level text for a message.

If you specify them as 4, 0, *SECLVL you will log almost everything they do.
I do notice, however, that some things you just can't see.  For instance, if
someone does STRPDM you can't really see what they do inside of PDM,
although you can see the commands they run while in that environment.

I would set it for 4, 0, *MSG, as you can usually get the second level 
information,
and are just interested in what happened.

Make sure you are using the automatic cleanup if you do this, though, as now
all jobs on the system for that job description will not produce a job log.

Regards,

Jim Langston

Bob Clarke 3rd x4502 wrote:

> 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
>
>   ------------------------------------------------------------------------
>                   Name: WINMAIL.DAT
>    WINMAIL.DAT    Type: Text Document 
>(application/x-unknown-content-type-txtfile)
>               Encoding: BASE64

+---
| 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
+---