RE: RE: SEQONLY(*NO) Message

[Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>]

>It shows up right at the bottom of the screen, 
>where we've got a message subfile showing what's 
>in the program's message queue (we send status and
>error messages to this message queue from within 
>the programs, so they automatically show up there. 
>(I don't know if that's unusual -- I haven't
>worked a lot of other places -- but it seems to work 
>pretty well.)

Hi Mike!
That's unusual.  It implies a high level of end-user competency to interpret
the messages (status!) and act accordingly.  This particular message is Very
Common.  It comes from the compiler trying to optimise the blocking.  Look
at the bottom of the compiler listing to see what I mean.  If it bothers the
end-users, you might consider copying it to your own message file and
changing the text to something more non-controversial.  Then use an OVRMSGF
command to 'blend; your message file with IBM's.  I can't imagine
intentionally changing every program this happens in just to avoid the
informational message, but every place is different!
  --buck