Re: Question about MONMSG

Al Mac wrote:

> So we go into that error message reply list & alter the
> rules so that if the user just presses enter, the least
> harmful option in general is taken.  We also adjust
> phraseology of error message so more users comprehend
> what just happened.

I see. You mean you alter the text and default replies of the message
descriptions in the vendor provided message file.

> We do this to scores of error messages in the vendor
> package.

This is really necessary?

> but seems to me that error messages do not work the
> same way as programs.
>
> LOAD PROGRAM X
> It goes through library list 1 2 3 4 5 library until
> it finds PROGRAM X which could be in libraries 5 7 9
> 11 but what is loaded is the version in library 5
>
> ERROR MESSAGE 1234
> It goes through library list 1 2 3 & finds error message
> member in library 3 which does not have error message
> 1234 ... that is actually in library 4 ... it quits
> looking

It works exactly the same way for programs and message files. It searches
the library list until it finds an object of the same name and type.
Remember that a message description is not an object. As you say, when it
finds the message file it stops looking even if the message description is
not found. You seem to be arguing for different behaviour in locating
message files and programs. The system would search the library list until
it found a message file containing the message description you are looking
for. This would save you the chore of merging your changes back into the
vendor's file whenever you get an update.

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.