Re: Get Record Creation Date

Henrik

Your point about journaling and disk space is well-taken. On the other hand, a trigger delays completion of the IO, because a trigger is executed in a synchronous manner during the IO. So no matter which approach William takes - and neither need be characterized as excrement - there is a cost. Using a trigger will eventually also have a disk space cost, if William stores the history of adding records (creation only, according to his original post).

As I and others have posted, journaling has no effect on format-level checks. And neither do triggers. If William turns on journaling for a file he's interested in, maybe with after image only - I forget which image is written when creating a new record - it would be wise and perhaps necessary to purge unneeded information.

On 1/5/2014 6:51 PM, Henrik Rützou wrote:

William

as you can't add a new field to the file a trigger program is the way to go
or a product that on a general level monitors any DB changes without any
changes to the DB.

Dieter state the journaling has no impact to the system! This is completely
wrong, journaling takes up disk space, it consumes CPU and what worse is
that it affects the performance in the disk controllers and disks that
traditionally are the bottleneck on a P7 machine.



On Mon, Jan 6, 2014 at 1:36 AM, William Salim <william.salim@xxxxxxxxx>wrote:

100 percent agree with you, this whole things are 'shits'. It is just
adding a new field or journalling.
A very simple things.

Just need to find the way and not be at the same company after that :)
On Jan 6, 2014 4:58 AM, "D*B" <dieter.bender@xxxxxxxxxxxx> wrote:

@Chuck:

using RRN is bad design and bad design will be punished, if not today, so
in the future, when you are'nt expecting it.
The original application could not be stabilized without changes to this
application - thinking about this and that we would know the time, when

it

fails, I would simply recommend to STRJRNPF to all files!!!, so that you
could see, what had happened and the effort would be minimized to repair.
Regardless what some people might tell: this would have no impact to your
running programms!!! Maybe the bestter idea would be to replace this
application, before it is replaced by soem MS toys - then journaling and
commit would no longer be an issue...

Dieter
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.