Schuh, Richard wrote:
IIRC, that is a configuration record that is written when the monitor is
initialized. It was required by MICS. ESAWRITE has the ability to start
each raw data file with one of these records. If you don't have
ESAWRITE, you can find a configuration record in any file, retain a copy
of it and include it in the files processed by the program.
Just found that out. The MDATPEEK stage that CP3KVMXT uses requires
that control record. So, now I have something to work on the rest of
the day. :-)
Leland
