Re: RSTOBJ then CPYF CPF5090

Just a clarification on my previous post after doing some detail tests:
SAVOBJ an empty physical file with deleted records and any logicals over
that physical. Then, later, RSTOBJ to an empty library like QTEMP triggers
the rebuilding of access paths.
RGZPFM with MONMSG(CPF2981) before the SAVOBJ ensures the access paths are
"cleaned". This ensures that those QDBSRVxx jobs running to rebuild access
paths don't cause CPYF to those files to blow up.
If the file has data, the access path will be saved and therefore restored.
So, that would not cause rebuilding the access path.
If the file is empty (no current or deleted records) it neither restores an
access path nor submits an access path rebuild.

So, to effectively stop CPYF from blowing up with CPF5090 then CPF2972
after a RSTOBJ, make sure the access paths aren't triggered to rebuild by
making sure deleted records are removed BEFORE the files are restored.
RGZPFM with MONMSG(CPF2981) before SAVOBJ and the access paths will be
cleaned inline with the RGZPFM (no QDBSRVxx jobs used).
Note that this doesn't stop all RSTOBJ access path rebuild submissions such
as restoring a physical without the logical.

Craig