I think "easier on them" in such a case would be to respond to
apparent repeated activity, by creating a utility that effects an
appropriate level of consistency to avoid their making mistakes which
cost them and the support people their time; from more important things.
For example create a command like DUPSFWPKG [maybe with NEWxxx() to
name the new /version/ library or TOxxx() if CRTLIB will not be part of
the setup] which duplicates and customizes all of the /typically/
duplicated objects; thus leaving the user to finish only those very
custom bits of [duplication and/or copy] work beyond what will be
getting done consistently for them each time when they create the new
environment using the command.
Regards, Chuck
This mailing list archive is Copyright 1997-2026 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.
midrange.com
