Re: Monitoring IFS directory for file creation

Carsten,

 1) I'll look at the file ID tip for sure.

 2) Friday's test was done on V5R3 but I just did a quick test on V5R2 (we
upgraded over the weekend and I feel so decadent having a model 270 all
to myself. Not sure how long that will last though...) and I did get 'CS'
records when journaling was set to 'anal-retentive'. Meaning that I used
OpsNav to set both the 'Include open, close and synchronization entries'
and the 'Journal new files and folders' checkboxes. These settings
resulted in the creation of 55 journal sequence numbers, but this volume
should not be a problem at this point since we're importing less that ten
files each day.

 3) Perhaps I used a different OpsNav function to start journaling? That's
the main thing that bothers me about this mouse-clicky OpsNav stuff - I
don't know how to record and rebuild the various object properties. If
there is a green-screen command I can write a CL to rebuild an object,
its logicals and other properties. With values contolled exclusively in
OpsNav I don't know how to automate the rebuild process!

 Again, many thanks. You've saved be a lot of time and I owe you a cold one!

John King


> Hello John,
>
> To take the last question first - it is the file ID - Bruce Vining
> mentioned
> a while ago the name of the API to turn that into something human
> readable:
> http://archive.midrange.com/midrange-l/200409/msg00045.html
>
> As for the CS journal entry: I don't get such an entry when a file is
> created in the IFS on my V5R2 system - I get a B0 (Begin create) and B1
> (Create summary). And the B1 is issued before the file is closed, that's
> why
> I had to resort to the object lock method. Judged by the description of
> the
> CS entry it pretty much sounds as if that would be a good one to monitor
> for - but as I said, I haven't noticed it on my system. What is your
> release?
>
> Best regards,
> Carsten Flensburg
>
>
> ----- Original Message -----
> From: <johnking@xxxxxxx>
> To: <midrange-l@xxxxxxxxxxxx>
> Sent: Monday, January 24, 2005 7:34 PM
> Subject: Re: Monitoring IFS directory for file creation
>
>
>> Carsten,
>>
>>  Thanks, I missed that article in "iSeries". I love that magazine (we've
>> subscribed since it was a stapled-together newsletter for the S34 back
>> in
>> the early '80s) but trying to locate anything on their website always
>> raises my bloodpressure <grin>!
>>
>>  Question about the lack of a journal event: When I enabled journaling
>> on
>> a test directory and used Explorer to copy a small file into that
>> directory, a 'CS' journal entry was visible from DSPJRN OUTPUT(*) as
>> shown below. This record's position in the journal, after the 'CM' and
>> 'EC' and 'CA' events leads me to think this is the record I should
>> monitor for. Am I missing something?
>>
>>  Interesting to note that the JOOBJ field created by DSPJRN
>> OUTPUT(*OUTFILE) results in some hex value - probably some file handle
>> that needs to be rsolved with yet another API!
>>
>> Many thanks, John King
>>
>> Journal  . . . . . . :   IFSMON          Library  . . . . . . :   JONLIB
>> Sequence . . . . . . :   88
>> Code . . . . . . . . :   B  - Integrated file system
>> Type . . . . . . . . :   CS - IFS object closed
>> Object . . . . . . . :   /home/JOHN/Junk/test.jpg
>> Flag . . . . . . . . :   0               Ref Constraint . . . :   No
>> Date . . . . . . . . :   01/24/05        Time . . . . . . . . :
>> 12:21:01
>> Count/RRN  . . . . . :   0
>> Job  . . . . . . . . :   003683/QUSER/QPWFSERVSO
>> Commit cycle ID  . . :   0
>> User profile . . . . :   JOHN            Program  . . . . . . :
>> QPWFSERVSO
>> Ignore APY/RMV . . . :   Yes               Library  . . . . . : *OMITTED
>> Trigger  . . . . . . :   No                ASP device . . . . : *OMITTED