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



Hi William

To go back to your first post - is this a requirement by your employer, to keep track of when records are added to a file?

If so, something does need to be done, obviously. I think your options are either using a trigger or journaling.

Each option will have no impact on existing options, at least with regard to level checks.

Triggers will have a possible impact on performance of the WRITE, since a trigger is called from the database low-level process and continues only after the trigger is done. There will also be some disk space concerns, since you will likely store each new record's identifying information (a unique key, if possible) and the timestamp when record was created. You could also store which job created the record. (Hmm, sounds like a journal entry.)

Journaling also adds some processing, although it might not be completely synchronous. And the journal receiver will take up space. That space will include the image of the record - not just unique identifying information - and other things. There will be more information than you need, so it will be necessary to purge unwanted journal entries from time to time - or extract what you want into a table periodically.

You will probably have to present alternative approaches - these seem to be the main options you have. Each has its own additional costs.

Journaling was once seen as a performance hog - someone who has worked at the same job for 20 years may still believe that - this is no longer true, however.

Triggers are a new thing - well, at least since maybe 10 years ago! Again, there may be resistance to something with which a person is unfamiliar.

But something has to be done, right?

Best wishes - and a happy new year!! Already!!

Vern

On 1/6/2014 12:32 AM, William Salim wrote:
There around 15 files like those, there are many applications that attach
to the files.
The program build by to many hard coded. Person who know details is only 1,
that make him the key person and has been here for around 20 years.
And no version control for the applications, everything right through the
productions without ALDON that we use for others.






On Mon, Jan 6, 2014 at 1:21 PM, Booth Martin <booth@xxxxxxxxxxxx> wrote:

Without mentioning personalities, what are the political issues? Someone
doesn't like changes? Someone trying to prove that the AS/400 is too
old and can't do modern stuff? Will whatever suggestion made be turned
down, even if it is simple, cheap, and easy?




On 1/6/2014 12:07 AM, William Salim wrote:
Sorry guys, not following this, since there is a production issue.
Agree that the app need to change but the things behind this is more
political than technical.

--
Booth Martin
www.martinvt.com
(802)461-5349
Skype: booth.martin

While you don't greatly need the outside world, it's still very
reassuring to know that it's still there.
--
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.





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.