Lee is absolutely correct.  VEAUDIT does a good job of providing the
information.  You need to have FILE CLOSE events logged, as Lee said,
in order to first find the fact that the file was purged.  Use the
following syntax:

%VEAUDIT LISTLOG FCLOSE @.@;SEARCH=(F='FFFFFFFF.GGGGGGGG.AAAAAAAA')

where FFFFFFFF.GGGGGGGG.AAAAAAAA is the filename, group and account.

You may want to add ;BEGIN=mm/dd/yy;END=mm/dd/yy   :-)

Look for the "purged" flag at the right-most column and then look
at the logon.  If you have JOB INITIATIONS logged, the logon
of the person who purged the file will show.  If you don't have
JOB INITIATIONS logged, the logon will be blank.  If this is the
case, you can get the session number.

If you have CONSOLE events logged, you can search for the
session number with the following syntax:

%VEAUDIT LISTLOG CONSOLE #Snnn;BEGIN=mm/dd/yy;END=mm/dd/yy

where "nnn" is the session number.

This will show you the file purging culprit.  If you don't have
CONSOLE logging enabled, well, I believe that the technical term
is "you're screwed"!

Sorry for the bad information earlier.


Bill Lancaster