RE: Re: Analysing DSPLOG to CFG

Vern:

What has me wondering is that I didn't find entries in QHST that weren't also 
in the QHST* files when I ran a couple trivial tests today. DSPLOG made no 
difference. I have a minor nagging memory that I ran across a mention that 
something was done about this a few years ago, but nothing remotely solid.

And maybe I just didn't have sufficient time for testing.

As much as I regularly rely on the manuals for documentation, I can also point 
to numerous errors that have been in some of them at least back to V4R3. (And 
yes, I do point them out to IBM support, but...) Sometimes there just aren't 
people in IBM who know about some of the older parts of OS/400. E.g., try 
tracking down how to connect alerts (e.g., ADDMSGD ALROPT()) into SNMP 
nowadays. There used to be people who knew how/when the journal was created and 
other details. They're retired or moved on.

QHST has been around and fairly unchanged for a long time. About the last 
change I clearly remember was when DSPLOG no longer allowed any value for LOG() 
other than QHST. Maybe nobody knows.

Tom

midrange-l-request@xxxxxxxxxxxx wrote:

>   7. RE: Re: Analysing DSPLOG to CFG (Vernon Hamberg)
>
>Tom, this is right. The trick is to DSPLOG MSGID(###0000) or other 
>bogus message ID - this will bring all messages off the QHST *MSGQ 
>that are not yet in the QHST* files.
>
>One other gotcha is that these files are deleted during system 
>cleanup, according to the schedule set in GO CLEANUP, I think.
>
>Another problem is that the order is not always that of the names of 
>the QHST* files - there is always the possibility of wrapping and 
>overrunning days. See the CL Programming manual and, IIRC, the Work 
>Management guide for more information. Most of the above is in the 
>manuals. Some was painfully learned.
>
>Vern
>
>At 06:35 PM 12/12/2005, you wrote:
>
>>Reading all QHST* files wouldn't reliably give you all available 
>>entries somewhere in the past.
>>
>>The problem was something like QHST itself is a form of message 
>>queue, not a physical file. Only messages that had been copied to 
>>the QHST* files would be available for reading through those files.
>>
>>It's been a while, but IIRC, it was necessary to execute a DSPLOG 
>>command first. This somehow caused the *MSGQ to be flushed to the files.