RSTLIB got duplicate member or member001

[andyw...@gmail.com]

I've heard that if I rstlib to overwrite the library, the existing(same name) member will be re-named to member001, and new object will be member.
But i tried in my both system, it can overwrite successfully. It doesn't create xxxx001 member. Anyone can confirm this?

[CRPence]

On 11-Nov-2013 06:47 -0800, andyw...@gmail.com wrote:
> I've heard that if I RSTLIB to overwrite the library, the existing

> (same name) member will be re-named to member001, and new object will

> be member. But I tried in my both system, it can overwrite

> successfully. It doesn't create xxxx001 member. Anyone can confirm
> this?

The noted effect is to prevent data loss, and *occurs when* both the
ALWOBJDIF(*ALL) has been specified on the RSTLIB [or RSTOBJ] request,
*and* the Member Level-Identifier of the member on the system does not
match the Member LvlId of the member saved to the media; a similar
result for the File Level-Identifier. The effect can be avoided in
older releases by specifying each desirable Allowed Object Difference,
as separate [up to four] values as elements on the ALWOBJDIF parameter,
and on newer releases [since it became available] to specify a new
single value special value that is similar to effecting *ALL but without
the effects of renaming; i.e. the SngVal *COMPATIBLE.

That is described in the docs for that parameter [e.g. of the RSTLIB
command]:
http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/cl/rstlib.htm
_i Restore Library (RSTLIB) i_
"...

_Allow object differences_ (ALWOBJDIF)

Specifies whether differences are allowed between the saved objects and
the restored objects.

Notes:

You must have all object (*ALLOBJ) special authority to specify any
value other than *NONE for this parameter.
If differences are found, the final message for the restore
operation is an escape message rather than the normal completion message.

...

Single values

*NONE
None of the differences listed above are allowed on the restore
operation. See the description of each individual value to determine how
differences are handled.

*COMPATIBLE
All of the differences listed above are allowed on the restore
operation. See the description of each individual value to determine how
differences are handled. This value allows differences that are
compatible with existing database files. This value is usually
preferable to the value *ALL which also allows differences that are not
compatible with existing database files.

*ALL
All of the differences listed above are allowed on the restore
operation. File level id and member level id differences are handled
differently than the *FILELVL value. If there is a file level difference
and *ALL is specified for the Data base member option (MBROPT)
parameter, the existing version of the file is renamed and the saved
version of the file is restored. If there is a member level difference,
the existing version of the member is renamed and the saved version of
the member is restored. This value will restore the saved data, but the
result may not be correct. You will need to choose whether the restored
data or the renamed data is correct, and you will need to make the
necessary corrections to the database. For other differences, see the
description of each individual value to determine how differences are
handled.
..."

http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/rzarm/rzarmwhathappens.htm
IBM i 7.1 Information Center -> Systems management -> Backup and
recovery -> Recovering your system -> Restoring the system: Introduction
_i What happens when you restore objects i_
"... The default value for the ALWOBJDIF parameter is *NONE. This means
that if important differences exist between the media version and the
system version of an object, you want the system to notify you and not
restore any differences. Normally, you should use the default value.
However, when you are restoring your information to a different system
or logical partition, such as during a disaster recovery, you should
specify ALWOBJDIF(*COMPATIBLE) which allows differences that are
compatible with existing database files.

You can specify a combination of up to four values on the ALWOBJDIF
parameter to allow specific types of differences for the restore
operation: *FILELVL, *AUTL, *OWNER, and *PGP. The *FILELVL value
attempts to restore physical file data when the file level ID or the
member level ID of the physical file on the system is different from
that of the physical file on the save media. The *AUTL value allows
differences in authorization lists. The *OWNER value allows differences
in object ownership. The *PGP value allows differences in the primary group.
..."

Additionally consider what member level decisions, for whether or
which members will be eligible to be restored, given what is on media
versus what is on disk and the Member Option (MBROPT) parameter:

http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/rzarm/rzarmmbropt.htm
IBM i 7.1 Information Center -> Systems management -> Backup and
recovery -> Recovering your system -> Restoring specific types of
information -> Restoring database files
_i How the system matches file members during a restore operation i_
"When you are restoring to an existing database file, you use the Member
option (MBROPT) parameter on either the Restore Object (RSTOBJ) command
or the Restore Library (RSTLIB) command to tell the system what to do if
the members do not match.
..."

--
Regards, Chuck