Jay,

Try  the following:

fcopy from=ksamfile;to=($newpass);new
save $oldpass,newksam
purge ksamfile
rename newksam,ksamfile

While the above is comprised by more commands it is actually faster AND
safer since the transaction manager is not being invoked (as it is in the
second fcopy), the ksamxl file is copied only once, and the usage of
'newksam' allows for recovery in case of failure.

If a failure was to occur while using the suggestion with the two 'fcopy'
commands (during the second fcopy), $oldpass would be gone and the
'ksamfile', at best, would contain a subset of the records.

Whether the original build should include the REUSE option?  It depends.
The advantage of NOT using it is that it allows one the capability of
'recovering' deleted records (records that were deleted in error?).

Regards
Paul Christidis

HP-3000 Systems Discussion <[log in to unmask]> wrote on 11/26/2003
05:43:21 AM:

> Thanks to everyone who responded.
>
> Ron and Stan are correct - the original build of the files should
> include the REUSE option.
>
> For now, though, I will use Tracy, Chris, and Mike's suggestion of using
> FCOPY.
>
> I especially liked Mike's idea:
>
> fcopy from=ksamfile;to=$newpass;new
> fcopy from=$oldpass;to=ksamfile
>
> Simple. And can be used on any nm ksam file.
>
> Thanks again. Happy Thanksgiving to everyone.
>
> Jay
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *