Re: SEQONLY(*NO) Message

["Michael Naughton" <mnaughton@xxxxxxxxxxxx>]

David,

Thanks for the advice, but  unfortunately it doesn'r really solve my
problem, which is that  when I rolled out the application all the users
noticed the message and called me asking, "What's that all about?" I
probably said, "Don't worry about it" about  two dozen times, but we
actually like our users to notice the messages (usually, they're conveying
useful information), and for all kinds of reasons we try to keep the rules
simple.

I solved it with the "input / add" combo, but I was just wondering if
there's some way to code an F-spec for output so that the message goes
away. The answer may well be "no", but I figured it never hurts to ask  .
. . 


rpg400-l@midrange.com writes:
>> When I run the program, I get this message:
>> Open of member MSI1C was changed to SEQONLY(*NO).
>
>Ignore the message ... it's just the query optimizer saying that,
>considering the way you opened the file (read only, probably without a
>key),
>it would be more efficient to process the file using that override
>parameter.
>
>david


Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA  01376
413-863-4357 x444
mnaughton@juddwire.com