|
On Mon, 2005-04-04 at 12:33, David Gibbs wrote: > Unfortunately, something like ErWin just isn't an option. This is on a > customers system and we don't have the access that a tool like ErWin > would require (let alone the tool itself). I understand. > Strictly speaking, this kind of thing should be a basic OS400 ability. > A normal library with database files can be restored to a different > name, so long as you have all the dependent objects (PF's for all LF's, > etc). Not being able to restore a database collection library to a > different name is a major defect IMHO. Backing up a database and > restoring it to a new location is something that should be able to be > done without any extra effort. Well, defect... I think what you will hear is "working as designed". I grant you that it would be much easier if they supported all that renaming... but do you really want a restore operation mucking around with data in a file? I may be in the minority here, but I for one don't want _data_ messed with by the restore itself. The defect would lie in the restore of the library from a savlib or other full save to that same name, which, you apparently have here. I would be interested in the outcome of reporting this to IBM on V5R3. -- "Bigamy is having one wife too many. Monogamy is the same." -- Oscar Wilde
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.