Re: system event trigger whenever a source file member is updated

["R. Bruce Hoffman, Jr." <rbruceh@xxxxxxxxxxxxx>]

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


> 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?

<LOL> Yeah...
Sorry to scare you.... <vbg>

The original process that I had set up ran on a 310 at V3R1 and was written
in CL and MI. The updates were made on one machine and then forwarded to an
F50 development machine across Token Ring and SNADS and processed through
another MI program.

If I remember correctly, the effect seemed instantaneous to the programmers,
so I would have to say, that unless you write some outrageous code on the
receiver end of the journals, you should be fine.

The act of performing the RCVJRNE and sending the data to a program is not a
serious performance issue on todays machines. It wasn't back then for us
either. So it would be that program and what it does. If it's just dropping
the data in a file... poof! No problem.



===========================================================
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