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



Etienne,

You can certainly use generic message ID's, but I have found
that message files are a valuable part of what the AS/400 offers.
If you are not concerned about platform independence, a message
file is an easy way to work with message information. I find them
easier to work with than some of the Java-centric alternatives
like resource bundles.

Whatever you do, I would centralize this type of logic. I extended
the support provided by the Apache Logkit framework. That
support is part of Avalon. The advantage is that they have
already built a reasonable equivalent to the AS/400 logging
in Java that can be adapted to the AS/400 environment.

David Morris

>>> Etienne.Richards@penske.com 02/07/02 06:07AM >>>
All,

A while back I asked a question about creating job log entries from
Java and
I did the correct answers, thanks.

But...

The Java world and the "old style " AS/400 world is sometimes worlds
apart
(As most of you have probably experienced). I am looking for a way of
logging application errors / warnings that will be easy for "old
style"
AS/400 users to accept. Writing this to a log file on the IFS seems to
be
counter intuitive for some users.

1. Can I write arbitrary messages to a Job log? (Without message id's)
2. Can you suggest another solution that is closer to the way other
typical
AS/400 apps' do this type of error reporting?

Etienne


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.