×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
James H. H. Lampert wrote:
<<SNIP>>
And the only allowable values I see for ALWOBJDIF are
*NONE and *ALL.
On any supported release? I thought that least *OWNER was
available since ages & releases ago.?
Of course, I could always restore the file to QTEMP,
and copy the members over individually.
Depending on copy options available [by data area or parameter],
the level identifier of the new member may not match the
saved\restored member. That is probably moot, since the database
*FILE already is not deemed to be the same on the disk as the one on
media due to the mismatch of File Level Identifiers.
If the existing *FILE [is left renamed] then RSTOBJ of the *FILE
using FILEMBR((*ALL *NONE)) MBROPT(*ALL) OPTION(*NEW), then _future_
restores from saves of the other file will be allowed without any
need to allow differences [for the file level; i.e. the file
restored *NEW will keep the file level ID of the saved file].
Regards, Chuck
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.
midrange.com
