Re: Quieter Monitors

[Rory Hewitt <rory.hewitt@xxxxxxxxx>]

Vern,

Yeah, I've seen that article, thanks. Actually, that was the first IBM
article I've seen which expicitly stated that MSGKEY can (and should) be
thought of as an integer rather than as a 4-byte character field - something
we all figured out long ago...

I also wrote an article for the SystemiNetwork magazine about a command I
wrote called RMVJLMSG (Remove Job Log Messages), which allows you to remove
job log messages based on a number of criteria (sendng program (generic),
receiving program (generic), message id (generic) and more). It doesn't
include the starting/ending concept, but I've also used that. I thought I
could maybe use that as a basis for this.

I guess you could send either a message at the start of the program, or (if
you need to be more precise) just after the monitor:

monitor;
  startMsg();
  //do work here
on-error;
  removeMsgs();
endmon;

where removeMsgs() would remove all messages since the previous call to
startMsg();

Rory

On Mon, Feb 22, 2010 at 8:30 PM, Vern Hamberg <vhamberg@xxxxxxxxxxx> wrote:

> Rory
>
> IBM has published technique for handling all messages generated during a
> certain process. The idea is to send a dummy message and get its message
> key, then do whatever you do, then send another dummy and get ITS key.
> Then do the RCVMSG RMV(*YES) or QMHRCVPM and use the keys between the
> starting one and the ending one. They might not all be there, so be sure
> to allow for that error.
>
> This method gets everything in between the 2 dummy messages, from
> whatever source.
>
> One might want to keep certain messages, so appropriate conditional
> statements can be included.
>
> I don't have the link to the KB article right now, but I bet you could
> search for QMHRCVPM in the software knowledge base and get close.
>
> HTH
> Vern