Previous Next        Current Page: NeXtMidas Training / Common Midas Concepts / Blue Files / File Types / Type 6000
Start Here   
Background   
Common Midas Concepts   
   + Version Numbering   
   + Basic Features   
   + Data Types   
   - Blue Files   
      - Basics   
      - Structure   
      - Detached   
      - File Types   
         - Type 1000   
         - Type 2000   
         - Type 3000   
         - Type 5000   
         - Type 6000   
      - Extended Type 3000/5000   
      - Qualifiers   
      - Trimmers   
      - ConsLength   
      - Time Code   
   + Lab 1   
Getting Started - Part 1   
Getting Started - Part 2   
Working with Files   
Option Trees   
Macros - Part 1 (Basics)   
Macros - Part 2 (Graphics)   
NetBeans - Part 1 (Setup)   
NetBeans - Part 2 (GUIs)   
NetBeans - Part 3 (Profiler)   
Eclipse - Part 1 (Setup)   
Eclipse - Part 2 (GUIs)   
Primitives   
Applets & WebStart   
Maps & Imagery   
X-Midas Interoperability   
RMIF & Remoting   
Installing NeXtMidas   
Support & Maintenance   
File Handlers   


  • Type 6000
    • Characteristics:
      Structure Record based
      Data Non-Homogeneous
      Example testxy6000.prm
    • Notes:
      • Type 6000 files are similar to Type 3000 files, except that they allow longer record names and more than 26 subrecords.
      • Type 6000 files were initially defined by users outside of the Midas community who were using them to store specialized data; as a result, some of their design aspects are not well-suited for general use within a Midas framework:
        • The subrecord definitions for a Type 6000 file are much more complex, than a Type 3000 file (96-bytes vs 8-bytes) and must be specified in the extended header rather than the main header. This adds significant overhead to the reading and writing of a Type 6000 file and causes problems if the file is shared between multiple processes.
        • Many of the special features of a Type 6000 subrecord definition (e.g. "Units Greek Prefix Code") are rarely used and have limited support in Midas.
      • Most of the Type 6000 files seen in X-Midas or NeXtMidas are created to get around the 26-subrecord limit in Type 3000 files.
    • Example:
       NAME OFFICE PHONE
      0Bill 401 555-2121
      1Mark 408a555-2739
      2Sarah408b555-2738
      3Lisa 407 555-6731
New Feature (Since NeXtMidas 2.6.0):
Support for reading and writing Type 6000 files was added to NeXtMidas 2.6.0.