On Aug 13,  1:15pm, Michael Berkowitz wrote:
> However, the 5.5 communicator writes on page 3-9 that the modification
> date of mapped files and compatilbility mode files are not affected by this
> change.  The modification date in the file label is always updated when
> these files are opened for write access.  Since CM KSAM file are
> compatibility mode files by definition, they should work as before.  Maybe
> the documentation and action don't jive.
>-- End of excerpt from Michael Berkowitz

Boy, you'd think this would be the case given the name "CM KSAM" but, as in
most things in life, you can't judge this book by its cover. A CM KSAM "file"
is actually composed of two ordinary fixed or variable length record files. The
"CM" part refers to the code that manages these two files, keeping key
information in one and user data in the other. Both the key file and the data
file of a CM KSAM file are very much supported in native mode.

You are very right to point out the other exceptions to the modification
timestamp update rule. Both CIRcular and RIO files will have their modification
timestamps updated anytime the file is opened for write access, regardless of
whether or not any data was actually changed. The same thing holds true for any
file that is opened for mapped access, with any form of write permission. The
file system must assume that the data was altered, since mapped access bypasses
the file system and writes directly to the file.

Thanks for the clarification.

Craig

--
Craig Fairchild

Email: [log in to unmask]               Phone: (408) 447-5990
USPS:  Hewlett-Packard Company           Fax:   (408) 447-4278
       M/S 47UA
       19447 Pruneridge Avenue
       Cupertino, CA 95014