SEQONLY(*NO) Message -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: SEQONLY(*NO) Message
From: "Michael Naughton" <mnaughton@xxxxxxxxxxxx>
Date: Wed, 22 Jan 2003 10:24:06 -0500
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo.cgi/rpg400-l>,<mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo.cgi/rpg400-l>,<mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

I have a  PF, MSI1C, and an LF over it, MSI1CL1. The LF is keyed, but the
PF is not. In my program I open MSI1CL1 for update with keyed access, and
I open MSI1C for output only.

When I run the program, I get this message:
Open of member MSI1C was changed to SEQONLY(*NO).

I'm not intentionally setting the file to SEQONLY(*YES) (as far as I
know), so I wonder why I'm getting this message. Is there any way to make
it disappear?

I have discovered that if I open MSI1C for input with "add records"
specified, then the message goes away, but since I'm not doing any input
on it that seems like kind of a hokey solution (?).

If anyone has any tips, I'd appreciate it! Thanks!

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

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: SEQONLY(*NO) Message , David Gibbs

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.