× 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.



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
>



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.