The original FAA5905 file has key fields, but having key fields has no
bearing on the record format level id.
From what I have learned, the record format level ID is dependent on the
format name and the name, number, placement, length, and attributes of the
(NOT whether or not it is a keyed file...)
In other words, if you change any of the following:
1) the record format name specified in the DDS,
2) the name of a field
4) the placement of fields within the file layout
5) length of any field
6) attributes of any field (char, numeric, etc.)
I created a copy of the DDS used to create FAA5905, except this DDS has NO
key fields specified, and when compiled it produces an arrival sequence file
which has record format level id of 2729492F22E27, same as the original
keyed physical file.
However, I have been wrong on numerous occasions, and I'm sure that someone
here will correct me if I am wrong!
"Gqcy" wrote in message
Does your MYLIB/FAA5905 file have Keys?
-they don't come across.
On 10/2/2012 4:01 PM, sjl wrote:
"Dennis Lovelady" wrote in message
Is there a question in here somewhere?
"Genius is one per cent inspiration and ninety-nine per cent
-- Thomas Edison
(Received the same result on both V5R4M0 and 7.1 systems...)
Permanent file MYLIB/FAA5905 has 19 fields, record length of 133,
record format level identifier 2729492F22E27.
Used green-screen (STRSQL) to execute SQL statement: "Declare global
temporary table FAA5905 like MYLIB/FAA5905"
DSPFD of QTEMP/FAA5905 shows that the file built by the above SQL
statement has 19 fields, record length of 133, but the record format
level identifier is 26F9492F22E27.
( DIFFERENT format level ID...)
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.