RE: Level Check Issue -- RPG400-L

James,

You are confused.

The "file level identifier" is generated uniquely when the file is created. It actually includes
create date & time.

From DSPFD:
Data Base File Attributes
Externally described file . . . . . . . . . : Yes
File level identifier . . . . . . . . . . . : 1080110151002
Creation date . . . . . . . . . . . . . . . : 01/10/08

HOWEVER, it is _NOT_ responsible for "level checks".

The identifier that is used for "level checks" is the "Format Level Identifier". It only changes when
the field names/types/sizes change, or fields are added or deleted, the record format changes, or a
couple of other reasons along the same lines.

From DSPFD:
Record Format List
Record Format Level
Format Fields Length Identifier
CPRCONP 6 36 3E38F1CFEEAA2

HTH,

Charles Wilt
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307
wiltc@xxxxxxxxxx

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of James.Hawkins@xxxxxxxxxx
Sent: Tuesday, January 15, 2008 4:22 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Level Check Issue

When any object is created on the system it is given a unique ID (level
identifier). Remember that programs need to be compiled after files? The
program records the unique level ID of the file, if this is different at
run time, you will get a level check error. I immediately see several
options.

1. change objects to level check *NO (Sorry list, it is an option-I do
not recommend this one)
2. Using your example. Change the program to use OETXX instead of OET08.
Call the program from a CL program that overrides OETXX with OET08.
3. Change the program to use OETXX. OETXX is current year data. At the
end of the year, archive (CPYF) OETXX to OET08 and purge (CLRPFM) OETXX to
prepare for 2009.
4. Redefine all of the files as internally described again (and endure the
maintenance nightmare--not a recommended solution either)
5. I believe (and someone is sure to correct me if I am wrong) that if you
use CPYF of OETXX to create OET08 instead of a compile you will avoid the
level check issue, I believe that the new file copies the level identifier
of the original file.
6. Instead of creating a new file each year, make the file a multiple
member file with each year a member in the file.

Jim
===========================

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.

This e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.