I like the way it behaves. That makes it easy to create a duplicate
set of files by CRTDUPOBJing the physical followed by the logicals.
The only thing that makes sense to me would be to have an additional
parameter on the CRTDUPOBJ command to control the behavior. The
default would be to behave as it does now, with additional values to
force it to stay with the original PF and to force it to switch to a
PF in the new library. And/or maybe a way to explicitly specify the
This mailing list archive is Copyright 1997-2015 by MIDRANGE dot 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 here. If you have questions about this, please contact