At 04:53 PM 10/25/1999 +0530, B T Vikram Kumar wrote:
>You could enable HWMPUT through DBUTIL. This will force TI to place the
records
>at the highwater mark.

This is true until the dataset's HWM reaches its maximum capacity.  Then it
will begin using the delete chain when new records are added, thus destroying
one's premise that the relative order of the entries corresponds to their
chronology.

You might want to obtain a date/time stamp after successfully locking the
target detail set, place this information on the record before the DBPUT.
This can then be used to validate/sort the chronology of the entries.
Whether or not this could also be used as a sort field to keep
chronology order is application dependent as well as the length of the
chain for the selected field (e.g. chain lengths of 1 don't make sense to
incur
the overhead cost of a sort field...)

/jf
                              _\\///_
                             (' o-o ')
___________________________ooOo_( )_OOoo____________________________________

                        Monday, October 25th

          Today in 1701 - Philadelphia was granted a city charter.

___________________________________Oooo_____________________________________
                            oooO  (    )
                           (    )  )  /
                            \  (   (_/
                             \_)