Re: System messages/journals help

Steff

The QHST* message files have a rather interesting layout. They can be read just fine in RPG - there's the RPG hook you need!!

They have a text description that tells you the dates included, as I recall - something like that. The NAMES are not necessarily in the right order alphabetically.

There is documentation in both the CL Programming manual and the Work Management manual - the information is not all duplicated between the 2 references.

Both manuals can be found at InfoCenter, so go have some fun!!!

2 very important messages that you find in the history logs are the job start (CPF1124) and job end (CPF1164) messages. There is information there that you will NOT see in DSPLOG at all. Performance data is stored there. So the only way to get to it is using a program.

HTH
Vern

----- Original Message -----
Thanks Chuck

This was the start.
Next step is to write the rpg programs that deal with/display this data.
That's the reason i thought I should start here. :)
Correct me if this is wrong place to start.

QSYSMSG - that is the MSGQ I was talking about.
I meant the audit journal.
And from your answer, I gather that the QHST###### will detain all my messages, and I can just sort through them for the specific messages I need.

Thanks


Sent from my iPad

On 30 באפר 2013, at 18:19, CRPence <CRPbottle@xxxxxxxxx> wrote:

On 30 Apr 2013 01:34, Steff wrote:

I'm new to the system part of iSeries.
Need some help understanding.

OK... but what is the tie-in to RPG?

We have the system journal, MSGQ, QHST.

Do you mean the /audit/ journal? A particular *MSGQ such as QSYSMSG?
The QHST is a message queue for which its data is manifest via the
QHST###### files.

What types of events will go to which destination?
Is there an overlap of data?

Am I right to assume that QHST will get info messages, that do not
need to be dealt with?
And the MSGQ will get messages that might need immediate attention?

QHST gets a copy of every message sent to QSYSOPR, plus other
messages that the OS component deemed worth having a copy logged, even
if not to the system operator; e.g. data that might be relevant to debug
an issue, but should not clutter the *SYSOPR message queue.

Perhaps the Opening Post should be clarified and then sent to an
appropriate list.... to address the more appropriate audience.

--
Regards, Chuck
--
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.