RE: Understanding a Query/400 Error Message

Al,

The only thing that would cause this is the structure of the file being
referenced is different from when the queries were last saved.   Either
something (or someone) has changed the structure of the file or as Peter
noted, you may be picking up an old version of the file from another
library.    However, usually the file library is hardcoded in the query.
Another possibility is you're picking up old versions of the queries from
another library.

Bud

-----Original Message-----
From: Al Gershen [mailto:aldg1@charter.net]
Sent: Friday, November 15, 2002 1:09 PM
To: mapics-l@midrange.com
Cc: Gershen, Al
Subject: Re: Understanding a Query/400 Error Message

Hi Peter Vidal & Bud Roble:

Thank you for your postings on this matter.

I did a typo when I indicated the last update for the
DATECTRL DB file.  It was done by myself last Sunday,
November 10, 2002.

I'm afraid I glanced at the calender and entered a date
that wasn't even a Sunday.  I'll try to be more careful
next time.

Our DATECTRL DB file is used in many other queries on a
daily basis and it is updated once a week.  Since its last
updating on the 10th, it was run in daily queries thru
this morning without any problem.

All of a sudden these error messages arise.  I find it
very strange.

Thanks you for your comments and I welcome your followup
coments, if any.

Regards,
Al Gershen
ECS Composites
Grants Pass, OR
aldg1@charter.net


On Fri, 15 Nov 2002 15:52:24 -0500
  "Peter Vidal" <Peter_Vidal@pall.com> wrote:
>
>The first "strange" thing I can see here is that the
>DATECTRL DB file with its
>one record that "was last updated on Sunday, Nov 23rd".
> I guessed it should be
>on or before year 2001?  Maybe the good file has suffered
>a change in its record
>layout and maybe this "bad" file version of DATECTRL is
>in a library that is
>above the library SLK in the library list, where the good
>file is.
>
>Obviously it is a level check and the system will allow
>the user to react at it
>by cancelling the program that calls this task
>("C") or to skip this error and continue processing
>("I").  If this is a job
>that prints reports, I guess is save to answer with "C"
>and verify that the file
>in use in the query is the right file.  You can also get
>in to the query itself
>and exit it, by doing a "save" of it and that will help
>the query to recognize
>the format of file DATECTRL.
>
>Hope that helps...
>
>Peter Vidal
>Pall Aeropower Corp. / SR Programmer Analyst
>www.pall.com  /  Peter_Vidal@Pall.com
>727-539-8448, x2414
>


On Fri, 15 Nov 2002 12:50:30 -0800
  Bud Roble <BRoble@CharlesRobleConsulting.com> wrote:

>Something must have changed the structure of the DATECTRL
>file.    The error
>you're receiving is similar to a level check you would
>get in an RPG program
>when the structure of a file has been changed without a
>recompile of the
>program.    All you need to do is bring the queries up in
>edit mode and
>resave them so the level identifier on the file will
>match the query
>definition.   Did you install some sort of upgrade of did
>someone add a new
>field to the DATECTRL file for some reason?    As far as
>the error
>messages....   I = Ignore, C = Cancel.    Note that you
>can get a more
>detailed explanation of the error messages if you place
>the cursor on the
>message and then press the F1 key.   If you page through
>the additional
>information, you will see an explanation of the "I" and
>"C" and what they
>will do.
>
>Bud Roble
>AS400 and PC Network Computer Consultant
>(805)794-3027
>broble@CharlesRobleConsulting.com
>

_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
To post a message email: MAPICS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/mapics-l
or email: MAPICS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mapics-l.