File Level Identifier will have created Time stamp Value. Format Level Identifiers will have system created value. This will be used in programs to check the format of the file. I dont think there is no member identifier. Please correct me if i am wrong
===============================================================
File and Member Level Identifiers are forms of timestamps that relate to creation date/time. But note that this can be different from the basic object creation date/time. That is, if you materially change the file definition through some interface such as SQL ALTER TABLE or similar means, the File Level Identifier will reflect the date/time of the last such change, while the object creation date/time will be unchanged.
Record Format Level Identifiers are essentially hashes of attributes of all of the fields in the format. Attributes such as lengths and buffer positions are hashed in order to generate a nearly unique value. This value can be used by programs to verify that the descriptions of record buffers that are compiled into the programs still match with the descriptions of the buffers of the files that are opened by those programs.
A difference between Format Level Identifiers in a program and in a file will result in a “level check” exception when the program attempts to open the file. This helps prevent programs from processing files that aren’t defined in the ways that programs expect them to be.
File/Member Level Identifiers are used by operations such as RSTOBJ to help avoid restoring files that are the wrong versions and destroying altered objects.
All types of level mismatches can be overridden when necessary.
Tom
Discuss This Question: 1  Reply
IDfier (13 characters long unique ID):
File level (for *FILE type members)
Member level (don’t exist for a source PF)
Rcd-Fmt Level (exist for PF/LF)
Field Level (do not exist)