|
Has anybody had any experience with OMS/400 and saving/restoring
shared access paths?
We have the situation where an access path is shared and the access
path owner has a name that comes after the LF that is sharing the
access path. E.g. SHARED1 owns the access path and LOGICAL1 makes
use of it.
As a result when saving the objects using OMSSAVOBJ logical file
LOGICAL1 is saved before SHARED1. This causes a problem when
restoring is made to the target system as SHARED1 doesn't exist so
the access path isn't restored and is rebuilt on next use and as the
physical file in question has 1.7 billion records it takes a little
while to complete.
I'm not that familiar with OMS/400, and was wondering if there would
be any problems with stopping the access path rebuild using the
EDTRBDAP command and then using RSTOBJ to re-restore the access path
directly from the OMS tape created using the OMSSAVOBJ command?
Any thoughts or suggestions would be gratefully welcome.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.