Well, I found this, but it seems to support your notion that this is a bug in 
the DDL format level hash...

http://publib.boulder.ibm.com/infocenter/iadthelp/v6r0/index.jsp?topic=/com.ibm.etools.iseries.pgmgd.doc/cpprog316.htm

ILE C/C++ Programmer's Guide

--------------------------------------------------------------------------------

Level Checking to Verify Descriptions
When an ILE C/C++ program that uses externally described files is compiled, the 
compiler extracts the record-level and field-level descriptions for the files 
referred to in the program and makes those descriptions part of the compiled 
program. When you run the program, you can verify that the descriptions with 
which the program was compiled are the current descriptions. This process is 
referred to as level checking. 

When it creates the associated header file, the server assigns a unique level 
identifier for each record format. The following information determines the 
level identifier: 

Record format name 
Field name 
Total length of the record format 
Number of fields in the record format 
Field attributes (for example, length and decimal positions) 
Order of the field in the record format




Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-297-2863 or ext. 1863



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, September 27, 2006 2:19 PM
To: Midrange Systems Technical Discussion
Subject: RE: How IS the Record Format Level Identifier calculated?


Good catch!

1 - I'd still like to know how they calculate the hash.
2 - How do I get the following to not change the default value?
CREATE TABLE JEFF2
  as (Select * from JEFF1)
WITH DATA
RCDFMT JEFF1

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.