• Subject: Re: of job logs, auditing and such ...
  • From: email@xxxxxxxxxxxxxxxxxxx (James W Kilgore)
  • Date: Mon, 27 Sep 1999 14:39:29 -0700
  • Organization: Progressive Data Systems, Inc.

Bob,

As Arlene and others have pointed out, the JOBD will control the degree
of logging. You also mentioned "keystroke if possible" and that gets a
little tougher.

If you have access to the display file source code, you may want to try
putting keywords LOGINP and LOGOUT which will log the display buffers
for input/output respectively.

I used this way back when to "prove" that screens were not being filled
in properly, but I don't think it worked for input from a window.

Besides, logging does create a performance hit.

Just as a side note, over the years I've learned to:
1) Deal with whatever mistake occurred
2) Find a programming solution to make sure it never happens again

Trying to determine if, or if not, something was run will involve asking
the user, and, without malicious intent, they will remember what they
were supposed to do, but rarely remember what they actually did.

We have a multiple stage process that gets run at month end and we
finally created a data area that contained the last stage processed. 
Each process tested the data area to make sure that the appropriate
stage had been completed.

Good luck


Arlene M Soderlund wrote:
> 

<<snip>>
> 
> Then Change that *JOBD  to have the following
> 
>                         Change Job Description (CHGJOBD)
> 
>  Type choices, press Enter.
> 
>  Message logging:
>    Level  . . . . . . . . . . . .   4             0-4, *SAME
>    Severity . . . . . . . . . . .   00            0-99, *SAME
>    Text . . . . . . . . . . . . .   *SECLVL       *SAME, *MSG, *SECLVL, 
>*NOLIST
>  Log CL program commands  . . . .   *YES          *SAME, *NO, *YES
> 
> When they signoff with *LIST you will get the JOBLOG of your dreams.
>
+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.