Re: Level Check Issue

Problem solved, or at least discovered. I was assured that the DDS had not changed in years. Well, after digging,there was a new field inserted just before the last field in the DDS before the 08 file was built. What is that saying, "trust but verify"?

Kelley

----- Original Message -----
From: "Kelley" <kshaddrick@xxxxxxxxxxxxxxxx>
To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Sent: Tuesday, January 15, 2008 2:18 PM
Subject: Level Check Issue

We have many files that are recreated each fiscal and calendar year end.
They are mainly detail files for A/R, O/E, and so on. The format of the
files is XXXYYN where XXX is related to the system, YY is the current year,
and N is any logical files. All of the files for the new year are created
automatically whenever a program that needs to update the detail files runs
in the new year. They are all built off of a dummy file.

As an example, our detail order entry file for 2007 would be OET07. The
first program that tried to add detail in 2008 created OET08. All of these
files have been built using a dummy file, OETXX. This file hasn't changed in
years. The problem started showing up as we convert all the legacy code to
external files.

Almost all of the programs that use the detail files have the XX version in
the file spec (OETXX if we follow the above example). It seems that
everytime a file gets created for the new year, nothing but level checks.
The program is compiled with OETXX and the new file is created using OETXX.
The only way to get around it is to compile with level check no, which I
don't want to do.

Any thoughts?

Kelley


--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.



--
No virus found in this incoming message.
Checked by AVG.
Version: 7.5.488 / Virus Database: 269.19.2/1224 - Release Date: 1/14/2008 5:39 PM