Re: Anyone using the *AFTER *READ Triggers in V5R1/V5R2?

Yes, but as I understand it, HIPPA compliance can be achieved
using the existing OS/400 *AFTER *READ triggers, because from
what I hear, all you need to do for HIPPA compliance is be able
to "log" some entries about who accessed what, etc. (e.g. by
writing entries to another file from within the *READ trigger).

But, from my point of view, what I want to do is to be able to
implement some 'business rules' in which the actual data returned
to the calling program may be different, depending on some "rules".

This allows me to implement an "object" my "encapsulating" the
access to a certain "file" (a table representing instances of a given
object type), and then "traditional" 3GL applications issuing a
"read" against this file are "invoking a method", and getting some
results, similar to invoking "getters" in true OO programming, while
I can use the *INSERT, *UPDATE and *DELETE triggers to cause
similar behavior for applications issuing a WRITE, UPDAT or a
DELET (in RPG/400 terms) to "trigger" the equivalent of the "setter"
methods of this object class.

This should allow me to come up with a coexistence strategy to
enable me to start to migrate "legacy" applications into a more and
more "object oriented" and more modern design, but gradually.

Mark

----- Original Message -----
From: "Al Barsa" <barsa@barsaconsulting.com>
To: <midrange-l@midrange.com>
Sent: Saturday, November 23, 2002 3:16 PM
Subject: Re: Anyone using the *AFTER *READ Triggers in V5R1/V5R2?


>
> We have IDed that *READ triggers are necessary for HIPAA compliance.
>
> Al
>
> Al Barsa, Jr.
> Barsa Consulting Group, LLC
>
> 400>390
>
> 914-251-1234
> 914-251-9406 fax
>
> http://www.barsaconsulting.com
> http://www.taatool.com
>
>
>
>
>
> |---------+----------------------------->
> |         |           jpcarr@tredegar.co|
> |         |           m                 |
> |         |           Sent by:          |
> |         |           midrange-l-admin@m|
> |         |           idrange.com       |
> |         |                             |
> |         |                             |
> |         |           11/23/2002 05:10  |
> |         |           PM                |
> |         |           Please respond to |
> |         |           midrange-l        |
> |         |                             |
> |---------+----------------------------->
>
>---------------------------------------------------------------------------
---------------------------------------------------|
>   |
|
>   |       To:       midrange-l@midrange.com
|
>   |       cc:
|
>   |       Subject:  Re: Anyone using the *AFTER *READ Triggers in
V5R1/V5R2?                                                     |
>
>---------------------------------------------------------------------------
---------------------------------------------------|
>
>
>
>
>
> "What the heck good is a read trigger if.... "
>
> I remember listening to a guy at CUDS at COMMON tell us he had somehow
> (thru tricks that would be in Leif's land of expertise)  had implemented
> READ Triggers
> a few years ago  around V4Rsomething.    It was Ask the experts Night at
> CUDS.
> (Which BTW, is a GREAT Source of learning some really neat things that are
> being done)
>
> (Oh, ya, The guys from Rochester were impressed).
>
> The reason he needed it was to  know "WHO" was accessing "WHAT"
> information.
>
> "Who is so interested in ......."     Fill In the Blank.      For his
> company it was critical to know that
> for certain tables.
>
> It's one of those things that you rarely would need the
> capability of  doing, but  if you do,  there is nothing else that will do
> it for ya.
>
> John
>
> (Naw, You can't advertently or Inadvertently alter the image that the
> application sees)
>
>
> ----------------------
>
>
> Hello, all:
>
> Has anyone used the "native" *AFTER *READ triggers that were
> introduced with V5R1?
>
> I tried using one, but no matter if I change data in the "original"
> buffer or the "new" buffer, it does not seem to matter; the actual
> data from the file is ALWAYS (apparently) returned to the calling
> program, regardless of what the read trigger does.
>
> What the heck good is a read trigger if there is no way to alter
> the data in the buffer?  I mean, after all, you can alter the data
> in other cases, such as an Insert or Update trigger, right?
>
> Thanks,
>
> Mark S. Waterbury
>
> _______________________________________________
> 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.
>