|
I know the answer to #2 Create table jeff2 as (select * from jeff1) with data including column defaults For an exact duplicate, one might want to use Create table jeff2 as (select * from jeff1) with data including column defaults including identity attributes rcdfmt jeff1 ****BINGO: The record formats are the same *** Charles Wilt -- iSeries Systems Administrator / Developer Mitsubishi Electric Automotive America ph: 513-573-4343 fax: 513-398-1121
-----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx Sent: Wednesday, September 27, 2006 3: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 -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Chris Bipes" <chris.bipes@xxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 09/27/2006 03:10 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> cc Subject RE: How IS the Record Format Level Identifier calculated? You do have a difference, default value of none and no default value specified, which equals blank on a character field. So the field properties are different. Christopher Bipes Information Services Director CrossCheck, Inc. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx Sent: Wednesday, September 27, 2006 12:04 PM To: midrange-l@xxxxxxxxxxxx Subject: How IS the Record Format Level Identifier calculated? Here's the great mystery to solve. Just exactly how IS the Record Format Level Identifier calculated? Some say it's a hash of the field properties and the record format name. However, if that is true then I shouldn't have this: File JEFF1 Record Format Information Record format . . . . . . . . . . . . . . . : JEFF1 Format level identifier . . . . . . . . . . : 1F394C6EFF0A2 Number of fields . . . . . . . . . . . . . : 2 Record length . . . . . . . . . . . . . . . : 20 Field Level Information Data Field Buffer Buffer Field Column Field Type Length Length Position Usage Heading MYCHAR CHAR 15 15 1 Both MYCHAR Coded Character Set Identifier . . . . . : 37 MYDEC PACKED 9 2 5 16 Both MYDEC File JEFF2 Record Format Information Record format . . . . . . . . . . . . . . . : JEFF1 Format level identifier . . . . . . . . . . : 1F394C77030E2 Number of fields . . . . . . . . . . . . . : 2 Record length . . . . . . . . . . . . . . . : 20 Field Level Information Data Field Buffer Buffer Field Column Field Type Length Length Position Usage Heading MYCHAR CHAR 15 15 1 Both MYCHAR Default value . . . . . . . . . . . . . . : None Coded Character Set Identifier . . . . . : 37 MYDEC PACKED 9 2 5 16 Both MYDEC Default value . . . . . . . . . . . . . . : None -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.