|
midrange.com
Matt,
You are correct as far as the DB journal receiver is concerned. When a
audit journal receiver reaches its maximum size, auditing is terminated.
The system will set the system value of audit control to *NONE. The OS
will continue on. QSYSOPR will be notified that auditing has been
terminated.
William J. Finch
Senior Services Consultant
Lakeview Technology
Home Office: (702) 256-4309
Fax: (702) 256-4315
Cell: (630) 215-4675
E-mail to finchb@lakeviewtech.com
"Tyler, Matt"
<mattt@wincofoods. To:
"'midrange-l@midrange.com'" <midrange-l@midrange.com>
com> cc:
Sent by: Subject: RE: Library trigger
midrange-l-admin@m
idrange.com
10/10/2002 08:10
AM
Please respond to
midrange-l
William,
Unfortunately, I can only speak of the horrors of journal
receivers
form the database journal pint of view. They tend to fill up the fastest.
We have a mirroring product that set ours to user control with out
notifying
us and the receivers filled up. Nothing else that used those database
objects was allowed to occur. Programs all over the system can to an
immediate halt. I would assume all journaling operates the same.
Thank you,
Matt Tyler
Mattt@wincofoods.com
-----Original Message-----
From: finchb@lakeviewtech.com [mailto:finchb@lakeviewtech.com]
Sent: Thursday, October 10, 2002 08:59
To: midrange-l@midrange.com
Cc: 'midrange-l@midrange.com'; midrange-l-admin@midrange.com
Subject: RE: Library trigger
Leland,
Matt is almost correct in his statement that all comes to a halt if a
journal receiver reaches its maximum size (2gb or 1tb depending on how it
is configured). When the audit journal receiver reaches its maximum size,
audit control system value is set to *NONE and auditing is turned off.
Letting the system manage the generating of new receivers at a specific
threshold is a good thing. The system manage deletion of journal receivers
could cause an opportunity that you may not want to have. If you delete a
receiver that has not been examined for entries (i.e. T-CO for you create
object), you cannot recover that entry. I would also recommend to set the
size of the audit journal receiver, if you have enough room on disk, to
1.5gb minimum. Journal receiver generation has system overhead attached to
it, the more it changes and generates a new receiver, the worse the
performance.
Hope this helps and have fun with journaling,
William J. Finch
Senior Services Consultant
Lakeview Technology
Home Office: (702) 256-4309
Fax: (702) 256-4315
Cell: (630) 215-4675
E-mail to finchb@lakeviewtech.com
"Tyler, Matt"
<mattt@wincofoods. To:
"'midrange-l@midrange.com'" <midrange-l@midrange.com>
com> cc:
Sent by: Subject: RE: Library
trigger
midrange-l-admin@m
idrange.com
10/10/2002 07:43
AM
Please respond to
midrange-l
Leland,
It depends, on how much work you want to put into managing the
journal. If you "user manage" you will need to write a program that can be
scheduled to manage receivers before they fill up. Once a receiver fills up
nothing else happens on the system for objects that create entries to that
journal. Programs can halt.
Using the system just requires you to write programming to
manage
the receivers after they have been filled and marked as online (not
currently being added to). Leaving receivers there can eat your DASD in a
hurry. If you need those journals for future auditing, save them to
tape/optical and then delete them, otherwise just delete them.
Thank you,
Matt Tyler
Mattt@wincofoods.com
-----Original Message-----
From: Leland, David [mailto:dleland@Harter.com]
Sent: Thursday, October 10, 2002 07:25
To: 'midrange-l@midrange.com'
Subject: RE: Library trigger
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
This is perfect. Now, one question about the QAUDJRN journal - should this
be system managed or user managed? Mine is currently set to user managed
but I think that's just because I created it some time ago when system
management was not an option.
Dave
-----Original Message-----
From: Vernon Hamberg [mailto:vhamberg@attbi.com]
Sent: Wednesday, October 09, 2002 5:19 PM
To: midrange-l@midrange.com
Subject: Re: Library trigger
Dave
It's possible to use security auditing, I think. You can set it up to get
an entry on a DTAQ every time something is added to the audit journal. The
CO entry type is for 'Create object'. You could wait on the DTAQ and filter
the entries for the library you're interested in. Somewhat brute force, I
supoose, but you can limit the kinds of entries collected, to some extent.
Of course, that is a never-ending-program, but IMO fairly low-impact - and
the system notifies it automatically.
Regards
Vern
At 03:14 PM 10/9/02 -0500, you wrote:
>This message is in MIME format. Since your mail reader does not understand
>this format, some or all of this message may not be legible.
>--
>[ Picked text/plain from multipart/alternative ]
>Anyone know of a way (outside of having a constantly running monitor
>program) to automatically trigger an event when an object is placed in a
>library? I would like to create a library that, when a user creates a
file
>in it (typically using Query), a trigger program of some type would
>automatically FTP that file somewhere.
>
>Dave
>_______________________________________________
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.
