Re: Monitoring QSYSOPR

Hello Ted,

(Copied to the list for archival reasons)

You wrote:
>Yeah, but I've also got other stuff I'd like to monitor on a global basis.
>Like "IPL Complete".  Which begs another question...After IPL I submit the
>MONITOR job, since the code looks at the last message and checks for blank
>keyvar, wouldn't it skip "IPL Complete" message?

That's correct, but that is what the example code was intended to do.  It
starts at the end of the message queue and shows new messages as the
arrive.  You could easily modify to start at the top of the queue and
process all messages currently in the queue.

Also,  QHST is initially a message queue but it also has a series of
database files associated with it that can be processed in your favourite
HLL.  See Chapter 8 of the CL Programmer's Guide for details of the file
layout etc.

The files exist in QSYS and are *PUBLIC *EXCLUDE.  The file names are of
the form QHSTyydddc where yy is the 2-digit year, ddd is the ordinal day of
the year (this format yyddd is commonly called a Julian date), and c is a
rolling character A to Z.  A new log file is created when the QHST message
queue exceeds the size threshold specified in the QHSTLOGSIZ system value.
The last character in the file name changes changes if a log file is rolled
more than once per day.  The text for the file shows the date range of the
messages contained in the file.

The QUSRTOOL examples used to provide a PRTQHSTANL command and supporting
programs showing how to do this.

Regards,
Simon Coulter.

--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists
   http://www.flybynight.com.au/

   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175   mailto: shc@flybynight.com.au   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------