- Detached Headers:
  - On occasion a file with binary data may be provided that users wish to "import" into a Midas framework.
  - This is done through the use of a Detached Header.
  - A detached header allows the Midas Blue header to be stored in a separate file from the data.
    - This file looks like a normal Blue file (with a `.tmp` or a `.prm` extension), except that it has no data section (the Extended Header immediately follows the Main Header) and it has the "detached" flag set in the Main Header.
    - The binary data is then stored in a corresponding file with a `.det` ("detached data") extension.
    - In this case there are two files, the Blue File header (`<filename>.tmp` or `<filename>.prm`) and the detached data (`<filename>.det`).
    - (Some Midas frameworks allow the file names and extensions for the detached file to be overridden through the use of qualifiers.)
  - When a Midas framework sees a Blue File with the detached flag set it knows to look there for the main header and extended header and to look in the `.det` file for the data.
  - In both X-Midas and NeXtMidas a detached header can be created using the `HEADERMOD` command.