Re: extracting audit journal info

Rob -

How does your SQL work given that a message file is not a "true file"? Are
you dumping the *MSGF to a *FILE? Or is there an IBM service or catalog
that also contains the messages from *MSGFs?

Thanks,

Steve McKay
(205) 585-8424
samckay1@xxxxxxxxx



On Wed, Sep 25, 2019 at 8:49 AM Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

Hey Rob!

Good find - turns out there are a whole bunch of messages with these
texts - CPX7064 - CPX7097. They all appear to have a count at the start
of how many texts are in the message.

Some of these look like later additions as more auditable events come
into play. So the OP could get the descriptions from here. It's
important to remember that the last 4 characters in a MSGID are
hexadecimal characters, so there is, if I remember what I saw 5 minutes
ago, a CPX708A, for example.

My assumption is that IBM keeps these in an orderly space - there is
more room in that basic range. Since we don't really know, there might
be things we'd miss.

What would be cool is to have an RFE to add these descriptions to the
output of the table function, since any change to these captions should
be known better to IBM than to us mere civilians.

Nonetheless, thanks for a great reminder of how much we see on the
screens comes from message files - format lines in SEU (yes, it's kind
of historical now, indeed!!) And how one method for globalization works.

Regards
Vern

On 9/25/2019 7:04 AM, Rob Berendt wrote:

Vern,
(responding to the slap in the face with a glove)
I accept your challenge. Let's start with a hypothesis. The hypothesis

being that a system which supports multiple languages probably does so
through the use of message files. So one would simply scan all message
files for that text.

One way to do that is with
SELECT MESSAGE_FILE_LIBRARY, -- MSGF_LIB VARCHAR(10)
MESSAGE_FILE, -- MSGF VARCHAR(10)
MESSAGE_ID, -- MSGID CHARACTER(7)
MESSAGE_TEXT, -- MSG_TEXT VARGRAPHIC(132)
...
WHERE MESSAGE_TEXT LIKE('%Previous journal receivers%') or
MESSAGE_SECOND_LEVEL_TEXT LIKE('%Previous journal receivers%') or
MESSAGE_TEXT like('%Journal or receiver operation%') or
MESSAGE_SECOND_LEVEL_TEXT like('%Journal or receiver operation%')
;
Results were
QSYS QCPFMSG CPX7064
QSYS QCPFMSG CPX7068
We win.

Rob Berendt
-- IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept
1600 Mail to: 2505 Dekko Drive Garrett, IN 46738 Ship to: Dock 108
6928N 400E Kendallville, IN 46755 http://www.dekko.com -----Original
Message----- From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>
On Behalf Of Vernon Hamberg Sent: Tuesday, September 24, 2019 7:00 PM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx> Subject: Re: extracting audit journal
info CAUTION: This email originated from outside of the organization.
Do not click links or open attachments unless you recognize the sender
and know the content is safe. Those layouts are for outfiles for the
different types of journal entries. The display_journal() table
function is a different animal. I don't remember whether the screen
presentation of DSPJRN has a textual meaning for the various codes -
if so, there is probably a place to pull them from. Cheers Vern

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com