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



Ahh, got it.  Although you frighten me a little bit:

> <snip> processing of the resultant journal entry could happen
>  in the next second or the next week, depending upon <snip>

*Generally speaking*, on an AS/400 for which we are seeing good response
times, batch jobs are running quickly, etc. etc., could we expect that this
might occur in the next second at least 99% of the time?  In other words, if
we're otherwise humming along on our system, there should be no reason why
the processing of the resultant journal entry shouldn't always be done
within, say, 5 seconds?

Will be looking into this further.

- Dan Bale

-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]On Behalf Of R. Bruce Hoffman, Jr.
Sent: Wednesday, March 13, 2002 4:29 PM
To: midrange-l@midrange.com
Subject: Re: system event trigger whenever a source file member is
updated


----- Original Message -----
From: "Dan Bale" <dbale@samsa.com>
To: <midrange-l@midrange.com>
Sent: Wednesday, March 13, 2002 11:29 AM
Subject: RE: system event trigger whenever a source file member is updated


> >It would operate asynchronously from the member changes, which is
> >also different from triggers. That might be a consideration.
>
> You lost me.  What do you mean by "operate asynchronously"?  FWIW, I have
> never done triggers, but I think I have the concept.

The process that deposits records, runs the trigger, and does not return
from the record operation until the trigger ends. This is synchronous.

The journal would run a totally separate process for the receive from the
journal, so the act of changing the member would be independant of and
therefore asynchronous from the process of receiver data. Two separate jobs
without any dependancy on the completion of one for the continuation of the
other.

In other words, the act of changing the member completes and goes on it's
merry way, and the processing of the resultant journal entry could happen in
the next second or the next week, depending upon design and performance of
the platform.

===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified Specialist - iSeries Administrator
 -- IBM Certified Specialist - RPG IV Developer

"Suppose you were an idiot...
  And suppose you were a member of Congress...
  But I repeat myself."
    - Mark Twain



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.