×
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.
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
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.