On 10/15/2010 7:53 PM, W. Kevin Kelley wrote:
MPF has the following behavior:
If SUP(YES) or SUP(ALL) is coded on an MPFLSTxx message definition or on
a .NO_ENTRY statement, any matching message will always be written to
hardcopy (unless overridden by an MPF exit) even if the message -- when
issued -- specified no hardcopy (i.e. MPF always forces a matching message
that is to be suppressed from display to be hardcopied).
I had no idea this was the case. IMHO, this behavior seems "wrong". At the very
least, it violates the "principle of least astonishment." Had someone noticed
this when MPF was first written, it might have been APARable.
--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
310-338-0400 x318
edja...@phoenixsoftware.com
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
