RSTLIB will either create a library or restore the saved library
"description" to an existing library, for the library named in the
RSTLIB() parameter. The RSTLIB will not delete an existing *LIB, nor
would a user have to [nor necessarily want to] delete the library prior
to a RSTLIB. There are valid reasons however, to want to delete the
library prior to RSTLIB [or CRTLIB] for the library into which objects
If the library to be restored-into is in a library list of a job, a
CLRLIB is the more desirable option over DLTLIB [DLTLIB is possibly
restricted, if its being in a *LIBL allocates the *LIB] to enable a
restore into an empty library. RSTLIB into an empty library mimics a
"scratch restore" effect for any objects within the library on media,
but not for the *LIB object which experiences a restore-over effect.
On 12-Apr-2012 11:25 , Jerry C. Adams wrote:
The RSTOBJ does not affect (and is not affected by) the library
list. It was the RSTLIB since the library would have to be deleted
(wouldn't it?) before the RSTLIB. That is, if the library to be
restored is TESTLIB and TESTLIB is in the library list, the DLTLIB
would blow off. Wouldn't it?
Or was I just my usual unclear self again?
CRPence on Thursday, April 12, 2012 1:20 PM wrote:
What about a RSTOBJ is presumed to be affected by Library List [of
the job making that restore request]?
This mailing list archive is Copyright 1997-2019 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