RE: Question about MONMSG

[KirkG@xxxxxxxxxxxxxx]

We are finishing a System 36 to AS/400 Native conversion for client. After
repeated requests for the client to do extensive testing and if possible
at least one month of parallel they did very little testing.  Now the
system isn't behaving like it used to and we are live. We used Target/400
to do a fair portion of the conversion but a lot of custom work still
needed to be done.

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.

All in all I just needed a warm fuzzy that I understood how monmsgs were
handled.

thanks






Kirk,

Your assumptions strike me accurate.  Perhaps I'm reading too much into
the question, but it sounds like something is not behaving the way you
expected.  If that's the case, what happened?

> Are my assumptions correct in that...
>
> #1 If I use a MONMSG after a CL cmd, that if the msgid matches then
"NO
> OTHER SYSTEM LEVEL" action will take place, only the action in the
MONMSG.

If the message id matches, then program control passes to the exec
statement within the MONMSG command.  I'm not sure what you mean by 'NO
OTHER SYSTEM LEVEL ACTION'.

> #2 A Global MONMSG does "NOT" take precedence over a local MONMSG at
the
> cmd that applies.

A local MONMSG will take precedence over a global, yes.

Andy Nolen-Parkhouse

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.