RE: Copying File Structures

I would probably just do a CPYLIB to NEW from OLD then run a quick and dirty CL over the NEW library to run a CLRPFM over each physical file.

Nick had a good point about the library list order if one uses CRTDUPOBJ to replicate the LF's. Not sure how the CPYLIB would react if an LF addressed a PF in another library. Or if the LF indexed PF's in multiple libraries. That's the kind of scenario I try to avoid - but have seen.

Thanks.

Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, May 28, 2008 3:24 PM
To: Midrange Systems Technical Discussion
Subject: RE: Copying File Structures

I'm a little busy. Try the CRTDUPOBJ on something small like RCO*. Check
the lf's in the new library and make sure they point to the new library
and not back to the old library. If I was being overly cautious, then
fire away.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Reinardy, James" <jreinardy@xxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
05/28/2008 04:18 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: Copying File Structures






Rob,

Thanks for the clarification, I guess I was way off base even after
reading online help!

Could you expand on your comment regarding logical files with CRTDUPOBJ?
There are lots of logicals in the particular libraries we are dealing
with. (This is a BPCS database, if it matters). We were hoping to
automatically bring over those referencing files in the same library,
but were resigned to manually recreating those that cross libraries.

Thanks,

Jim

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, May 28, 2008 3:02 PM
To: Midrange Systems Technical Discussion
Subject: Re: Copying File Structures

That save file data parameter is NOT the solution. What that means if I

do this:
CRTLIB BIGJIM
CRTSAVF BIGJIM/REINARDY
SAVOBJ OBJ(MYOBJ) LIB(MYLIB) DEV(*SAVF) SAVF(BIGJIM/REINARDY)
And if I save the library BIGJIM then I have a choice of whether or not
I
also save the data in the save file BIGJIM/REINARDY or not.

This can do it but be careful of logical files, etc.
CRTDUPOBJ OBJ(*ALL)
FROMLIB(OLDLIB)
OBJTYPE(*ALL)
TOLIB(NEWLIB)
DATA(*NO)

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Reinardy, James" <jreinardy@xxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
05/28/2008 03:56 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Subject
Copying File Structures






We are migrating our development work to a separate LPAR and want to
copy the structure of our main ERP database without all of the data. It
appeared that doing a SAVLIB to a *SAVF with SAVFDTA(*NO) might do the
trick, but this still copies data in our tests. Do I need another
parameter, or is there an easier way to do this?

Thanks,

Jim Reinardy
Badger Meter, Inc.
Milwaukee, WI
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.