× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: who changed the file?
  • From: Richard Reeve <richreeve@xxxxxxxxx>
  • Date: Mon, 4 Dec 2000 15:52:50 -0800 (PST)

I believe that if you do a WRKOBJ <lib/filename> then
select option 8, you will see a 'last changed by'
field.  This will identify the user id of the last
person to perform a maint function (add/change/delete)
on the file.  If you already restored the file then
you are out of luck unless it was journaled.  

Since it was the weekend that it probably occurred,
you could also do a dsplog and see who was signed on. 
That should narrow it down a bit, unless it was
cleared by a submitted job, in which case you should
be able to see that as well.

Hope this helps.  Good luck.

Rich

--- Jodi Walker <Jodi_Walker@ccmail.columbia.com>
wrote:
>      I'm hoping that there is something I haven't
> yet thought of, because 
>      everything else has been a dead end.  How can I
> identify who last 
>      changed a physical file if that file is not
> journaled? I'm not 
>      concerned with a particular record, but who
> last touched the file for 
>      something other than input. 
>      
>      On our development box, we had a file
> containing a good amount of test 
>      data in it that had been setup in advance of
> user testing.  Over the 
>      weekend, that data disappeared.  We are
> attempting to restore that 
>      file from a backup, assuming the damage wasn't
> already done.  
>      
>      The concern is that no one will admit to
> touching, either though a 
>      cmd, DB utility or program, this file.  (CPYF
> is used quite frequently 
>      when trying to duplicate production errors on
> the development box.)  
>      This is a file that is maintained very
> infrequently, so there is 
>      little chance that the last person who touched
> it wasn't the person 
>      who is 'guilty.' And the guilty must be
> punished - or at least 
>      reminded that they don't work in a vacuum. <g>
>      
>      tiafah
>      jw
> +---
> | 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
> +---


=====


__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/
+---
| 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 ...

Follow-Ups:

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.