× 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.



Pete,

The "File Level Identifier" changes any time you create the file and
the "Member level identifier" changes when you create a member. But
neither one of those cause level checks.

"Format Level Identifier" is the one you need be concerned about. It
changes whenever the record format changes.
- add/remove fields
- change types or sizes of fields
- change the short system name of a field or the record format name
- change other attributes of the field, CCSID, ALWNULL, DEFAULT...

Basically, any attribute of the field or record format that effects
how the data is seen/handled by the system. In fact, the "format
level identifier" is basically a hash of those various attributes.

So for example, you can change the COLHDG or TEXT of a field without
changing the "Format Level Identifier" and thus without causing a
level check.

HTH,
Charles


On Wed, Oct 27, 2010 at 4:58 PM, Pete Helgren <pete@xxxxxxxxxx> wrote:
"See you in May?" Absolutely!

As for the logical /physical file issue. It's not huge.  A nuisance.
But helpful to know if I run into this again, I'll need recreate the
logical.

As a follow up: If the source for the logical hasn't changed and the
file is recompiled, does it cause a level check?  I have always been
fuzzy on what causes the level indicator to change on a compiled file.

Pete Helgren
Value Added Software, Inc
www.asaap.com
www.opensource4i.com



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.