On Thu, Jan 15, 2009 at 7:01 PM, Schuh, Richard <[email protected]> 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. Constructing you own raw monitor data out of snippets that you have kept is probably not a good idea. The configuration data provides the context for the subsequent sample data. That's the reason programs that process monitor data need the configuration records. Though borrowed data from somewhere else may bypass the check that such a program does, it's likely to affect the quality of your numbers. And since you mention ESAWRITE: apart from raw monitor data, MXG also reads the history data format that ESAWRITE produces. This is much smaller and probably makes the entire problem go away. It also saves the staging disk space both on VM and MVS, and uses less resources on MVS to process it. Rob -- Rob van der Heij Velocity Software http://www.velocitysoftware.com/
