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?

               _________  ,___o
             __________   _\ <;_
           ___________   (_)/ (_)
The opinions expressed in this communication are my own and do not
necessarily reflect those of my employer.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.