I agree, if file disposition is being logged, it will show
Chuck
Sent from my Verizon Wireless BlackBerry
-----Original Message-----
From: Neil Armstrong <[log in to unmask]>
Date: Wed, 16 Sep 2009 10:45:29
To: <[log in to unmask]>
Subject: Re: [HP3000-L] files just randomly disappearing
At 10:33 AM 16/09/2009, Craig Lalley wrote:
>However, if someone logs on to the command prompt and simply purges
the file, I doubt there will be any trace in the system logs.
I'm wondering why that would be the case. Clearly purge calls fclose
with a delete disposition:
Calvin:debug
DEBUG/iX C.39.06
HPDEBUG Intrinsic at: a.0107ffc0 hxdebug+$e8
$1 ($67) nmdebug > b FCLOSE
added: NM [1] SYS a.014951f0 FCLOSE
$2 ($67) nmdebug > c
Calvin:purge zint
Break at: NM [1] SYS a.014951f0 FCLOSE
$3 ($67) nmdebug > tr
PC=a.014951f0 FCLOSE
* 0) SP=41847530 RP=a.014951bc ?FCLOSE+$8
export stub: a.01468ea4 hxpurge_purge_a_file+$378
1) SP=41847530 RP=a.01468af8 ?hxpurge_purge_a_file+$8
export stub: a.00e386ec ol_nmlst_execute_ci+$30c
2) SP=41847030 RP=a.010855f4 hxpurge+$2d4
3) SP=41846f70 RP=a.01259560 exec_cmd+$11fc
4) SP=41842e30 RP=a.01258330 ?exec_cmd+$8
export stub: a.0125aee8 try_exec_cmd+$c8
5) SP=41842db0 RP=a.012580a8 command_interpret+$318
6) SP=41842930 RP=a.01257d5c ?command_interpret+$8
export stub: a.0125ba28 xeqcommand+$18c
7) SP=41842330 RP=a.0125b888 ?xeqcommand+$8
export stub: 93.00006774 main_ci+$68
8) SP=418422b0 RP=93.00007460 PROGRAM+$284
9) SP=41842230 RP=93.00000000
(end of NM stack)
$5 ($67) nmdebug > USE MACROS
$12 ($67) nmdebug > show_fclose
filenum : #12
disposition : #4
securitycode: #0
$13 ($67) nmdebug > c
/=4,b
Result=%(2)00000000 00000100 <= delete disposition
It would seem a bug to me not to include this.
Neil
>Just a minor point about logging, Keven eluded to it.
>
>System log events 105 and 160, report a file closure. So if the
>process was closed with a disposition to purge the file, it can be
>seen in the log files.
>
>However, if someone logs on to the command prompt and simply purges
>the file, I doubt there will be any trace in the system logs.
>
>-Craig
>
>
>
>--- On Wed, 9/16/09, Legault, Raymond D <[log in to unmask]> wrote:
>
> > From: Legault, Raymond D <[log in to unmask]>
> > Subject: files just randomly disappearing
> > To: [log in to unmask]
> > Date: Wednesday, September 16, 2009, 7:44 AM
> > Do you have system logging
> > turned on for file close?
> >
> > Allegro has a program that will allow you to toggle the log
> > file settings.
> >
> > http://www.allegro.com/software/hp3000/allegro.html
> >
> > The also have Filerpt.
> >
> > FILERPT is a log file analyzer. It has since been
> > superceded by the REDWOOD Tool, but this version is free.
> > Its main focus is on "File Close" records.(LZW), (std),
> > (Plain text information.)
> >
> > I also have a program that can read the log files searching
> > for job or session number, or
> > Filename or logon or console. Is this program we should the
> > file disposition. A 4 means purge.
> > So if you know the file name and time period that is was
> > purged, this can show you what program and
> > Session purged the file. If you want my LOGXL program, let
> > me know what format you need it in? ( Wrq, Std )
> >
> > Logxl
> >
> > B.C.S. MPE-XL Y2K Logfile Analyzer Version 1.4 WED,
> > SEP 16, 2009, 5:39 AM
> >
> > Enter Group.Acct for Log Files (Return=Pub.Sys)?
> > How do you want to access the Logfile? by:
> >
> >
> > 1. Session/Job Number.
> >
> > 2. Logon.
> >
> > 3. File Name.
> >
> > 4. Console.
> >
> > Enter your choice by Number.
> >
> >
> > Ray
> >
> > -----Original Message-----
> > From: John Bawden [mailto:[log in to unmask]]
> >
> > Sent: Tuesday, September 15, 2009 4:53 PM
> > Subject: Running FSCHECK in a job
> >
> > We are having some very strange problems with files just
> > randomly disappearing with absolutely no reason that we can
> > determine. It has been recommended that we run FSCHECK with
> > the CHECKALL option to see what it shows for a possible
> > explanation or to rule out some areas. The file structure is
> > very large and we would like to run FSCHECK in a job since
> > all users have to be off and this would have to run on a
> > weekend night. But we have heard that there
> > can be problems doing this, up to a system crash, but no
> > further explanation. I've run FSCHECK with the
> > SYNCACCOUNTING option in job mode for several years on
> > another system with no problems at all. Does anyone know
> > what problems there might be that are related to the
> > CHECKALL or has anyone experienced problems.
> >
> > TIA for nay advice pro and con.
> > John Bawden
> > Homestead3000 Consulting
> > MPE Forever
> >
> > * To join/leave the list, search archives, change list
> > settings, *
> > * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
> >
> > * To join/leave the list, search archives, change list
> > settings, *
> > * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
> >
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
