RE: Question about MONMSG

[KirkG@xxxxxxxxxxxxxx]

I don't have many details as to which messages or the exact problem. The
client and I were discussing the overall flow of monmsgs. You are right
there are times when getting the "RIGHT" thing monitored.



---------------------------------
Kirk Goins
IBM Certified iSeries Technical Solutions Design
IBM Certified iSeries Technical Solutions Implementation
Pacific Information Systems - An IBM Premier Business Partner
503-674-2985           kirkg@pacinfosys.com
"WE KNOW TECHNOLOGY"
---------------------------------





David.X.Kahn@gsk.com
Sent by: midrange-l-admin@midrange.com
12/17/2001 03:30 AM
Please respond to midrange-l


        To:     midrange-l@midrange.com
        cc:
        Subject:        RE: Question about MONMSG


Kirk wrote:

> Somewhere along the line it appears monmsg's were put in
> the code that are causing more problems that not. By system
> level I meant things like the system reply list if it was
> used. The customer's SW is ALL CUSTOM CODE.

Kirk, I often find that confusion with MONMSG and inquiry messages is
caused by a misunderstanding of the sequence of events and what can be
monitored for. For example, if a physical file exceeds its maximum size
during a copy an inquiry message CPA3138 is issued. This can be auto
answered through the system reply list or by a default answer in the
message file, but it cannot be monitored for in the CL program because it
is not an escape, notify or status message. If the inquiry message is
answered with a 'C' then a CPF3140 is sent to the program message queue
and
this is what can be monitored for. By then of course the inquiry message
has already been answered, either manually or by default.

Does this sound like the sort of thing that's happening?

Dave...
               _________  ,___o
             __________   _\ <;_
           ___________   (_)/ (_)       http://www.twickenhamcc.co.uk
=======================================================
The opinions expressed in this communication are my own and do not
necessarily reflect those of my employer.