|
One radical way for the users to define their own rules might be through ADDPFCST. Write/update the record with the (e) extender and check for the error. I believe the file information data structure should be filled in with the name of the constraint. (name 'em, don't use system generated names). I am not suggesting the users enter in the raw ADDPFCST command but you handle that programmatically. Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.